Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
Rolling Back a Restore
20 posts, Page 1 of 2
1
2
»»
Rolling Back a Restore
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Saturday, March 20, 2010 11:20 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 2:54 PM
Points: 31,410,
Visits: 13,726
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
Post #886934
Lynn Pettis
Lynn Pettis
Posted Saturday, March 20, 2010 12:35 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 9:18 PM
Points: 21,596,
Visits: 27,409
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.
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)
Post #886947
SQLRNNR
SQLRNNR
Posted Sunday, March 21, 2010 7:00 PM
SSCoach
Group: General Forum Members
Last Login: Today @ 1:07 PM
Points: 18,733,
Visits: 12,332
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 2008
SQL RNNR
Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #887133
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Monday, March 22, 2010 1:25 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 2:54 PM
Points: 31,410,
Visits: 13,726
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
Post #887190
mpa
mpa
Posted Monday, March 22, 2010 1:47 AM
Forum Newbie
Group: General Forum Members
Last Login: Friday, May 17, 2013 5:34 AM
Points: 3,
Visits: 139
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.
Post #887199
GSquared
GSquared
Posted Monday, March 22, 2010 6:27 AM
SSCoach
Group: General Forum Members
Last Login: Monday, May 06, 2013 1:09 PM
Points: 15,439,
Visits: 9,569
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
Post #887309
jay-h
jay-h
Posted Monday, March 22, 2010 8:03 AM
Say Hey Kid
Group: General Forum Members
Last Login: Today @ 8:55 AM
Points: 685,
Visits: 1,707
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 --
Post #887397
Charles Kincaid
Charles Kincaid
Posted Monday, March 22, 2010 8:54 AM
Right there with Babe
Group: General Forum Members
Last Login: Friday, May 17, 2013 9:18 AM
Points: 772,
Visits: 1,825
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?
ATB
Charles Kincaid
Post #887428
fhanlon
fhanlon
Posted Monday, March 22, 2010 9:06 AM
SSCrazy
Group: General Forum Members
Last Login: Friday, May 17, 2013 8:51 AM
Points: 2,100,
Visits: 1,789
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
Post #887436
Stephen Grimshaw
Stephen Grimshaw
Posted Monday, March 22, 2010 9:52 AM
Grasshopper
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:55 AM
Points: 15,
Visits: 351
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.
Post #887469
« Prev Topic
|
Next Topic »
20 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.