SQL Server Performance Forum – Threads Archive

Distributed App, Technology Question ?

Hi Everyone. I am trying to get ideas for a possible technology we could use for a certain scenario. In a nutshell we want to run a distributed application at hundred of remote stores, anything that happens at the store must be propagated to a central sort of hub server. Now i have already thought about replication, but maintaining replcation across hundreds or even a thousand remote instances would be a nightmare.Also the App must work offline so if no link exists the app must still work and sort of reliably queue the transactions. So i been experimenting with service broker, to write transactions, that then queue on to service broker to the central hub, therefore enabling remote stores to continue to work even if no comms exist between the remote app and the hub. But also maintaining service broker at hundred of remote sites would be an administrative nightmare. So basically i am trying to pick your brains out there, can anyone reccomend a possible technology out there worth looking at for this solution , the simpler the better, even if it simply pushes database somewhere , must it must be reliable and queue like in case comms are down. I am not focussing on microsoft either, whatever i dont care. Any reccomendations just to look into would be greatly appreciated. Thanx

Just digging old thread [<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ />], did you get any solution for this problem. <hr noshade size="1">Satya SKJ Microsoft SQL Server MVP Contributing Editor & Forums Moderator http://www.SQL-Server-Performance.Com</a> <center>This posting is provided AS IS with no rights for the sake of knowledge sharing.</center>

<blockquote id="quote">quote:<hr height="1" noshade id="quote">Originally posted by [email protected] Also the App must work offline so if no link exists the app must still work and sort of reliably queue the transactions. <hr height="1" noshade id="quote"></blockquote id="quote"> I favour Service broker in this scenario.. if you have 100 or 1000+ instances whatever solution you apply, would require complicated administration processes..but yes service broker would be more reliable and closely meeting requirments.. http://www.codeproject.com/dotnet/IntroServiceBroker.asp</a> Although, I can not say final ‘yes’ to service broker, because there can be lot more dependencies involved in your application architecture. But yes you can start with a test scenario having less number of remote sites. Another good must read link for "Building Reliable, Asynchronous Database Applications Using Service Broker" http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5_SrvBrk.asp</a> [<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ />] Deepak Kumar MVP, MCDBA – SQL Server Disclaimer: This post is provided as is with no rights & warranty for accuracy, for the sake of knowledge sharing only.

]]>