I guess this is an age old problem, managing database changes such that they respect applications dependent on them. We are bolting more applications to a couple of sql databases so the management exercise is becoming more complex, risky and expensive to maintain.
Currently we have a database version number, use schema naming for application specific views and procedures and have a folder of each change in sequential order that has to be applied to production. Over the holiday break I thought I might research how we can improve our approach. What systems have you or your organisations adopted to keep it all under control , and are they successful? -- ----------------------------------------------------------------------------- Stuart Kinnear Mobile: 040 704 5686. Office: 03 9589 6502 SK Pro-Active! Pty Ltd acn. 81 072 778 262 PO Box 6117 Cromer, Vic 3193. Australia Business software developers. SQL Server, Visual Basic, C# , Asp.Net, Microsoft Office. -----------------------------------------------------------------------------
