SQL Server load in idle time is 5% total processor time or less, with the occasional spike (which is normal because of other integrations). I was trying to stay away from the Legacy connector because I read they will be removing it in a future release. But can't hurt to try it right now to see if it will make a difference. I will try that as well. Here's a picture of PerfMon for the duration of the report. The highlighted line is the CPU on the SQL Server. It spikes during the "Request data" stage when running the report in MR.
↧