Where that backup goes..

Question

Post reply

Where that backup goes..

forsqlserver

SSCoach

Points: 18902
More actions
August 4, 2010 at 11:48 pm

#157129

When we use backup with NO_Log.
Where that backup goes..
Can explain ...
Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

It doesn't go anywhere. This was a method for clearing out the log. It should not be used and it is being deprecated.

http://technet.microsoft.com/en-us/library/ms186865.aspx

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

guptaajay1985 (8/4/2010)
When we use backup with NO_Log.
Where that backup goes..

Nowhere. That command says to SQL 'do as if you were doing a log backup, but throw away what you would have backed up in if that option wasn't there.'

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

forsqlserver SSCoach Points: 18902 More actions · Answer 3

Suppose from a long time we havent taken the full and txn log backup,and now we are not able to do the even dbcc shrink as well as no full backup due to no disk space available then we use this No_log,but on using it ,it truncate the logs since full backup.

suppose my database is just corrupted after running command backup log with NO_log , how Will I restore my databse?

This is my question...

Thanks

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

guptaajay1985 (8/5/2010)
suppose my database is just corrupted after running command backup log with NO_log , how Will I restore my databse?

Restore your last full backup and any transaction log backups that you do have. Same way you restore any other time. Since that command breaks the log chain, you won't be able to take a tail-log backup and so the best you'll be able to restore to is the last transaction log backup that you had taken.

You shouldn't need to run that command. If you want to auto-truncate the log, switch the database to simple recovery model. Then sort out the large log file, switch the database back to full recovery, take a full backup and set up log backups.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass