April 3, 2008 at 9:49 am
What would be the best way to refresh the database from my production environment to my test environment. I need to do this on a weekly basis. I am brand new to SQL.
April 3, 2008 at 3:49 pm
Do you mean copy? If so, the prime candidate is probably to setup a SSIS (SQL 2005) / DTS (SQL 2000) package which you can schedule to simply copy the database across.
April 4, 2008 at 5:32 am
Yes Thankyou I would like to copy the database from live to pilot or test everyweek so that we can test changes. Im not sure if i only have to copy the live data base or the Master as well. Thanks again for your input.
April 4, 2008 at 7:19 am
If it's a total refresh, restoring your backup of the source database to the target is probably the easiest way, especially if your talking about large amounts of data/tables. If the database is relatively small, the DTS/SSIS routine should work nicely. Put it on the scheduler for the desired time and when you come into work, viola, done! If your pilot server is already in place, you don't have to worry about master. You may need to run sp_change_users_login to sync your logins with your users in the newly restored database (check BOL for more info).
-- You can't be late until you show up.
April 7, 2008 at 4:06 am
Restoring from your backup is proably the easiest. You can then script the restore and schedule it in a job. So it will run automatically.
Re query with master. You don't need to restore master for this task to work but you may need to create/fix logins on the the test instance after the restore so your test users can access. Again this can be scripted and included in the job
Gethyn Elliswww.gethynellis.com
April 7, 2008 at 5:44 am
Thank you all for this information. I am new to this and hope my questions are not to dumb
Thank all again
Bob Silenzi
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply