November 4, 2016 at 9:58 am
Hello,
I am not in any way an SQL admin and certainly not a tuning specialist, but I feel there must be some low hanging fruit here to rule out?
I recently began a position sharing tasks with another network admin. We handle everything from top to bottom. The company uses 2 main programs each running on their own SQL server. One program is particularly problematic, with reported random freezing and slowness by users.
Memory:
I already noticed the memory was as issue as it was using the paging file from time to time.
We added the maximum the server would take and now that appears to be fine.
Processor:
I do not see much processor usage at all, but I did set parallelism to 8 to match advice I read online.
Disk:
We were getting 100% disk usage, but I traced that down to ill timed SQL backups and resolved that.
Datto backups slow things down a touch every 2 hours for a few minutes, could the Datto agents themselves be an issue on a SQL server?
The server was originally setup wrong. 4 discs are setup in a raid array and C D E, are all part of the same physical RAID.
C, D and E are partitioned with the same underlying hardware. This leave the OS, SQL, tempdb, logs and DB's all running on the same physical discs.
We can add 2 more discs in a mirror to potentially move the logs off to the new drive, but would this help a lot or maybe not much?
The DB itself is about 560 GB - could this be an issue? I do not want to suggest a new server if we can optimize something we are missing.
My first step in monitoring was an average disk queue length.
It is showing consistent leaks over 40 and even areas of 100% for 15 seconds at a time.
This appears to show a level that is too high, correct?
November 4, 2016 at 2:17 pm
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply