Database Source Control - version control

I am curious about what people out there are using for managing database code, database data, and version control of databases.

For example, we have an application that is installed and a number of clients and each client potentially has a different version of the codebase.

We do a decent job of managing this, but it does feel painful at times.

Please post responses if you are using tools and/or comments that work well!

Generate Script using Scriptio (Free Codeplex Utility)

Check into SVN using Tortoise Client from Explorer each time we make a change.

For Checking SQL differences between Test and Prod enc, I use DbDiff(another Free codeplex utility)

I prefer Serena Verson Control as it is nicely linked with other applications like Issue tracking, work progress tracking etc.

My previous organisation was using SVN to store different versions of code.

We're working with Visual Studio Team System for Database Professionals. We have an MSDN subscription and now that DBPro is included with a Developer Edition, it seemed like a better choice.  Besides, this way we can branch the DB along with the code.  Still trying to figure out how best to handle the small data updates/inserts that are supposed to go with each version. That part is always tricky.

We are starting to explore using more of MS's Team Foundation Server to help us.  Right now, were are managing the change log/version control ourselves.

You might want to try this as well

http://www.red-gate.com/products/solutions_for_sql/database_version_control.htm

nitya said:

Check into SVN using Tortoise Client from Explorer each time we make a change.

My IT team uses SVN as well.  I only wish it could work with VS2005 like Source Safe.

Tonja B

TFS here...

I've used TFS before, but encountered some issues using it's source control with the way we'd divided our warehouse up (by schema)