Use vCenter Media to Install Standalone SQL 2005 Express and SQL Native Client
September 17th, 2009 | 
Author: Every once in a while I end up installing a standalone instance of SQL 2005 Express. It could be for the back end database of a virtualized vCenter or a separated instance of VMware Update Manager (VUM). In the past I have wasted time waiting to download the .NET Framework, SQL 2005 Express, and the SQL Native Client from the web, but I recently explored the vCenter 4 install DVD and discovered those components are all already there on the media! I knew all of these were automatically called by the vCenter installer, but I had no idea I could easily invoke these pieces independently and therefore eliminate the downloads.
Here is an overview for installing a standalone instance of SQL 2005 Express using the vCenter media with some screen shots. I also briefly mention using the free SQL Server Management Studio Express edition to easily create multiple databases, logins, and permissions. Finally I skim through enabling remote connections and creating ODBC connections for the vCenter and / or VUM installation.
| Browsing the Media Put the vCenter media in the server’s DVD drive that will become the standalone database instance. (or mount the .iso if a VM) Both the dotnet fix and the SQL Express installers can be found in the d:\redist folder on the VIM media. |
 |
| Installing SQL 2005 Express Before installing SQL Express you need the dotnet fix. Run dotnetfx30SP1setup in the dotnet sub folder. |
 |
| After that you are ready to switch to the SQLEXPR sub directory and install SQL Express 2005. Start the install from the appropriate folder for your server OS – either 32 bit or 64 bit. |  |
| Install SQL Native Client Back on your vCenter server, just run the first part of the SQLEXPR install to get the SQL Native Client and Support Files. You’ll be given the opportunity to cancel the full Express install after that. |
 |
| SQL Server Management Studio Express
Go ahead and download SQL Management Studio Express, and use it to create separate databases for vcenter and VUM |
 |
| Enable Remote Connections Be sure to enable remote connections by following the instructions found at http://www.linglom.com/2007/08/31/enable-remote-connection-to-sql-server-2005-express/ Although it does not say so, I found that I had to restart my SQLEXPR database instance after following that post. Using the SQL 2005 Express Studio again, right click the instance and click restart. |
 |
| ODBC Configure the System ODBC connections with the SQL Native driver on the vCenter server |
|
| Create a separate ODBC connection for vCenter and VUM |  |
| Installing vCenter and VUM When you finally install vCenter and VUM select “use an existing supported database” and the installer should pre populate the configured ODBC connections. |
 |
Posted in 
Tags: 
It's good how-to Rich…
I wonder why is better to separate the SQL database for VUM and vCenter… Keep the updates apart of vCenter.. ?
And also what do you mean by “back end database of a virtualized vCenter”.
Vladan,
Different tables and fields and unrelated data would be my guess. Plus
the mobility/felxibility to put VUM on a standalone server for
complex, multi ip subnet, or heavy security environments.
The VUM dbase is primarily for the patch repository and status of
patches and updates, I guess? Never really looked at the tables that
close …
It's good how-to Rich…
I wonder why is better to separate the SQL database for VUM and vCenter… Keep the updates apart of vCenter.. ?
And also what do you mean by “back end database of a virtualized vCenter”.
Vladan,
Different tables and fields and unrelated data would be my guess. Plus
the mobility/felxibility to put VUM on a standalone server for
complex, multi ip subnet, or heavy security environments.
The VUM dbase is primarily for the patch repository and status of
patches and updates, I guess? Never really looked at the tables that
close …