Security Model for Analysis Services - Microsoft SQL Server 2008 Analysis Services - page 722

</Members>
</Role>
</ObjectDefinition>
</Alter>

Then, you send the DDL statement in Listing 35.4 to create a CubePermission object and
to grant Read access to the BudgetCubeUsers Database role.

LISTING 35.4

DDL to Create a CubePermission Object

<Alter AllowCreate=”true” ObjectExpansion=”ObjectProperties”
➥ xmlns=”http://schemas.microsoft.com/analysisservices/2003/engine”>
<Object>
<DatabaseID>FoodMart 2008</DatabaseID>
<CubeID>Budget</CubeID>
<CubePermissionID>CubePermission</CubePermissionID>
</Object>
<ObjectDefinition>
<CubePermission xmlns:xsd=”http://www.w3.org/2001/XMLSchema”
➥ xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<ID>CubePermission</ID>
<Name>CubePermission</Name>
<RoleID>Role</RoleID>
<Read>Allowed</Read>
<ReadSourceData>None</ReadSourceData>
</CubePermission>
</ObjectDefinition>
</Alter>

Defining Object Permissions

The Permission object has a set of properties that allow for defining the type of access to
various objects in the system. Like many other Analysis Server metadata objects, the
Permission object has Name , ID , Description , and Annotations properties. The Permission
object properties depend on the type of the parent object, but some of its properties are
common for all Permission objects, as listed in Table 35.1.