|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 11:35 PM
Points: 1,413,
Visits: 663
|
|
Echoing everyone else's comments - great article!
However, I was all prepared to query your statement in the article:
It is important to note that while a full or differential backup starts a log chain, full and differential backups don't break the log chain
My understanding was always that performing a Full backup would break the log chain, and if you wanted to restore to a given point using your log backups, you would have to restore from the last full backup. That's what I thought copy_only backups were introduced for, to ensure an ad-hoc full backup would not disrupt the log chain.
However, having now tested it against a 2008 R2 instance sure enough taking a full backup does not break the log chain, so I have learned something new today! Thank you! 
But having said that, it begs the question what is the point of copy_only backups now?
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:47 PM
Points: 38,096,
Visits: 30,391
|
|
SQLPhil (1/12/2012) But having said that, it begs the question what is the point of copy_only backups now?
This: http://sqlinthewild.co.za/index.php/2011/03/08/full-backups-the-log-chain-and-the-copy_only-option/
You wouldn't be the first to argue with me about full backups breaking the log chain, it's an (unfortunately) commonly held belief. They've never broken the log chain though.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 11:35 PM
Points: 1,413,
Visits: 663
|
|
Thank you very much Gail for clarifying all of this (and for the excellent article on COPY_ONLY). You have certainly added a lot of clarity to my understanding of backups and restores.
Speaking amongst my fellow DBA colleagues we were all under the (misguided) understanding that full backups broke the log chain. In fact, even in some training courses we've been told that this has been the case. It'll be nice to have the opportunity to turn round and inform the instructor for once!
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:47 PM
Points: 38,096,
Visits: 30,391
|
|
SQLPhil (1/12/2012)
It'll be nice to have the opportunity to turn round and inform the instructor for once! 

Just be polite if you do. Speaking as a occasional trainer and presenter, there's nothing worse than a student who thinks he's right and you're wrong and makes a public issue out of it.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP 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
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: 2 days ago @ 2:13 PM
Points: 6,866,
Visits: 8,071
|
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 28, 2013 9:41 AM
Points: 1,622,
Visits: 592
|
|
Great article, company I contract for are constantly changing the recovery model and shrinking the log then changing the RM back - have presented them with the URL for this, fingers crossed they will see sense! 
qh
SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Saturday, June 08, 2013 6:32 PM
Points: 10,
Visits: 53
|
|
Can we do point in time recovery in Bulk loged recovery model? If yes then how?
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 7:18 AM
Points: 33,112,
Visits: 27,038
|
|
best_yunus (5/12/2012) Can we do point in time recovery in Bulk loged recovery model? If yes then how?
Yes but only if there were no minimally logged transactions in the final log file that you want to recover up to the point in time.
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... 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/
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Saturday, June 08, 2013 6:32 PM
Points: 10,
Visits: 53
|
|
Now i got...
Thanks
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 3:47 PM
Points: 38,096,
Visits: 30,391
|
|
|
|
|