Log file behavior

We have a 43 gig database that we are adding lots of data too. The recovery
mode is set to Full. The log file will grow for a while and then shrink
back down. I thought the log file would grow until it was backed up?
I did set the recovery to simple before we started our tests and truncated
the log and then set the recovery mode back to Full.
It's acting like it's still in simple mode...Kevin,
It might be possible that "Auto Shrink" is checked on the Options tab of the
Database Properties dialog.
If not, have you inspected the SQL Server Log files or run profiler to see
what is happening?
Is it possible that someone or some batch process is periodically conducing
a manual Shrink operation?
--
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
news:%23Ue3AvnuDHA.1876@.TK2MSFTNGP09.phx.gbl...
> We have a 43 gig database that we are adding lots of data too. The
recovery
> mode is set to Full. The log file will grow for a while and then shrink
> back down. I thought the log file would grow until it was backed up?
> I did set the recovery to simple before we started our tests and truncated
> the log and then set the recovery mode back to Full.
> It's acting like it's still in simple mode...
>|||It appears that when switching back to Full from Simple, you have to do a
BACKUP LOG statement for it to act like Full again. At least that is what
we did and it's now behaving like Full usually behaves
"Keith Wilson" <keithwi@.online.microsoft.com> wrote in message
news:3fcf6cb5$1@.news.microsoft.com...
> Kevin,
> It might be possible that "Auto Shrink" is checked on the Options tab of
the
> Database Properties dialog.
> If not, have you inspected the SQL Server Log files or run profiler to see
> what is happening?
> Is it possible that someone or some batch process is periodically
conducing
> a manual Shrink operation?
> --
> Keith Wilson
> This posting is provided "AS IS" without express or implied warranty,
> guarantee, or rights.
>
> "Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
> news:%23Ue3AvnuDHA.1876@.TK2MSFTNGP09.phx.gbl...
> > We have a 43 gig database that we are adding lots of data too. The
> recovery
> > mode is set to Full. The log file will grow for a while and then shrink
> > back down. I thought the log file would grow until it was backed up?
> >
> > I did set the recovery to simple before we started our tests and
truncated
> > the log and then set the recovery mode back to Full.
> >
> > It's acting like it's still in simple mode...
> >
> >
>|||Kevin, You actually need a backup DATABASE after changing from simple =to full.
Mike John
"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message =news:OJyyQ%23ouDHA.684@.TK2MSFTNGP09.phx.gbl...
> > It appears that when switching back to Full from Simple, you have to =do a
> BACKUP LOG statement for it to act like Full again. At least that is =what
> we did and it's now behaving like Full usually behaves
> > "Keith Wilson" <keithwi@.online.microsoft.com> wrote in message
> news:3fcf6cb5$1@.news.microsoft.com...
> > Kevin,
> >
> > It might be possible that "Auto Shrink" is checked on the Options =tab of
> the
> > Database Properties dialog.
> > If not, have you inspected the SQL Server Log files or run profiler =to see
> > what is happening?
> >
> > Is it possible that someone or some batch process is periodically
> conducing
> > a manual Shrink operation?
> >
> > -- > > Keith Wilson
> >
> > This posting is provided "AS IS" without express or implied =warranty,
> > guarantee, or rights.
> >
> >
> > "Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message
> > news:%23Ue3AvnuDHA.1876@.TK2MSFTNGP09.phx.gbl...
> > > We have a 43 gig database that we are adding lots of data too. =The
> > recovery
> > > mode is set to Full. The log file will grow for a while and then =shrink
> > > back down. I thought the log file would grow until it was backed =up?
> > >
> > > I did set the recovery to simple before we started our tests and
> truncated
> > > the log and then set the recovery mode back to Full.
> > >
> > > It's acting like it's still in simple mode...
> > >
> > >
> >
> >
> >|||"Kevin Jackson" <kjackson@.powerwayinc.com> wrote in message news:<#Ue3AvnuDHA.1876@.TK2MSFTNGP09.phx.gbl>...
> We have a 43 gig database that we are adding lots of data too. The recovery
> mode is set to Full. The log file will grow for a while and then shrink
> back down. I thought the log file would grow until it was backed up?
> I did set the recovery to simple before we started our tests and truncated
> the log and then set the recovery mode back to Full.
> It's acting like it's still in simple mode...
Kevin,
A few suggestions :
Check that the Auto Shrink property is set. You can find this in the
properties of the database in enterprise manager, or using
databasepropertyex.
You may also like to check that you are not running a maintenance plan
to shrink the file.
Rod Colledge.|||Kevin,
If you enable the "Auto Shrink" option, the transaction log will grow with insert operations even
the recovery mode of the database is Simple.
After you change the recovery mode to Full, the log willl be shrinked at this time and later the
log will NOT grow with the insert operations until the next log shrink or backup. On the other
hand, if you disable the "Auto Shrink" option, the transaction log will always grow under the Full
recovery mode.
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.