March 6, 2012 at 9:52 pm
Comments posted to this topic are about the item Full Recovery Model
March 6, 2012 at 9:54 pm
Thank you for the simple question. + 1 added.
March 6, 2012 at 10:47 pm
EZ PZ
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
March 6, 2012 at 10:48 pm
Good one.
M&M
March 6, 2012 at 11:15 pm
<cough>referense</cough>
/T
March 6, 2012 at 11:26 pm
Nice back to basics question. Very thorough reference though, took me hours to wield through 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 7, 2012 at 1:03 am
easy and basic but i love it !!!!!!!!! :hehe:
March 7, 2012 at 1:09 am
Wasn't the "explanation" more or less a repeat of the question? It really felt like "Is X true? Yes it is, because X is true!". Needed a reference at the very least.
March 7, 2012 at 1:24 am
This was removed by the editor as SPAM
March 7, 2012 at 1:48 am
What do you mean for "created and loaded database"?
March 7, 2012 at 3:08 am
Stewart "Arturius" Campbell (3/7/2012)
Nice, simple back-to-basics question, thanks, PeterFor the explanation, refer to Working with Transaction Log Backups, specifically the third paragraph
+1
😎
March 7, 2012 at 3:55 am
Stewart "Arturius" Campbell (3/7/2012)
Nice, simple back-to-basics question, thanks, PeterFor the explanation, refer to Working with Transaction Log Backups, specifically the third paragraph
And to add to that reference, the reason for this is that a restore always has to start with the restore of a full backup. A full backup contains the information in the database at a given point; a log backup contains a list of changes. When you need to restore to a point in time, you HAVE to restore to the complete content of a previous point in time first, then reapply the changes by following the chain of log backups.
Without a starting point to base the changes on, a set of changes is useless. That's why SQL Server refuses to let you save such a set of changes. (In fact, when setting a database to FULL or BULK_LOGGED recovery, the actual running mode always remains SIMPLE until you take a full backup. And the same is true for newly created databases.)
March 7, 2012 at 7:23 am
Hugo Kornelis (3/7/2012)
(In fact, when setting a database to FULL or BULK_LOGGED recovery, the actual running mode always remains SIMPLE until you take a full backup. And the same is true for newly created databases.)
Ooohh... did not know that, never thought about it since I start backups immediately, but that is good to know. This implies that therefore should a backup be forgotten, the changes are immediately lost even to a log reader should a transaction log backup be taken later on after the full backup. Good to know indeed.
Viewing 15 posts - 1 through 15 (of 29 total)
You must be logged in to reply to this topic. Login to reply