- Thanks received
- 3
ok, we've all been there. version 1 of your killer app is on the streets and selling like hotcakes. lots of happy clients have filled lots of tables with lots of data. one year on and you have finished version 2. naturally there are lots of new tables and lots of new fields in existing tables, some movement in the old table structure, relationships etc and of course lots of new stored procs as well as changes to existing ones. question is, what is the best way of managing this? backup all legacy data, re-install the complete new database and import or somehow tiptoe around what is already there, adding here, tweaking there. a friend who works for a large multi told me of a tool they spent 2 years developing to do exactly this and which now works seamlessly [so he says]. does anyone in the congregation know of a similar tool available that would do the job?
but really, sql change management is a black art!