Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,480 of 19,505    |
|    Erland Sommarskog to Anton Shepelev    |
|    Re: `sqlcmd' defective by design?    |
|    14 May 24 21:23:05    |
      From: esquel@sommarskog.se              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.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca