ThomasH (thomasherskind (AT) gmail (DOT) com) writes:
Quote:
Three physical locations (A, B and C) share the same database. When a
person at location A puts something in the database, it should be
updated for B and C.
My best solution is 1 database at location A, which also has a terminal
server that users from B and C log on to. Voila, the see the same data.
If that's not an option, what's the best solution? |
Certainly solutions where the database is not only logically the same,
but also the physically are very palatable, since introducing replication
raises the level of complexity considerably.
Quote:
We've got lots of small alterations to the data in the course of the
day, so I'm thinking Merge Replication. But we need something like
instant replication... is that feasible? |
Replication is not my game, so I don't know how fast merge replication is.
The alternative would be some custom-built, which may be feasible if only
a small amount of tables are involved. This could with Service Broker.
But it's a not path I would take easily.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx