Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
vermorel
Starting Member
26 Posts |
 Posted - 2008-02-03 : 04:29:02
|
| I have developing a .NET web app that depends on SQL Server 2005. The database needs to evolve as well as the as the database. I would like to know what are the "best practicing" when it comes to database schema versioning?So far, I was keeping the SQL diff file in a very ordered manner like diff001.sql, diff002.sql, diff003.sql (applied in sequence to produce the final database schema).Yet, the database in production gets manually upgraded with the lastest diff script. In order to avoid manual error in the future, I am considering adding a 'app_version' table into the database just for the sole sake of checking that the SQL scripts get applied once but only once.How does this sound?What would be your suggestions is this matter?Thanks in advance,Joannès Vermorelhttp://www.lokad.com sales forecasting |
|
|
|
|
|
Database versioning - dev best practice