Notifications
Clear all
Topic starter
I was wondering how people troubleshoot CPS slowness? for example, if you suspect a user is running a huge report, how can you find out what they are running and who is running it? if you suspect the sql server is the issue, what query/commands do you use? if you suspect the terminal server, what do you look for? I usually check the memory, harddrive, and cpu usage. They seem the same whether CPS is runnig normal or slow.
Any tips/trick would be appreciated. Thanks.
Posted : June 10, 2013 1:25 am
You can first check the task manager on the server that your SQL Server is running on to make sure it is SQL that is the cause. Then you can run Activity Monitor on the SQL server to get an overview of what's going on in SQL.
If we don't find anything here, we usually have to restart the server that is running SQL.
Posted : June 10, 2013 1:46 am
Topic starter
I always check the task manager and activity monitor but never really noticed anything. is there something i'm looking for in the activity monitor?
Posted : June 10, 2013 2:00 am
If the task manager on the server isn't showing anything, then it's not SQL giving you slowness. You're bottle-necking somewhere else. The server will show 100% CPU usage and/or 100% memory usage when SQL is your bottle-neck.
When looking at the Activity Monitor, I look for processes taking up a lot of memory and also the Recent Expensive Queries can give you an idea of what was ran recently that might have slowed things down.
Posted : June 10, 2013 2:08 am
I had a ton of issues awhile back, here are some things you can do.
1. Open up SQL Manager, run an analyzer and see if you can see some major spikes on the CPU column. This will tell you user and query that is being executed.
2. You can also run a report from SQL that explains what queries are utilizing the CPU the most.
3. Another way is to ask everyone who runs reports. Then take all of those reports in the evenign or off hours, run them one by one and see what spikes the CPU the most. Then modify that report so it does not perform porly.
4. Last, always check to make sure you have enough memory, disk space, and are utilizing your server to the max.
If you need any help feel free to contact me.
George
Posted : June 26, 2013 3:30 am
