To add to Ray's response, in the SIMPLE recovery model the transaction
log needs to be sized large enough to accommodate data changes since the
oldest uncommitted transaction. Committed data are automatically
removed from the log in the SIMPLE model and your only recovery option
is to restore from database backup. Any changes made since the backup
will be lost.
In the FULL or BULK_LOGGED model, the log needs to be large enough to
contain all logged modifications since your last transaction log backup.
Committed data are only removed from the log during a transaction log
backup. Consequently, you'll need to backup your log periodically or
the log will grow indefinitely. The backups can be applied to a
restored database to reduce the amount of data lost following a
recovery.
--
Hope this helps.
Dan Guzman
SQL Server MVP
-----------------------
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index....partmentID=800 http://www.sqlserverfaq.com http://www.mssqlserver.com/faq
-----------------------
"enigma" <jo***@pure-commerce.com> wrote in message
news:7a**************************@posting.google.c om...
Just wondering if you could help me on this one. I'm not sure if my
transaction logs are behaving oddly or what. I've successfuly managed
to shrink my transaction logs from 7GB down to 1MB and now I find it
strange that the log file doesn't seem to increase its size. The
timestamp of the logfile is updating as well. But the size of the file
is constant. I haven't configured my database to do auto-shrink so Im
really confused why it hasn't changed its size for more than a month
now.
Hope I'm not losing any data here.
Kindly advise.