Anastasios Angelidis wrote:
> Mark Parker wrote:
>
>> We do exactly that; everything goes in it's own folder (Functions/,
>> Tables/, Procedures/, etc.), and I developed a tool that puts them all
>> together (resolving interdependencies) into a single script that can
>> be used to "build" the database.
>>
>> To do an "upgrade" of an existing database, we do a "build" of the new
>> version, then use a db-sync tool (red-gate SQLCompare, if you're
>> wondering, but there's others out there) to make the existing database
>> look just like the new database.
>
>
> So you only keep create scripts?
>
> What if you do a column update on a table? It's not like you can rerun a
> create table on production. You only need to run a table update.
>
<snip>
Yes, we only keep create scripts. If we change some column on a table,
our tool (red-gate SQLCompare, as I mentioned) makes the change in the
production database. The process goes a little something like this:
1) run tool to make a create-script for the new version
2) run script to create a temporary copy of the new database
3) run SQLCompare to make production database look just like temp copy
4) remove temp copy
It's worked very well for us so far, but do note that SQLCompare isn't free.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 4 17:50:30 2005