[00:00:00.00]
Now that the SharePoint software is on the disk and ready to be configured, I’m going to go ahead and run the SQL Installer to load the PowerPivot for SharePoint software, and at the same time that will load in a relational instance that SharePoint will use. From there we’ll just let PowerPivot configure the farm and initialize services.
[00:00:21.19]
I’ve mounted the SQL Server 2012 DVD. I’ll go ahead and run “Setup”. When I get to the product key page, in this case I’ll specify the Evaluation edition. If you have a license key to enter, you can enter that here.
[00:01:12.03]
On the setup support rules page, I can just click “Next”. The setup role is where I want to change from the default of “SQL Server Feature Installation” to “SQL Server PowerPivot for SharePoint”. Then below there’s a checkbox to add the relational engine at the same time. This is going to have the impact that my relational instance will have an instance name of “POWERPIVOT”. If you don’t like that, you can install a relational instance yourself and then come back and run this installer later.
[00:01:42.17]
For me this is fine, because this is a POC environment and it doesn’t matter to me what the instance name is for my relational instance. I’ll go ahead and let the installer do that. You can see the instance features will be preconfigured. Selecting this PowerPivot installation mode is much automated–there’s not that much to change.
[00:02:10.25]
The default paths are fine, since I only have one drive anyway. The named instance is called POWERPIVOT, which you should leave as the default.
[00:02:26.03]
I have plenty of disk space, so I’ll click next on the Disk Space page. For Analysis Services I need to enter my domain account for the SQL Server Analysis Services Account Name. Don’t forget to enter the domain name before the backslash. Enter the password. You could enter a service account for the agent and relational engine, but for a POC environment like this, these accounts are fine. So I’ll now proceed.
[00:03:02.15]
Don’t forget to add your account as a SQL Server administrator so you have access to the engine when you login later. The Data Directories are fine (we only have one drive).
[00:03:13.26]
The same with Analysis Services–don’t forget to give yourself access to it. Click “Next”, “Next” on “Error Reporting”, “Next” on “Installation Rules”, and go ahead and press “Install. From this point we can wait for all the software to be installed. After this is complete we’ll come back and run the PowerPivot configuration tool to get the farm initialized and all services up and running.
[00:03:49.21]
Once the installation wizard completes, just read through the list and make sure everything succeeded– in this case it did. Then close the installation wizard.
At this point we’re done with enough of the SQL install to get PowerPivot up and running. The relational instance is there for us to use to get SharePoint running as well. In the next lesson we’ll go through configuring SharePoint and PowerPivot in one step.
