Post reply

decoupling systems

  • November 20, 2009 at 5:35 am

    #216974

    Hi We have 2 sqlservers that are linked with one pushing information to the other. Seems like a tightly coupled solution to me. I'd rather change this to a loosley coupled solution, but am not sure on the options. We have a low tolerance to latency within our company so the solution has to take this into consideration

    Thanks guys

  • November 20, 2009 at 5:49 am

    #1082132

    It sounds like a job for Service Broker.

    It's a little bit tough to get it started, but once it's runnning, it's running...


    Lutz
    A pessimist is an optimist with experience.

    How to get fast answers to your question[/url]
    How to post performance related questions[/url]
    Links for Tally Table [/url] , Cross Tabs [/url] and Dynamic Cross Tabs [/url], Delimited Split Function[/url]

  • November 20, 2009 at 5:54 am

    #1082137

    oops forgot to mention we are using sqlserver 2000

  • November 20, 2009 at 8:51 am

    #1082290

    If latency is an issue, replication works well. It can tolerate failures pretty well. One of the draw backs is that sometimes in 2000, replication will stop when one of the servers fails, and you will need to recreate a snapshot, which is time consuming. The other one is that each table needs a valid primary key, or SQL will add one when creating the destination database, which can wreak havoc on a poorly coded front end application (SELECT * FROM MyTable will fail sending data to an app).

    Hope this helps.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply