Sep 172012
 

VMware’s vCenter Server 5.1 requires a new single sign-on server, and it uses a database back-end. For the SQL Server installation, guess what? It’s loaded with problems. I know a LOT of people out there will have issues installing this service, and it’s a pre-requisite for the successful upgrade to vCenter 5.1 Server.

Argh.

I can’t see how anything in this script is a good thing. NEVER auto-shrink a database! Initial size of 10MB and auto-growth by 10%? Putting everything on the C: drive?

Wow… VMware, you’re better than this. I’m disappointed, and I know your support crews are going to be hammered by VMware administrators struggling to get this installed.

This script above also tells me that currently VMware vCenter Single Sign On Server is not supported on SQL Server 2012, as the SP_DBOPTION system proc was removed.

Think about this too… lots of folks will perform default installs of this service, as well as of the other core products, such as Update Manager. You could have quite a number of SQL Server Express instances floating on a vCenter Server without any maintenance or backups taking place.

Be warned! VMware admins – get your SQL Server DBAs involved with this upgrade!

Contact me if you need help installing this…

 Posted by at 7:01 pm  Tagged with:

  3 Responses to “VMware vSphere 5.1 vCenter Single Sign On Server SQL Server Installation Woes”

  1. Uh.. did you not even look at the script before running it??

    — Before running this script, customize the file paths (CHANGE ME) below.
    — 1. Decide on a folder to hold the database files (10 GB of space required).
    — For example, it can be the DATA folder of the SQL Server, usually
    — C:\Program Files\Microsoft SQL Server\MSSQL10_50.\MSSQL\DATA
    — 2. Replace all 3 occurrences of C:\CHANGE ME with the path to the folder

  2. I’m sorry you misinterpreted my post. I have no problems with the syntax of the script itself. I do have problems with the things they set up by default, such as enabling database autoshrink (a huge no-no), and the starting file size at 10MB and auto-growth by 10%. Auto-growth should never be enabled, and they should start the log file at a much larger size (depending on how big the file is expected to grow on average) with a fixed growth size by a reasonable amount. A 10MB file with a 10% autogrowth will create way too many VLFs to help anything.

    Also, it’s really not a good idea to put your database objects on the C: drive anyways. That creates a whole new set of problems, but I’m not going to bash VMware for this one. I always place my database objects on separate drives, usually one or more for database data files and one for logs, but this is freely up to the DBA to determine and called out visibly in this script. The more subtle options, like the database auto-shrink, are the ones that will get you into more immediate trouble.

    I hope this clarifies my stance on this topic. I’ll be releasing some updated documentation in the next month that better describes how to set this database up, as well as the other databases in the vSphere vCenter 5.1 bundle.

  3. Hello !
    They doesn´t support Windows Authentication !! That sucks !!!!