September 18, 2002 at 8:46 am
Hello. I am building a system for client using SQL Server 2000. The client has a main site and 4 child sites spread across the world. One of the possible solutions we have is to store a main Database at the home site and then replicate the database down to 4 local site's servers for use. The second, simplier option is to just have the 4 sites connect directly to main DB via the WAN. The Replcation would only be one-way, basically being pushed down to the child sites.
It would EXTREMELY helpful if you guys could give me a nice, detailed list of Pros and Cons to replication using SQL Server OR maybe point me to a book or website that would have this information.
September 18, 2002 at 2:35 pm
One con is "complexity". Replication isnt rocket science, but it does add a layer to things. Another is licensing and hardware. You'll have to buy more of each for your subscribers probably. A third is depending on the size of your data snapshots may be difficult to transmit. Other than that transactional replication is easy enough to use and will let your users query locally. That should provide faster response and less traffic on your WAN. Even if you need to do updates you can handle transparently by enabling immediately updating subscribers.
Andy
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply