7 SQL Servers working seperately need joining.

Microsoft SQL Server 2000
I am working in small bank with 6 branches and a Headquarter. Each Branch is running a SQL server with 8 workstation connected to it over LAN. At each day end branches closes their work send their data to headquarter in an export file format. Where it is imported to Headquarter Sql Server database through an email. Now bank wants to connect its branches directly over a private network to Headquarter. But the branches should not connect each other directly. Bank wants that branches connect each other through the central ( Headquarter ). and customer can make transactions across the branches. For example a customer of bank A in city A can draw its money through bank B in City B. Then in this case to avoid any mistake the customer record bank A in city A should be instantly available to the staff at Bank B in City B. the one anwer to this scenario is that the branches maintain a Central Database Server at Headquarter and connect it directly. But banks do not want this answer. As central database server is unavailble or network link to central server at headquarter of a branch is down then the branches cannot work. The bank do not want to change its current scenario but only want to allow cross transactions among the branches online to facilitate the its customer. Kindly suggest the solution that how the sqL servers are placed and confiured to communicate in such a way. Hoping soonest soluion.... Thanks Naveed Khan

Answer Wiki

Thanks. We'll let you know when a new response is added.

I think in your case SQL replication is very usefull.. you need to choose merge replication from snashotp,transactional etc..
go throught the SQL replication funcationlity and implement it. it will help you.
Best Luck.
Mehul Patel

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Denny Cherry
    I agree. SQL Server Replication will be what you want to use. You will need to be very careful when setting this up, as doing it incorrectly will cause you major problems and could cause you to loose customer data. If thought out and impimpented correctly it can be setup and done without loosing any data.
    69,065 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: