May 16, 2016 at 8:08 am
Currently I have inherited production, stage, qa and dev SQL environments. I am seeing what others have in place for restoring the lower environments and the schedules?
So for stage, have log shipping to have the most current data. QA on x schedule and DEV on x schedule.
Just seeing what others have configured.
Thanks.
May 16, 2016 at 1:20 pm
Everyone is going to be different. I don't have any environment setup to keep data in sync 24X7.
I have SQL Agent jobs setup to backup and restore to Non Prod whenever the apps folks want the data refreshed.
May 16, 2016 at 11:28 pm
rodto3rd (5/16/2016)
Currently I have inherited production, stage, qa and dev SQL environments. I am seeing what others have in place for restoring the lower environments and the schedules?So for stage, have log shipping to have the most current data. QA on x schedule and DEV on x schedule.
Just seeing what others have configured.
Thanks.
As mentioned above, have SQL Agent jobs configured for automated refreshes.
Our environment is PROD -> UAT -> TST -> DEV.
UAT - I do regular weekly refreshes which is as simply as Scheduling the Job. In the steps I have tasks such as kill connections, restore DB, creates users / assign permissions, hashes data etc.
TST / DEV - this is not scheduled but on demand from testers / developers. I generally rarely restore these environments as a lot of work is going on.
Whatever works in your environment - stick to it.
May 17, 2016 at 10:11 am
Thanks guys...this is generally what I was looking for. Just to see what others are currently doing.
Thanks!
May 18, 2016 at 4:42 am
rodto3rd (5/17/2016)
Thanks guys...this is generally what I was looking for. Just to see what others are currently doing.Thanks!
Simply use the GUI for the restore and click on generate script. Put that and any alter login, grant logins into that script and you have everything you need to refresh an environment.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply