October 10, 2008 at 12:31 pm
Is the problem reproducible?
Can you get a trace to see what is actually being executed?
This kind of error can be returned if, for example, you are trying to retrieve a column by name, but the recordset returned does not contain a column with that name. (Hence my question about the trace).
October 10, 2008 at 4:05 pm
rbarryyoung (10/10/2008)
tendayit (10/10/2008)
I added the SET NOCOUNT ON line as someone was saying that it missing was causing the problem.You may need to move the corresponding SET NOCOUNT OFF to right before the EXEC(...) statement.
Though I thought that ADO solved all of those SET NOCOUNT problems that DAO and RDO had.
As I recall - NOCOUNT was off by default in ADO connection. There was a way to turn it back on however......
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
October 11, 2008 at 4:54 am
I made the NOCOUNT change, restarted the server because machines were still slow. %disk time on the server was rocketing before the shutdown. Users went back on and they did not get a problem. This might be, in all fairness, because there were now fewer users on the system as others had gone home. Today the system is not being used to full capacity and i haven't heard of any problems.
1. The procedure i have put on this forum searches for the person to view. There are others that will summarize his financial details, get address info, get id info etc, before the details of that person are displayed on the screen. Some use the SET NOCOUNT ON feature, others don't. Does that mean that i have to put the line in all procedures?
2. Was the MatterSearch procedure error in your opinion responsible for the call centre application hanging and causing high %disk times?
3. I have noticed when trouble rises that the Available memory counter value will be around 450 say. When you restart the server and let people work, the counter will have be sitting on say 890. Users won't complain. After a day or 2, the value drops and can reach 450. Disk activity will be high. Does the server need more memory as it might be reaching a threshold where it now has to start using the disk?
4. I will try to set up a trace to see what really happens when the problem starts. I will have to force this one through because in the past when i set a trace for 10 mins on the server, users would complain that performance is slow. Would setting up the trace on my machine which would point to the server use my machines resources alone and not hamper server performance like if i was doing the trace on the server?
Viewing 3 posts - 31 through 32 (of 32 total)
You must be logged in to reply to this topic. Login to reply