From: esquel@sommarskog.se   
      
   Anton Shepelev (anton.txt@g{oogle}mail.com) writes:   
   > I have a nasty problem in my automation batch scripts that   
   > invoke `sqlcmd`[1]: whatever I try, I cannot cause it to   
   > terminate with an error level in case of a timeout.  The   
   > parameters `-V1 -b' do not help a wee whit.  The article on   
   > error severities[2] says:   
   >   
   >   For compatibility reasons, the Database Engine converts   
   >   severity 10 to severity 0 before returning the error   
   >   information to the calling application.   
   >   
   > This alone sounds crazy, but the apparent inabilty to   
   > override this illogical behavior makes `sqlcmd' incurably   
   > broken. Please, tell me I am wrong.   
   >   
      
   What sort of timeout are we talking about? I guess this is something   
   that involves a linked server - or how would you else get a timeout   
   with SQLCMD?   
      
   There are situations when query timeouts on calls to stored procedures   
   on linked server only results in an informational message. I've   
   written about it here:   
   https://www.sommarskog.se/error_handling/Appendix1.html#querytimeout   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)