Information Technology Reference
In-Depth Information
Creating the Open Database Connectivity Data Source Name
After you coni gure the separate database server, you must create an ODBC DSN to connect to
the backend database. You'll need to have the ODBC DSN created before you start VUM instal-
lation, and because VUM is a 32-bit application, the ODBC DSN must be a 32-bit DSN. This is
true even though VUM installs only on a 64-bit version of Windows.
Perform the following steps to create an ODBC DSN for the VUM database:
1.
Run the 32-bit ODBC Data Source Administrator application found at %systemroot%\
SysWOW64\odbcad32.exe.
The 32-bit ODBC Data Source Administrator application looks identical to the 64-bit ver-
sion. If you're unsure which one you launched, exit and restart to be sure that you have
the correct version.
Is There Any Way to Tell the Difference?
h ere is a way to tell the diff erence between the 64-bit and 32-bit versions of the ODBC Data Source
Administrator application: h e 64-bit and 32-bit system DSNs are not shared between the two
applications. So, if you see your vCenter Server DSN listed on the System DSN tab, you're running
the 64-bit version of the tool (because vCenter Server requires a 64-bit DSN).
2.
Select the System DSN tab.
3.
Click the Add button.
4.
From the list of available drivers, select the correct driver for the database server you're
using.
As with vCenter Server, you will need to ensure that the correct ODBC driver is installed
for the database server hosting the VUM database. SQL Server 2005, 2008, and 2012 all
have their own optimized SQL Server Native Client. Make sure the appropriate Native
Client is installed.
5.
On the i rst screen of the Create A New Data Source Wizard, i ll in the name of the DSN,
a description, and the name of the server to which this DSN will connect.
Be sure to make a note of the DSN name; you'll need this information later. Click Next
when you're i nished.
6.
On the next screen you need to supply an authentication type and credentials to connect
to the separate database server. Select With SQL Server Authentication Using A Login
ID And Password Entered By The User, and specify an SQL login and password that are
valid on the database server and that have the appropriate permissions assigned to the
VUM and MSDB databases. Click Next.
Windows Integrated Authentication is an option only if you have installed the database
server component locally on the same server as VUM. It is advised that you use SQL
Server Authentication in all cases, even if the database is local, because it makes mov-
ing the database easier in the future should your environment grow and require scaling
beyond a local instance.
