Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


how to migrate changes to production server


how to migrate changes to production server

Author
Message
Andrew Gothard-467944
Andrew Gothard-467944
SSC-Enthusiastic
SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)SSC-Enthusiastic (198 reputation)

Group: General Forum Members
Points: 198 Visits: 2357
In addition to the advice from Eliott W and robert.mcleod, I would also recommend that you have a QA version of the database that mirrors live. First test all your scripts for the migration against that. Then have a number of users test all apps which access the database and SIGN OFF the tests - or highlight weaknesses or failures against the testing schedule.
If you do not have a formal testing and signoff process agreed by management, which they know can be traced back to them in the event of issues arising, you are - in my experience - going to get no worthwhile effort from a significant proportion of the user base. <waves hand in airy fashon> yeah, yeah. Whatever, I'm busy you know. User may actually bother trying to log in ... if you're lucky.
Amend your scripts AND DOCUMENTATION to take into account any issues arising from the qa - then restore and do EVERYTHING again. Once you have full signoff - then you can use the exact process you have set up, and documented, to do the move to live.
While this process is undertaken, there should be a code freeze on both the database and the apps accessing it. If the freeze has to be broken - eg to fix a critical bug, then it's back to the start with qa, etc to ensure the changes work with the updated functionality.
You should also have tested your rollback in a qa enviromnent so if you get a user who has signed off, but not done thier testing job effectively - or indeed if you make an error in your process - whatever, and something critical breaks, your way back has also been tested appropriately.
steve block
steve block
Mr or Mrs. 500
Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)Mr or Mrs. 500 (520 reputation)

Group: General Forum Members
Points: 520 Visits: 1563
I like to use Red Gates Sql-Compare to generate a script that will synchronize the test and production databases. I then use the script as a starting point for a script to make the changes to production. This helps me to not miss anything.

Steve



Mauve
Mauve
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1246 Visits: 2049
First off, you should be using a Source Code Control system.

Then you need to create an "Upgrade Schema" script that can be run in batch mode against your QA databases first and then, after all testing has been done, against your production database(s).

Watch out for automated tools that perform comparisons between two databases. They will not get it right or will only handle the "simple" changes. See: http://www.sqlservercentral.com/Forums/FindPost702354.aspx which describes a schema change that involved XML binding.

See the following post which describes our process.
http://www.sqlservercentral.com/Forums/FindPost474053.aspx You may wish to read the entire thread as a lot of the "experts" provided some good advice to this exact problem.


(PHB) I think we should build an SQL database. (Dilbert) What color do you want that database? (PHB) I think mauve has the most RAM.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search