SQL Server change management [closed]

Closed. This question is seeking recommendations for books, tools, software libraries, and more. It does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can 开发者_JS百科be answered with facts and citations.

Closed 7 years ago.

Improve this question

Does anybody know of a good change management tool for SQL Server?

We would like to use it to migrate our existing clients database to newer version via an api.

---

I work as a product manager at Red Gate. We have the SQL Comparison SDK, which provides access to an API that you can use to compare two schemas and generate a change script to apply to the target. However, this has limitations if complex data migrations are required as part of the change.

We're working on improving this in the next release. We're adding a new feature, SQL Migrations, that will allow you to specify your own custom scripts for 'complex' changes. The comparison and synchronization tool, SQL Compare, will work in conjunction with SQL Source Control to provide this functionality. If you're interested, there's an early access program. We're hoping to get a beta release out in September 2011.

---

I found a tool that will do the work for me DB Ghost from http://www.innovartis.co.uk/

Cheers

---

there is no 100% solution out there...

Bute in my experience the tools from redgate are rather good at this - see http://www.red-gate.com/products/sql-development/sql-developer-bundle/ and esp. http://www.red-gate.com/products/sql-development/sql-packager/

---

Not really - not out of the box. The best and most flexible approach would be to create change scripts for all your changes to the database, and then include those into your regular deployment, and run them, either on your own, or using a tool such as SSW SQL Deploy (which can be run as a stand-alone command line tool, a stand-alone wizard, or from your app through a .NET interface).

The .NET Entity Framework team has started an initiative called EF Code-First Migrations which aims at easing this database upgrade scenario - this is very new and very much still work in progress, but it looks quite promising, if you're using the code-first approach with Entity Framework.

---

We at a government ministry, are using Kal Admin, and like it a lot . We are using it for Change Management, source control aka version control and Compare. I am not sure but I think it's not expensive.