this morning i has some problems in monitoring one of our server with Idera Check.
As suggested I updated to the new version of Idera SQL Check, but still i have the following error when I try to connect
“Arithmetic overflow error for data type tinyint, value = 256.”
Can you give me some hits of how to solve this problem?
I have the same issue, but not with every server I try to monitor. I’m also very interested in a solution.
Antonella and Frank,
It would be best to review logs to determine what the underlying issue is. I would recommend contacting firstname.lastname@example.org regarding this issue so that the freeware department can track this issue with you directly.
I have this same error, well similar. my number after value is different. As suggested I sent a note to the address listed….
Arithmetic overflow error for data type tinyint, value = 1025
As others have noted, it’s not on every server — but I wonder from those that are getting the error…. similar setups?
SQL server 2008 (note NOT r2)
VM installation, 32gb
This appears to be related to the number of processes on the server exceeding limitation of tinyint (255).
Thank you all for bringing this to our attention. We have investigated and fixed this issue and placed an updated version of SQL Check on our website.
You can download it again from this link.
This new version also fixes the erratic bubble behavior other users have been describing in other posts.
Thanks for your continued support!
Please change this:
CAST((@@CPU_BUSY + @@IO_BUSY + @@IDLE) AS BIGINT) as TotalCPU,
,CAST(@@CPU_BUSY AS BIGINT) + CAST(@@IO_BUSY AS BIGINT) + CAST(@@IDLE AS BIGINT) AS TotalCPU
and the error is gone.
Thank you! I added this fix to our issue tracking system for a potential future release.