A few days ago I posted about the SQL Server 2005 Performance Dashboard Reports. In my post I commented about two know issues with the report. While looking for an answer I ran into this link http://dbaonline.wordpress.com/2008/07/10/troubleshooting-sql-2005-performance-dashboard. In that link the author address three problems/ Issues and gives the solution to all three.
Issue 1 – Difference of two datetime columns caused overflow at runtime.
Issue 2 – Blue Zone Problem (Server is running for 24 or more days).
Issue 3 – Arithmetic overflow error converting expression to data type datetime.
I found many blogs, but this one gave me the most detailed information on how to solve the issues. I will try to go even further in details so that it will be even easier to change the issues number 2 and 3.
Issue 2 – Blue Zone Problem (Server is running for 24 or more days):
If you just copy paste the solution from the link you may get some errors so I decide to make clear which changes you need to make to enable the report to run.
After inserting that script in the “recent_cpu.rdl” report you may need to do the following changes to avoid errors in the report:
You can delete the following lines:
Line 3274 “– s.host_name,”
Line 3282 “ — s.logical_reads as session_logical_reads,”
Line 3283 “– r.logical_reads as request_logical_reads,”
Line 3292 “– Steve: Fixes begin here:”
Line 3307 “– Steve: Fixes end here”
Make sure you add the quotes on “@WithActivitySince”, line 3311.
Issue 3 – Arithmetic overflow error converting expression to data type datetime:
Issue number three can be solve by editing the same report “recent_cpu.rdl” in line 12 the parameter “WithActivitySince” is defined and in line 13 the data type is defined as a “string”, that have to be changed to “DateTime”.