3

I'm a programmer/DBA by accident and we're running SQL Server 2005 with Performance Dashboard for basic monitoring. The server has been up for a few weeks and now we can't drill into certain reports. Is there any way to reset these reports without a complete reboot?

edit: I bet the error message would help.

I get this when I drill into the CPU graph: Error: Difference of two datetime columns caused overflow at runtime.

2 Answers 2

4

What are the errors your getting?

Have you tried re-running the dashboard set-up script?

One approach you could try is to close SSMS and then delete reports.xml from %userprofile%\Application Data\microsoft\Microsoft SQL Server\90\Tools\Shell which clears your custom report data I think - see http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/780bac33-663a-4532-a23c-fb10564cb328

Then make sure that it's the performance_dashboard_main that you open - the other reports are accessed from it.

2
  • It's not a custom report and I did try re-running the setup script. I read somewhere there was a 24 day limit to some reports due to a int overflow when doing date math. Now I can't find where I read it.
    – Mike L
    Jun 18, 2009 at 18:10
  • 1
    There's a fix for that error on this blog which mentions the 24 day limit blogs.msdn.com/sqlrem/archive/2007/03/07/…
    – Chris W
    Jun 19, 2009 at 8:33
1

go to system database >> msdb >> programmability >> Stored procedure >> usp_Main_GetSessionInfo

sum(convert(bigint, datediff(ms, login_time, getdate()))) - sum(convert(bigint,s.total_elapsed_time)) as idle_connection_time,

replace above by below

sum(convert(bigint, CAST ( DATEDIFF ( minute, login_time, getdate()) AS BIGINT)*60000 + DATEDIFF ( millisecond, DATEADD ( minute, DATEDIFF ( minute, login_time, getdate() ), login_time ),getdate() ))) - sum(convert(bigint, s.total_elapsed_time)) as idle_connection_time,

1

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .