Part 2: DB Server Configuration

Written by Ross Davies on . Posted in Virtualization

This entry is part 2 of 3 in the series vCenter Installation

Now that vCenter 5.1 Update 1 supports SQL Server 2012 I decided to go ahead and use it over SQL Server 2008 R2.

Your DB server must be set not to force SQL SSL encryption or the SSO installation will likely fail. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2035831

The DB instance will also need to be set to run in mixed mode, allowing both integrated windows authentication and SQL Server authentication to your database instance.

I like to pre-create my databases rather than allowing the application installer to do it – that way I can ensure that they are configured just how I need. I have included my scripts below to allow you to do the same, just replace the passwords & service accounts (as well as changing paths and/or db names to suit you conventions and environment needs).

SSO Database

I chose to name my database “vCenter1_SSO” and used the following script to create the database and configure the SQL server user accounts to access it. Modify this script however you like to configure your environment, but you cannot alter the DB file logical names from RSA_DATA or RSA_INDEX as the SSO application is hardcoded to look for them and it will fail is they do not exist. It’s also noted in the documentation that the RSA_DBA and RSA_USER accounts require at least one lowercase character, one uppercase character, one number, and one special character to be included and the following non-AsCII characters are not supported for use; semicolon (;), double quotation mark (“), single quotation mark (‘), circumflex (^), and backslash ().

[sql]

USE MASTER

GO

CREATE DATABASE [vCenter1_SSO]

CONTAINMENT = NONE

ON  PRIMARY

( NAME = N’RSA_DATA’, FILENAME = N’Y:MSSQLDatavCenter1_SSO_Data.mdf’ , SIZE = 10240KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%),

FILEGROUP [RSA_INDEX]

( NAME = N’RSA_INDEX’, FILENAME = N’Y:MSSQLDatavCenter1_SSO_Index.mdf’ , SIZE = 10240KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)

LOG ON

( NAME = N’translog’, FILENAME = N’Z:MSSQLLogvCenter1_SSO_Log.ldf’ , SIZE = 10240KB , MAXSIZE = 2048GB , FILEGROWTH = 10%)

GO

ALTER DATABASE [vCenter1_SSO] SET COMPATIBILITY_LEVEL = 110

GO

ALTER DATABASE [vCenter1_SSO] SET RECOVERY SIMPLE

GO

USE MASTER

GO

CREATE LOGIN RSA_DBA WITH PASSWORD = ‘Your Password’, DEFAULT_DATABASE = vCenter1_SSO

GO

CREATE LOGIN RSA_USER WITH PASSWORD = ‘Your Password’, DEFAULT_DATABASE = vCenter1_SSO

GO

USE vCenter1_SSO

GO

ALTER AUTHORIZATION ON DATABASE::vCenter1_SSO TO RSA_DBA

GO

CREATE USER RSA_USER FOR LOGIN RSA_USER

GO

CHECKPOINT

GO

[/sql]

vCenter & VUM Databases

[sql]

EXEC(‘CREATE LOGIN [Your DomainYour Service Account] FROM WINDOWS’)

USE MSDB
<span style="font-family: Georgia, ‘Times New Roman’, ‘Bitstream Charter’, Times, serif; font-size: 13px; line-height: 19px;">EXEC sp_grantdbaccess ‘[Your DomainYour Service Account] ‘</span></pre>
EXEC sp_addrolemember db_owner, ‘[Your DomainYour Service Account] ‘
<pre>USE master

create database "vCenter1"

on

( name = ‘vCenter1’,

filename = ‘Y:MSSQLDatavCenter1.mdf’,

size = 2000MB,

filegrowth = 500MB )

log on

( name = ‘vCenter1 log’,

filename = ‘Z:MSSQLLogvCenter1.ldf’,

size = 200MB,

filegrowth = 20MB )

COLLATE SQL_Latin1_General_CP1_CI_AS;

create database "vCenter1_VUM"

on

( name = ‘vCenter1_VUM’,

filename = ‘Y:MSSQLDatavCenter1_VUM.mdf’,

size = 250MB,

filegrowth = 25MB )

log on

( name = ‘vCenter1_VUM log’,

filename = ‘Z:MSSQLLogvCenter1_VUM.ldf’,

size = 25MB,

filegrowth = 2MB )

COLLATE SQL_Latin1_General_CP1_CI_AS;

EXEC(‘ALTER AUTHORIZATION ON DATABASE::"vCenter1" TO [Your DomainYour Service Account]’)

EXEC(‘ALTER AUTHORIZATION ON DATABASE::"vCenter1_VUM" TO [Your DomainYour Service Account]’)

GO

[/sql]

Series Navigation<< Part 1: vCenter installation Planning & Pre-Req’sPart 3: Create Certificates >>

Tags: , , , , , ,

Trackback from your site.

Leave a comment