Creating and maintaining a database, which is then developed and developed by many developers, is what happens in software development all the time. We create the build script and support further upgrade scripts that apply when the database grows over time. There are many ways to manage this: from manual updates to console applications / build scripts that help automate these processes.
Has anyone created or managed these processes switched to Source Control to manage the database schema? If so, what did they find the best solution for? Are there any pitfalls to avoid?
Red Gate seems to be a major player in the MSSQL world, and their DB source code management looks very interesting:
http://www.red-gate.com/products/solutions_for_sql/database_version_control.htm
Although it does not seem like it replaces the default data management process (default), therefore it replaces only half of the change management process from my pov.
(when I talk about data, I mean search values and such things, data that needs to be deployed by default or in a DR script)
We work in a .Net / MSSQL environment, but I am sure that the premises are the same in all languages.
source
share