Once the installer for the AdventureWorks Community Sample Database has finished, we then need to complete the process (not mandatory, but nice to do to play with the OLAP content).
The first thing we need to do is make sure we note the location of the script files and samples.
The path if you are working with SQL Server 2008 R2 is as follows:
“C:\Program Files\Microsoft SQL Server\100\Tools\Samples\AdventureWorks 2008R2 Analysis Services Project\enterprise”
I am working with the developer edition, so the enterprise path works for both Enterprise and Developer edition. There is also a path for Standard.
Once I get to that location I will double click on the Adventure Works.sln file. This will open Business Intelligence Development Studio. Take time to review the artifacts that are part of the solution.
The next step is to make sure the Adventure Works.ds file points to the correct server. To edit, we can do a right-click and select Open, then Edit
The edit screen is as follows
Click Test Connection to make sure we have the correct server instance and have access to the database.
Now that we have validated connection information, we can proceed to deploy. Let’s validate the correct server information is set in the deployment properties. We will right-click the Solution name, and select Properties. From the Configuration Properties, select Deployment, and check the values in the Target Server and Database fields. If not pointing to the correct values, change them to read as you need them.
We are ready to deploy, once again, right-click on the Solution Name, and select Deploy.
When deployment starts, you will see a Deployment Process dialog. It will change values as it moves along the artifacts to deploy.
Once complete you will see the following:
This means deployment has completed and it was successful. To validate, open SQL Server Management Studio, at the logon screen, make sure your values are as follows: (make sure it points to the information that corresponds to your deployment
We need to see the following
This confirms the deployment was successful.