Re: Table Synchronization across databases on the same server



(chandrub78@xxxxxxxxx) writes:
> We have a third party tool which maintains its own custom
> database,DB1 on SQL Server 2000 on Server A (Windows 2000). We built an
> inhouse application which maintains a transactional database, DB2 also
> on Server A derived from DB1. Since the DB1 is frequently updated the
> synchronisation between the databases is currently maintained by using
> views in DB2 which pulls in all the required data from across tables in
> DB1.
> But we found that the cost of employing views, referencing tables
> across databases has made the inhouse application slower and so as a
> apparent performance tuning measure we plan to maintain a subset of
> data(for a specific time period) from DB1 in actual tables with same
> schema in our transactional database DB2. But since the tables in DB1
> are frequently updated during the day we are required to the
> synchronise the corresponding tables in DB2 with their counterparts in
> DB1. The only constraint in this synchronization being that the third
> party custom database,DB1 cannot not be subjected to any changes (like
> creation of triggers) as it is maintained by a different group of
> personnel.

Hm, wonder if transactional replication can be used here? Normally, when
you replicate a table, you replicate it all. Here you only want some
data to be replicated. But you should be able to set up filter for this,
I believe.

Anyway, I'm not very good at replication myself, I would encourage you to
pursue this in microsoft.public.sqlserver.replication.


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

.



Relevant Pages

  • Table Synchronization across databases on the same server
    ... inhouse application which maintains a transactional database, DB2 also ... Since the DB1 is frequently updated the ...
    (comp.databases.ms-sqlserver)
  • Table Synchronization across databases on the same server
    ... inhouse application which maintains a transactional database, DB2 also ... Since the DB1 is frequently updated the ...
    (microsoft.public.sqlserver.replication)
  • Re: Table Synchronization across databases on the same server
    ... Triggers will add to the overhead of the application which uses DB1. ... should be able to use log shipping or transactional replication for what you ... you will be unable to update tables on db2. ...
    (microsoft.public.sqlserver.replication)
  • how to configure one-way merge replication?
    ... database to another database. ... i set up a merge replication - DB1 is the ... The subscriber is pulling from DB1. ... Instead i want to just pull from DB1 into DB2. ...
    (microsoft.public.sqlserver.replication)
  • Transactional replication: Deadlock issue
    ... I have a replication setup like ... replication, it shows that there is some sort of deadlock situation ... copying the data from DB1 to DB2(as reinitializing from scratch will ... erase the data in DB2 and also DB3) create a new subscription at DB2. ...
    (microsoft.public.sqlserver.replication)