As you begin developing reports for deployment to a Report Server, what security considerations need to be taken into account in order to grant users access to run a report.Securing Reporting Services can be a daunting task for a rookie report developer.
When using SQL Server Reporting Services, there is no reason that all of your reports, regardless of sensitivity, can't be stored in a single report server.
ABOUT THE AUTHOR Eric Johnson (MCSE, MCITP: Database Administrator, MCSD) is co-founder of Consortio Services and the primary Database Technologies Consultant.
SQL Server Reporting Services (SSRS) is an extremely handy tool in the SQL Server 2005 suite.
You can use it to easily create, deploy and manage reports for your entire organization.
He has delivered numerous SQL Server training classes and webcasts as well as presentations at national technology conferences.
He is president of the Colorado Springs SQL Server Users Group.
All you have to do now is name the role, give it a description, and then select all the tasks you want this role to be able to perform. (Click on image for enlarged view.) To assign users to this newly created role, go back to the site settings screen and select Configure Site-wide Security.
This will open the System Role Assignments screen and you can simply click New Role Assignment to add new Windows users or groups to one of your SSRS system-level roles.
This will open the System Roles page: To create a new role, click the New Role button.
This will open the New System Role page, shown in the screenshot.
If these roles aren't enough, you can build additional roles and assign users any combination of the item-level tasks we just looked at.