Strategy Companion Corporation

- 1 -

Configure AS Cube and Database Visibility

Background Many users are new to the world of SQL Server Analysis Services (SSAS or AS); therefore, one of the most frequently asked questions is how to setup database visibility, cube visibility, and privilege control through the use of AS roles. This document is intended to provide a step-by-step setup for two common scenarios, and will hopefully provide a starting point for users to follow. This document will also show how to control the AS database and cube visibility through AS roles, while using a single Analyzer Data Source within the Multi-Company version of Analyzer, also referred to as Analyzer SaaS. The following example uses the SaaS version of Analyzer; however, the same principle can be applied to any version of Analyzer since the AS database and cube access privilege and visibility are totally controlled by the AS role, and Analyzer simply displays whatever AS has returned.

Environment AD Server: “m2n-eAD” IIS and AS on two different machines Basic Authentication is used Two companies, since we are using the Multi-Company version of Analyzer: CompanyA, CompanyB Each company will have a Report Designer – CompanyAadmin, CompanyBadmin

Scenario 1 – To show how individual cube access can be controlled by the AS role (You

may assign a cube to be viewed only by a specific company.)

1. AS is installed on M2n-e. There are several databases within this AS. Currently, no role has been defined in any of the databases. We are using SQL2005 x64 9.00.3042.00.

Strategy Companion Corporation

- 2 -

2. Refer to the below image, where we are using the database “OLAP-Jacky01” as an example.

There are 4 cubes contained within, none of which have a role defined.

3. At this point, user CompanyAadmin is unable to view the categories circled in red. This is standard behavior from AS.

Strategy Companion Corporation

- 3 -

4. Now add “Role01” to AS (sample database), Membership = “M2N-AD\CompanyAAdmin”.

Cubes = “Internet Sales” only has the Read privilege.

Strategy Companion Corporation

- 4 -

5. Now create a new Analyzer report. As expected, the user can now see the “OLAP-Jacky01” Database and the “Internet Sales” Cube.

Strategy Companion Corporation

- 5 -

6. Now switch to user CompanyBadmin’s account to create a new report. Again, we see no database or cube listed since this user has not been added to the AS role.

7. Now create a new role (“Role02”) in AS using the same database (“Olap-Jacky01”). Define the following privileges:

Strategy Companion Corporation

- 6 -

Strategy Companion Corporation

- 7 -

8. Use “m2n-ead\CompanyBAdmin” and enter Analyzer to create a new report. Now the user can see the “OLAP-Jacky01” Database and the “Jacky Test DB” Cube

This proves that individual cube access can be controlled by the AS role and that each cube can be assigned to a different company.

Strategy Companion Corporation

- 8 -

Scenario 2 – To show how database visibility can also be controlled by the AS role

9. Continue from the previous step. Delete “Role02” and switch to the “Adventure Works DW” database.

10. Now create “Role03” in the Adventure Works DW Database. Define the following privileges.

Strategy Companion Corporation

- 9 -

11. Now enter Analyzer again and create a new report using CompanyBadmin as the user. Where previously shown, “Olap-Jacky01” has been removed and replaced with “Adventure Works DW”.

This proves that database visibility can also be controlled by the AS role.

Note: If you wish to run the same tests, please make sure that the user you choose is not the local administrator of the AS server; otherwise, the AS local administrator will have full access to all of the AS database and cubes by default.