Had a big project today that consisted of a web interface and SQL Reporting Services. Exactly 9.5 hours after starting we finished the project and oh boy did we have a party configuring the servers during the whole process. If you haven`t used SQL Reporting Services let me start by saying that it is very interesting to say the least. Take a process as easy as generating a dataset from a large stored procedure to bind to a repeater having a nice report-like layout and then complicating that process to the point of insanity by adding role-based security, authentication and a web service or two and you will have had your own introduction to SQL Reporting Services. Maybe I`m full of it? I have only been using SRS for the past week or so and obviously I haven`t become a ninja yet. After getting the hang of it I realize that after the initial introduction it is a pretty fun and powerful tool to use.
Seriously though. As if Web Services weren't complicated enough. Now you have to worry about passing the proper credentials to a remote web service and also having role-based security configured. The fact that SRS is a combination of SQL Server and IIS components makes (at least for me) a frustrating experience at times to configure. This is mostly due to the fact that I haven't had all that much experience with configuring servers and permissions-related issues. I am learning though and look forward to contributing (hopefully) to the SRS community.
Authentication, Role-based Security, and SQL Reporting Services Web Services