Path: csiph.com!news.swapon.de!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: `sqlcmd' defective by design? Date: Tue, 14 May 2024 21:23:05 +0200 Organization: Erland Sommarskog Lines: 18 Message-ID: References: <20240513142445.206132420c1c47759b78c197@g{oogle}mail.com> <20240514010559.361a252eb7de61db42f229d1@gmail.moc> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 14 May 2024 21:23:05 +0200 (CEST) Injection-Info: dont-email.me; posting-host="63c41009b687972af2c073eeb75e084e"; logging-data="379352"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+97vWGWe6bGsP/NADkYOkd" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:kSEmvE1S7N7Af144PuXj3CPXpXc= Xref: csiph.com comp.databases.ms-sqlserver:2246 Anton Shepelev (anton.txt@gmail.moc) writes: > Erland Sommarskog: > >> 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? > > Nothing of the sort. It is the usual timeout that occurs > when the command or script executed via `sqlcmd' is taking > longer than the number of seconds speciffied in the -t > command-line parameter. In my test, I was executing: > > echo WAITFOR DELAY '00:00:10' | sqlcmd -S mytesty -V 11 -r -b -t 8 > I see. They have a new SQLCMD, written in go. It behaves the same way, but you could file an issue on https://github.com/microsoft/go-sqlcmd.