Replicating the schema while preserving existing data

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello All,

Here is my situation:

I have a core database that is used to define the schema
of a client-owned database for use with some software. As
the software evolves and changes so too will the schema of
the core database. Ideally these changes should be
propogated down to the client-owned database;altering the
schema to match the new core version without destroying
the data that may already exists.

My attempts to use replication for this have failed when I
perform the following:

-The core database has a single table with three fields.
-The client database has nothing.

*I configure and activate replication

- Now the client database has an identical copy of the
table from the core database.

*I make changes to the core database schema by adding
three more fields to the table.

- Now the client database and core database have
differeing schemas.

*I add data to the client database table.

*I initiate replication from the core to the client
database expecting my three new fields to be appended to
the table without destroying my existing data.

-I don't get what I expect, instead I get a the original
three field table that was first replicated into the
client database and the data is missing.

How can I replicate a schema change from one database into
another without destroying any of the data that may
already exist on the target database?

Thanks,

Marc Deskins
marcdeskins@xxxxxxxxxxx

.



Relevant Pages

  • Re: Replicating the schema while preserving existing data
    ... database from the core database the data that was added to ... the client database before synchronizing is deleted. ...
    (microsoft.public.sqlserver.replication)
  • Re: Java is becoming the new Cobol
    ... In the Unisys 2200 environment using their Network Database Server, you get a schema work area depending on how you invoke the schema. ... However, it not only copies the schema area into the program, but the "DMCA" (Database Management Communication Area - basically, the block of information that holds your connection state) is copied in too. ... So, you're left with working-storage, which makes it visible to your program only, or common-storage, which makes it visible to programs linked in. ...
    (comp.lang.cobol)
  • Re: Renaming databse objects
    ... we may need to change the database name and in some cases want to rename ... existing database objects. ... Just in case this database object renaming project is in response to ... Create a new schema, ...
    (microsoft.public.sqlserver.programming)
  • Split messages
    ... This is based off the northwind database. ... Create document schema: ... Select the SQL entry, make sure that we are pointing to the SQL ... For the item select a receive pipeline and name it EmpSplitPipe.btp. ...
    (microsoft.public.biztalk.general)
  • Renaming databse objects
    ... While working on an existing database, we may need to change the database name and in some cases want to rename existing database objects. ... Just in case this database object renaming project is in response to ... Create a new schema, ... The schema with the original column names is still there, ...
    (microsoft.public.sqlserver.programming)