Report Builder Usage in the Business
Hello all, My company recently built out a 2008R2 instance of Reporting Services (no sharepoint integration). Previously we used 2005 and did not use report builder. As the functionality around 3.0 report builder is much greater I'd like to roll it out to end users. I'm interested in your experiences in rolling out the tool at your own company. Here are some questions 1. Do you only allow users to create reports and store them in their user folders? 2. Do you allow users to create dataset / shared data sources, etc.? Subscriptions? Snapshots? 3. How did you approach sharing of reports within a department? For instance, if members of the finance department are creating reports, do you allow them to publish the reports in a shared locations for other finance employee to see? My concern revolves around having a process in place by which users can publish reports to a wider audience. I've considered assigning and training a department 'super user' who would filter reports that would go to a 'production' folder. Or perhaps this should be a member of IT? Security of sensitive data is also an issue. I'd like to guard against an end user being able to open up sensitive info to anyone they choose. Thanks!
October 22nd, 2010 6:38pm

Hi, For non-technical users, we still suggest them use Report Builder 1.0 rather than 3.0, which is for power user to build reports. You can grant individual subscription permission to non-technical users for creating their own reports' subscription/snapshot. thanks, Jerry
Free Windows Admin Tool Kit Click here and download it now
October 25th, 2010 9:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics