Re: database version control question

Here is a couple of alternatives ... depending on your taste and/or access

1. Use a database tool to compare schemas and the like. I think Erwin & SQL Programmer do this sort of thing. Not sure if these tools compare stored procedures. DBDiff is an inexpensive alternative here.
2. Export all the stuff that matters (e.g. schemas, stored procs) to flat files and then checksum them (ala Java CRC32). This works well if you cannot perform the compare across environments or if you just want to know what your dealing with. Gives you some level confidence about the environment your dealing with and, with the right level of detail, can bring some sanity to the chaos. Maybe in cannot say what or why things changed, but it can tell you where.

Good Luck, Bob

Nhuan_at_Lieu_NoSpam.org <Nhuan_at_Lieu.org> wrote in message news:<8cbev6$c94$1_at_nnrp1.deja.com>...
>
>
> Hi, I am relatively new DBA, in your opinion what is your suggestion in
> handling version controlling database changes from
> Development->QA->Production in an environment where the several
> developing teams have multiple and/or independent database change
> requests to the _same_ database at _different_ timeframe. Below is a
> typical example:
> DEV_TEAM1 have Table1 (increase a column size) & StoreProcedure1 update
> request and change priority is Important (not Emergency). This request
> to move into Production in 2 weeks. However, before the above change
> took place, DEV_TEAM2 request an "unrelated" functional change Emergency
> request to update Table1 (add an NULLable column) & StoreProcedure2.
> This second is to move into Production in 1 week. To summarize, Request
> 2 comes to DBA after Request 1 but need to move into Production sooner
> than Request 1 with one common & unrelated table change. To make it even
> worst, we have 7 such outstanding and similiar requests right now on the
> queue and I need to way to keep track of these changes as to minimuize
> impact.
> Any systematic way to help to manage this chaos is highly appreciated
> and would like hear from you on your person experience how you did your
> change management.
> Thanks.
> PS - I works in a startup where change requests occur weekly.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Mon Apr 03 2000 - 00:00:00 CEST