urgent help in this senario - SQL Server Forums

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.

All Forums

SQL Server 2005 Forums

Replication (2005)

urgent help in this senario

Author

Topic

engola2008
Starting Member

1 Post

Posted - 2009-11-26 : 18:13:16

i have an issue in a replication scenario,i need help
aheadquarter of a company has sql server2005 server,and it has three branches ,each branches has it's own server, each branch has about 10 users,all are networked by internet with the HQ,any change in the hq affects the three servers and viceverse of course ,the most important thing is the speed of extracting the information at the user of every branch so i want to know

1-what type of replication to be used in this case,and how can i configure sql server in this case in details as possible.in two cases
first ,if i want the replicated data done by agents at the end of the day for example
second ,if i want the replicated data done at the moment.

(btw the first scenario of that case was that there was only one server at hq and the branches was with no server,every user connects the hq server using the application,so the performance and the speed of the application was so slow and bad)

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-11-27 : 01:11:44

Why is this urgent? Production doesn't seem to be down. Late on your homework?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."

krishnarajeesh
Yak Posting Veteran

67 Posts

Posted - 2009-11-27 : 13:37:11

Hello,

Its all depends on the business needs.

You may try Transactional with updatable subscriptions with immediate updating. (Example: Could work best in ATM bank scenarios) In this case if two subscribers update the same row at the same time, only 1 which reaches and get acknowledgement from publisher first complets its part of updating the row. The same row will be then updated in the second subscriber. The second subscriber update will start now.

There should be a direct connection between publisher & subscribers here since the subsciber updates publisher with out going through a distibutor. Also network bandwidth matters here.

Note : Microsoft says that this feature will be removed in future versions.

Thanks,
Krishna Rajeesh
www.SQLServer.in
Blogs.SQLServer.in

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources