Moving and restoring the db from latest backup -- Priority

Question

Post reply

Moving and restoring the db from latest backup -- Priority

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Ed Wagner SSC Guru Points: 287026 More actions · Answer 1

Have you been able to answer the basic questions yet? They will determine the approach you take.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

Mitch C. Stein SSChasing Mays Points: 658 More actions · Answer 2

+1 on DeWayne_McCallie's answer. I see a few incredibly knowledgeable folks advocating moving or copying the file. However, I know SQL 2012 will back up and restore from network drives.

I personally run scripted jobs that back up my production server to a shared drive from which a development server later restores. Is this a bad approach? What do I lose if I am sure of my backup chain and how my backup file is then backed up?

Thanks folks.

Jeff Moden SSC Guru Points: 1003896 More actions · Answer 3

Mitch C. Stein (9/23/2015)
I know SQL 2012 will back up and restore from network drives.

So will everything from 2005 and up. And, 2005 also had the "COPY ONLY" feature... just not in the GUI. Since the files are on network drives, I don't both SQL Server with making another backup. I let the "lesser" machines do the copy/restore.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Mitch C. Stein SSChasing Mays Points: 658 More actions · Answer 4

Jeff Moden (9/23/2015)
Mitch C. Stein (9/23/2015)
I know SQL 2012 will back up and restore from network drives.
So will everything from 2005 and up. And, 2005 also had the "COPY ONLY" feature... just not in the GUI. Since the files are on network drives, I don't both SQL Server with making another backup. I let the "lesser" machines do the copy/restore.

That's what I do.

Veeam controlled backups that are then backed up with the local machine backup.

Independent of this, a copy-only backup to a drive on the development box that has a scripted restore pointed at it.