Very Computer

Your data is forever changing. So, if your intent is to version the changes
in the data in the database then it's really a waste of effort. However, if
you intend to keep track of changes in your ddl, then you should look into
sourcesafe and then create an user table to store the timestamp/version each
time you push new code into production.

--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net

Quote:> What would be the best way to version a database if several different
> versions are running in production?  The problem is the database name
never
> changes so it is hard to keep track of which version of database a
> particular application version is running.

> Thanks,
> Enoch

SQL Server MVP Erland Sommarskog has a freeware tool on his website that
allows for versioning etc called AbaPerls. I have played around with it and
it has a lot of functionality, but it will take some time to learn.

--
Jacco Schalkwijk MCDBA, MCSD, MCSE
Database Administrator
Eurostop Ltd.

Quote:> What would be the best way to version a database if several different
> versions are running in production?  The problem is the database name
never
> changes so it is hard to keep track of which version of database a
> particular application version is running.

> Thanks,
> Enoch