June 2, 2008 at 10:19 am
Need and idea or place to look to implement the above..
I am considering a 3rd party messaging (A on machine A sends transaction to B on machine B for update and the the other way around).
I thought about App on machine A writing directly via connection to machine B database and machine B updating machine A database...
is there a better way or other approaches
thanks
ben
June 2, 2008 at 10:58 am
replication does this. bidirectional transactional handles this fine.
Messaging is preferred, but if you're doing this, why not use Service Broker? Why a third party?
Having the updates occur means that you might have two phase commit. This means that if one server has issues, you can't update the second. Better to decouple with replication or service broker.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
June 2, 2008 at 12:26 pm
thank you...
i did not know about service broker... it is exactly what i was looking for
thanks again
ben
June 2, 2008 at 12:51 pm
You can use Merge replication too...
http://www.sqlmag.com/Article/ArticleID/50532/sql_server_50532.html
MohammedU
Microsoft SQL Server MVP
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply