• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1273
  • Last Modified:

vCenter 4.1 - Can I create a 64 bit DSN to a 32 bit SQL 2005 server?

We are switching to a 64 bit server for vCenter 4.1 (Windows Server 2008 R2).  The documentation for the vCenter server installation says it requires a 64 bit DSN to the SQL database (which in our case is MS SQL Server 2005 32-bit).  Is this possible?  If so, how can I accomplish this?
0
waverazor
Asked:
waverazor
  • 4
  • 4
  • 3
1 Solution
 
Luciano PatrãoICT Senior Infraestructure Engineer Commented:
Hi

I think this is what you need

http://kb.vmware.com/kb/1010401

Jail
0
 
bgoeringCommented:
If you create it on a 64 bit system with the standard admin tools -> ODBC administrator it is a 64 bit DSN. As you further along it may ask for a 32-bit DSN for VMware Update Manager if you are installing that component. Follow the steps in the article Bestway listed above to access the 32-bit ODBC admin tool

Good Luck
0
 
waverazorAuthor Commented:
Thank you for the comments, but...

Bestway - I am not trying to make a 32bit DSN on my server.

bgoering - I did as you suggested, but the vCenter install says the following:

"The DSN is pointing to an unsupported ODBC driver.  Please re-configure your DSN to use one of the supported drivers."

So my next question is: where do I get the 64bit ODBC driver?
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
waverazorAuthor Commented:
I solved my issue.  I used the Microsoft SQL Server Native Client X64 Package (sqlncli_x64.msi) - 6486 KB.  Located at: Microsoft SQL Server 2005 Feature Pack

Thank you for your comments & assistance!
0
 
Luciano PatrãoICT Senior Infraestructure Engineer Commented:
Hi

But you said you have a 64-bit server and need to implement the vCenter into a SQL 2005 32-bit right? So you need to create a ODBC 32 bit.

Jail
0
 
bgoeringCommented:
@Bestway - he needs a 64-bit DSN because vCenter Service is 64-bit code - no matter what version of database is being accessed.

VUM on the other hand is still 32-bit code and requires a 32-bit DSN
0
 
Luciano PatrãoICT Senior Infraestructure Engineer Commented:
Hi

Humm thats new for me, I tough that we need to use ODBC 32 bit on SQL 32-bit version.
I never used 64 bit server into a 32 bit SQL for vCenter, but I have used in other tools, and all I need to create a 32-bit ODBC using SysWoW64.

But we are always learning on this EE :)

Jail
0
 
bgoeringCommented:
Yeah - maybe http://robertoschiabel.wordpress.com/2008/02/28/windows-x64-32bit-odbc-vs-64bit-odbc/ explains it a bit better than I did. I guess they didn't want to put resources into VUM to upgrade it to be 64-bit code. I think I saw somewhere that VUM (for virtual machines) is going away, and there will be some new process for patches and upgrades to ESX(i).
0
 
bgoeringCommented:
Anyway - glad you got it going waverazor
0
 
waverazorAuthor Commented:
None
0
 
waverazorAuthor Commented:
The sqlncli_x64.msi worked.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 4
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now