MSFTASProdSamples Wiki & Documentation Rss Feed

New Comment on "Katmai!Data Mining Web Controls Library"

thesuraj — Wed, 13 Jul 2011 18:39:06 GMT

I cannot see folder " C:\Program Files\Microsoft SQL Server\100\Samples\Analysis Services\DataMining\Data Mining Web Controls" after installation. I am using 32 bit msi file.

New Comment on "SS2005!Readme For Command-line Utility Sample"

mavericklbj — Tue, 14 Sep 2010 14:39:55 GMT

Am I the only one who have problems with deploying roles ?

Updated Wiki: Home

bonniefe — Tue, 08 Dec 2009 23:47:16 GMT

SQL Server Samples Portal Page > SQL Server Analysis Services Product Samples

SQL Server Analysis Services provides, a unified and integrated view of all your business data as the foundation for all of your traditional reporting, online analytical processing (OLAP) analysis, Key Performance Indicator (KPI) scorecards, and data mining.

This project contains Analysis Services samples released with Microsoft SQL Server product. These samples are in the following three categories: Administrator, Data Mining, and Programmability. If you are interested in contributing Analysis Services samples, please let us know by posting in the developers' forum.

To download these samples click on the Releases tab (or click here), optionally select another (older) release, then click on the Windows Installer package (MSI file) which matches the architecture of the installation computer.

For information about how to use CodePlex to access SQL Server samples, click here.
To download samples databases, click here and then click the appropriate MSI file.
For release notes and brief descriptions of all the sample databases and code, including restrictions on SQL Express and Vista, click here.

Administrator

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Activity Viewer	SS2005	n/a
Aggregation Manager Sample	SS2005	n/a
Analysis Services Upgrade Verification Tool Sample	SS2005	n/a
ASTrace Utility Sample	SS2005	n/a
Command-line Utility Sample	SS2005	SQL Server 2008 SR1

Data Mining

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Data Mining Web Controls Library	SS2005	n/a
SQL Server Plug-In Algorithms	SS2005	n/a

Extensibility

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
Analysis Services Personalization Extensions Sample	n/a	SS2008

Programmability

Sample	SQL Server 2005	SQL Server 2008 & SQL Server 2008R2
AMOBrowser	SS2005	SS2008
BackupAndRestore	SS2005	SS2008
DisplayObjectsName	SS2005	SS2008
AS Simple Sample	SS2005	SS2008
AMOAdventureWorks	SS2005	SS2008

Got questions? Want to contribute? Check out the SQL Server Community & Samples Discussion Forum!

New Comment on "SS2005!Readme_AMOAdventureWorks"

Roman_K — Tue, 01 Dec 2009 06:06:52 GMT

where is code?

New Comment on "SS2005!Activity Viewer"

brucenan — Fri, 28 Aug 2009 08:35:38 GMT

Why program want to load a XML from "C:\documents and settings\Microsoft\Microsoft SQL Server\90\Tools\Shell\RegSrvr.xml", But I can not find this file in my machine. How can I run this program sucessfully?

New Comment on "SS2008!Readme_AMOAdventureWorks"

jcolaizzi — Fri, 14 Aug 2009 00:33:48 GMT

I'm working with Visual Studio 2005 or 2008 and the AmoAdventureWorks sample and Sql Server 2008 Standard edition. I've made two changes to the AmoAdventureworks project, both in Program.cs. First I put an immediate return in the CreateCurrencyRatesMeasureGroup method to avoid the issue of semiadditive measures not being available in the Standard Edition. Second in the CreateRolesAndPermissions method for the reader role I used this statement: role.Members.Add(new RoleMember("EIT\test1")); // e.g. redmond\johndoe instead of: role.Members.Add(new RoleMember("")); // e.g. redmond\johndoe and then role.Update(); gets this exception: {"The following system error occurred: No mapping between account names and security IDs was done. .\n"} If I use this statement: role.Members.Add(new RoleMember("EIT\test1", "S-1-5-21-107385321-1855232891-3196306309-513")); // e.g. redmond\johndoe it runs to completion and creates the cube. That is a valid user\sid combination in our domain and as a Server Admin in Analysis Services I can browse the cube. However if I go into SSMS 2008 and open the AmoAdventureWorks AS database, then open roles and right click on Readers -> Properties -> Membership it shows S-1-5-21-107385321-1855232891-3196306309-513 as the user for this role. If I add a user and immediately remove that user and click ok I once again get a dialog box with: The following system error occurred: No mapping between account names and security IDs was done. Will someone please explain what I'm doing wrong or missing here? Thanks

Updated Wiki: SS2008!Readme for Analysis Services Personalization Extensions Sample

cmslydia — Thu, 09 Apr 2009 02:39:02 GMT

Readme_Analysis Services Personalization Extensions Sample

11/05/2008 21:36:06

This sample works only with SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2008.
The Analysis Services Personalization Extensions sample is a C# program that illustrates how to create user-based personalizations. These personalizations are not permanent objects in the cube, but are objects that the client application applies dynamically during the user's session.
The Analysis Services Personalization Extensions sample dynamically creates a different object for three different users. For each user connection, the sample enables only the object that is associated with that user. Each of these personalization objects is only visible during the user's session.

Scenario

An independent software vendor (ISV) creates an interface that enables a user to design business metrics for his or her company, and then share those metrics with that user's peers. The metrics are dynamic and adjustable to the person who uses them. For example, the ISV designs a client interface that enables a company's business analyst to design a Sales Monthly Goal Tracking indicator. This indicator calculates and tracks the monthly sales goal for each salesperson. The business analyst can then share this indicator with the company's sales team. Now, any member on the team can easily know how he or she is doing towards the monthly goal, as the indicator is automatically tailored to the goals of each salesperson.
Without the personalization extensions, the indicator would have to be passed to the company's Analysis Services team. This Analysis Services team would have to incorporate the indicator directly into the cube design and then redeploy the cube to the end users. Because the indicator would be an object in the cube, the indicator would not be personalized to each user.

Languages

Features

The Analysis Services Personalization Extensions Sample uses the following features of SQL Server 2008 Analysis Services (SSAS).

Application Area	Features
AdventureWorks	ADOMD.NET Server, MDX

Prerequisites

Before you run this sample, you should have SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on Itanium-based computers. The 64-bit development environment is supported on x64-based operating systems. SQL Server 2005 samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based computer.
Updated versions of the following SQL Server sample databases: the AdventureWorks data warehouse and the AdventureWorks database. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases.
Updated versions of the following SQL Server samples: Analysis Services samples and SQL Server Database Engine samples. You can download these samples from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases. You also need .NET Framework SDK 3.5 or Microsoft Visual Studio 2008 installed. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK

Building the Sample

The Analysis Services Personalization Extensions Sample is composed of one binary file, ASPE.dll.
If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2008 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2008, select Visual Studio Tools, and then click Visual Studio 2008 Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the Analysis Services Personalization Extensions Sample

Rename SampleKey.snk to ASPE.snk and move the file to the same location where ASPE.sln is.
Compile ASPE.dll by using:
Visual Studio 2008 and the ASPE.sln file. — or —
Microsoft MSBuild, which is included in the .NET Framework SDK 3.5. Change directory to the location where the solution file ASPE.sln is located. Run a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug ASPE.sln You can use other MSBuild build options depending on your needs.

Deploying the Sample

To deploy the Analysis Services Personalization Extensions sample, you must add the assembly that you built in the previous procedure to a running instance of Analysis Services.

To add ASPE.dll assembly to a running instance of Analysis Services

In SQL Server Management Studio, connect to the instance of Analysis Services.Localhost is assumed as the default instance for this sample. Replace localhost in with the name of the instance that you have selected.
At the server level, open the Assemblies folder and verify that the ASPE assembly is not listed.If the ASPE assembly is listed, remove this assembly by right-clicking the assembly and selecting Delete. Continue following the steps on the screen.
Right-click Assemblies and select New Assembly.
In the Register Server Assembly dialog box, select the following options:
For Type, select .NET Assembly.
For Filename, click the browse button … and find the ASPE.dll file in your project folder under bin/debug folders.
For Permissions, select Unrestricted.
For Impersonation, select Use the Service Account.
Click OK.

At the server level, open the Assemblies folder and verify the ASPE assembly is listed.
To enable the correct management of all events, open SQL Server Configuration Manager, select SQL Server Services, and then select the SQL Server Analysis Services row. Click the restart button to restart the service

Preparing the Environment to Test the Sample

On the same server where you are running Analysis Services and have deployed ASPE.dll, use the following procedures to set up the environment to test the sample.

To add three users to your current system

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Right-click the Users folder and select New User.
In the New User dialog box, select the following options:
For User name, type user1.
For Password, type a strong password that meets your company standards.
For Confirm password, re-type your selected password.
Clear the User must change password at next logon check box.
Select the Password never expires check box.
Repeat step 4 for user2 and user3.

To verify Adventure Works DW database is deployed and contains Adventure Works cube

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server name, localhost.
Expand the Databases node and verify that the Adventure Works DW database exists.
Expand the Adventure Works DW node, expand the Cubes node, and verify that the Adventure Works cube exists.
Right-click the Adventure Works cube and select Properties. Verify that the cube State is Processed.
If any one of the previous steps cannot be completed, see the Books Online topic, Running Setup to Install AdventureWorks Sample Databases and Samples, in the MSDN Library.

To add a role for the new users and give them access to the cube and dimensions

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server Name, localhost.
Expand the Databases node, and then expand the Adventure Works DW database.
Right-click Roles, and then select New role.
In the Create Role dialog box, click the General page, and select the following options:
For Role name, type ASPE Test Users.
Select the Read definition check box.
Clear the Full control (Administrator) and Process database check boxes.
Click the Membership page, and select the following options:
Click Add.
In the Select Users or Groups window, for Enter the object names to select, type user1; user2; user3.
Click Check Names. The values should now appear underlined, with the server or domain name in front of each name.
Click OK.

Click the Data Sources page. In the Access column for the Adventure Works DW row, select Read.
Click the Cubes page, and select the following options for the Adventure Works row:
In the Access column, select Read.
In the Local Cube/Drillthrough Access column, select Drillthrough and Local Cube. Click OK to accept the message.
In the Process column, select the check box.
Click the Dimensions page. For each of the rows in Dimensions, select the Process column check box.
Click OK, and then wait until the command is processed and the new role is created.

Testing the Sample

Testing the sample demonstrates that new personalization objects are created in different user contexts and that those objects are associated with the user profile.

To verify your context

In SQL Server Management Studio, connect to the Server Name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server Name, localhost.
On the SQL Server Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node.
Expand the Internet Sales node, and verify that there is no ISV_1 folder under this node.
Expand the Geography dimension, and verify that there is no ISV_1 folder in this dimension.
Expand the Product dimension, and verify that there is no ISV_1 folder in this dimension.

To verify the context for user1

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user1. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user1 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the SQL Server Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if it is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, and then expand the Internet Sales node to see the ISV1 folder.Unlike your user context, user1 has an *ISV1 *folder under the Internet Sales node.
Expand the ISV1 folder, expand the Common folder. Notice the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, expand the ISV1 folder, and then expand the Operations folder.Notice that the Operations folder contains the Average Item Freight Cost member.
Expand the Geography dimension, expand the ISV1 folder, and then expand the Common folder to see the ISV1 - Western Coast set.Unlike your user context, user1 does have access to the ISV1 - Western Coast set.
Expand the Product dimension, expand the ISV1 folder, and then expand the Operations folder to see the Touring Bikes set.Unlike your user context, user1 has access to the Touring Bikes set.

To verify the context for user2

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user2. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user2 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV1 folder, and expand the Common folder. Notice the Gross Internet Profit member is also visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV1 folder in this group.Only user1 has an ISV1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, expand the ISV1 folder, and then expand the Finance folder to see the *Rate Difference *member.Notice that for user2 only, the Exchange Rates measure group has an ISV1 folder.
Expand the Geography dimension, expand the ISV1 folder, and then expand the Common folder to see the ISV1 - Western Coast set.Notice that user2, just like user1, has access to the ISV1 - Western Coast set.
Expand the Product dimension, expand the ISV1 folder, and then expand the Finance folder to see the Mountain Bikes set.While user2 has access to the Mountain Bikes set, user2 does not have access to the Touring Bikes set in the Operations folder. Only user1 has access to the Touring Bikes set.

To verify the context for user3

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user3. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user3 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV1 folder, and expand the Common folder. Notice that the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV1 folder in this group.Only user1 has an ISV1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, and verify that there is no ISV1 folder in this group.Only user2 has an ISV1 folder in the Exchange Rates measure group.
Return to the Measures node and expand the Reseller Orders measure group, expand the ISV1 folder, and then expand the Marketing folder to see the Discount per Order member.Notice that for user3 only, the Reseller Orders measure group has an ISV1 folder.
Expand the Geography dimension, expand the ISV1 folder, and expand the Common folder to see ISV1 - Western Coast set.user3, just like user1 and user2, has access to the ISV1 - Western Coast set.
Expand the Product dimension, expand the ISV1 folder, and then expand the Marketing folder to see the All Terrain Bikes set.While user3 has access to the All Terrain Bikes set, user3 does not have access to the Touring Bikes set in the Operation folder. Only user1 has access to the Touring Bikes set. User3 also has access to the Mountain Bikes set in the Finance folder. It is user2 who has no access to the All Terrain Bikes set.

Troubleshooting the Sample

Use the following set of procedures to troubleshoot the Analysis Services Personalization Extensions sample.

To define debug breakpoints in the code

In Visual Studio 2008, open ASPE.sln.
Open the source code for the ASClientExtensions.cs source file, and then set a breakpoint on the opening brace of the ASClientExtensions constructor.
Open the source code for the SessionMgr.cs source file, and then set the following breakpoints:
Set a breakpoint on the opening brace of the SessionMgr constructor.
Set a breakpoint on the opening brace of the CubeOpened method.
Open the source code for the AuthoringAndManagement.cs source file, and then set the following breakpoints.
Set a breakpoint on the opening brace of the AuthoringAndManagement constructor.
Set a breakpoint on the opening brace of the DefineMembers method.
Set a breakpoint on the opening brace of the DefineSets method.
Set a breakpoint on the opening brace of the DefineKPIs method.

To attach to the running instance of Analysis Services

In the menu bar, select Debug, and then select Attach to process.
In the Available Processes pane, browse to find msmdsrv.exe, and then select it.
Click Attach, and then wait until the debugger attaches to the running process.

To run through the breakpoints

Repeat all the steps in the procedure, To verify the context for user1.Notice that SQL Server Management Studio does not immediately appear. Instead, Visual Studio opens.
To see the sequence of events, press F11 repeatedly.If there are no more events, check SQL Server Management Studio to continue with the steps in the procedure, To verify the context for user1.

Removing the Sample

Use the following procedure to remove the Analysis Services Personalization Extensions Sample.

To remove the roles and assembly from the current Analysis Services instance

Open SQL Server Management Studio.
Connect to the Server Name, localhost
Expand the Databases node, and then expand Adventure Works DW database.
Expand Roles, right-click ASPE Test Users, select Delete, and then click OK.
At server level, expand Assemblies, right-click ASPE, select Delete, and then click OK.
Close SQL Server Management Studio.
Restart the service

To remove the user created for this sample

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Expand the Users folder.
Remove user1, user2, user3 by right-clicking each user, selecting Delete, and then clicking OK.

To remove the ASPE sample

From your solution folder, in the ASPE folder, remove the bin and obj folders. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme for Analysis Services Personalization Extensions Sample

cmslydia — Fri, 27 Mar 2009 03:18:23 GMT

Readme_Analysis Services Personalization Extensions Sample

Scenario

Languages

Features

The Analysis Services Personalization Extensions Sample uses the following features of SQL Server 2008 Analysis Services (SSAS).

Application Area	Features
AdventureWorks	ADOMD.NET Server, MDX

Prerequisites

Before you run this sample, you should have SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on Itanium-based computers. The 64-bit development environment is supported on x64-based operating systems. SQL Server 2005 samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based computer.
Updated versions of the following SQL Server sample databases: the AdventureWorks data warehouse and the AdventureWorks database. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases.
Updated versions of the following SQL Server samples: Analysis Services samples and SQL Server Database Engine samples. You can download these samples from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases. You also need .NET Framework SDK 3.5 or Microsoft Visual Studio 2008 installed. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK

Building the Sample

To generate a strong name key file

Open a Microsoft Visual Studio 2008 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2008, select Visual Studio Tools, and then click Visual Studio 2008 Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the Analysis Services Personalization Extensions Sample

Rename SampleKey.snk to ASPE.snk and move the file to the same location where ASPE.sln is.
Compile ASPE.dll by using:
Visual Studio 2008 and the ASPE.sln file. — or —
Microsoft MSBuild, which is included in the .NET Framework SDK 3.5. Change directory to the location where the solution file ASPE.sln is located. Run a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug ASPE.sln You can use other MSBuild build options depending on your needs.

Deploying the Sample

To deploy the Analysis Services Personalization Extensions sample, you must add the assembly that you built in the previous procedure to a running instance of Analysis Services.

To add ASPE.dll assembly to a running instance of Analysis Services

In SQL Server Management Studio, connect to the instance of Analysis Services.Localhost is assumed as the default instance for this sample. Replace localhost in with the name of the instance that you have selected.
At the server level, open the Assemblies folder and verify that the ASPE assembly is not listed.If the ASPE assembly is listed, remove this assembly by right-clicking the assembly and selecting Delete. Continue following the steps on the screen.
Right-click Assemblies and select New Assembly.
In the Register Server Assembly dialog box, select the following options:
For Type, select .NET Assembly.
For Filename, click the browse button … and find the ASPE.dll file in your project folder under bin/debug folders.
For Permissions, select Unrestricted.
For Impersonation, select Use the Service Account.
Click OK.

At the server level, open the Assemblies folder and verify the ASPE assembly is listed.
To enable the correct management of all events, open SQL Server Configuration Manager, select SQL Server Services, and then select the SQL Server Analysis Services row. Click the restart button to restart the service

Preparing the Environment to Test the Sample

On the same server where you are running Analysis Services and have deployed ASPE.dll, use the following procedures to set up the environment to test the sample.

To add three users to your current system

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Right-click the Users folder and select New User.
In the New User dialog box, select the following options:
For User name, type user1.
For Password, type a strong password that meets your company standards.
For Confirm password, re-type your selected password.
Clear the User must change password at next logon check box.
Select the Password never expires check box.
Repeat step 4 for user2 and user3.

To verify Adventure Works DW database is deployed and contains Adventure Works cube

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server name, localhost.
Expand the Databases node and verify that the Adventure Works DW database exists.
Expand the Adventure Works DW node, expand the Cubes node, and verify that the Adventure Works cube exists.
Right-click the Adventure Works cube and select Properties. Verify that the cube State is Processed.
If any one of the previous steps cannot be completed, see the Books Online topic, Running Setup to Install AdventureWorks Sample Databases and Samples, in the MSDN Library.

To add a role for the new users and give them access to the cube and dimensions

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server Name, localhost.
Expand the Databases node, and then expand the Adventure Works DW database.
Right-click Roles, and then select New role.
In the Create Role dialog box, click the General page, and select the following options:
For Role name, type ASPE Test Users.
Select the Read definition check box.
Clear the Full control (Administrator) and Process database check boxes.
Click the Membership page, and select the following options:
Click Add.
In the Select Users or Groups window, for Enter the object names to select, type user1; user2; user3.
Click Check Names. The values should now appear underlined, with the server or domain name in front of each name.
Click OK.

Click the Data Sources page. In the Access column for the Adventure Works DW row, select Read.
Click the Cubes page, and select the following options for the Adventure Works row:
In the Access column, select Read.
In the Local Cube/Drillthrough Access column, select Drillthrough and Local Cube. Click OK to accept the message.
In the Process column, select the check box.
Click the Dimensions page. For each of the rows in Dimensions, select the Process column check box.
Click OK, and then wait until the command is processed and the new role is created.

Testing the Sample

Testing the sample demonstrates that new personalization objects are created in different user contexts and that those objects are associated with the user profile.

To verify your context

In SQL Server Management Studio, connect to the Server Name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server Name, localhost.
On the SQL Server Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node.
Expand the Internet Sales node, and verify that there is no ISV_1 folder under this node.
Expand the Geography dimension, and verify that there is no ISV_1 folder in this dimension.
Expand the Product dimension, and verify that there is no ISV_1 folder in this dimension.

To verify the context for user1

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user1. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user1 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the SQL Server Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if it is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, and then expand the Internet Sales node to see the ISV_1 folder.Unlike your user context, user1 has an *ISV_1 *folder under the Internet Sales node.
Expand the ISV_1 folder, expand the Common folder. Notice the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, expand the ISV_1 folder, and then expand the Operations folder.Notice that the Operations folder contains the Average Item Freight Cost member.
Expand the Geography dimension, expand the ISV_1 folder, and then expand the Common folder to see the ISV_1 - Western Coast set.Unlike your user context, user1 does have access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Operations folder to see the Touring Bikes set.Unlike your user context, user1 has access to the Touring Bikes set.

To verify the context for user2

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user2. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user2 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV_1 folder, and expand the Common folder. Notice the Gross Internet Profit member is also visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV_1 folder in this group.Only user1 has an ISV_1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, expand the ISV_1 folder, and then expand the Finance folder to see the *Rate Difference *member.Notice that for user2 only, the Exchange Rates measure group has an ISV_1 folder.
Expand the Geography dimension, expand the ISV_1 folder, and then expand the Common folder to see the ISV_1 - Western Coast set.Notice that user2, just like user1, has access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Finance folder to see the Mountain Bikes set.While user2 has access to the Mountain Bikes set, user2 does not have access to the Touring Bikes set in the Operations folder. Only user1 has access to the Touring Bikes set.

To verify the context for user3

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user3. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user3 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV_1 folder, and expand the Common folder. Notice that the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV_1 folder in this group.Only user1 has an ISV_1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, and verify that there is no ISV_1 folder in this group.Only user2 has an ISV_1 folder in the Exchange Rates measure group.
Return to the Measures node and expand the Reseller Orders measure group, expand the ISV_1 folder, and then expand the Marketing folder to see the Discount per Order member.Notice that for user3 only, the Reseller Orders measure group has an ISV_1 folder.
Expand the Geography dimension, expand the ISV_1 folder, and expand the Common folder to see ISV_1 - Western Coast set.user3, just like user1 and user2, has access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Marketing folder to see the All Terrain Bikes set.While user3 has access to the All Terrain Bikes set, user3 does not have access to the Touring Bikes set in the Operation folder. Only user1 has access to the Touring Bikes set. User3 also has access to the Mountain Bikes set in the Finance folder. It is user2 who has no access to the All Terrain Bikes set.

Troubleshooting the Sample

Use the following set of procedures to troubleshoot the Analysis Services Personalization Extensions sample.

To define debug breakpoints in the code

In Visual Studio 2008, open ASPE.sln.
Open the source code for the ASClientExtensions.cs source file, and then set a breakpoint on the opening brace of the ASClientExtensions constructor.
Open the source code for the SessionMgr.cs source file, and then set the following breakpoints:
Set a breakpoint on the opening brace of the SessionMgr constructor.
Set a breakpoint on the opening brace of the CubeOpened method.
Open the source code for the AuthoringAndManagement.cs source file, and then set the following breakpoints.
Set a breakpoint on the opening brace of the AuthoringAndManagement constructor.
Set a breakpoint on the opening brace of the DefineMembers method.
Set a breakpoint on the opening brace of the DefineSets method.
Set a breakpoint on the opening brace of the DefineKPIs method.

To attach to the running instance of Analysis Services

In the menu bar, select Debug, and then select Attach to process.
In the Available Processes pane, browse to find msmdsrv.exe, and then select it.
Click Attach, and then wait until the debugger attaches to the running process.

To run through the breakpoints

Repeat all the steps in the procedure, To verify the context for user1.Notice that SQL Server Management Studio does not immediately appear. Instead, Visual Studio opens.
To see the sequence of events, press F11 repeatedly.If there are no more events, check SQL Server Management Studio to continue with the steps in the procedure, To verify the context for user1.

Removing the Sample

Use the following procedure to remove the Analysis Services Personalization Extensions Sample.

To remove the roles and assembly from the current Analysis Services instance

Open SQL Server Management Studio.
Connect to the Server Name, localhost
Expand the Databases node, and then expand Adventure Works DW database.
Expand Roles, right-click ASPE Test Users, select Delete, and then click OK.
At server level, expand Assemblies, right-click ASPE, select Delete, and then click OK.
Close SQL Server Management Studio.
Restart the service

To remove the user created for this sample

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Expand the Users folder.
Remove user1, user2, user3 by right-clicking each user, selecting Delete, and then clicking OK.

To remove the ASPE sample

From your solution folder, in the ASPE folder, remove the bin and obj folders. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme for AS Simple Sample

leilu — Thu, 19 Mar 2009 06:44:15 GMT

Readme_AS Simple Sample

11/05/2008 21:36:06

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
AS Simple Sample is a sample C# program that illustrates the use of the Analysis Management Objects (AMO) to create complex OLAP cubes and the use of ADOMD.NET to access the contents of the newly created cubes.
Default location: C:\Program Files\Microsoft SQL Server\100\Samples\Analysis Services\Programmability\AMO\AS Simple Sample
AS Simple Sample is a complete developer sample for Analysis Services multidimensional databases; it covers both sides of the coin for developers: the server administration (using AMO) and the client access to the data (using ADOMD.NET.Client).
From the server administration perspective the AS Simple Sample covers most major objects creation, modifications and process. On the enhancement side it covers aggregation design, perspectives, KPIs, actions, translations, and proactive caching. It also mentions security by using roles and permissions. The sample also covers a data mining structure and model creation and processing.
From the client access perspective, the AS Simple Sample covers most major objects, metadata browsing, and access to the values; it also shows how to implement KPIs, actions, and browsing a data mining model.
While working with the AS Simple Sample, developers can see and understand the impact of using AMO and see the results using ADOMD. One of the most common challenges that developers working with Analysis Services face is how to see the results of what they are doing in AMO from the user perspective. This is because when you design an object (for example, a KPI) you cannot see the results from AMO. In addition, if you are implementing a client interface using ADOMD that permits the user to execute designed actions, there is no easy way to discover the actions implemented unless you browse the actions collection using AMO. The AS Simple Sample therefore the need to have an integrated sample.

Scenario

The AS Simple Sample uses a guided set of procedures to create a subset of the functionality of the AdventureWorks cube located in the AdventureWorks Analysis Services Project. Then, the sample allows the user to view results in a client interface.

Languages

Features

The Analysis Services sample uses the following features.

Application Area	Features
AdventureWorks	AMO, ADOMD.NET Client, ADOMD.NET Server

Prerequisites

Before you run this sample, you should have Microsoft SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.
Updated versions of the following SQL Server sample databases: the AdventureWorksDW data warehouse and the AdventureWorks database. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.
Updated versions of the following SQL Server samples: Analysis Services samples and SQL Server Database Engine samples. You can download these samples from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases. You also need .NET Framework SDK 2.0 or Microsoft Visual Studio 2005 installed. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

The AS Simple Sample is composed of three different binaries:

'Simple Sample Stored Procedures.dll'
'Simple Sample AMO Access.exe'
'Simple Sample ADOMD ClientAccess.exe' The only requirement to build the sample is to compile 'Simple Sample Stored Procedures.dll' before you compile 'Simple Sample AMO Access.exe'. There is no binary interdependency between the AMO sample and the ADOMD sample.

To build the Simple Sample Analysis Services sample

Compile 'Simple Sample Stored Procedures.dll' by using Visual Studio 2005 and the 'StoredProcedures.sln' file.— or —Compile the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, by executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug "CS/StoredProcedures.sln" You can use other MSBuild build options depending on your needs.
Compile 'Simple Sample AMO Access.exe' by using Visual Studio 2005 and the 'ServerAdmin.sln' file.— or —Compile the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, by executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug "CS/ServerAdmin.sln" You can use other MSBuild build options depending on your needs.
Compile 'Simple Sample ADOMD ClientAccess.exe' by using Visual Studio 2005 and the 'ClientAccess.sln' file.— or —Compile the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, by executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug "CS/ClientAccess.sln" You can use other MSBuild build options depending on your needs.

Running the Sample

To run the Simple Sample Analysis Services sample

Build the 'Simple Sample' database using 'Simple Sample AMO Access'.
In Visual Studio 2005, with ServerAdmin solution opened, press F5.— or —In Visual Studio 2005, on the Debug menu, click Start.— or —At a command prompt, use the change directory (CD) command to go to the folder where the sample was built. The default build location is .\CS\ServerAdmin\bin\Debug. In that directory, run the following command (including quotation marks): "Simple Sample AMO Access.exe"
Execute the suggested steps in the sample interface.
In Visual Studio 2005, with ClientAccess solution opened, press F5.— or —In Visual Studio 2005, on the Debug menu, click Start.— or —At a command prompt, use the change directory (CD) command to go to the folder where the sample was built. The default build location is .\CS\ClientAccess \bin\Debug. In that directory, run the following command (including quotation marks): "Simple Sample ADOMD ClientAccess.exe"
Connect to a server and explore the user objects. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme for Analysis Services Personalization Extensions Sample

libinzhao — Thu, 19 Mar 2009 04:03:18 GMT

Readme_Analysis Services Personalization Extensions Sample

Scenario

Languages

Features

The Analysis Services Personalization Extensions Sample uses the following features of SQL Server 2008 Analysis Services (SSAS).

Application Area	Features
AdventureWorks	ADOMD.NET Server, MDX

Prerequisites

Before you run this sample, you should have SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on Itanium-based computers. The 64-bit development environment is supported on x64-based operating systems. SQL Server 2005 samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based computer.
Updated versions of the following SQL Server sample databases: the AdventureWorks data warehouse and the AdventureWorks database. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases.
Updated versions of the following SQL Server samples: Analysis Services samples and SQL Server Database Engine samples. You can download these samples from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases. You also need .NET Framework SDK 2.0 or Microsoft Visual Studio 2005 installed. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK

Building the Sample

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the Analysis Services Personalization Extensions Sample

Rename SampleKey.snk to ASPE.snk and move the file to the same location where ASPE.sln is.
Compile ASPE.dll by using:
Visual Studio 2005 and the ASPE.sln file. — or —
Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Change directory to the location where the solution file ASPE.sln is located. Run a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug ASPE.sln You can use other MSBuild build options depending on your needs.

Deploying the Sample

To deploy the Analysis Services Personalization Extensions sample, you must add the assembly that you built in the previous procedure to a running instance of Analysis Services.

To add ASPE.dll assembly to a running instance of Analysis Services

In SQL Server Management Studio, connect to the instance of Analysis Services.Localhost is assumed as the default instance for this sample. Replace localhost in with the name of the instance that you have selected.
At the server level, open the Assemblies folder and verify that the ASPE assembly is not listed.If the ASPE assembly is listed, remove this assembly by right-clicking the assembly and selecting Delete. Continue following the steps on the screen.
Right-click Assemblies and select New Assembly.
In the Register Server Assembly dialog box, select the following options:
For Type, select .NET Assembly.
For Filename, click the browse button … and find the ASPE.dll file in your project folder under bin/debug folders.
For Permissions, select Unrestricted.
For Impersonation, select Use the Service Account.
Click OK.

At the server level, open the Assemblies folder and verify the ASPE assembly is listed.
To enable the correct management of all events, open SQL Server Configuration Manager, select SQL Server Services, and then select the SQL Server Analysis Services row. Click the restart button to restart the service

Preparing the Environment to Test the Sample

On the same server where you are running Analysis Services and have deployed ASPE.dll, use the following procedures to set up the environment to test the sample.

To add three users to your current system

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Right-click the Users folder and select New User.
In the New User dialog box, select the following options:
For User name, type user1.
For Password, type a strong password that meets your company standards.
For Confirm password, re-type your selected password.
Clear the User must change password at next logon check box.
Select the Password never expires check box.
Repeat step 4 for user2 and user3.

To verify Adventure Works DW database is deployed and contains Adventure Works cube

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server name, localhost.
Expand the Databases node and verify that the Adventure Works DW database exists.
Expand the Adventure Works DW node, expand the Cubes node, and verify that the Adventure Works cube exists.
Right-click the Adventure Works cube and select Properties. Verify that the cube State is Processed.
If any one of the previous steps cannot be completed, see the Books Online topic, Running Setup to Install AdventureWorks Sample Databases and Samples, in the MSDN Library.

To add a role for the new users and give them access to the cube and dimensions

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server Name, localhost.
Expand the Databases node, and then expand the Adventure Works DW database.
Right-click Roles, and then select New role.
In the Create Role dialog box, click the General page, and select the following options:
For Role name, type ASPE Test Users.
Select the Read definition check box.
Clear the Full control (Administrator) and Process database check boxes.
Click the Membership page, and select the following options:
Click Add.
In the Select Users or Groups window, for Enter the object names to select, type user1; user2; user3.
Click Check Names. The values should now appear underlined, with the server or domain name in front of each name.
Click OK.

Click the Data Sources page. In the Access column for the Adventure Works DW row, select Read.
Click the Cubes page, and select the following options for the Adventure Works row:
In the Access column, select Read.
In the Local Cube/Drillthrough Access column, select Drillthrough and Local Cube. Click OK to accept the message.
In the Process column, select the check box.
Click the Dimensions page. For each of the rows in Dimensions, select the Process column check box.
Click OK, and then wait until the command is processed and the new role is created.

Testing the Sample

Testing the sample demonstrates that new personalization objects are created in different user contexts and that those objects are associated with the user profile.

To verify your context

In SQL Server Management Studio, connect to the Server Name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server Name, localhost.
On the SQL Server Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node.
Expand the Internet Sales node, and verify that there is no ISV_1 folder under this node.
Expand the Geography dimension, and verify that there is no ISV_1 folder in this dimension.
Expand the Product dimension, and verify that there is no ISV_1 folder in this dimension.

To verify the context for user1

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user1. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user1 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the SQL Server Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if it is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, and then expand the Internet Sales node to see the ISV_1 folder.Unlike your user context, user1 has an *ISV_1 *folder under the Internet Sales node.
Expand the ISV_1 folder, expand the Common folder. Notice the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, expand the ISV_1 folder, and then expand the Operations folder.Notice that the Operations folder contains the Average Item Freight Cost member.
Expand the Geography dimension, expand the ISV_1 folder, and then expand the Common folder to see the ISV_1 - Western Coast set.Unlike your user context, user1 does have access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Operations folder to see the Touring Bikes set.Unlike your user context, user1 has access to the Touring Bikes set.

To verify the context for user2

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user2. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user2 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV_1 folder, and expand the Common folder. Notice the Gross Internet Profit member is also visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV_1 folder in this group.Only user1 has an ISV_1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, expand the ISV_1 folder, and then expand the Finance folder to see the *Rate Difference *member.Notice that for user2 only, the Exchange Rates measure group has an ISV_1 folder.
Expand the Geography dimension, expand the ISV_1 folder, and then expand the Common folder to see the ISV_1 - Western Coast set.Notice that user2, just like user1, has access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Finance folder to see the Mountain Bikes set.While user2 has access to the Mountain Bikes set, user2 does not have access to the Touring Bikes set in the Operations folder. Only user1 has access to the Touring Bikes set.

To verify the context for user3

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user3. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user3 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV_1 folder, and expand the Common folder. Notice that the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV_1 folder in this group.Only user1 has an ISV_1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, and verify that there is no ISV_1 folder in this group.Only user2 has an ISV_1 folder in the Exchange Rates measure group.
Return to the Measures node and expand the Reseller Orders measure group, expand the ISV_1 folder, and then expand the Marketing folder to see the Discount per Order member.Notice that for user3 only, the Reseller Orders measure group has an ISV_1 folder.
Expand the Geography dimension, expand the ISV_1 folder, and expand the Common folder to see ISV_1 - Western Coast set.user3, just like user1 and user2, has access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Marketing folder to see the All Terrain Bikes set.While user3 has access to the All Terrain Bikes set, user3 does not have access to the Touring Bikes set in the Operation folder. Only user1 has access to the Touring Bikes set. User3 also has access to the Mountain Bikes set in the Finance folder. It is user2 who has no access to the All Terrain Bikes set.

Troubleshooting the Sample

Use the following set of procedures to troubleshoot the Analysis Services Personalization Extensions sample.

To define debug breakpoints in the code

In Visual Studio 2005, open ASPE.sln.
Open the source code for the ASClientExtensions.cs source file, and then set a breakpoint on the opening brace of the ASClientExtensions constructor.
Open the source code for the SessionMgr.cs source file, and then set the following breakpoints:
Set a breakpoint on the opening brace of the SessionMgr constructor.
Set a breakpoint on the opening brace of the CubeOpened method.
Open the source code for the AuthoringAndManagement.cs source file, and then set the following breakpoints.
Set a breakpoint on the opening brace of the AuthoringAndManagement constructor.
Set a breakpoint on the opening brace of the DefineMembers method.
Set a breakpoint on the opening brace of the DefineSets method.
Set a breakpoint on the opening brace of the DefineKPIs method.

To attach to the running instance of Analysis Services

In the menu bar, select Debug, and then select Attach to process.
In the Available Processes pane, browse to find msmdsrv.exe, and then select it.
Click Attach, and then wait until the debugger attaches to the running process.

To run through the breakpoints

Repeat all the steps in the procedure, To verify the context for user1.Notice that SQL Server Management Studio does not immediately appear. Instead, Visual Studio opens.
To see the sequence of events, press F11 repeatedly.If there are no more events, check SQL Server Management Studio to continue with the steps in the procedure, To verify the context for user1.

Removing the Sample

Use the following procedure to remove the Analysis Services Personalization Extensions Sample.

To remove the roles and assembly from the current Analysis Services instance

Open SQL Server Management Studio.
Connect to the Server Name, localhost
Expand the Databases node, and then expand Adventure Works DW database.
Expand Roles, right-click ASPE Test Users, select Delete, and then click OK.
At server level, expand Assemblies, right-click ASPE, select Delete, and then click OK.
Close SQL Server Management Studio.
Restart the service

To remove the user created for this sample

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Expand the Users folder.
Remove user1, user2, user3 by right-clicking each user, selecting Delete, and then clicking OK.

To remove the ASPE sample

From your solution folder, in the ASPE folder, remove the bin and obj folders. © 2008 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!BackupAndRestore

libinzhao — Thu, 19 Mar 2009 03:51:39 GMT

Readme_Backup and Restore Sample

11/05/2008 21:36:06

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The Backup and Restore sample lets you use Analysis Management Objects (AMO) to connect to a server that is running Microsoft SQL Server Analysis Services. The sample creates a new empty database, completes a backup of that database, deletes the database, restores the database from the backup, and deletes that database.

Scenario

This sample shows you how to back up and restore your Analysis Services databases programmatically.

Languages

Features

The Analysis Services sample uses the following items.

Application area	Features
AMOAdventureWorks	AMO Objects

Prerequisites

Before you run this sample, you must have the following software installed:

.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.
Analysis Services
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.
The AdventureWorks AS database. You can download this sample database from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online. After your sample has been successfully compiled, you have to access one of the Analysis Services sample databases to test your program. We recommend that you use the AdventureWorks sample database that is provided with SQL Server.

User Permissions for Backup

For each backup file, the user who runs the backup command must have permission to write to the backup location specified. Also, the user must have one of the following roles: a member of a server role for the Analysis Services instance, or a member of a database role with Full Control (Administrator) permissions on the database to be backed up.

User Permissions for Restore

For each backup file, the user who runs the restore command must have permission to read from the backup location specified. To restore an Analysis Services database that is not installed on the server, the user must also be a member of the server role for that Analysis Services instance. To overwrite an Analysis Services database, the user must have one of the following roles: a member of the server role for the Analysis Services instance, or a member of a database role with Full Control (Administrator) permissions on the database to be restored.

Note:
After restoring an existing database, the user who restored the database might lose access to the restored database. This loss of access can occur if, at the time that the backup was performed, the user was not a member of the server role or was not a member of the database role with Full Control (Administrator) permissions.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the Backup and Restore sample

Build the sample by using Visual Studio 2005 and the provided Visual Studio solution.— or —
Build the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, and run a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/BackupAndRestore.sln Other Microsoft MSBuild build options can be used depending on your needs.

Running the Sample

To run the Backup and Restore sample

In Visual Studio 2005, press F5.— or —
In Visual Studio 2005, click Start on the Debug menu.— or —
At a command prompt, run a command similar to the following: CS\BackupAndRestore\bin\Debug\BackupAndRestore.exe The path might vary depending on the options that were used to compile the sample and the starting folder when at command prompt.After you run the sample, the backup file of the temporary database created by the sample will be located at <systemdrive>:\backup_file_generated_by_AMO_sample_code.abf.

Updated Wiki: SS2008!DisplayObjectsName

libinzhao — Thu, 19 Mar 2009 03:28:57 GMT

Readme_DisplayObjectNames Sample

11/05/2008 21:36:06

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
With the DisplayObjectNames sample, you can use Analysis Management Objects (AMO) objects to connect to a server that is running Microsoft SQL Server Analysis Services and then display the names of some of the AMO objects.

Scenario

This sample shows how to create a connection to an Analysis Services server by using AMO objects.

Languages

Features

The Analysis Services sample uses the following items.

Application area	Features
AMOAdventureWorks	AMO Objects

Prerequisites

Before you run this sample, you must have the following software installed:

.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.
Analysis Services
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.
The AdventureWorks AS database. You can download this sample database from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.
The DisplayObjectNames sample. You can download this sample from the Microsoft SQL Server Samples and Community Projects Web site at http://www.codeplex.com. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online. After your sample has been successfully compiled, you will have to access one of the Analysis Services sample databases to test your program. We recommend that you use the AdventureWorks sample database that is provided with SQL Server.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the DisplayObjectNames sample

Build the sample by using Visual Studio 2005 and the provided Visual Studio solution.— or —
Build the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, and run a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/DisplayObjectNames.sln Other MSBuild build options can be used depending on your needs.

Running the Sample

To run the Display Object Names sample

At a command prompt, run a command similar to the following: CS\DisplayObjectNames\bin\Debug\DisplayObjectNames.exe localhost The path might vary depending on the options that are used to compile the sample and your starting folder.

Updated Wiki: SS2008!AMOBrowser

libinzhao — Thu, 19 Mar 2009 03:18:33 GMT

Readme for AMOBrowser Sample

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
The AMOBrowser sample lets you use Analysis Management Objects (AMO) objects to connect to a Microsoft SQL Server Analysis Services server, and then browse different AMO objects and their properties.
AMOBrowser uses a TreeView to display the AMO hierarchy and a PropertyGrid to display the properties of a selected object.

Scenario

This sample shows you how to create a connection to an Analysis Services server by using AMO objects. The sample also shows you how to grab all AMO objects, together with their corresponding properties.

Languages

Features

The Analysis Services sample uses the following items:

Application area	Features
AMOAdventureWorks	AMO Objects

Prerequisites

Before you run this sample, you should have the following software installed:

.NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.
Analysis Services
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.
The AdventureWorks AS database. You can download this sample database from the Microsoft SQL Server Samples and Community Projects Web site at http://www.codeplex.com/sqlserversamples. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.
The AMOBrowser sample. You can download this sample from the Microsoft SQL Server Samples and Community Projects Web site at http://www.codeplex.com/sqlserversamples. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online. After your sample has been successfully compiled, you will have to access one of the Analysis Services sample databases to test your program. We recommend that you use the AdventureWorks sample database that is provided with SQL Server.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the AMOBrowser sample

Build the sample by using Visual Studio 2005 and the provided Visual Studio solution.— or —
Build the sample by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, and executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/AmoBrowser.sln

Running the Sample

To run the AMOBrowser sample

In Visual Studio 2005, press F5. — or —
In Visual Studio 2005, on the Debug menu, click Start.— or —
At a command prompt, run a command similar to the following path: CS\AmoBrowser\bin\Debug\AmoBrowser.exe © 2007 Microsoft Corporation. All rights reserved.

Updated Wiki: SS2008!Readme_AMOAdventureWorks

libinzhao — Thu, 19 Mar 2009 02:56:25 GMT

Readme_AMOAdventureWorks Sample

11/05/2008 21:36:06

This sample works only with SQL Server 2005 and SQL Server 2008. It will not work with any version of SQL Server earlier than SQL Server 2005.
AMOAdventureWorks is a sample C# program that illustrates the use of the Analysis Management Objects (AMO) to create complex OLAP cubes.
Default location: C:\Program Files\Microsoft SQL Server\100\Samples\Analysis Services\Programmability\AMO\AMOAdventureWorks

Scenario

This sample creates a subset of the functionality of the AdventureWorks cube located in the AdventureWorks Analysis Services Project.

Languages

Features

The SQL Server Analysis Services sample uses the following features.

Application Area	Features
AMOAdventureWorks	AMO

Prerequisites

Before you run this sample, you should have Microsoft SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.
Updated versions of the following SQL Server sample database: the AdventureWorksDW data warehouse. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.
Updated versions of the following SQL Server samples: Analysis Services and SQL Server Database Engine. You can download these samples from the Microsoft SQL Server Samples and Community Projects Web site at http://www.codeplex.com. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online. You also must have .NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the AMOAdventureWorks sample

Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution.— or —
Compile the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, by executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/AMOAdventureWorks.sln Other MSBuild build options can be used depending on your needs.

Running the Sample

To run the AMOAdventureWorks sample

In Visual Studio 2005, press F5.— or —
In Visual Studio 2005, on the Debug menu, click Start.— or —
At a command prompt, use the change directory (CD) command to go to the folder where the sample was built. In that directory, run the following command: AMOAdventureWorks.exe

Updated Wiki: SS2008!Readme_AMOAdventureWorks

libinzhao — Wed, 18 Mar 2009 03:41:50 GMT

Readme_AMOAdventureWorks Sample

Scenario

This sample creates a subset of the functionality of the AdventureWorks cube located in the AdventureWorks Analysis Services Project.

Languages

Features

The SQL Server Analysis Services sample uses the following features.

Application Area	Features
AMOAdventureWorks	AMO

Prerequisites

Before you run this sample, you should have Microsoft SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on computers that run the Itanium-based operating system; the 64-bit development environment is supported on x64-based operating systems. SQL Server samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based operating system.
Updated versions of the following SQL Server sample database: the AdventureWorksDW data warehouse, the AdventureWorksAS OLAP database, and the AdventureWorks database. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online.
Updated versions of the following SQL Server samples: Analysis Services and SQL Server Database Engine. You can download these samples from the Microsoft SQL Server Samples and Community Projects Web site at http://www.codeplex.com. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases in SQL Server Books Online. You also must have .NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK in SQL Server Books Online.

Building the Sample

If you have not already created a strong name key file, generate the key file using the following instructions.

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the AMOAdventureWorks sample

Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution.— or —
Compile the sample using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0, by executing a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS/AMOAdventureWorks.sln Other MSBuild build options can be used depending on your needs.

Running the Sample

To run the AMOAdventureWorks sample

In Visual Studio 2005, press F5.— or —
In Visual Studio 2005, on the Debug menu, click Start.— or —
At a command prompt, use the change directory (CD) command to go to the folder where the sample was built. In that directory, run the following command: AMOAdventureWorks.exe

Updated Wiki: Home

ReedMe — Fri, 06 Mar 2009 19:43:52 GMT

Administrator

Sample	SQL Server 2005	SQL Server 2008
Activity Viewer	SS2005	n/a
Aggregation Manager Sample	SS2005	n/a
Analysis Services Upgrade Verification Tool Sample	SS2005	n/a
ASTrace Utility Sample	SS2005	n/a
Command-line Utility Sample	SS2005	SQL Server 2008 SR1

Data Mining

Sample	SQL Server 2005	SQL Server 2008
Data Mining Web Controls Library	SS2005	n/a
SQL Server Plug-In Algorithms	SS2005	n/a

Extensibility

Sample	SQL Server 2005	SQL Server 2008
Analysis Services Personalization Extensions Sample	n/a	SS2008

Programmability

Sample	SQL Server 2005	SQL Server 2008
AMOBrowser	SS2005	SS2008
BackupAndRestore	SS2005	SS2008
DisplayObjectsName	SS2005	SS2008
AS Simple Sample	SS2005	SS2008
AMOAdventureWorks	SS2005	SS2008

Got questions? Want to contribute? Check out the SQL Server Community & Samples Discussion Forum!

Updated Wiki: Home

ReedMe — Thu, 29 Jan 2009 23:01:13 GMT

Administrator

Sample	SQL Server 2005	SQL Server 2008
Activity Viewer	SS2005	n/a
Aggregation Manager Sample	SS2005	n/a
Analysis Services Upgrade Verification Tool Sample	SS2005	n/a
ASTrace Utility Sample	SS2005	n/a
Command-line Utility Sample	SS2005	SQL Server 2008 SR1

Data Mining

Sample	SQL Server 2005	SQL Server 2008
Data Mining Web Controls Library	SS2005	n/a
SQL Server Plug-In Algorithms	SS2005	n/a

Extensibility

Sample	SQL Server 2005	SQL Server 2008
Analysis Services Personalization Extensions Sample	n/a	SS2008

Programmability

Sample	SQL Server 2005	SQL Server 2008
AMOBrowser	SS2005	n/a
BackupAndRestore	SS2005	SS2008
DisplayObjectsName	SS2005	SS2008
AS Simple Sample	SS2005	SS2008
AMOAdventureWorks	SS2005	SS2008

Got questions? Want to contribute? Check out the SQL Server Community & Samples Discussion Forum!

Updated Wiki: Home

carlrabeler — Sat, 15 Nov 2008 00:04:01 GMT

Administrator

Sample	SQL Server 2005	SQL Server 2008
Activity Viewer	SS2005	n/a
Aggregation Manager Sample	SS2005	n/a
Analysis Services Upgrade Verification Tool Sample	SS2005	n/a
ASTrace Utility Sample	SS2005	n/a
Command-line Utility Sample	SS2005	SQL Server 2008 Samples Refresh 1

Data Mining

Sample	SQL Server 2005	SQL Server 2008
Data Mining Web Controls Library	SS2005	n/a
SQL Server Plug-In Algorithms	SS2005	n/a

Extensibility

Sample	SQL Server 2005	SQL Server 2008
Analysis Services Personalization Extensions Sample	n/a	SS2008

Programmability

Sample	SQL Server 2005	SQL Server 2008
AMOBrowser	SS2005	n/a
BackupAndRestore	SS2005	SS2008
DisplayObjectsName	SS2005	SS2008
AS Simple Sample	SS2005	SS2008
AMOAdventureWorks	SS2005	SS2008

Updated Wiki: SS2008!Readme for Analysis Services Personalization Extensions Sample

bonniefe — Thu, 06 Nov 2008 23:18:04 GMT

Readme_Analysis Services Personalization Extensions Sample

Scenario

Languages

Features

The Analysis Services Personalization Extensions Sample uses the following features of SQL Server 2008 Analysis Services (SSAS).

Application Area	Features
AdventureWorks	ADOMD.NET Server, MDX

Prerequisites

Before you run this sample, you should have SQL Server and the following SQL Server components installed:

SQL Server Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio Note: Business Intelligence Development Studio is not supported on Itanium-based computers. The 64-bit development environment is supported on x64-based operating systems. SQL Server 2005 samples can be modified and run on computers that run either x86 or x64-based operating systems when databases used by the samples are deployed on an Itanium-based computer.
Updated versions of the following SQL Server sample databases: the AdventureWorks data warehouse and the AdventureWorks database. You can download these sample databases from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install sample databases, see Installing SQL Server Samples and Sample Databases.
Updated versions of the following SQL Server samples: Analysis Services samples and SQL Server Database Engine samples. You can download these samples from the Microsoft SQL Server Samples and Community Projects Web site. For more information about how to download and install samples, see Installing SQL Server Samples and Sample Databases. You also need .NET Framework SDK 2.0 or Microsoft Visual Studio 2005 installed. You can obtain .NET Framework SDK free of charge. For more information, see Installing the .NET Framework SDK

Building the Sample

To generate a strong name key file

Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.-- or --Open a Microsoft .NET Framework command prompt. Click Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click SDK Command Prompt.
Use the change directory command (CD) to change the current directory of the command prompt window to the folder where the samples are installed. Note: To determine the folder where samples are located, click the Start button, point to All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click Samples Directory. If the default installation location was used, the samples are located in <system_drive>:\Program Files\Microsoft SQL Server\100\Samples.
At the command prompt, run the following command to generate the key file: sn -k SampleKey.snk Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.

To build the Analysis Services Personalization Extensions Sample

Rename SampleKey.snk to ASPE.snk and move the file to the same location where ASPE.sln is.
Compile ASPE.dll by using:
Visual Studio 2005 and the ASPE.sln file. — or —
Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Change directory to the location where the solution file ASPE.sln is located. Run a command similar to the following at a command prompt: msbuild /nologo /verbosity:quiet /property:Configuration=Debug ASPE.sln You can use other MSBuild build options depending on your needs.

Deploying the Sample

To deploy the Analysis Services Personalization Extensions sample, you must add the assembly that you built in the previous procedure to a running instance of Analysis Services.

To add ASPE.dll assembly to a running instance of Analysis Services

In SQL Server Management Studio, connect to the instance of Analysis Services.Localhost is assumed as the default instance for this sample. Replace localhost in with the name of the instance that you have selected.
At the server level, open the Assemblies folder and verify that the ASPE assembly is not listed.If the ASPE assembly is listed, remove this assembly by right-clicking the assembly and selecting Delete. Continue following the steps on the screen.
Right-click Assemblies and select New Assembly.
In the Register Server Assembly dialog box, select the following options:
For Type, select .NET Assembly.
For Filename, click the browse button … and find the ASPE.dll file in your project folder under bin/debug folders.
For Permissions, select Unrestricted.
For Impersonation, select Use the Service Account.
Click OK.

At the server level, open the Assemblies folder and verify the ASPE assembly is listed.
To enable the correct management of all events, open SQL Server Configuration Manager, select SQL Server Services, and then select the SQL Server Analysis Services row. Click the restart button to restart the service

Preparing the Environment to Test the Sample

On the same server where you are running Analysis Services and have deployed ASPE.dll, use the following procedures to set up the environment to test the sample.

To add three users to your current system

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Right-click the Users folder and select New User.
In the New User dialog box, select the following options:
For User name, type user1.
For Password, type a strong password that meets your company standards.
For Confirm password, re-type your selected password.
Clear the User must change password at next logon check box.
Select the Password never expires check box.
Repeat step 4 for user2 and user3.

To verify Adventure Works DW database is deployed and contains Adventure Works cube

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server name, localhost.
Expand the Databases node and verify that the Adventure Works DW database exists.
Expand the Adventure Works DW node, expand the Cubes node, and verify that the Adventure Works cube exists.
Right-click the Adventure Works cube and select Properties. Verify that the cube State is Processed.
If any one of the previous steps cannot be completed, see the Books Online topic, Running Setup to Install AdventureWorks Sample Databases and Samples, in the MSDN Library.

To add a role for the new users and give them access to the cube and dimensions

On an Analysis Services instance, open SQL Server Management Studio and connect to the Server Name, localhost.
Expand the Databases node, and then expand the Adventure Works DW database.
Right-click Roles, and then select New role.
In the Create Role dialog box, click the General page, and select the following options:
For Role name, type ASPE Test Users.
Select the Read definition check box.
Clear the Full control (Administrator) and Process database check boxes.
Click the Membership page, and select the following options:
Click Add.
In the Select Users or Groups window, for Enter the object names to select, type user1; user2; user3.
Click Check Names. The values should now appear underlined, with the server or domain name in front of each name.
Click OK.

Click the Data Sources page. In the Access column for the Adventure Works DW row, select Read.
Click the Cubes page, and select the following options for the Adventure Works row:
In the Access column, select Read.
In the Local Cube/Drillthrough Access column, select Drillthrough and Local Cube. Click OK to accept the message.
In the Process column, select the check box.
Click the Dimensions page. For each of the rows in Dimensions, select the Process column check box.
Click OK, and then wait until the command is processed and the new role is created.

Testing the Sample

Testing the sample demonstrates that new personalization objects are created in different user contexts and that those objects are associated with the user profile.

To verify your context

In SQL Server Management Studio, connect to the Server Name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server Name, localhost.
On the SQL Server Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node.
Expand the Internet Sales node, and verify that there is no ISV_1 folder under this node.
Expand the Geography dimension, and verify that there is no ISV_1 folder in this dimension.
Expand the Product dimension, and verify that there is no ISV_1 folder in this dimension.

To verify the context for user1

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user1. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user1 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the SQL Server Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if it is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, and then expand the Internet Sales node to see the ISV_1 folder.Unlike your user context, user1 has an *ISV_1 *folder under the Internet Sales node.
Expand the ISV_1 folder, expand the Common folder. Notice the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, expand the ISV_1 folder, and then expand the Operations folder.Notice that the Operations folder contains the Average Item Freight Cost member.
Expand the Geography dimension, expand the ISV_1 folder, and then expand the Common folder to see the ISV_1 - Western Coast set.Unlike your user context, user1 does have access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Operations folder to see the Touring Bikes set.Unlike your user context, user1 has access to the Touring Bikes set.

To verify the context for user2

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user2. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user2 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select the Adventure Works DW database if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube if it is not already selected.
Select the Metadata tab if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV_1 folder, and expand the Common folder. Notice the Gross Internet Profit member is also visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV_1 folder in this group.Only user1 has an ISV_1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, expand the ISV_1 folder, and then expand the Finance folder to see the *Rate Difference *member.Notice that for user2 only, the Exchange Rates measure group has an ISV_1 folder.
Expand the Geography dimension, expand the ISV_1 folder, and then expand the Common folder to see the ISV_1 - Western Coast set.Notice that user2, just like user1, has access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Finance folder to see the Mountain Bikes set.While user2 has access to the Mountain Bikes set, user2 does not have access to the Touring Bikes set in the Operations folder. Only user1 has access to the Touring Bikes set.

To verify the context for user3

Users running Windows XP or Windows Server 2003. Right-click the SQL Server Management Studio icon, select Run as, and then select the following options:
Select The following user.
Replace with user3. Make sure that the domain or server name is correct.
Proceed to step 3.
Users running Windows Vista or Windows Server 2008. Open a command window and run the following command: runas.exe /profile /user: <Domain> \user3 " <Path-to-ssms> \Ssms.exe"
Replace <Domain> with the correct domain or server name.
Replace <Path-to-ssms> with the complete path to ssms.exe, the executable file for SQL Server Management Studio. Note: Windows Vista and Windows Server 2008 no longer have the Run as option when you right-click an application.
Ensure that Server type is set to Analysis Services, then connect to the Server name, localhost.
On the Standard toolbar, click Analysis Services MDX Query.
Connect to the Server name, localhost.
On the Analysis Services toolbar, select Adventure Works DW database, if it is not already selected.
In the left pane of the MDX tab, in the Cube list, select the Adventure Works cube, if is not already selected.
Select the Metadata tab, if it is not already selected.
Expand the Measures node, expand the Internet Sales node, expand the ISV_1 folder, and expand the Common folder. Notice that the Gross Internet Profit member is visible to this user.
Return to the Measures node and expand the Reseller Sales measure group, and verify that there is no ISV_1 folder in this group.Only user1 has an ISV_1 folder in the Reseller Sales measure group.
Return to the Measures node and expand the Exchange Rates measure group, and verify that there is no ISV_1 folder in this group.Only user2 has an ISV_1 folder in the Exchange Rates measure group.
Return to the Measures node and expand the Reseller Orders measure group, expand the ISV_1 folder, and then expand the Marketing folder to see the Reseller Discount per Order member.Notice that for user3 only, the Reseller Orders measure group has an ISV_1 folder.
Expand the Geography dimension, expand the ISV_1 folder, and expand the Common folder to see ISV_1 - Western Coast set.user3, just like user1 and user2, has access to the ISV_1 - Western Coast set.
Expand the Product dimension, expand the ISV_1 folder, and then expand the Marketing folder to see the All Terrain Bikes set.While user3 has access to the All Terrain Bikes set, user3 does not have access to the Touring Bikes set in the Operation folder. Only user1 has access to the Touring Bikes set. User3 also has access to the Mountain Bikes set in the Finance folder. It is user2 who has no access to the All Terrain Bikes set.

Troubleshooting the Sample

Use the following set of procedures to troubleshoot the Analysis Services Personalization Extensions sample.

To define debug breakpoints in the code

In Visual Studio 2005, open ASPE.sln.
Open the source code for the ASClientExtensions.cs source file, and then set a breakpoint on the opening brace of the ASClientExtensions constructor.
Open the source code for the SessionMgr.cs source file, and then set the following breakpoints:
Set a breakpoint on the opening brace of the SessionMgr constructor.
Set a breakpoint on the opening brace of the CubeOpened method.
Open the source code for the AuthoringAndManagement.cs source file, and then set the following breakpoints.
Set a breakpoint on the opening brace of the AuthoringAndManagement constructor.
Set a breakpoint on the opening brace of the DefineMembers method.
Set a breakpoint on the opening brace of the DefineSets method.
Set a breakpoint on the opening brace of the DefineKPIs method.

To attach to the running instance of Analysis Services

In the menu bar, select Debug, and then select Attach to process.
In the Available Processes pane, browse to find msmdsrv.exe, and then select it.
Click Attach, and then wait until the debugger attaches to the running process.

To run through the breakpoints

Repeat all the steps in the procedure, To verify the context for user1.Notice that SQL Server Management Studio does not immediately appear. Instead, Visual Studio opens.
To see the sequence of events, press F11 repeatedly.If there are no more events, check SQL Server Management Studio to continue with the steps in the procedure, To verify the context for user1.

Removing the Sample

Use the following procedure to remove the Analysis Services Personalization Extensions Sample.

To remove the roles and assembly from the current Analysis Services instance

Open SQL Server Management Studio.
Connect to the Server Name, localhost
Expand the Databases node, and then expand Adventure Works DW database.
Expand Roles, right-click ASPE Test Users, select Delete, and then click OK.
At server level, expand Assemblies, right-click ASPE, select Delete, and then click OK.
Close SQL Server Management Studio.
Restart the service

To remove the user created for this sample

Click Start, right-click My Computer, and select Manage.
Expand Local Users and Groups to see the Users and Groups folders.
Expand the Users folder.
Remove user1, user2, user3 by right-clicking each user, selecting Delete, and then clicking OK.

To remove the ASPE sample

Updated Wiki: SS2005!Readme for SQL Server Plug-In Algorithms

bonniefe — Thu, 06 Nov 2008 23:17:45 GMT

Readme for SQL Server Plug-In Algorithms

Updated: 17 July 2006
Microsoft provides a complete framework that enables third-party data mining providers to integrate the following data mining objects into Analysis Services:

Data mining algorithms, known as plug-in algorithms.
Data mining viewers, known as plug-in viewers.
Data Mining Web Controls Library, a library that extends data mining viewers to the Web. For more information, see Data Mining Web Controls Library in SQL Server 2005 Books Online. To help you understand how to implement data mining algorithms and viewers into Analysis Services, this readme provides instructions for the following samples:

Data Mining Algorithm Plug-InThis sample allows data mining algorithm developers to concentrate on the algorithm instead of on the implementation issues. Data Mining Viewer Plug-InThis sample allows third-party algorithm providers to use their own viewers to display their new discovered patterns. The documents and source code associated with each of these samples are located in the C:\Program Files\Microsoft SQL Server\90\Samples\Analysis Services\DataMining\SQL Server Data Mining Plug-In Algorithms folder. Included in this folder are tutorials that describe how to implement and use each of these samples.

Note:

| By default, the samples are not installed. To install samples, run Setup and use the Advanced option as described in the topic Running Setup to Install AdventureWorks Sample Databases and Samples in SQL Server 2005 Books Online. An updated version of AdventureWorks database is also available for download on the Web page.
An updated version of the SQL Server 2005 Database Engine samples is also available for download on the Web page. |

Note:
SQL Server 2005 Business Intelligence Development Studio is not supported on computers that run the Itanium-based platform; the 64-bit development environment is supported on x64-based platforms. SQL Server 2005 samples can be modified and run on computers that run either x86 or x64-based platforms when databases used by the samples are deployed on an Itanium-based platform.

Scenario

A provider wants to integrate a new data mining algorithm, which is named Pair-wise Linear Regression, into Analysis Services. After integrating this new algorithm into Analysis Services, the provider wants add a new viewer for the Pair-wise Linear Regression algorithm.

Languages

C++, for the algorithms.
C#, for the viewer.

Features

Algorithm Plug-In

Interface	Explanation
IDMAlgorithm	Implements both a model-producing learning algorithm and the prediction operations of the resulting model.
IDMAlgorithmNavigation	Enables browsers to access the content of your model.
IDMPersist	Enables the models learned by your algorithm to be saved and loaded by Analysis Services.
IDMAlgorithmMetadata	Describes the capabilities and input parameters of your learning algorithm.
IDMAlgorithmFactory	Creates instances of the objects that implement the algorithm interface and provides Analysis Services access to the algorithm metadata interface.

Viewer Plug-In

Interface	Explanation
IMiningModelViewerControl	Implements the viewer.

Prerequisites

Before you run this sample, you should have the following software is installed:

Microsoft SQL Server 2005, which includes the following components:
SQL Server 2005 Database Engine
Analysis Services
SQL Server Management Studio
Business Intelligence Development Studio
Two sample databases—AdventureWorksDW (data warehouse) and AdventureWorks (OLTP)
Analysis Services Samples
Adventure Works DW sample Analysis Services project, deployed to an instance of Analysis Services
An updated version of AdventureWorks database is also available for download on the SQL Server Developer Center Web page.
An updated version of the SQL Server 2005 Database Engine samples is also available for download on the SQL Server Developer Center Web page.

Building the Samples

Before building the plug-in samples, you must deploy both the AdventureWorksDW (data warehouse) and AdventureWorks (OLTP) databases.

To deploy the Adventure Works DW and AdventureWorks sample databases

In Windows Explorer, open C:\Program Files\Microsoft SQL Server\90\Tools\Samples, and then double-click the SQLServerSamples.msi file.
In Windows Explorer, open C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks Analysis Services Project, open the folder corresponding to the version of SQL Server that has been installed, and then double-click the Adventure Works.sln file. The Adventure Works DW project opens in Business Intelligence Development Studio.
Press F5 to build and deploy the project. Note: Building and deploying the AdventureWorksAS project deploys the mining model to the server.After you deploy the databases, you can implement the algorithm and viewer plug-ins.

To implement and use the data mining algorithm plug-ins

In Windows Explorer, open C:\Program Files\Microsoft SQL Server\90\Samples\Analysis Services\DataMining\SQL Server Data Mining Plug-In Algorithms, and then double-click the SQL Server Data Mining Plug-In Algorithms Tutorial.doc file. Note: Implementing the plug-in sample might be easier for you if you print the tutorial and then use the printout to complete the tutorial.
To build the Pair-wise Linear Regression Algorithm plug-in, complete Chapter 6, "Building a Shell Plug-In Algorithm" in the tutorial.
To customize the Pair-wise Linear Regression Algorithm plug-in, complete Chapter 7, "Customizing the Algorithm: Pair-wise Linear Regression" in the tutorial.
To use the customized Pair-wise Linear Regression Algorithm plug-in, complete Chapter 8, "Using the Customized Plug-In Algorithm" in the tutorial.

To implement the proprietary viewer

In Windows Explorer, locate C:\Program Files\Microsoft SQL Server\90\Samples\Analysis Services\DataMining\SQL Server Data Mining Plug-In Algorithms, and then double-click the SQL Server Data Mining Plug-In Viewers Tutorial.doc file. Note: Implementing the plug-in sample might be easier for you if you print the tutorial and then use the printout to complete the tutorial.
Complete all steps in the tutorial.

Comments

To obtain a better understanding about how to implement plug-in algorithms, read the file, SQL Server Data Mining Plug-In Algorithms Whitepaper.doc, which is included with the sample tutorials.

Change History

Release	History
17 July 2006	New content: Added note on availability for Itanium-based platform.