L
Lloyd Dupont
I don't know replication well yet in an upcoming product we will develop we
will meet a problem I wonder if replication could solve although I have some
doubt.
there is 1 master DB
and different slave DBs
all with an Item table.
my purpose is to have a copy of all item in each slave DBs in the big master
DB.
is the replication a solution?
or does it sync just 1 DB with an other DB ?
my main concern / doubt is about identity column.
while an INSERT INTO Item xxx VALUES xxx might be replciated well, I will
generate different value for my ID (Identity) column and I won't know which
is which.....
IS there any build-in / generally accpeted solution for that ?
I'm thinking, otherwise, to build my own synchronization code (which would
require to add in each table 2 index/colum: LocationId, SyncDate) and write
my own webservices/sql to do it..
any tips? links? similar experiences?
will meet a problem I wonder if replication could solve although I have some
doubt.
there is 1 master DB
and different slave DBs
all with an Item table.
my purpose is to have a copy of all item in each slave DBs in the big master
DB.
is the replication a solution?
or does it sync just 1 DB with an other DB ?
my main concern / doubt is about identity column.
while an INSERT INTO Item xxx VALUES xxx might be replciated well, I will
generate different value for my ID (Identity) column and I won't know which
is which.....
IS there any build-in / generally accpeted solution for that ?
I'm thinking, otherwise, to build my own synchronization code (which would
require to add in each table 2 index/colum: LocationId, SyncDate) and write
my own webservices/sql to do it..
any tips? links? similar experiences?