February 22, 2013 at 3:36 am
Hi All
I am going to introduce SSRS to develop reports , now I need to know what are the prerequisites / Requirements and access required to make simple SSRS report developed, running and make it available by end user?
If I start from scratch, according to me, I need access to SSRS reporting services, Report manager and Report server URL , and reporting services configuration tool to achieve the above? Is there any thing else I need to have or am missing , please input your comments.
March 5, 2013 at 5:10 pm
meghna.bhargav (2/22/2013)
Hi AllI am going to introduce SSRS to develop reports , now I need to know what are the prerequisites / Requirements and access required to make simple SSRS report developed, running and make it available by end user?
If I start from scratch, according to me, I need access to SSRS reporting services, Report manager and Report server URL , and reporting services configuration tool to achieve the above? Is there any thing else I need to have or am missing , please input your comments.
I recommend carefully reading the install instructions for SSRS. You should only need to run the configuration tool once initially when you are setting up your environment.
Creating another special domain user, e.g. "reportuser" is also helpful because in the report server configuration tool you can set this user to be used for running unattended reports.
Helpful tips:
Having a good Active Directory setup with all your users in appropriate groups will make your life easier when defining access to reports. Using windows authentication is the recommended way to provide access, but not on an individual level if you can avoid it because that is a maintenance headache. Defining security groups will allow you to grant access for those groups at the folder level in report manager. Individual report access can be defined too but I recommend sticking to folder level because it's easier to maintain. Domain security groups are also good for sharepoint access, user policies and even .NET application security and provides consitency across your environment.
Reporting services uses datasource connection objects that are stored in report manager which can contain embedded credentials. The worst thing I have seen is people using sQL Server's sa user in these connection objects just because it's easy to do. The ideal here is to use windows authentication again and users will pass through their credetials to the datasource. Again the ideal is if you have the appropriate groups set up on your SQL server with the right roles, then you don't need to manage access at the individual user level. It makes your enterprise IT policy simple if in order to grant access to reports that all you need to do is add someone to a group in Active directory - of course these map to the groups you have predefined access for on report manager. If you can't do that for whatever reason then the second best option is to use the reportusers@domain.com as embedded credentials I mentioned above. The next best option is to use sql authentication, but you really should avoid that.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply