April 17, 2010 at 10:18 pm
this article http://msdn.microsoft.com/en-us/library/ms156421.aspx suggest to take backup with copy_all , is this valid option? , i am not able to use this , any pointers?
April 18, 2010 at 3:17 am
sqlquery-101401 (4/17/2010)
this article http://msdn.microsoft.com/en-us/library/ms156421.aspx suggest to take backup with copy_all , is this valid option? , i am not able to use this , any pointers?
It's a mis-print; it should read COPY_ONLY.
See the Community Content section at the end of the article.
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
April 18, 2010 at 3:19 am
i could be wrong but i believe that should be COPY_ONLY, this stops the backup interferring with the usual backup regime currently in force on the source server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 18, 2010 at 8:34 am
thanks , but i believe copy_only will not take the full log , does it?
April 18, 2010 at 10:26 am
It does the same as any other full backup, it takes the active part of the transaction log so the database can be restored to a consistent point.
---------------------------------------------------------------------
April 18, 2010 at 6:55 pm
george sibbald (4/18/2010)
It does the same as any other full backup, it takes the active part of the transaction log so the database can be restored to a consistent point.
Exactly - it backs up enough log to enable a successful, consistent, restore - without taking part in the 'normal' chain of backups for the database.
Full details in Books Online:
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply