Re: Database schema version control techniques

> I am in a development environment which is prototyping a database application. > Currently we have 4 beta sites with different executables and database > schemas. As the application evolves there are additions/modifications to the > schemas. We have taken a rolling release approach to the executables, but will > soon strike a version. > What aides are there to maintain some version control on the database schemas > as this application develops?? > It seems that there is some tools/tricks available. If you keep your schemas under a version control system, like RCS or SCCS, how about something like this in your schema: create table version ( v char(100) ); then insert into version(v) values "$Id$";or insert into version(v) values "%W% %G%"; then revoke all on version from public; grant select on version to public; The SCCS eg may not work because at least some of the SCCS keywords expand into strings with tabs in them, and I don't know if SQL allows tabs as char data, but you could always post-process the schema with a filter to replace tabs with spaces if that is the case. > All responses appreciated > Steve Wallick > Harris Publishing > spw@sur1a.ess.harris.com -- Cheers Bill =========================================================================== | Bill Hails <bill@tardis.co.uk> | Reisner's rule of conceptual inertia: | | C.L.I. Connect Ltd. | | | 19, Quarry St., Guildford, Surrey | If you think big enough, you'll never | | GU1 3UY. Tel (UK) 0483 300 200 | have to do it. | ===========================================================================