|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Sunday, September 25, 2011 6:50 AM
Points: 55,
Visits: 155
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Sunday, August 30, 2009 9:55 PM
Points: 6,
Visits: 27
|
|
why not just use: DECLARE @TEST BIT EXEC @test = SP_TESTLINKEDSERVER [mylinkedservername]
IF @test = 0 BEGIN PRINT 'test failed' END else BEGIN PRINT 'test succeeded' END
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Friday, May 10, 2013 9:59 AM
Points: 264,
Visits: 633
|
|
I agree, sort of. In tests on SQL 2005, seems to me the proc call needs to be in TRY/CATCH else control does not flow down to the PRINT stmts when linked server is not available. But I have not been able to simulate this problem on SQL 2008 R2. Maybe MS have implemented TRY/CATCH internally.
Thanks to the author, though, for bringing light to SP_TESTLINKEDSERVER, it's new for me.
|
|
|
|