Re: Table Synchronization across databases on the same server

Triggers will add to the overhead of the application which uses DB1. You
should be able to use log shipping or transactional replication for what you
are trying to do.

With log shipping your db2 database will go offline as you synchronize and
you will be unable to update tables on db2. With transactional replication
you can only replicate tables with pks.

HTH

--
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
<chandrub78@xxxxxxxxx> wrote in message
news:1130358745.662470.143440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hello Everyone
> 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.
> I read about Triggers,Maintenance Jobs and Replication but not sure
> which would suffice our needs.Are there any recommendations on how this
> could be carried out? Any suggestion would be welcome.
>
> Thanks
> chandra
>


.

Relevant Pages

  • Re: Table Synchronization across databases on the same server
    ... > inhouse application which maintains a transactional database, DB2 also ... Since the DB1 is frequently updated the ... Anyway, I'm not very good at replication myself, I would encourage you to ...
    (comp.databases.ms-sqlserver)
  • 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)
  • Re: Multi-Master Replication
    ... From db2 we would like to replicate only changes concerning two tables to db1. ... Do I need to create two replication groups. ... I'd suggest you take a look a Streams, ...
    (comp.databases.oracle.server)
  • Re: Eine Tabelle in der Datenbank 1 mit Formular aus Datenbank 2 f
    ... DB2 dient zur Erfassung der Mitarbeiter und der Schulung, DB1 dient der ... da gibt es eben bereits das Formular mit den Stammdaten. ... Stammdatentabelle DB2 auf, geht in das Formular und legt den MA an, schließt ...
    (microsoft.public.de.access)
Quantcast