Groups | Search | Server Info | Keyboard shortcuts | Login | Register


Groups > comp.databases.ms-sqlserver > #2242

`sqlcmd' defective by design?

From Anton Shepelev <anton.txt@g{oogle}mail.com>
Newsgroups comp.databases.ms-sqlserver
Subject `sqlcmd' defective by design?
Date 2024-05-13 14:24 +0300
Organization A noiseless patient Spider
Message-ID <20240513142445.206132420c1c47759b78c197@g{oogle}mail.com> (permalink)

Show all headers | View raw


Hello, all (and how many is that?)

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.

____________________
1. <https://learn.microsoft.com/en-us/sql/tools/sqlcmd/sqlcmd-utility>
2. <https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-error-severities>

-- 
()  ascii ribbon campaign -- against html e-mail
/\  www.asciiribbon.org   -- against proprietary attachments

Back to comp.databases.ms-sqlserver | Previous | NextNext in thread | Find similar


Thread

`sqlcmd' defective by design? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-05-13 14:24 +0300
  Re: `sqlcmd' defective by design? Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-05-13 17:32 +0300
  Re: `sqlcmd' defective by design? Erland Sommarskog <esquel@sommarskog.se> - 2024-05-13 22:44 +0200
    Re: `sqlcmd' defective by design? Anton Shepelev <anton.txt@gmail.moc> - 2024-05-14 01:05 +0300
      Re: `sqlcmd' defective by design? Erland Sommarskog <esquel@sommarskog.se> - 2024-05-14 21:23 +0200

csiph-web