Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
meristema
Starting Member
8 Posts |
 Posted - 2012-11-27 : 06:12:49
|
| Hello guys,I ask advice, I have 2 SQL Server 2008R2 communicating with each other for only a few procedures for updating tables (snap of the trigger), but only in a way, server A write to table on server B. The goal is to separate the 2 servers so they do not communicate directly, and to do that I thought of an additional database to serve as a bridgehead or intermediary. In practice:Server "A" writes to server "C", server "B" goes to read the data on the server "C" to update their tables.The SQL Server Replication service would be ok in my case, but even if it is a database "C" is NOT read-only?Any feedback is welcomeThanks very muchAndrea |
|
|
srimami
Posting Yak Master
160 Posts |
Posted - 2012-11-27 : 07:07:19
|
| I do not get your complete requirement but you can create linked server between these two and use views to read/fetch/update the tables from respective servers. |
 |
|
|
|
|
|
SQL server replication is the correct choice?