Am I correct in assuming that the chart scale in SQL PI (seconds/s) is seconds per session?
Am I correct in assuming that the chart scale in SQL PI (seconds/s) is seconds per session?
I cant seem to add a new topic so I'll ask my question here, Is the time range on the SQL PI screen showing the items based on the time (and time zone) they occurred on the SQL server being monitored…
Don, You have to convert. Some of our servers are in UTC; when they fail and I search the server logs, I have to add 5 from the Foglight error time to get to the right Server log time. On my local terminal…
Hi,
The seonds/s metric is seconds per second. It represents the number of seconds of db workload (cpu usage + wait time) per second (time).
If you had a single CPU instance you would have 3600 seconds of compute available each hour. If you had queries using all of the CPU, it would average 1 second/s
If additional SQL starts waiting on cpu or other resource, that graph starts to climb.
In multi-core servers, you will have "core count" x 3600 seconds available each hour for CPU.
There's also a support KB available here with additional explanations.
Hi,
The seonds/s metric is seconds per second. It represents the number of seconds of db workload (cpu usage + wait time) per second (time).
If you had a single CPU instance you would have 3600 seconds of compute available each hour. If you had queries using all of the CPU, it would average 1 second/s
If additional SQL starts waiting on cpu or other resource, that graph starts to climb.
In multi-core servers, you will have "core count" x 3600 seconds available each hour for CPU.
There's also a support KB available here with additional explanations.
Thank you for the explanation