Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > comp.databases.ms-sqlserver > #2246
| From | Erland Sommarskog <esquel@sommarskog.se> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Re: `sqlcmd' defective by design? |
| Date | 2024-05-14 21:23 +0200 |
| Organization | Erland Sommarskog |
| Message-ID | <XnsB172D989BE32CYazorman@127.0.0.1> (permalink) |
| References | <20240513142445.206132420c1c47759b78c197@g{oogle}mail.com> <XnsB171E75C59835Yazorman@127.0.0.1> <20240514010559.361a252eb7de61db42f229d1@gmail.moc> |
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.
Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Find similar
`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