We have 12 production servers with roughly the same configuration, same data structure and same reports on SQL 2005. On one server, the reports render very slowly. For example, one report will execute on most servers in less than 30 seconds, but on our problem server, it takes at least 35 minutes. Looking in the ExecutionLog shows that 98% of the time is spent processing. This particular report has 5 subreports. All the stored procedures run in less than a second. Our take is that it's not SQL, it's the reporting engine. We have tried running these reports from another server by changing the data source to point at the problem server. The reports run great in that scenario. It's something on that server. We have tried everything. Reindexed all tables. Republished all the reports. Nothing in the event logs. Nothing in the report logs. We even went so far as to completely reinstall SQL. Nothing seems to make a difference. I have read all the forum postings about slow performance and nothing seems to make a difference at all. I've run all Windows updates and SQL Server SP4. I've checked all the security and WINS and DNS settings. Can anyone offer any help at all?

Hi Jon, "Looking in the ExecutionLog shows that 98% of the time is spent processing." Could you post the TimeDataRetrieval,TimeProcessing,TimeRendering here from the problem and healthy servers? so that we can compare them. On the problem server, have other reports the same issue? please also check whether any antivirus program running on the server, if yes, uninstall it and then retry to see if the issue goes away. thanks, Jerry

We have been on a Microsoft support call for the past 3 days looking at this problem. So far, we have no solution. To answer your questions, other reports on this server exhibit similar slowness. Today, as part of the support call, we tried uninstalling antivirus, but it didn't help. Problem server InstanceName ReportID UserName RequestType Format Parameters TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount Server10 870A1037-0CF8-493B-9982-0C3343980E20 xxx 0 HTML4.0 xxx 2/16/11 10:21 AM 2/16/11 10:55 AM 630 1988541 13 1 rsSuccess 31145 1545 Server10 870A1037-0CF8-493B-9982-0C3343980E20 xxx 0 HTML4.0 xxx 2/17/11 7:42 AM 2/17/11 8:16 AM 4652 2029904 13 1 rsSuccess 31144 1565 Server10 870A1037-0CF8-493B-9982-0C3343980E20 xxx 0 HTML4.0 xxx 2/17/11 8:11 AM 2/17/11 8:44 AM 679 2002829 19 1 rsSuccess 31144 1561 Server10 870A1037-0CF8-493B-9982-0C3343980E20 xxx 0 HTML4.0 xxx 2/17/11 8:46 AM 2/17/11 9:19 AM 657 2005328 14 1 rsSuccess 31144 1567 Another server - same report, different data (actually more data) InstanceName ReportID UserName RequestType Format Parameters TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount Server04 436F391A-F71C-441C-B065-C6D23DD25AAF xxx 0 HTML4.0 xxx 3/3/11 2:52 PM 3/3/11 2:53 PM 1063 63348 31 1 rsSuccess 111822 2880 jon b

Microsoft support could not solve the problem last week, so we nuked and paved the server on Friday night. That report now runs in about 15 seconds.jon b

We believe we found the smoking gun. After rebuilding the server, we were re-installing some of the ancillary services and discovered that when we added the agent for Symantec Backup Exec, the reports started running slowly. When we uninstalled it, the reports were back to running quickly. We are currently pursuing this notion.jon b