database diff tool

I need to find a way of comparing the installed database with the database I wish to install. For example, we want to create the database and populate it This is all fine when you are installing on a new site, however it becomes more tricky when you start to consider you might have 10 sites all on different releases (e.g. say Customer A is on patch 3, and we release patch 23 which fixes a bug they need - they have to install 20 patches to get to that level...) What would be much more desirable is if you could just install patch 23 and have enough intelligence built into the install to alter what's needed. Ideally what we need is some way of the install figuring out what is different between the database we have in the release against what is on the client site - and then generate and run a list of alter commands to bring the client database structure up to date (i.e.. from patch 3 -> 23 in the example above). Kevin.

I'm sure this exact same query was posted about a week ago, check the archive. -- --------------------------------------- Tony Flaherty aef@mfs.misys.co.uk Analyst Programmer Misys Financial Systems All statements and opinions are my own, Misys don't pay me enough to have opinions on their behalf . Doyle, Kevin wrote in message <8427475C51D5D211A0DC00062B000D8F1F40A0@tampa.credo.ie>... >I need to find a way of comparing the installed database with the >database I wish to install. > >For example, we want to create the database and populate it > >This is all fine when you are installing on a new site, however it >becomes more tricky when you start to consider you might have 10 sites >all on different releases (e.g. say Customer A is on patch 3, and we >release patch 23 which fixes a bug they need - they have to install 20 >patches to get to that level...) > >What would be much more desirable is if you could just install patch 23 >and have enough intelligence built into the install to alter what's >needed. > >Ideally what we need is some way of the install figuring out what is >different between the database we have in the release against >what is on the client site - and then generate and run a list of alter >commands to bring the client database structure up to date >(i.e.. from patch 3 -> 23 in the example above). > >Kevin. >

In article <8h0mtf$5to$1@hermes.mfs.misys.co.uk>, Tony Flaherty <aef@mfs.misys.co.uk> writes >I'm sure this exact same query was posted about a week ago, check the >archive. > www.smooth1.demon.co.uk. Check out dbdiff2.4gl a database comparison tool which I recently enhanced. Compile with c4gl -o dbdiff2.4ge dbdiff2.4gl This allows comparing databases and generates the required sql to make the scheme the same. >-- >--------------------------------------- >Tony Flaherty aef@mfs.misys.co.uk >Analyst Programmer >Misys Financial Systems >All statements and opinions are my own, >Misys don't pay me enough to have opinions >on their behalf > >. >Doyle, Kevin wrote in message ><8427475C51D5D211A0DC00062B000D8F1F40A0@tampa.credo.ie>... >>I need to find a way of comparing the installed database with the >>database I wish to install. >> >>For example, we want to create the database and populate it >> >>This is all fine when you are installing on a new site, however it >>becomes more tricky when you start to consider you might have 10 sites >>all on different releases (e.g. say Customer A is on patch 3, and we >>release patch 23 which fixes a bug they need - they have to install 20 >>patches to get to that level...) >> >>What would be much more desirable is if you could just install patch 23 >>and have enough intelligence built into the install to alter what's >>needed. >> >>Ideally what we need is some way of the install figuring out what is >>different between the database we have in the release against >>what is on the client site - and then generate and run a list of alter >>commands to bring the client database structure up to date >>(i.e.. from patch 3 -> 23 in the example above). >> >>Kevin. >> > -- David Williams