Which strategy should you use?

You design a Business Intelligence (BI) solution by using SQL Server 2008. You plan to create a SQL Server 2008 Reporting Services (SSRS) solution. Developers generate random reports against a data source that contains 200 tables. Power users generate random reports against four of the 200 tables. You need to design a strategy for the SSRS solution to meet the following requirements:
-Uses minimum amount of development effort.
-Provides two sets of tables in SSRS to the developers group and the power users group.

Which strategy should you use?

You design a Business Intelligence (BI) solution by using SQL Server 2008. You plan to create a SQL Server 2008 Reporting Services (SSRS) solution. Developers generate random reports against a data source that contains 200 tables. Power users generate random reports against four of the 200 tables. You need to design a strategy for the SSRS solution to meet the following requirements:
-Uses minimum amount of development effort.
-Provides two sets of tables in SSRS to the developers group and the power users group.

Which strategy should you use?

A.
Create two Report Builder models.
Include the four frequently used tables in the first model and all the tables in the second model.

B.
Create a Report Builder model by using all the tables.
Create a perspective within the model to use only the four frequently used tables.

C.
Create a Report Builder model by using all the tables.
Create two folders.
Place the four frequently used tables in the first folder and the remaining tables in the second folder.

D.
Create two Data Source Views.
Include all the tables in one Data Source View and the four frequently used tables in the other Data Source View.
Create two Report Builder models so that each model uses one of the Data Source Views.

Explanation:
Tip: "development effort … developers group" = "a Report Builder model … a perspective"

Creating a Report Model
Like reports, Report Models are created in the Business Intelligence Development Studio and then deployed to a report server. Unlike reports, Report Models can have
security rights assigned to different pieces of their structure to provide the fine-grained security that is often required in ad hoc reporting situations. We use the Report Model Wizard to create the Report Model, and then do some manual tweaking to make it more usable. We then deploy the Report Model to the report server. Finally, we set security within the model itself.
A perspective is a subset of the information in the model. Usually, a perspective coincides with a particular job or work area within an organization. If a plus sign is to the left of the model, the model contains one or more perspectives. Click the plus sign to view the perspectives. If you select one of these perspectives as the data source for your report, only the entities in that perspective will be available to your report. Because perspectives reduce the number of entities you have to look through to find the data you need on your report, it is usually a good idea to choose a perspective, rather than using the entire Report Model.
(McGraw-Hill – Delivering Business Intelligence with Microsoft SQL Server 2008 (2009))

http://msdn.microsoft.com/en-us/library/ms345316.aspx
For models that contain many subject areas, for example, Sales, Manufacturing, and Supply data, it might be helpful to Report Builder users if you create perspectives of the model.
A perspective is a sub-set of a model. Creating perspectives can make navigating through the contents of the model easier for your model users. I



Leave a Reply 0

Your email address will not be published. Required fields are marked *