home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.ms-sqlserver      Notorious Rube Goldberg contraption      19,505 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 18,939 of 19,505   
   migurus to Lutz   
   Re: pitfalls of accessing linked server    
   21 Aug 13 17:21:52   
   
   From: migurus@yahoo.com   
      
   On Wednesday, August 21, 2013 1:02:34 AM UTC-7, Lutz wrote:   
   > You can test the connection to your remote server   
   >   
   >   
   >   
   > EXEC @bTest = sys.sp_testlinkedserver N'remoteserver'   
      
   Thank you.   
      
   I tried it against a linked server while the remote box was down to simulate   
   WAN down situation and it takes 50 sec to come back with messages   
      
   OLE DB provider "SQLNCLI10" for linked server "REMOTEBOX" returned message   
   "Login timeout expired".   
   etc...   
      
   That long wait is not acceptable for application, I'd like to know if we can   
   possibly decrease that 50 seconds to 5 seconds, in our environment it is   
   reasonable to conclude that link is down if connection is not obtained within   
   5 sec.   
      
   I tried   
   EXEC master.dbo.sp_serveroption @server=N'REMOTEBOX', @optname=N'connect   
   timeout', @optvalue=N'5'   
   EXEC master.dbo.sp_serveroption @server=N'REMOTEBOX', @optname=N'query   
   timeout', @optvalue=N'5'   
      
   but that had no effect on the long wait time for login.   
      
   Are there any ways to do what I am trying to achieve?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca