It is definitely the sqlserver process chewing up the CPU. I think I now know the cause of the problem. I ran the profiler and found a slow running query,...

Hi Allan,

I've already done a dbreindex and statistics update. I will run the profiler and take a look at the CPU and plan.

Thanks,

Dave

Thanks for the reply. I will ensure MSSQL2000 has max memory available. I don't expect that this is the issue, because (1) I don't have 7 and 2000 running at...

Hi Tim,

No actually. I got busy yesterday, and didn't have a chance to look. I think you may be correct about the statement cache being the issue. My SELECTSs show...

Hi Calvin,

Thanks for the code. I'll take a look.

Dave

Hi Calvin,

I agree but I've been unable to get any data in the MSSQL7 profiler for the Duration, Reads, Writes and CPU columns for statements. The column cells are blank...

Hi Tim,

I will take a look at the query plan, statement caching and stats, and see if this is an issue.

Mark, the issue I think is at a somewhat lower...

It's not in a proc. It is a series of SELECTs wrapped in a BEGIN TRAN/ROLLBACK TRAN.

Dave

Hi Andy,

Yeah, yeah. The app shouldn't be inserting the data and then immediately retrieving it. But that's an app problem to be solved another day.

Nonetheless, Here are some timings using...

Hi hbkdba,

What should I be looking for in particular with the profiler? Running the profiler, I see that the SELECTs being run are identical. The only difference is that for...