After updating from NT 8 to NT 10 we stated having trouble with the server thread count maxing out and the server locking up. Whenever this would happen I ran a query on the MSSQL server to list the currently active queries. Their would always be 2 queries that where "AWAITING COMMAND". These weren't always the same queries, but were always one that were run frequently. I'm just guessing that it is fairly random when these lock ups happen.
Looking through NT code I found that it used the SetSqlTimeout procedure, and I tried using that in some of my custom code. The result was fewer lockups, but also 'Set Lock_Timeout -1' would be one, or both of the queries that are "AWAITING COMMAND" when the server would lock up.
It looks as if NT generated code hasn't be "AWAITING COMMAND", however that may be because my own hand code runs much more often. I use Access:[Filename] in my custom code rather the the NT methods. IT would take a lot of work to switch them all over, and I don't know of a NT method to use a SQL dummy file for custom queries.
I have no idea why a NT update would cause this problem, but it was the only significant change we made at the time. I haven't yet been able to replicate the problem in a test environment.
We are still using Clarion 8 and that may be contributing to the problem, however as I said when we were on NT 8 our server was vary stable.
My driver options are "/BUSYHANDLING=2 /MULTIPLEACTIVERESULTSETS=TRUE /TRUSTEDCONNECTION=TRUE"
Thank You
Matthew
Topic: SQL Errors after NT 10 Upbrade (Read 4192 times)