Enterprise manager times out prematurely on some queries and the maximum setting for timeout threshold seems to be 30000 ms. I have been told this is a bug (not being able to increase the timeout threshold). Any fix?
Do you mean the actual driver setting for the card? I am on a token ring network for the first time in my life and not sure what or where stuff is. The Olicom card setup does not have any reference to duplex, isn't that ethernet?
IN any case, the ODBC timeouts occur locally to the database using EM.
There is a Technet article I found acknowledging that the max of 30000 ms is a bug, but they say they have no fix other than to run all queries in Query Analyzer!
You need network administrator to change the setteing of network adapter. Before it, try just append a 100 records to SQL linked table. If still get time out error, I am sure that it is network performance problem. I have the same case.
I don't think it's a network performance problem, though a slow network would aggravate it. Some queries just take more than 30 seconds. I'm having the same problem running the Enterprise Manager locally on the server and remotely.
And, I'm pretty sure the problem is in Enterprise Manager becaues I have no problem accessing the views from the Query Analyzer, or a remote MS Access applition with the ODBC time out jacked up to cover the query time.
My query time out is set to the default 0 (infinite) and also 0 in the Tools/Options/Connections/Query Time Out text box in the Enterprise Manager. 0 is not documented as infinite here, but 300 seconds doesn't help a 75 second query. It still times out in 30.
I think that the 30,000 ms referred to the discriminator for saving query results on long queries in the ODBC settings. I don't believe that this is a time out.
I've also searched the Microsoft SQL Server Knowledge Base to no avail. Any ideas?
I did find a TechNet note on this and it is one of the famous "Microsoft acknowledges that this is an issue, but at this time there is no fix.".
Sorry, I don't have the article #, but they give the wonderful suggestion that you don't run queries using EM, but use query analyzer!!! They also mention the 30,000 ms setting and it is somehow related.
No fix for this in SP3 either as I have tried. If I find the Tech Net reference, I will post it. At least I know I am not the only one with the problem.
I ordered 2000 in hopes that this is fixxed (even though I know chances are something equally ugly will raise its head in 2000). When I get it loaded I will let everyone know.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.