Administering Analysis Services - Professional SQL Server Analysis Services 2005 with MDX - page 574

Sales</MeasureGroupID>
<PartitionID>Fact Internet Sales
New</PartitionID>
</Source>
</Sources>
<Target>
<DatabaseID>AnalysisServices2005Tutorial</DatabaseID>
<CubeID>Adventure Works DW</CubeID>
<MeasureGroupID>Fact Internet
Sales</MeasureGroupID>
<PartitionID>Fact Internet Sales</PartitionID>
</Target>
</MergePartitions>
Managing Assemblies
You learned about .NET and COM assemblies in Chapter 10 . Assemblies,
also referred to as stored procedures, can only be added by Analysis Ser-
vices administrators. You need to make sure your instance of Analysis Ser-
vices is safe and secure irrespective of the operations done by the stored pro-
cedures. Security is always a concern, and you do not want any assemblies
to bring down the server. Because hackers try to hack servers, most software
products now are built to be secure by default. The administrator needs to en-
able certain components and options to make them available to users. By de-
fault, Analysis Services does not allow execution of stored procedures. The
administrator first needs to enable the server properties
Feature\ManagedCodeEnabled and Feature\ComUdfEnabled to true (value
of 1 in the Analysis Services config file) for enabling managed assemblies
and COM DLLs respectively. This is accomplished by using the server proper-
ties dialog to enable registration and execution of assemblies.
The key to managing assemblies is to understand the nature of the assembly
and setting appropriate properties while adding assemblies to your Analysis
Services. Figure 12-17 shows the dialog to add assemblies to the Server or to
a specific database.
You saw in Chapter 10 that Analysis Services supports two types of assem-
blies: COM and .NET CLR assemblies. Once you specify the type and name