January 7, 2009 at 3:50 am
The Gurus,
I get the following error in my log files but after changing the recovery option to full, I still continue to get the same error message. Is there any other way to approach this?
Message
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.
Many thanks.
Regards,
Ola.
January 7, 2009 at 3:57 am
Why are you truncating the transaction log? If you don't want to backup the log and point-in-time recovery is not required, put the DB into simple recovery and leave it alone.
If you do need point-in-time recovery, you should not be truncating the log, as it discards log records and breaks the recovery chain.
Please read through this - Managing Transaction Logs[/url]
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 7, 2009 at 4:05 am
Can you explain what are you trying to do? If the database was in simple mode, then there is no reason to truncate the log. If you modified it to full mode (from simple mode) you are doing the opposite operation of truncating the log (at least after the first full backup). If you are trying to shrink the log file, can you explain why? If you are trying to do something else pleas explain it.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply