|
Home > Archive > MS SQL Server Tools > April 2005 > utilize replication transaction log to synchronize with legacy system?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
utilize replication transaction log to synchronize with legacy system?
|
|
| Robert Eubank 2005-04-25, 11:23 am |
| Hello,
I am researching solutions to a problem I have and was wondering if anyone
could recommend a tool that might help me, or had any other ideas about how
I might go about addressing the issue.
I have a legacy SQL Server 2000 system (with transactional replication
enabled) and a newly designed system, also in SQL Server 2000. Of course,
the table structures between the two systems are completely different.
Until I can get all of the applications that point to the legacy system
converted to the new API, I am going to be forced to use both systems.
Therefore, I need to synchronize the data between both new and legacy
systems. I have several ideas for options for doing the synchronization,
one of which is somehow utilizing the transaction log that is used in the
transactional replication to let me know what data has changed so that I can
call a procedure in the corresponding system to change the data there too.
Several things to note about the legacy system:
1.. It utilizes transactional replication to synchronize data among
several copies of the database
2.. It already has performance issues so would like to add as little
overhead as possible
3.. It utilizes nested transactions heavily
Does anyone have any ideas about how I could go about synchronizing the two
systems, or whether or not there is a third party tool that could help me in
the above scenario?
Any help or pointers would be greatly appreciated.
Regards,
Robert
| |
| Hilary Cotter 2005-04-25, 1:23 pm |
| You have two choices. Either represent the new schema as indexed views on
your publisher and replicated the idnexed views to the susbcriber as tables
or encapsulate the logic to repicate to the different scheme in your
replication stored procedures.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Robert Eubank" < reubank@broadviewnet
.com> wrote in message
news:edQqDQbSFHA.2964@TK2MSFTNGP15.phx.gbl...
> Hello,
>
>
>
> I am researching solutions to a problem I have and was wondering if anyone
> could recommend a tool that might help me, or had any other ideas about
how
> I might go about addressing the issue.
>
>
>
> I have a legacy SQL Server 2000 system (with transactional replication
> enabled) and a newly designed system, also in SQL Server 2000. Of course,
> the table structures between the two systems are completely different.
> Until I can get all of the applications that point to the legacy system
> converted to the new API, I am going to be forced to use both systems.
> Therefore, I need to synchronize the data between both new and legacy
> systems. I have several ideas for options for doing the synchronization,
> one of which is somehow utilizing the transaction log that is used in the
> transactional replication to let me know what data has changed so that I
can
> call a procedure in the corresponding system to change the data there too.
>
>
>
> Several things to note about the legacy system:
>
> 1.. It utilizes transactional replication to synchronize data among
> several copies of the database
> 2.. It already has performance issues so would like to add as little
> overhead as possible
> 3.. It utilizes nested transactions heavily
>
> Does anyone have any ideas about how I could go about synchronizing the
two
> systems, or whether or not there is a third party tool that could help me
in
> the above scenario?
>
>
>
> Any help or pointers would be greatly appreciated.
>
>
>
> Regards,
>
>
>
> Robert
>
>
|
|
|
|
|