Permissions needed for the metadata and warehouse to use MicroStrategy products

To access MicroStrategy product we need some specific permissions. Without proper permission, we will not able to check and execute the reports and use the specific options if required.

Below are the few permission related to metadata and warehouse that will required for MicroStrategy user to use MicroStrategy products.

For the metadata, the permissions are with respect to the user account that Intelligence Server is setup to connect to the metadata (or if using a 2-tier project source, the user account that Developer is setup to connect to the metadata).

 For the warehouse, the permissions are with respect to the user account that is specified in the Database Connection -> Database Login to the warehouse.

These are the required permissions to create the Metadata, History List and Statistics repositories:

• Tables: Select, Insert, Update, Create, Drop, Delete
• Indexes: Create, Drop
• Triggers: Create, Drop
• Functions: Create, Execute
• Packages: Create
• Procedures: Create, Execute

For the metadata below are the required permissions.

1. The Select, Insert, and Update permissions are required.
2.  Intermediate tables are created in the metadata for recursive search queries, which requires Create and Drop permissions as well.
3.  Updating the schema requires the Delete permission.

For the data warehouse below are the required permission.

1. The Select, Create, Insert, and Drop permissions are required. This is because intermediate tables are created in the warehouse. One could argue that Administrators could do away with giving the user account the Drop privilege, by setting the Very Large Database (VLDB) property, 'Drop Temp Table Method' to 'Do Nothing'. However, this would entail that the administrator would manually have to drop intermediate tables every day and it would be a cumbersome option to have. Therefore, it would be preferable to give the user account Drop permission as well. If the intermediate tables are created as true temporary tables (an option set through the VLDB property, 'Intermediate Table Type' and assuming the database supports the same), then these tables are automatically dropped at the end of the session.
2. The user account does not need Update and Delete permissions against the warehouse.

When creating statistics repositories, we do also create views (the queries executed can be seen through the Configuration Wizard, when creating a new statistics repository) and therefore the user will need the following permissions:

• Create : It will consists of  Create Table/Index/Sequence/Procedure/View/Trigger

• Drop : It will required for dropping the old tables if exists.

Hope this would helps  ! . Please comments if there is any more things.