• I've seen that, and had trouble getting it to work for SQL Server 2008. Never put much effort into it. In general, I find SQL Server Reporting Services, and thereby any tool built on top of its infrastructure, to be poorly designed and ill-thought out. For example, the index report built-in to SSMS 2008 is stupid and doesn't take into account internal vs. external fragmentation! Ugh. And it is proprietary so you can't open the code that wrote the report and change it. How dumb. And it doesn't have workflow integrated, for push-button resolution of problems.

    It is only a matter of time (20 years? :)) before Microsoft wakes up, buys Tableau Software (the best reporting tool out there), and re-engineers SSIS to work more like Google Refine (a free tool not currently geared toward massive ETL, but could be).

    We will have to wait a long time, primarily due to reporting zombies who are satisfied with the status quo.

    My current pet project is to build a performance dashboard with PowerShell that automatically launches, in sync, PerfMon traces and SQLserver server-side traces simultaneously and gathers the data and reports it in a useful manner. It was inspired by dealing with how stupid SQL Server Management Studio is. I tried talking to the guys who designed SSMS and SMO and basically got thumbs-in-ears replies.

    As a software developer, I hate looking at the tools DBAs torture themselves with and know that it is still the best they have available.