Prev: temp_MS_AgentSigningCertificate_database
Next: Locking Diagnostics
From: Pat on 24 May 2010 14:57
My SQL database is called Clinic. All developments are carried out in my
local SQL server. Once the development is done, Clinic will be pushed to the
production SQL server. Client's data are stored in the production SQL server.
Now, the same client needs enhancement features, which also use the same
database Clinic. So, I do new development in the database Clinic in my local
box. As the new development has been finished, I need to migrate all changes
made in my local SQL server to the production server. How can I do it? I
cannot wipe out the production Clinic because it already has client's data.
Basically, the developmental Clinic does not have client's data which are
saved in the production box. The production Clinic does not have new changes
(e.g., new stored procedures/views/triggers/tables, etc) which are created in
the developmental Clinic. How can I unify the production Clinic and the
developmental Clinic?

NSIG - Pat
From: John Bell on 24 May 2010 15:27
On Mon, 24 May 2010 11:57:01 -0700, Pat <Pattt(a)newsgroups.nospam>
wrote:

>My SQL database is called Clinic. All developments are carried out in my
>local SQL server. Once the development is done, Clinic will be pushed to the
>production SQL server. Client�s data are stored in the production SQL server.
> Now, the same client needs enhancement features, which also use the same
>database Clinic. So, I do new development in the database Clinic in my local
>box. As the new development has been finished, I need to migrate all changes
>made in my local SQL server to the production server. How can I do it? I
>cannot wipe out the production Clinic because it already has client�s data.
>Basically, the developmental Clinic does not have client's data which are
>saved in the production box. The production Clinic does not have new changes
>(e.g., new stored procedures/views/triggers/tables, etc) which are created in
>the developmental Clinic. How can I unify the production Clinic and the
>developmental Clinic?
>
>NSIG - Pat

Hi

I'd always recommend that you store your code a version control
system, that way you will always be able to manage the changes and
have a complete understanding of what has been released.

There are various tools available that compare two schemas and produce
an upgrade script such as
Apex - SQL Diff
Redgate - SQL Compare
Microsoft - Visual Studio for DB pros..
to mention a few.

John
From: TheSQLGuru on 24 May 2010 23:24
I too recommend the first choice. ANY data or schema modification should be
done via scripts that are controlled in a rigorous source code control
system. Error handling, rollbacks, recovery, etc should all be part of the
plan...

--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net


"John Bell" <jbellnewsposts(a)hotmail.com> wrote in message
news:6cklv59cvmu8vf95ptveq6r32c71sfq761(a)4ax.com...
> On Mon, 24 May 2010 11:57:01 -0700, Pat <Pattt(a)newsgroups.nospam>
> wrote:
>
>>My SQL database is called Clinic. All developments are carried out in my
>>local SQL server. Once the development is done, Clinic will be pushed to
>>the
>>production SQL server. Client's data are stored in the production SQL
>>server.
>> Now, the same client needs enhancement features, which also use the same
>>database Clinic. So, I do new development in the database Clinic in my
>>local
>>box. As the new development has been finished, I need to migrate all
>>changes
>>made in my local SQL server to the production server. How can I do it? I
>>cannot wipe out the production Clinic because it already has client's
>>data.
>>Basically, the developmental Clinic does not have client's data which are
>>saved in the production box. The production Clinic does not have new
>>changes
>>(e.g., new stored procedures/views/triggers/tables, etc) which are created
>>in
>>the developmental Clinic. How can I unify the production Clinic and the
>>developmental Clinic?
>>
>>NSIG - Pat
>
> Hi
>
> I'd always recommend that you store your code a version control
> system, that way you will always be able to manage the changes and
> have a complete understanding of what has been released.
>
> There are various tools available that compare two schemas and produce
> an upgrade script such as
> Apex - SQL Diff
> Redgate - SQL Compare
> Microsoft - Visual Studio for DB pros..
> to mention a few.
>
> John


From: Double_B on 25 May 2010 06:37
On May 24, 11:57 pm, Pat <Pa...(a)newsgroups.nospam> wrote:
> My SQL database is called Clinic. All developments are carried out in my
> local SQL server. Once the development is done, Clinic will be pushed to the
> production SQL server. Client’s data are stored in the production SQL server.
>  Now, the same client needs enhancement features, which also use the same
> database Clinic. So, I do new development in the database Clinic in my local
> box. As the new development has been finished, I need to migrate all changes
> made in my local SQL server to the production server. How can I do it? I
> cannot wipe out the production Clinic because it already has client’s data.
> Basically, the developmental Clinic does not have client's data which are
> saved in the production box. The production Clinic does not have new changes
> (e.g., new stored procedures/views/triggers/tables, etc) which are created in
> the developmental Clinic. How can I unify the production Clinic and the
> developmental Clinic?
>
> NSIG - Pat



It all depends on what the new development is , lets say all you have
is only code changes, you could script out the current database using
the SSMS & then run the new scripts. Incase the client needs the old
objects, you could deploy them using the scripts.
Take a full backup of the Db before you make any changes.
If its the data, you could rename the object with the _old name & then
create a new one & push all the data needed via DTS/SSIS from the old
to the new.

Regards
Bharat Butani.


 | 
Pages: 1
Prev: temp_MS_AgentSigningCertificate_database
Next: Locking Diagnostics