 | |
Table replication question
comp.databases.ms-sqlserver comp.databases.ms-sqlserver
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Table replication question -
02-19-2008
, 01:47 AM
#2
| |||
| |||
|
|
I have two identical databases - with one exception: they have different names (etc database1 and databse2), but their structure is completely same. Is it possible to replicate one table between those databases? |
do what to achieve?
Which version on SQL Server?
Are the databases on the same server?
Do you need the replication to be syncronous, or can you accept a lag?
Do you want to replicate data in both directions?
Are the tables victims to massive concurrent updating?
Sorry for asking all these questions, but there are several options,
but not all may be suitable to you.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#3
| |||
| |||
|
|
zgb (zgb23 (AT) vip (DOT) hr) writes: I have two identical databases - with one exception: they have different names (etc database1 and databse2), but their structure is completely same. Is it possible to replicate one table between those databases? Could you give more details about your requirements? What more exactly do what to achieve? Which version on SQL Server? Are the databases on the same server? Do you need the replication to be syncronous, or can you accept a lag? Do you want to replicate data in both directions? Are the tables victims to massive concurrent updating? Sorry for asking all these questions, but there are several options, but not all may be suitable to you. SQL server is version 2005. |
I will simplify configuration:
I have two pairs of master - backup servers, each pair is replicated in
both directions (merge replication). Let's call them master1, backup1
and master2, backup2.
Also I have two rooms, room1 (here are master1 and backup1) and room2
(here are master2 and backup2). Databases on all four servers have
completely same structure, but databases in room1 have name db1, in
room2 db2. Between two rooms there is no any replication, imagine two
systems that are working completely separated, each in his own room.
What I want to do is establish replication between two rooms but in way
to replicate only one table - I'll call it myTable. As databases are
identical I have myTable on all four servers. Problem are names of
databases (on room level). Also complete replication inside room1 and
inside room2 must remain. Unfortunately I can't rename databases.
So, result must be: both direction replicated databases on master1 and
backup1, both direction replicated databases on master2 and backup2,
myTable replicated on all four servers.
Table is not victim of massive concurrent updating.
#4
| |||
| |||
|
|
I will simplify configuration: I have two pairs of master - backup servers, each pair is replicated in both directions (merge replication). Let's call them master1, backup1 and master2, backup2. Also I have two rooms, room1 (here are master1 and backup1) and room2 (here are master2 and backup2). Databases on all four servers have completely same structure, but databases in room1 have name db1, in room2 db2. Between two rooms there is no any replication, imagine two systems that are working completely separated, each in his own room. What I want to do is establish replication between two rooms but in way to replicate only one table - I'll call it myTable. As databases are identical I have myTable on all four servers. Problem are names of databases (on room level). Also complete replication inside room1 and inside room2 must remain. Unfortunately I can't rename databases. So, result must be: both direction replicated databases on master1 and backup1, both direction replicated databases on master2 and backup2, myTable replicated on all four servers. |
suggestions to the first question, becase they would all be off.
I would suggest that you post your question to
microsoft.public.sqlserver.replication, where I believe some people
with very good experience of replication hangs out.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
#5
| |||
| |||
|
|
zgb (zgb23 (AT) vip (DOT) hr) writes: I will simplify configuration: I have two pairs of master - backup servers, each pair is replicated in both directions (merge replication). Let's call them master1, backup1 and master2, backup2. Also I have two rooms, room1 (here are master1 and backup1) and room2 (here are master2 and backup2). Databases on all four servers have completely same structure, but databases in room1 have name db1, in room2 db2. Between two rooms there is no any replication, imagine two systems that are working completely separated, each in his own room. What I want to do is establish replication between two rooms but in way to replicate only one table - I'll call it myTable. As databases are identical I have myTable on all four servers. Problem are names of databases (on room level). Also complete replication inside room1 and inside room2 must remain. Unfortunately I can't rename databases. So, result must be: both direction replicated databases on master1 and backup1, both direction replicated databases on master2 and backup2, myTable replicated on all four servers. Thanks for the details! I am very glad that I did not offer any suggestions to the first question, becase they would all be off. I would suggest that you post your question to microsoft.public.sqlserver.replication, where I believe some people with very good experience of replication hangs out. I will try at suggested group, thank you for your effort, you are very kind. |
Regards
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.