From: esquel@sommarskog.se   
      
   migurus (migurus@yahoo.com) writes:   
   >   
   >> you should test that your code behaves as expected. For a simple   
   >> procedure   
   >>   
   >> like this one, I would recommend that you open a direct connection   
   >>   
   >> from the application instead.   
   >>   
   >>   
   >   
   > Unfortunately we can not modify app   
   >   
      
   Why not? Apparently you can fiddle with it so much that you can add a new   
   stored procedures.   
      
   Of course, if this is a third-party application for which you don't have the   
   source code, I see that it is difficult. But does the license for the   
   application permit you to put tables on remote servers?   
      
   The point is that the solution you are looking at will give you headache,   
   and I pointed you to a simpler solution.   
      
   Two more options:   
      
   1) Rather than using a linked server, use a CLR stored procedure where you   
   habe more control over the connection string and set a short connection   
   timeout, and where you more easily can trap errors.   
      
   2) Replicate the table from the remote server to the local server.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Books Online for SQL Server 2005 at   
   http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx   
   Books Online for SQL Server 2000 at   
   http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)