vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 – Part 1

Page content

vCenter-5.5 on Windows Server 2012 R2 with SQL Server 2014 Part 1

It has been a while since I was dealing with vCenter on SQL Server simply because I used vCenter Server appliance. In series of post, I would like to guide you through the installation of Microsoft SQL Server 2014, vCenter database creation and preparation and vCenter 5.5 Update 2 installation.

In my guide I will use following software:

  • Operating System - Windows Server 2012 R2 Datacenter Edition
  • Database - Microsoft SQL Server 2014 Enterprise Edition
  • VMware - VMware vSphere 5.5 Update 2b

Microsoft SQL Server 2014 preparation

Following Microsoft SQL Server best practices  I will install SQL Server 2014 with following disk layout:

  • Disk 1 : OS/SQL Binaries
  • Disk 2: System databases (aside from tempdb)
  • Disk 3: tempdb
  • Disk 4: User databases
  • Disk 5: User DB transaction logs
  • Disk 6 : VMware vCenter Server binaries

vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 1

  1. Before installation, I recommend running System Configuration Checker. It is a tool which checks if all necessary components required by SQL Server 2014 are installed.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 2

  2. Another thing that we have to do before installation is enabling of.Net Framework 3.5 Service Pack 1. We can do it simply from PowerShell by executing following command.
Install-WindowsFeature Net-Framework-Core -Source D:\sources\sxs

vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 3

  1. We will create application users: **ap-mssql **and ap-vcenter and we will use it to run SQL Server services and vCenter services. I described how to do it in this post: https://www.wojcieh.net/how-to-create-application-user-in-active-directory/

Microsoft SQL Server 2014 installation

  1. We switch to Installation section and select New SQL Server stand-alone installation or add features to existing installation.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 3

  2. Provide SQL Server 2014 product key or select evaluation.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 4

  3. Accept the license terms and if you want you can join **Customer Experience Improvement Program **also called CEIP.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 5

  4. Choose if you want to receive Microsoft Updates to patch SQL Server 2014.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 6

  5. Click next and Setup will initiate another check to make sure that there will be no problems.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 7

  6. Click next and select SQL Server Feature Installation

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 8

  7. Choose following features:
    • Database Engine Services
    • Client Tools Connectivity
    • Integration Services
    • Management Tools – Basic
    • Management Tools – Complete

      vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 9

  8. And select following directories:

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 10

  9. In Instance Configuration, I selected Default instance and I clicked Next.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 11

  10. To run all SQL services we will use user called ap-mssql.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 12

  11. I added my user as SQL Server administrator. I selected Windows authentication mode.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 13

  12. As I wrote at the beginning I will distribute directories across different disks.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 14

    13 .Select Install and watch the progress.

    vCenter 5.5 on Windows Server 2012 R2 with SQL Server 2014 - 15

Summary

This concludes the installation of Microsoft SQL Server 2014 on Windows Server 2012 R2. In the next post, I will proceed with SQL Server configuration.