Log File Size - Sudden Growth

I have a relatively small database that I use for development purposes (this
isn't the production database).
The .mdf is about 10 MB. The log file size - for over 1 year - has been
about 7MB in size. During the past couple of ws the log file has grown to
over 15 MB in size. The amount of db-related development activity has
remained roughly constant over the past year. So I'm curious as to what
could be causing the log file to suddenly grow this large (small as it is in
the relative scheme of things).
Thanks!Felipe,
A couple of guesses: 1. Importing data 2. index creation or maintanence 3.
log backup didn't occur
HTH
Jerry
"Felipe" <aye@.bee.calm> wrote in message
news:OAgDoxGxFHA.3892@.TK2MSFTNGP12.phx.gbl...
>I have a relatively small database that I use for development purposes
>(this isn't the production database).
> The .mdf is about 10 MB. The log file size - for over 1 year - has been
> about 7MB in size. During the past couple of ws the log file has grown
> to over 15 MB in size. The amount of db-related development activity has
> remained roughly constant over the past year. So I'm curious as to what
> could be causing the log file to suddenly grow this large (small as it is
> in the relative scheme of things).
> Thanks!
>sql

log

I checked our SQL server log/ current activities.
There is a message: starting up database tester,and this
is the testing database before we put our real database
on the server. Now we've already changed our application
to use our production database.
But we still get a lot of above messages. and every 20
seconds.
What caused this and what should we do about it?
I delete the database tester now from the server, for we
are not going to use it. I just wonder if this is a
security issue or not?That was probably due to the fact you had the Auto-Close option set to ON.
Andrew J. Kelly
SQL Server MVP
"Ann" <anonymous@.discussions.microsoft.com> wrote in message
news:024001c3ce40$32d0cf40$a101280a@.phx.gbl...

quote:

---

> I checked our SQL server log/ current activities.
> There is a message: starting up database tester,and this
> is the testing database before we put our real database
> on the server. Now we've already changed our application
> to use our production database.
> But we still get a lot of above messages. and every 20
> seconds.
> What caused this and what should we do about it?
> I delete the database tester now from the server, for we
> are not going to use it. I just wonder if this is a
> security issue or not?

---

|||Or if you are doing periodic restores. Every time, you
perform a database restore or log restore, an entry
of 'starting up database xyz' will be written to the SQL
errorlog.
Linchi

quote:

---

>--Original Message--
>That was probably due to the fact you had the Auto-Close

---

option set to ON.

quote:

---

>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Ann" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:024001c3ce40$32d0cf40$a101280a@.phx.gbl...
>
>.
>

---