Just spoke to 120 people and lived

Cisco Unified CCX Historical Reports Problems

Cisco Unified CCX Historical Reports – printing problems
In order to print a report to a network printer you must set the hrcConfig file to
UseSharedMemory = 1
Default setting is 0

If your DB is using Windows NT Authentication you need set hrcConfig file to connection method = 1
Default setting is 0 which is mixed mode

If you ever need to restore your UCCX CRA_DB and create reports that match Cisco Unified CCX Historical Reports here’s the short cut.
set the hrcConfig file LogLevel = 3 , ( logLevel = 3 then debug messages, warnings and errors)
Launch Cisco Unified CCX Historical Reports on a client, select and run a report
Find the CiscoAppReports0 file by default the file is located in
C:\Program Files\Cisco UCCX Historical Reports\logs\(Machine name)_CiscoAppReports0
You will see the stored procedure that was executed in the file; it will look something like this:
Exec db_cra.dbo.sp_agent_summary '$StartDate', '$EndDate', $SortBy, N'$ResourceGroup', N'$AgentName', N'$SkillName', N'$TeamName', $TopRatio, $BottomRatio, $TopHold, $BottomHold, $TopTalk, $BottomTalk, $TopWrap, $BottomWrap, $TopHandle, $BottomHandle 117: 3/15/2010 3:44:09 PM %CHC-LOG_SUBFAC-7-UNK:DB Layer Current Query=Exec db_cra.dbo.sp_agent_summary '03/14/2010 12:00:00 AM', '03/15/2010 12:00:00 AM', 0, N'NULL
Copy and paste in the management studio run against the DB of the server.
Execute the query and the results will match what would have been available in Cisco Unified CCX Historical Reports
The above scenario is great if you are running UCCX using MSDE and the db purges after 2gb or if you have just migrated and do not want to import historical data.
Additionally you can prove or disprove the application is having problems not the database.
Just make sure you have a backup scheduled to run daily so you can restore prior to running the report.