What is the right strategy for replication in this scenario

Last Post 09 Jun 2006 11:08 PM by parhiya. 0 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
parhiya
New Member
New Member

--
09 Jun 2006 11:08 PM
We are running attendance system on SQL Server 2000. In order to reduce traffic on WAN, we are going towards replication. In order to ensure proper working of attendace system, we will have to replicate three tables. The attendance system is based on "time in" and "time out" so that user can "time in" from any terminal and can "time out" from any terminal. So we are planning to use merge replication because sometimes for troubleshooting terminal systems, running attendace, loose connection with the main server. Are we going right?

AT - Attendance Terminal


Main Server
|
|
Subscriber (to AT-1 and AT-2)
|
Distributor (to AT-1 ANT AT-2)
|
Publisher (to AT-1 ANT AT-2)
|
|
--------------------------------------------------------------------------------
| |
| |
AT-1 AT-2
| |
| |
Subscriber (to Main Server) Subscriber (to Main Server)
Distributor (to Main Server) Distributor (to Main Server)
Publisher (to Main Server) Publisher (to Main Server)


Acceptable Use Policy
---