There's a tool in SQL that lets you see what is going on. It was mentioned very recently in a similar thread. Identify users running large reports
When a member of staff runs off a big report, it makes SIMS unusable for anyone else at the time. SQLServ.exe CPU usage gets pegged to 50% (Dual core, so it's only using one)
Is there anything I can do to stop this from happening? or at least find out who's running the big report and slap them. It's really. REALLY annoying >.<
Thanks - I'll take a look. is there no way to stop users from doing this full stop tho? I have no issue with them running said reports, but I think it's insane from a design point of view that a single user is able to hog all the CPU resources.
Capita's response will be throw more resources at it. Microsoft will tell you (or rather Capita) to build a data warehouse, or get a MIS with proper reporting. I'm sure I know what @GREED will say.
I would say setup a spare server as a backup then get them to use that, but the best guide I've seen about setting that up was from Bob Carswell and I doubt he'll be updating that. Also users can get confused and end up working in the copy that's going to get overwritten later that day. Guess the best option would be to educate them in scheduling reports.
We've had issues with reports recently too, more noticeable since the Summer upgrade.
Two things I'd suggest, 1 try editing the report and saving again, sometimes has made a difference to use for whatever reason, whether it just refreshes some details. 2. Capita sent us the reindexing patch through to run again which has helped again generally, so might be worth getting hold of that too.
There are currently 1 users browsing this thread. (0 members and 1 guests)