Extending MDX using External Functions - Professional SQL Server Analysis Services 2005 with MDX - page 501

4. Run the assembly under an anonymous account. This is
the least-privileged account and will not have any access to
any data. Typically, stored procedures that are computation-
intensive can be specified with this option.
5. Default. When the default option is chosen it is actually
translated to one of the four options you just learned based
on the selected permission set. If the permission set is Safe,
selecting the default option for impersonation will set the im-
personation mode to Impersonate Service Account. If the
permission set is Unrestricted or External Access, selecting
the default impersonation mode results in the impersonation
mode being set as Impersonate current user.
8. Select the default option and click OK.
9. Following steps 2 through 6, add the AMO stored procedure AMOS-
proc but select the permission as Unrestricted. You will learn why
Unrestricted permission is used for AMOSproc in the next section.
You have successfully created stored procedures and added them to the Ana-
lysisServices2005Tutorial database. Next you see examples of using them in
queries.
Querying Stored Procedures
Similar to COM UDFs, you can call the stored procedures using the assembly
name, interface name and function name. However, for .NET assemblies you
need to specify the assembly name followed by the fully qualified class name
and then the function name. You can just specify the assembly name followed
by function name if there is no ambiguity in the function name.
You can use the PartialSumSproc assembly's PartialSum function to calculate
the cumulative profit as shown in Figure 10-5 .
Now that you have added the ADOMD stored procedure, you'll want to see
how to use it. Assume you want to see all the cities that contributed to a profit
of $1000 or more; you would use the following MDX Query.