We are looking at migrating exisiting (around 500) reports from Actuate to SSRS. Actuate has a feature built into the product known as Page-level security by which different users can be given access to different pages on the same report. We need to find out if the same can be implemented using SSRS. A few more points to consider here are that reports will be run from History snapshots and accessed on demand. Also there are large number of users (10000+ grouped in 400-450 different roles). So breaking the reports based on UserID etc and creating separate snapshots will be nightmare from maintenance perspective. Large report volume is another concern. Is there some way to implement the same in SSRS and what are the limitations/concerns we need to keep in mind? Thanks.

I'm not familiar with the product you mentioned but you can look into subreports and providing "page level" access that way. Either that or internal links in the reports that lead to new reports and security will stop them there if they are not in the browser group. You can look into modifying the code behind functionality to validate the users account but that would be quite a bit of work involved in changing the reports vs controlling report level security. I would highly recommend testing that method out in a simple report before taking on the task of modifying your security model with SSRS.Ted Krueger Blog on lessthandot.com @onpnt on twitter Please click the Mark as Answer button if a post solves your problem!

Hi SomaG, I understand your issue as we also use Actuate. As of yet, I haven't found a way to duplicate what Actuate does regarding Page-level security when you wish to generate once instead of on demand. I have converted reports to SSRS, but not using the snapshot method. For on-demand reports, I use the UserID parameter in the query as a means of securing data. To somewhat duplicate the roles, I have created a user table with specific information like plant and department. Bill

Thanks for your response Bill. Unfortunately on-demand is not an option here as the reports are huge in size (snapshots sometimes may reach size of 8GB) with complicated query and we will only have access to the report data source at off-peak hours. We were considering creating a overall snapshot and applying filters on it for individual user (UserID based filter like you have mentioned) but I am reading in the net that is not a very stable solution, specially given our number of users and volume of report. Thanks, Soma

Hi SomaG, There is no need for you to create so many snapshoot, just create one snapshott, then filter this report with UserID. Then different users could only see the record belong to them. This link supply some information about process large report, http://msdn.microsoft.com/en-us/library/ms159638.aspx There are some Configuration Recommendations, Rendering Recommendations and Deployment and Distribution Recommendations, you could click this link to get a reference. For more information about filter please see http://msdn.microsoft.com/en-us/library/dd255287.aspx Thanks,Challen Fu [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Thanks Challen. We were thinking of the same approach but are concerned about the performance due to snapshot size and high number of users. Will follow the recommendations in the link and give it a try. Thanks again, Soma

Hi SomaG ... Were you able to work this issue out? and if so, how?.