Professional SQL Server™ 2005 Programming

17.4. Summary

Reporting Services is new with SQL Server 2005. Just how big of an impact it is going to have in the average SQL Server installation and the average project is yet to be seen. There is definitely a very strong base set of functionality, and using report projects, the sky is the limit in terms of the possibilities. That said, experience tells me that IT departments will resist having a Web server deployed on their SQL Servers (report server doesn't have to be on the relational engine server, but it does add minor install complexity if it isn't). I find they also often resist installations where new functionality (in this case, new reports) can be deployed without their control. Now, lest I sound like an anti-IT bigot, they have some sound reasons to resist such "on-the-fly deployments" — a single poorly structured query or one that is new and may not have sufficient index support can drag a server to its knees in a hurry if it is abused. Your IT department is responsible for keeping that server up and responsive to everyone, so they have a reasonable basis to be skeptical of engines that allow backdoor queries.

All IT concerns aside, Reporting Services is a fine addition that provides developers a new and flexible way to empower end users without requiring a programming class to do it.