Saving a report In Reporting Services, you save

Managing reports Remember that managed reports are reports stored on the report server, where they can be stored in folders within the Report Manager. You can add reports to folders, move reports between folders, create new folders, rename old ones, and create folders within other folders, much the same way you d work with folders for your computer s file system in something like Windows Explorer. You publish your data sources to the report server when you deploy your report project; these data sources can be shared among many reports. You control access to such data by using data source connection properties to set the access permissions of a data source. Within Report Manager, you can move shared data sources into their own folder if you so desire. You can also save images used in your reports as resources in your folders, thus providing for easy access and maintenance. Report Manager also allows the administrator to control which users have access to which specific folders. Report Manager also provides access to various report properties that govern how reports will execute (such as scheduled runs or execution frequency), how reports should use the memory cache (cache temporary copy when run, when to expire the cache), how parameters are used (default parameter values, parameter interactivity), report-delivery techniques, and how users will be able to interact with the report content. You can use Report Manager to create snapshots of the report, and you can save report histories so that you can review how the data has changed over a period of time. All these properties provide great control over your managed reporting environment. I describe the capabilities in more detail in Chapter 9. Securing a report Reporting Services has a robust security model. It makes use of a role-based, user-based, and task-based security model to ensure proper permissions are established for access to critical business information. The security model can also be extended, and Microsoft will provide the bits for security model extensions to support proprietary authentication schemes. A role is a way to categorize users into groups based on the way they need to interact with the system and its resources. Users can belong to many roles like content manager, publisher, or browser (of information). User-based security is specific to a specific user in unique aspects of how they interact with the system. Tasks are different functions that a given user can perform. 22 Part I: Just the Basics

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Adult Web Hosting services

Bookmark the permalink.

Comments are closed.