CODEWITHSUNDEEP
asp.netsql-serverdatabase-migration
Dan
Dan

Reputation: 29365

Database Migrations on an existing large database

Is it feasible to start using a Migration framework such as RikMigrations or Tarantino on an existing large legacy database? The schema is still being tweaked all the time, so I was hoping to use migrations to manage these tweaks.

The database is SQL Server 2008 and has 600 tables 300 views and 2000 storedprocs? I'm just a bit concerned that the initial migration to get where we are now, would be impractical/slow/error prone?

Upvotes: 2

Views: 205

Answers (1)

David Duffett
David Duffett

Reputation: 3145

Why not version control your database and keep track of changes that way? Red Gate has some brilliant products for managing changes to databases:

  • SQL Source Control: version controls your database (almost any VCS: Mercurial, Git, SVN, etc) and enables easier database development within a team as you can all have your own dedicated databases to work on. You can also version control your static data using this tool.
  • SQL Compare: Used to compare 2 databases (say, version control vs your TEST or PRODUCTION database), export scripts and synchronise databases
  • SQL Data Compare: Used to compare static reference data required by your applications (like enum values, country lists, etc)

Our team has been much more productive and database changes done with confidence by using these tools. I wrote a couple of posts about it here: http://davidduffett.net/post/4663483715/database-continuous-integration-and-deployment-with-red

Upvotes: 1

Related Questions