3 replies
by sgt_shultz
what you wish to do is set up a test environment? i love it when you guys talk like that.
so you would need a second 'lab' sql server in addition to a 'lab' workstation. you will need to have the username and password of the account with admin rights on the sql server and that/those databases. and some way to get big amounts of data to it. backup tape? external drive? you could it on your network but that whole set of new problems. best for now if on separate subnet with internet access only maybe.
after you set up your lab server you'd 'restore' a recent backup from your production server. so you have rehearsed restoring operations after destruction of server.
depending on how you are backing up sql server, you could find out how using articles from the websites of either microsoft support or your sql backup software support.
if you don't get a fully operational backed up to the time you expect, you could explore how it *should* be getting backed up at support.microsoft.com
and write it down or print it out from the backup software and put in notebook
You'd setup the workstation using an odbc System connection via Control Panel (see Help for your OS). so maybe take a look at a working client pc now and see how it is setup.
IMHO sql is made to move around and fail safe and backup practically to real time if you learn the nuts and bolts of how it works. getting a complete backup and knowing how to put stuff back to a particular point in time will tell you almost all you need to know so this is a great idea imho. can be funded under disaster recovery.
by jpb
Poster rated this answer.
by jpb
This discussion is closed to new replies.
Trending Software posts
Sort by Trending