May 15, 2015 at 1:08 pm
Hi,
In my book it says:
All restore sequences begin with either a full backup or filegroup backup. When restoring backups, you have the option to terminate the restore process at any point and make the database available for transactions.
This is contradictory to:
If you are restoring over the top of an existing database and the restore process aborts, you no longer can access anything in the database prior to the restore operation.
in the same book, and also this here:
Undoing the effects of a restore is not possible
I just asked in another thread about overwritten databases by restore function and understood the overwritten database is gone even when you abort.
So does anyone understand those first fancy reassuring Words?
May 15, 2015 at 3:29 pm
afw (5/15/2015)
All restore sequences begin with either a full backup or filegroup backup. When restoring backups, you have the option to terminate the restore process at any point and make the database available for transactions.
This is contradictory to:
If you are restoring over the top of an existing database and the restore process aborts, you no longer can access anything in the database prior to the restore operation.
No, it's not. They're talking about different things.
The first is talking about when restoring multiple backups, either multiple filegroup backups or full, diff, log. You can stop at any point in the set of files and make the DB available at that point, so I could chose to restore the full, one diff and 3 of the 10 log backups and make the DB available at that point.
The second is talking about interupting a restore in process, ie you start restoring the diff and kill the session part way through.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 15, 2015 at 3:38 pm
Aah, makes sense. But boy was I getting that wrong...
Thank you once again 🙂 🙂
May 15, 2015 at 9:58 pm
afw (5/15/2015)
Aah, makes sense. But boy was I getting that wrong...Thank you once again 🙂 🙂
My Dad has a saying about such things.
"Half of what is written is true. The other half is written in such a fashion that you can't actually tell".
--Jeff Moden
Change is inevitable... Change for the better is not.
May 16, 2015 at 2:50 pm
Jeff Moden (5/15/2015)
afw (5/15/2015)
Aah, makes sense. But boy was I getting that wrong...Thank you once again 🙂 🙂
My Dad has a saying about such things.
"Half of what is written is true. The other half is written in such a fashion that you can't actually tell".
Brilliant Jeff, you just came up with the best description of NOLOCK I've ever seen!
😎
May 16, 2015 at 3:28 pm
Jeff Moden (5/15/2015)
afw (5/15/2015)
Aah, makes sense. But boy was I getting that wrong...Thank you once again 🙂 🙂
My Dad has a saying about such things.
"Half of what is written is true. The other half is written in such a fashion that you can't actually tell".
*Looks at a 3/4 finished article*.....
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 16, 2015 at 3:52 pm
GilaMonster (5/16/2015)
Jeff Moden (5/15/2015)
afw (5/15/2015)
Aah, makes sense. But boy was I getting that wrong...Thank you once again 🙂 🙂
My Dad has a saying about such things.
"Half of what is written is true. The other half is written in such a fashion that you can't actually tell".
*Looks at a 3/4 finished article*.....
Touché, and that makes me almost blush, got a collection of those
😎
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply