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 |
|
nlocklin
Yak Posting Veteran
69 Posts |
 Posted - 2002-10-11 : 16:12:31
|
| I have an active server page that calls a stored procedure in SQL Server 2000. The stored procedure has been taking a few seconds to execute and has steadily been increasing as the data in the database increases. It's up to 55 seconds now (almost enough that it's not feasible to use for a web page), and I've started getting the following error message in the ASP: "Microsoft OLE DB Provider for SQL Server error '80004005' Unspecified error"I tried messing with the Server.ScriptTimeout setting in ASP, but I guess that only has to do with the loading time for the page, as opposed to any database connection. Does anyone know how can I resolve this error?Thanks in advance!--"It's not that I'm lazy... it's that I just don't care." |
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-10-11 : 16:28:57
|
| The error that you are getting does not sound like a timeout error. But I think you are asking about the query timeout, and the way to control that is through the CommandTimeout property via the ado connection object.*************************Someone done told you wrong! |
 |
|
|
M.E.
Aged Yak Warrior
539 Posts |
Posted - 2002-10-11 : 17:31:04
|
| I think thats the error you will get if it times out or is killed on the MSSQL server side isn't it? If you kill process on a query you get an unspecified error like that-----------------------SQL isn't just a hobby, It's an addiction |
|
|
|
Lavos
Posting Yak Master
200 Posts |
Posted - 2002-10-12 : 02:08:02
|
| Hmmm, I have no idea what error that could be. I'm assuming you are using ADO, are there any other messages in the connection.Errors collection? Is the server logging anything like the thread being selected as the victim to be killed when a deadlock is detected? Have you used SQL Profiler to see the messages being passed back and forth?Personally, I'd be more concerned about the procedure taking more time. Is it *just* data increasing, or has usage also been increasing? Does the execution plan for the stored procedure show table scans being performed? Execution plans can help you learn a lot about how your code is performing. I've swapped the placement of columns in an index when I saw the server was constantly rebuilding it in queries. For that matter, is the data fragmented across pages? Are there lots of locks in the system?----------------------"O Theos mou! Echo ten labrida en te mou kephale!" |
|
|
|
|
|
|
Unspecified error in ASP