Hi,
Is it somehow possible to merge two databases with identical schema? We
have two or more sites whose data are supposed to be merged into the
main database at night. Data at each site is unrelated to the data at
other sites. Each site has limited bandwidth (satellite). Some sites
may even lack network, requiring the data to be transported on a DVD-R
from site to main office.
regards,
Knut Eldhuset
You might want to roll your own solution using checksum's or use Red-Gate
software's data compare.
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
"Knut Eldhuset" <knut.eldhuset@.gmail.com> wrote in message
news:1115636465.617229.291830@.g14g2000cwa.googlegr oups.com...
> Hi,
> Is it somehow possible to merge two databases with identical schema? We
> have two or more sites whose data are supposed to be merged into the
> main database at night. Data at each site is unrelated to the data at
> other sites. Each site has limited bandwidth (satellite). Some sites
> may even lack network, requiring the data to be transported on a DVD-R
> from site to main office.
> regards,
> Knut Eldhuset
>
Showing posts with label schema. Show all posts
Showing posts with label schema. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Merge always deletes inserts on subscriber
Hey.
Table1 replicates to table3
Table2, just another table with the same schema as Table1 and 3.
In my setup, I created a copy table, copied 66 rows from table1 on publisher
to table2 on subscriber and deleted all 66 rows. The changes were replicated
to the subscriber to Table2(66 deletes made). Now i insert all 66 rows from
Table2 to table3 on the subscriber side. The change should have gone to
publisher. Instead, the inserts get deleted on the subscriber... Why would
SQL do this?
The inserts done later should be taken as new changes on subscriber and
should be replicated to publisher, isn't it?
Forgot to add, it took it as a conflict between pub and sub and for me, by
default, the pub wins... The problem with this is though, it shouldn't be a
conflict. I've ADDED these rows right now and ONLY to the subscriber...
Any clues.
Table1 replicates to table3
Table2, just another table with the same schema as Table1 and 3.
In my setup, I created a copy table, copied 66 rows from table1 on publisher
to table2 on subscriber and deleted all 66 rows. The changes were replicated
to the subscriber to Table2(66 deletes made). Now i insert all 66 rows from
Table2 to table3 on the subscriber side. The change should have gone to
publisher. Instead, the inserts get deleted on the subscriber... Why would
SQL do this?
The inserts done later should be taken as new changes on subscriber and
should be replicated to publisher, isn't it?
Forgot to add, it took it as a conflict between pub and sub and for me, by
default, the pub wins... The problem with this is though, it shouldn't be a
conflict. I've ADDED these rows right now and ONLY to the subscriber...
Any clues.
Subscribe to:
Posts (Atom)