Post reply

Error Handling in Merge Replication Custom Conflict Resolver

  • January 4, 2005 at 3:58 am

    #535740

    This is an 'old' problem - when a Transact SQL statement refers to a non-existing or non-responding remote server, it aborts hard. AFAIK, there's not much you can do about it, it's how things currently work.

    One way to go around it I've seen is to set up either the query itself, or a 'ping' query in a job-fashion as separate steps. The step after the one trying the remote access can then decide if it was successful or not, and in any case, flow can continue even though the remote access failed.

    Not entirely sure how feasible it would be in a merge replication scenario though...

    /Kenneth

  • January 4, 2005 at 8:12 am

    #535785

    have a look at this thread. There is a DMO solution to detect if the connectivity to the server is good

    http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=8&messageid=152697#bm152737


    * Noel

  • January 5, 2005 at 2:17 am

    #535920

    Personally I'd never touch the sp_OAxx procs, they're just too much risk crashing the entire server imo...

    Granted, this is a personal opinion only

    On the other hand, you can easily enough get the same end result the 'batch' way by using, say xp_cmdshell and have  isql/osql query the server with an output file specified, then parse that file for the results.

    There are many ways to skin this cat, though none currently as lean as one would like.

    /Kenneth

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

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