Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
avinashily
Starting Member
10 Posts |
Posted - 2010-12-08 : 05:52:18
|
hi all,we are having sql server 2005 database running backend and asp.net application runing in front end for accessing the database to view and make modifications to the database. at times users report that there is a error while accessing the application and pulling the data from the server "timeout expired prior to completion of operation or ther server is not responding." i have searched through many forums and i could not get the exact reason why this error is occuring. the server on which sql server 2005 is ruuning has 3gb ram and ldf and mdf files are stored on SAN box. please provide the solution for this issue. |
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-12-08 : 06:04:25
|
I'm guessing that it's taking too long to get a response from the server.Not really possible to give more than that with the info given.Is it all users running things at that time or just a few. How often does it happen. Is there any bolcking on the system at that time. Are there heavy processes going on at that time (reports maybe). Do the queries actually get through to the database. When things succeed how long do they take - is it close to the timeout.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
avinashily
Starting Member
10 Posts |
Posted - 2010-12-08 : 06:28:46
|
hi nigelrivett,there are no blocking on the system at that time. i have observed the cpu usage and found that it was normal. i have run the trace and found that duration of the completion of batch and statement are around 1000 ms, for few queries but i think apart from that i could not get any information as to why i am getting the error. it would be great if you can suggest me the troubleshooting the issue. |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-12-08 : 06:42:39
|
If the max time taken for a query is 1 second and this is less tan the timeout (and the timeout is for a single query) then it can't be a query performance issue. It must be something not database connected (like the application failing to process the resultset) or failing to action the query.How long is it before the application issues the timeout after trying to execute the query.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
avinashily
Starting Member
10 Posts |
Posted - 2010-12-08 : 06:52:20
|
hi nigelrivettsome times it issues the timeout expired in the application around 3 minutes and some times it even takes more than 10 minutes to issue the timeout expired. i have found few procedures which were taking 6 sec but, i think even this is below the remote query timeout in configuration settings. users are really fed up of this issue as it is effecting the production. can you just guide me how i can get to the root cause of the issue and solve it. |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-12-08 : 06:58:49
|
Given that the tieout is sometimes 3 minutes and sometimes 10 minutes and nothing on the database takes longer than a second it doesn't sound like it's database related.Thik you'll have to delve into the application to find out what it's doing and maybe try to replicate on a test system.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|