October 28, 2005 at 7:21 am
Okay, I'll take a look at these suggestions and get back to you.
Also, I ran the trace while while running perfom monitor and came up with 3 queries that took about 2 to 3 minutes to run. But there where about 10 of each query running at the same time. I ran the queries again this morning at around 7am when our CPU is only at about 15-20%. At this time each query took a short time to run. The longest one may have run for about 19secs. So I'm taking the more users....the longer it takes for this huge queries to run.
During my research I read that Pages/sex should be between 0 and 20. Why is it that one day it was at o and the next day it was at avg 86.
I did notice that the SQL server logs are enormous. I have to cycle them every day. Maybe twice a day. They're so huge that they just hang when I try to open them.
The other thing is the network admin and I view this server thru a VPN. Unfortunately he knows less than I do. 🙁
October 28, 2005 at 7:27 am
Oh yeah..forgot. We are using stored procs and huge views that are not indexed.
October 28, 2005 at 8:14 am
Could you post the stored procedures or the query that takes a long time to run?
Seems it could use some review.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply