April 20, 2010 at 7:53 am
hi all
we have our current live sql server, and a new test sql server.
when im finished with test it will be the new live and i cant take the current live down.
do i need to restore all system DB's to the test? we have various jobs, security, users etc setup that i want carried accross!
iv tried retoring msdb on test to that of the live system, by simply doing a restore on sqlmanagement, but it failed as the test server has sql patched to sp2 and live does not!
any advice appreciated!
April 20, 2010 at 8:07 am
Hi,
I wouldn't necessarily go about it that way... I would script out all the objects required. & just run the scripts against the new SQL instance. This can be achieved relatively easily, for SQL logins, SQL Agent jobs etc
You will find a lot of the scripts here within SSC.
btw it may be a good opportunity to apply SP3 to the new instance.
Cheers,
Mark
April 20, 2010 at 8:11 am
I am in pretty much the same situation and we are planning to move the server to a different location ...I have all the scripts ready to move the logins/jobs ..I was wondering if the system databases needs to be moved as well..
April 20, 2010 at 8:22 am
didnt even know sp3 was out!
so you reckon get scripts to move systemdbs, users and jobs and run on the new server?
would that put much of a strain on the live system when pulling the data? as its pretty unstable!
April 20, 2010 at 8:23 am
hi journey man , would you be able to share your scripts 😀
April 20, 2010 at 8:29 am
ours is not a 24/7 workshop and the server can be taken down for the weekend ....the only question I have is if we are deleting the old server and creating new server which will be named as the old server , should I be moving the system databases too ..?
April 20, 2010 at 8:32 am
im asking the question on my own behalf journey man!
April 20, 2010 at 8:34 am
malachyrafferty (4/20/2010)
im asking the question on my own behalf journey man!
Chill.
No, don't move the system databases. Script out the objects you need from the source server and run those scripts on the destination server.
April 20, 2010 at 8:36 am
Thanks Lynn, I found my inbox slowly drowning in reponses to this thread!
April 20, 2010 at 8:41 am
im chilled 🙂 we were just getting mixed up in our questions
cheers lynn for the answer ! i dont have that many jobs or users and for a novice like me it seems the easiest option!
April 20, 2010 at 8:43 am
didnt even know sp3 was out!
SQL 2005 SP3 has been available for quite some time!
so you reckon get scripts to move systemdbs, users and jobs and run on the new server?
No, work out which objects you need to transfer to the new SQL instance and leave the System db's alone.
would that put much of a strain on the live system when pulling the data? as its pretty unstable!
If you are that concerned could you not perform these actions during a maintenance window?
April 20, 2010 at 8:49 am
i dont have that many jobs or users and for a novice like me it seems the easiest option!
This sounds like a straightforward job, don't be afraid to post back here if you have any questions or concerns. We're here to help!
April 20, 2010 at 8:51 am
thanks all for help, i get a bit overly worried i might break something!
the only service days are sundays. i like sundays at home 🙂
April 20, 2010 at 8:53 am
sorry for the confusion malachyrafferty ...I got my answers too..
April 20, 2010 at 8:55 am
the only service days are sundays. i like sundays at home 🙂
But they are normally double time 😉
Viewing 15 posts - 1 through 15 (of 39 total)
You must be logged in to reply to this topic. Login to reply