Hi gurus,

I am taking care a offsure development centre database core , and sending
builds for a homecare web besed product at
US sites.

We are maintaining a clone of prod database here at offshore office to test
the build and patches on that then send to prod server sites.

We are sending builds once in a fortnight,and patches as and when required.
There are many database changes due to enhancement or bug fixing. In our
current process we are maintaining day wise database change file , for patch
we send selective sql reqd for patch , and for build we cumulate all the
sqls in cronological order from last build to current build date, use a
database version stamp in a table in the database to keep track build/patch
version.

While using this process we are phasing some problems sometimes. -

1. In builds many of the sql/scripts gets duplicated which we have already
sent in patch, which leads to unnecessay error s while executing script at
prod database.

2. Sometimes any sql/script might not be a part of build or patch which
should be.

Pl. suggest refinement in this process or any standard approch of
builds/Patches matching our requirement. Any site / article will help us a
great.

TIA,

Sheilesh




---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 4/10/2003

MS Sql Server LazyDBA home page