Posted by Erland Sommarskog on 07/05/06 22:07

metaperl (metaperl@gmail.com) writes:
> I'm actually taking Microsoft's 2779 and just finished a lab where we
> kept track of our changes to the database.
>
> However, I'm not happy with the scripts interface because it does not
> tell me the chronological order of my changes to the database.
>
> Could someone share with me their technique for keeping track of
> database changes?
>
> I'm actually thinking a set of tables would be best, because sometimes
> you want to know what database object you made a change to and other
> times you want to know when you did something...

The baseline for all such activities is the version-control system. SQL
objects have source code just like any other program code.

In our shop we use Visual SourceSafe out of habit. On top of that we
have a toolset, that also adds its own "system tables" to the database,
so we also have a track for a specific database. The whole thing is
available for public download on http://www.abaris.se/abaperls/.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]