Move changes from test to production

Question

Move changes from test to production

tomjuo

SSC Rookie

Points: 32
More actions
August 2, 2008 at 11:57 am

#99206

I'm developing test database and now I need to move all changes to the production database. How can I do this? I have read some articles and decided to use third party soft to compare schema and to generate script.
May be is it better way? How are you doing this? Can you give some hints?

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Grant Fritchey SSC Guru Points: 399332 More actions · Answer 1

That's a pretty standard approach. Not necessarily the most accurate since you're only capturing what's different, not specifically what needs to be moved. At some point, depending on your development processes, you may need a more specific deployment process so that you can move a set of changes associated to a particular version or release of the software. When you get to that, you'll want to look at building something in-house or possibly using SQLGhost or Microsoft Visual Studio Team Edition for Databases, or possibly Red Gate's SQL Compare, because these tools can build a database from source control, allowing you to version control the database.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

tomjuo SSC Rookie Points: 32 More actions · Answer 2

So, I'm in a right way. I'm using Red Gate SQL Compare 6 at the moment. I downloaded DB Ghost also. It looks like very powerful tool.

Thanks.

Steve Jones - SSC Editor SSC Guru Points: 739661 More actions · Answer 3

either of those tools can help.

One other thing to be aware of is documentation. You may not deploy all changes, so even with a third party tool, you want to be able to determine which changes to not move forward.