Have you ever noticed one of your SQL Server instances running unusually slowly?
Have you had difficulty quickly identifying what areas could be affecting its performance?
One of our customer support Escalation Engineers, Keith Elmore, specializes in understanding these types of problems. He has worked with customers all over the world on diagnosing their toughest and most critical performance bottlenecks. Keith has put together a set of Reporting Services reports that will help DBAs diagnose potential performance problems. These reports were designed to leverage the new Custom Reports functionality in SQL Server Management Studio (Service Pack 2).
The SQL Server 2005 Performance Dashboard Reports only use Dynamic Management Views and Catalog Views. They do not poll performance counters from the OS, nor do they store a history of your server's performance over time. These are very light-weight reports that will help diagnose performance problems as they are occurring.
I encourage you to check them out. Feel free to comment here with your thoughts and questions.
SQL Server 2005 Performance Dashboard Reports:http://www.microsoft.com/downloads/details.aspx?FamilyId=1D3A4A0D-7E0C-4730-8204-E419218C1EFC&displaylang=en
Paul A. Mestemaker IIProgram ManagerMicrosoft SQL Server Manageability
i have a problem when i click on any blue region in the chart for the SQL CPU utilization on the performance dashboard where you normally would get further infos (reports for the last 15 minutes).
There comes no repport but an Error: Arithmetic overflow error conferting expression to data type datetime.
This happens on two different servers with SQL Server 2005 Enterprise Editions, but all other driil through is functioning. What' s the problem, is it a problem in recent_cpu.rdl or performance_dashboard_main.rdl or in the called stored procedures. Please help, it is a really good tool, but not good when functioning only partly.
Thanks for help
I also have problem when I click on the blue region for the CPU (CPU System Utilization), and it happens on only one server, other servers works fine
An error has occurred during report processing.
Cannot read the next data row for the data set SESSION_REQUEST_ACTIVITY.
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Any ideas how to fix it?
I am facing an error saying ‘Arithmetic overflow error converting expression to data type datetime.’ In data base due to my following query.
Then I tried with cast and convert function too, still I got the error.
where cast(('May 29 2007 6:30:00:000PM' - endtime) as int) >=2
and cast(('May 29 2007 6:30:00:000PM' - endtime) as int)<=3
and datetable_id = 102
order by datetable_id desc
I got this beacause of some bad ‘endtime’ data in datetable for datetable_id 102 : 5465-08-12 12:00:00.000.
But I need to support all type of date here and the table is also huge. So I have this col as indexed.
I thought of to use datediff func here. again I am not sure what will be the performance impact on my query, coz it will diff and convert to int and compare for each of the row.
So can any body suggest how efficiently can i handle this?
as i have wrote before (May 23, 2007) i wasn't able to use the Performance Dashboard because of the described failure. A week later the report functions without changing something. It works fine for some days until 08. June 07, then in the morning i want to look again in the chart for SQL CPU utilization and nothing functions again, but now i get the failure as described from other users, that is: Difference of two datetime columns caused overflow at runtime. I have implemented the fix as described by David, but it doesn't help, i think there must be more bugs in the programming with datetime-conversion etc.
Now again, i am not able to use this fantastic tool.
Does anyone have a fix for this problem? Please help.
In my case it was an inconsistency in the language settings between the web server and SQL server (or SQL server user).
Check that the user you're using to browse the reports has british english as a language.
About the "Arithmetic overflow error converting expression to data type datetime." after clicking the blue-CPU-Line:
This is an conversion error between the main and the recent_cpu report. You can solve this by changing the type of the "WithActivitySince" Parameter from String to DateTime (at the top of the XML file).
I applied the fix as identified above back in May 2007 to my setup.sql script and it was working for a short time. However now I am receiving the same "Difference of two datetime columns caused overflow at runtime." error. I have reloaded the fixed setup.sql script on my box and I continue to get the error. The problem happens when clicking on the CPU utilization graph to see what processes were running on a given server at a specific time.
Can anyone help?
I'm getting the parameter issues mentioned by Ron above. Any help?
Nevermind. Duh...should have read directions. For others...open through the performance_dashboard_main.rdl which supplies params.
The datetime value is days - fractional part is time. 86400000 = 24 * 60 * 60 * 1000 converts days to ms. This should should avoid overflow here and in most cases. I have not tried extreme dates - perhaps the difference won't be in the range of a valid datetime?
CAST(FLOOR(86400000 * CAST(getdate() - login_time as float)) as bigint) -- ms
Microsoft SQL Server 2005 Performance Dashboard Reports предназначен для контроля и получения необходимой
I saw your update. Do you know where I need to do the CAST update? Also when will Microsoft update the Performance Dashboard?
I'm getting the "Difference of two datetime columns caused overflow at runtime" error when trying to drill down into the Blue SQL Server CPU usage on the main dashboard screen. I understand the problem with uptime (server has been up for more than 24 days), datediff, and ms but I'm having some problems tracking down where the change from ms to ss needs to be made for this drill down functionality to work again. I tried a profiler trace, but the only procedure I see executing is the usp_CheckDependencies. After that I just see a bunch of execute_sql statements.
Any help would be appreciated
Any idea if there are any issues while converting from timestamp to big int???
I do where the following change in the datetime difference should be made:
I get the error now on any SQL Server environment where connections have been online for more than a month.
Can someone please help me. Or can you let me know when the Performance Dashboard will be updated?