August 1, 2015 at 9:54 am
I read in Brad McGehee’s Backup and recovery book that when you perform a restore you only need to provide the Full, Differential and the last transaction log backup.
Unfortunately I can't fine the text.
It is not necessary to specify each transaction SQL Server will detect all Transaction Log backups since the last Full backup or differential Backup.
Does anyone have a check list to recover from the GUI?
I inherited transaction log backups for every 5 minutes. Complete backups one a week and differential each night.
I have requested that we perform more differential backups more often then risk a breakup in the log chain.
Your input would be greatly appreciated.:-)
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/
August 1, 2015 at 11:35 am
is this the book you are referring to?
http://www.sqlservercentral.com/articles/books/89519/
free download
________________________________________________________________
you can lead a user to data....but you cannot make them think
and remember....every day is a school day
August 1, 2015 at 4:56 pm
J Livingston SQL (8/1/2015)
is this the book you are referring to?http://www.sqlservercentral.com/articles/books/89519/
free download
Yes Sir.
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/
August 2, 2015 at 11:49 am
Welsh Corgi (8/1/2015)
I read in Brad McGehee’s Backup and recovery book that when you perform a restore you only need to provide the Full, Differential and the last transaction log backup.
Not correct. You need to restore the last Full, Differential, and ALL transaction log backups that occurred (lsn-wise) after the Differential.
The SQL Server Restore GUI is pretty good at figuring all that out.
As a bit of a sidebar, I've found that Dif files grow to sizes larger (sometimes, MUCH larger) than a Full backup of the database that run a lot of batch imports and so I simply avoid them. Remember that Dif backups are CUMULATIVE OF ALL CHANGES until the next successful FULL backup occurs.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 2, 2015 at 2:37 pm
Jeff,
That was I thought. Thank you for responding and have a great day.
We do transaction log backups every 5 minutes and I had this new women zap a table on her second day.
Thanks again. Jeff 🙂
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/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply