|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Friday, March 15, 2013 10:35 AM
Points: 594,
Visits: 654
|
|
Paul White NZ (3/31/2010) Thank you, Peter. Of course, there are some edge cases and subtleties, but unless Mr Randal appears and tells me I know nothing about nothing...I'm happy with it.
I don't sweat the exceptions. Concepts first, exceptions later. Can't understand the exceptions until the normal process makes sense. I get grief for using broken analogies to explain concepts like joins but the students like simple explanations, even if they are flawed by real world applications.
Peter Trast Microsoft Certified ...(insert many literal strings here) Microsoft Design Architect with Alexander Open Systems
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 3:07 PM
Points: 7,096,
Visits: 7,156
|
|
Paul White NZ (3/31/2010)
The whole backup operation is conceptually quite simple: Force a database checkpoint (flush all updated-in-memory pages to disk before anything is read by the backup) Record the minimum recovery LSN (LSN1) Database data read begins Record the current LSN (LSN2) Read the transaction log from LSN1 to LSN2 Thanks Paul, that's a very clear description. It answers all the questions I had about whether dirty data is flushed first, when the start LSN is recorded, and whether the final LSN is allowed to be later than the current LSN at the end of the DB read.
And I see the MS design does include flushing already dirty pages to disc despite Hugo's suggestion that this is not a useful thing to do.
Tom Que conclure à la fin de tous mes longs propos? C'est que les préjugés sont la raison des sots. (Voltaire, 1756)
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 2:13 PM
Points: 5,237,
Visits: 7,044
|
|
Tom.Thomson (3/31/2010) And I see the MS design does include flushing already dirty pages to disc despite Hugo's suggestion that this is not a useful thing to do. Yes, I noticed that as well. And was a bit surprised by it.
I'm glad Paul was able to find and post such a detailed description of the process. Thanks, Paul!
Hugo Kornelis, SQL Server MVP Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Yesterday @ 7:18 PM
Points: 10,989,
Visits: 10,532
|
|
Thanks, everyone. Glad I am not the only one to find this whole area fascinating.
Paul White SQL Server MVP SQLblog.com @SQL_Kiwi
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 12, 2013 9:43 AM
Points: 142,
Visits: 171
|
|
Paul White NZ (4/1/2010) Thanks, everyone. Glad I am not the only one to find this whole area fascinating.
Yes, I do too [for reasons unfathomable]
And I'm glad I kinda kicked off the discussion about when the backup knew when to stop. I'm slogging my way through all of Paul's postings, and drawing diagrams of my own.
Again, thanks to all.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, September 14, 2011 8:14 AM
Points: 189,
Visits: 26
|
|
Good question! Tests ones' understanding in a better ways.
Kudos to the Question submitter!
|
|
|
|