VMware Cloud Community
khughes
Virtuoso
Virtuoso

Win 2003 VC to Win 2008 x64 SQL ODBC connection

I'm trying to get a vSphere setup running in my RD environment prior to upgrading our production environment, but I'm running into a pretty big snag with linking up my WinServer 2003 virtual center to my Windows 2008 x64 SQL 2008 server. Is there any catches to creating the ODBC connection? I'm just getting a failed connection attempt when I go to create it. I've asked around some of my sources and some have run into the same issue.

*Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
15 Replies
SurfControl
Enthusiast
Enthusiast

use odbcad32.exe to create DSN name

Reply
0 Kudos
khughes
Virtuoso
Virtuoso

I've read that you need to run that if you're connecting a Windows 2008 x64 Virtual Center server to the database, but I didn't think you needed to run the special odbc32.exe for a Windows 2003 x86 server running Virtual Center.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

there should be nothing different. Just make sure you have the SQL Native Client and you have DBO on both the VCDB and MSDB (to create the rollup jobs)

Reply
0 Kudos
SurfControl
Enthusiast
Enthusiast

never mind

Reply
0 Kudos
khughes
Virtuoso
Virtuoso

That's another thing, on my Win2003 SP2 x86 VC server, I don't get the option for SQL Native client, all I get when I go to make a System DSN is the SQL Server. Is there an update I'm missing that enables the SQL Native for the ODBC?

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

you will have to download the sql native client and install it on your vCenter Server

http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displa...

Microsoft SQL Server 2008 Native Client

Microsoft SQL Server 2008 Native Client (SQL Native Client) is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver. It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server 2000, 2005, or 2008. SQL Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2008 features. This redistributable installer for SQL Native Client installs the client components needed during run time to take advantage of new SQL Server 2008 features, and optionally installs the header files needed to develop an application that uses the SQL Native Client API.

Audience(s): Customer, Partner, Developer

X86 Package (sqlncli.msi) - 4549 KB

X64 Package (sqlncli.msi) - 7963 KB

IA64 Package (sqlncli.msi) - 11112 KB

khughes
Virtuoso
Virtuoso

Thanks for the updated link, I'm in the process of rebuilding my SQL server because I assumed it was something I did in the configuration of it all. Its almost done installing SQL so I should have it up and running soon and I'll test the client connection.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
admin
Immortal
Immortal

Answered here: http://www.vmwarewolf.com/32-bit-odbc-dsn-for-vsphere/

Rick Blythe

Social Media Specialist

VMware Inc.

Reply
0 Kudos
khughes
Virtuoso
Virtuoso

Sorry Rick but I'm not using a 64bit OS for the VirtualCenter server.

Troy- I'm still running into issues with the ODBC. I've created the database on the SQL2008, created a user, attached the user to the database, gave it DBO rights. I went on the virtual center server to the ODBC connections, selected Native Client, gave the name, pointed it to the correct remote SQL server, tried both windows / sql authentication but I keep getting can't communicate with the sql server / timeout errors when I try and authenticate. The windows firewall is disabled on the SQL server

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
SurfControl
Enthusiast
Enthusiast

how about the MSDB? take a look at Troy's comments above, the 5th post I think?

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

can you telnet from your vCenter host to your SQL Server using port 1433? remember you must also give the user db_owner on the MSDB as well as the vcdb.

You didn't even get to the point in your system DSN setup to "test connection"

Reply
0 Kudos
khughes
Virtuoso
Virtuoso

Yes it was configured with dbo on both databases. No I'm not getting to the point to test the connection, and when I try to telnet to the server I get a connection refused.

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

i'm no DBA, so this may be beyond me. However, you need 1433 open, that is what the client will use to connect to SQL

khughes
Virtuoso
Virtuoso

So I finally just figured out what was going on and thought I would share with the rest of you. On my SQL 2008 installation, the TCP/IP and Naming Pipes protocols aren't enabled by default, which would cause the issues I was having of trying to connect to them via ODBC. I love having to try and pretend to be a DBA.

Question is, besides the obvious security reason... why would the TCP/IP protocol be disabled by default? Really?

  • Kyle

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos