• Thanks for the reply.

    Yes, I have corrected the math error.

    Yes, I can successfully run the the sql in SSMS. Now... what I see SQL Profiler when I run performance_dashboard_main.rdl on the SQL 2008 R2 server where this is working correctly is that it calls the 5 main procs:

    -usp_Main_GetRequestInfo

    -usp_Main_GetCPUHistory

    -usp_Main_GetSessionInfo

    -usp_Main_GetRequestWaits

    -usp_Main_GetMiscInfo

    Then, when I click the blue CPU Utilization line, there are no SQL calls that occur at all - so I'm presuming that is is using cached data from the initial calls to populate the "Recent CPU Consumption" report. This is the part that generates the data source error on the other 2008 r2 server. Since I'm using the same .rdl files and identical procs on both servers, I would expect to get the same results. Very peculiar.