Prev: Windows/SQL Authentication...
Next: Thanks
From: Teh TL Teh on 12 Nov 2009 20:01
I have a DB at location that uses a database that was created about a year ago.
In a test environment we have made numerous upgrades to that exact db with
new procedures and a couple new columns in certain tables.

What is the most efficiant way to upgrade the Old DB while keeping all data
intact.
I was thinking to Check the DB Columns from the system tables and just
showing me what doesn't exist in the old table then add it in via a alter
script... (If someone already has this script please let me know).

As for the stored procedures, I was just going to drop them all and re-create.
Is this the the best way? The tables have me more worried, because I need to
keep the data in tact and just want to check for the added colums to have a
script automatically create, so ideally I would like to compare the entire
table structure including triggers index's etc, and not just the colums
From: Jeffrey Williams on 12 Nov 2009 22:03
Take a look at Redgate's SQL Compare tool. You perform a schema
comparison - which will identify all of the differences between the two
databases schema's and provide a script to synchronize them.

There are other tools available - Apex SQL has one, Quest has one, as well
as some free versions (check out codeplex.com).

Jeff

"Teh TL" <Teh TL(a)discussions.microsoft.com> wrote in message
news:9795BA6F-6319-43F5-A460-DFB123578881(a)microsoft.com...
> I have a DB at location that uses a database that was created about a year
> ago.
> In a test environment we have made numerous upgrades to that exact db with
> new procedures and a couple new columns in certain tables.
>
> What is the most efficiant way to upgrade the Old DB while keeping all
> data
> intact.
> I was thinking to Check the DB Columns from the system tables and just
> showing me what doesn't exist in the old table then add it in via a alter
> script... (If someone already has this script please let me know).
>
> As for the stored procedures, I was just going to drop them all and
> re-create.
> Is this the the best way? The tables have me more worried, because I need
> to
> keep the data in tact and just want to check for the added colums to have
> a
> script automatically create, so ideally I would like to compare the entire
> table structure including triggers index's etc, and not just the colums

 | 
Pages: 1
Prev: Windows/SQL Authentication...
Next: Thanks