April 1, 2003 at 2:17 pm
I am having several lastwaittype networkio.
The application is running the same query. And locks up all the other users. It is always the same query which is a simple select statement. But the application with the waittype of networkio has to be killed to free up the locks.
I have checked network bandwith, network cards and tried too different servers
April 1, 2003 at 3:58 pm
I wrote an article on waitstats. It's at
http://www.sqlservercentral.com/columnists/ckirkwood/wait_types.asp
With what you describe, it sounds like your app is making many many calls to this select statement. Is it wrapped in a cursor? Is it transferring gigs of data? Give us more info....
April 2, 2003 at 8:00 am
Actually that is what i thought too, but the particular app only uses the select statement
once and locks up. The database it is on is only .5 gb altogether. It does have a like '%1232%' which is an issue but there are 1000 users using the same app and select statement. Only a couple of times a day does it lock.
quote:
I wrote an article on waitstats. It's athttp://www.sqlservercentral.com/columnists/ckirkwood/wait_types.asp
With what you describe, it sounds like your app is making many many calls to this select statement. Is it wrapped in a cursor? Is it transferring gigs of data? Give us more info....
April 2, 2003 at 9:46 am
In that case, I would say you have another problem, possibly with concurrency, and are seeing its simptoms here as well. Trace back just prior to the networkio waits, and see what is occurring there. Profile it for a while if you need to, but I bet you find something else going on prior to the waits your seeing that is the actual cause of them.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply