Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Rolling Back a Restore


Rolling Back a Restore

Author
Message
Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36176 Visits: 18751
Comments posted to this topic are about the item Rolling Back a Restore

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Lynn Pettis
Lynn Pettis
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24227 Visits: 37978
Interesting idea. I think it would be good idea and perhaps implemented by extending the RESTORE statement, perhaps RETAIN_OLDDB with maybe a couple of options to it.

Curious what others may think.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21093 Visits: 18259
I like the idea. I see the only way of implementing it is as a new command or as an option on the restore command. Obvious complications would be disk space. You couldn't require that double your production database be stored side by side on the same storage, especially not if the space was limited already.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36176 Visits: 18751
It would definitely double disk space, though for many dbs, this isn't an issue. I'd think you ought to be able to configure the "new dbs" on alternate storage if available.

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
mpa
mpa
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 162
As someone who measures five times, cuts once, I can certainly see the usefulness in this idea. It would be nice if there was an option to manually make the "switch" after verifying that everything went OK, or just make it do it automagically when the restore is done, though I'm not entirely sure how this would be accomplished.
GSquared
GSquared
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14375 Visits: 9729
So long as it was an option, I think it would be a good idea.

Of course, as a workaround, you can restore as a different name, then issue a drop on the database you're overwriting and a rename on the restored database. Wouldn't be "instant", but since the restore itself wouldn't be instant, I think it's a valid way to handle it.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
jay-h
jay-h
SSC Eights!
SSC Eights! (927 reputation)SSC Eights! (927 reputation)SSC Eights! (927 reputation)SSC Eights! (927 reputation)SSC Eights! (927 reputation)SSC Eights! (927 reputation)SSC Eights! (927 reputation)SSC Eights! (927 reputation)

Group: General Forum Members
Points: 927 Visits: 2222
mpa (3/22/2010)
As someone who measures five times, cuts once, I can certainly see the usefulness in this idea. It would be nice if there was an option to manually make the "switch" after verifying that everything went OK, or just make it do it automagically when the restore is done, though I'm not entirely sure how this would be accomplished.


You can also re-name the existing db (users would need to be bounced off in any case before the restore), then restore the db. If anything goes wrong, you still have the original, or you can delete it when you are happy.

...

-- FORTRAN manual for Xerox Computers --
Charles Kincaid
Charles Kincaid
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1041 Visits: 2383
I agree with what has been said. Disk space is a big issue. Also if your restore fails part way through will SQL server have enough resources to "roll back"?

I dislike the way restore operates from the GUI anyway. If my restore is not an exact overwrite of the backup then things get tricky. Unlike many of the Microsoft dialogs it does not warn you that you are about to overwrite existing files. I think that is should. It also does not warn you that referenced directory paths don't exist. For example some of my customers have databases on D: and for me D: is the DVD drive. Even if I use the "force restore over existing database" it does not always put the files in the right place.

Would many of your concerns be addressed if the GUI restore tools were improved?

ATBCharles Kincaid
fhanlon
fhanlon
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2327 Visits: 2271
While its an interesting idea, I'm not sure I really see a benefit here. I can already restore to a different name if I want so if this fuction is useful to me I can esentially do this already. The RESTORE statement is pretty flexible already. I'm not sure I would want default behavior restoring to a test name.



Francis
Stephen Grimshaw
Stephen Grimshaw
Grasshopper
Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)Grasshopper (18 reputation)

Group: General Forum Members
Points: 18 Visits: 415
This sounds like something we do .
We have a file that tells a browser-based application the name of the database it should use. New versions of the database (built behind our firewall from wider data) are restored using a different name. If Restore is successful, the name in the file ia changed.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search