SQL Clone
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

SQL Server 2012 and SharePoint 2013: Installing on a Virtual Machine

With the preview of SharePoint 2013 now available, I have updated my post SQL Server 2012: Installing on a Virtual Machine to use SharePoint 2013 instead of SharePoint 2010.  If you would like to get a head start on learning what is new with SharePoint 2013 and Excel 2013, follow the instructions below to create a virtual machine where you can play with the following products: Windows Server 2008 R2 Enterprise x64 (setup as a domain controller), SQL Server 2012 Enterprise x64 SP1 CTP3, SharePoint 2013, PerformancePoint, Power View, PowerPivot, SSRS (SharePoint mode), Report Builder, SSAS (Tabular mode), and SSDT.

  1. The first thing I did was follow Jonathan Kehayias’s post Building a Completely Free Playground for SQL Server – (1 of 3) – Downloading the Software and Setting up a Windows Server 2008R2 VM Template to create a template, or base, VM using Windows Server 2008 R2 Enterprise, 64-bit (you must use 64-bit for SharePoint 2013).  Use VirtualBox for your VM, since Microsoft Virtual PC does not support 64-bit.  Make sure to change the computer name to something other than the default, since the default name is usually hard to remember
  2. Next I cloned the template VM from step 1 to create another VM and will make this a domain controller.  Then I followed the post Step By Step Guide for Windows Server 2008 Domain Controller and DNS Server Setup (or check out this video) to set up the VM as a domain controller, which is required by SharePoint 2013 for these reasons:
    1. A PowerPivot installation integrated with SharePoint requires the SSAS PowerPivot service account to be a domain user that can manage the installation through Central Administration
    2. I have always found that it is significantly easier to setup all of the BI services if there is a separate domain account for each core group of services.  This makes it easy to manage the accounts and ensure that the services remain isolated from each other
  3. Downloaded SQL Server 2012 SP1 CTP.  You need SQL Server 2012 Service Pack 1 in order to integrate the BI features (PowerPivot for SharePoint and SSRS) with SharePoint 2013. If you run the RTM version of SQL Server 2012 setup, you won’t get too far because it will fail the installation rule that SharePoint 2010 is required. That’s because the setup doesn’t know anything about SharePoint 2013 and the latest release includes major architectural changes
  4. Followed the steps at SQL Server 2012 (RC0) Business Intelligence Configuration for setting up the domain accounts to use in the SQL Server installation. See SQL Server 2012 (RC0) Installation and Configuration for the way you should use these domain accounts when installing SQL Server in step #6
  5. Downloaded SharePoint 2013 at Download Microsoft SharePoint Server 2013 Preview
  6. Followed the steps at Installing the BI features of SharePoint 2013 Preview. Make sure to also choose SQL Server Data Tools on the Features Selection menu
  7. Created a SSRS report document library and installed Report Builder 3.0 from the steps at Create SSRS Report with SharePoint 2010 Integrated Mode (this is for SharePoint 2010 but it’s very similar to SharePoint 2013)
  8. Download the 64-bit version of Excel 2013 from Excel 2013 Preview (choose Microsoft Office Professional Plus) and install Excel 2013 and Office Shared Features.  NOTE: PowerPivot is now integrated with Excel 2013 so installing the PowerPivot add-in is no longer needed. You just need to enable it via Start PowerPivot in Excel 2013 add-in.  Also a new feature in Excel 2013 is the ability to use Power View: Create a Power View sheet in Excel 2013
  9. I installed SSDT.  I had thought I installed this when I went thru the SQL Server 2012 installation process since it was an option on the Features Selection menu that I selected.  However, this does not install the full SSDT product (SSDT is missing the database project piece), but only a pointer to it that makes SSDT visible when you create a project in Visual Studio 2010.  So to fully install SSDT, follow Install SQL Server Data Tools.  Yes this is very confusing and I blogged about it at SSDT – Installation confusion
  10. Then I installed Microsoft SQL Server 2012 Report Builder.  This installs the stand-alone version of Report Builder and is optional since you can run Report Builder other ways: How to: Start Report Builder (Report Builder 3.0)
  11. Created a business intelligence center site in SharePoint 2013 via Configure a Business Intelligence Center in SharePoint Server 2013 Preview
  12. I then ran Windows Update and installed the many patches

James Serra's Blog

James is a big data and data warehousing technology specialist at Microsoft. He is a thought leader in the use and application of Big Data technologies, including MPP solutions involving hybrid technologies of relational data, Hadoop, and private and public cloud. Previously he was an independent consultant working as a Data Warehouse/Business Intelligence architect and developer. He is a prior SQL Server MVP with over 30 years of IT experience. James is a popular blogger (JamesSerra.com) and speaker, having presented at dozens of PASS events including the PASS Business Analytics conference and the PASS Summit. He is the author of the book “Reporting with Microsoft SQL Server 2012”. He received a Bachelor of Science degree in Computer Engineering from the University of Nevada-Las Vegas.


Leave a comment on the original post [www.jamesserra.com, opens in a new window]

Loading comments...