I had a very slow power pivot report and wanted to identify which query was taking the time so I enabled the tracing
![clip_image001[5]](http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-45-98-metablogapi/1351.clip_5F00_image0015_5F00_thumb_5F00_5E307788.jpg "clip_image001[5]")
The trace is generated by default in your desktop, the trace is a SQL Profiler trace so you will need to use SQL Profiler to open it.
When is open, organize the columns by eventclass
![clip_image002[4]](http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-45-98-metablogapi/1856.clip_5F00_image0024_5F00_thumb_5F00_3DA937D6.png "clip_image002[4]")
Now filter the eventSubclass to 25 which is execute SQL
![clip_image003[4]](http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-45-98-metablogapi/4118.clip_5F00_image0034_5F00_thumb_5F00_3FE5C092.png "clip_image003[4]")
Now you can focus in Progress Report End event and check what TSQL is taking longer
![clip_image004[4]](http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-45-98-metablogapi/4846.clip_5F00_image0044_5F00_thumb_5F00_1B54330E.png "clip_image004[4]")