vCenter 4.1 DSN question

[vmproteau]

I had to rebuild my vCenter server (WIndows 2008 R2) and do a fresh install of vCenter connecting to my existing SQL2005 databases.

Install appeared to run fine and everything looks normal but, I noticed afterword that I installed and used the SQL 2008 Native DSN driver for the whole process.

(1) Could this become a problem (connecting and using an SQL 2008 DSN to connect to a SQL 2005 database)?

(2) Should I change it now or am I fine to continue the way it is?

(3) This was a Lab test to define my production process so, when I do roll out to production, does it mak sense to go ahead and use the SQL 2008 DSN like I did here. One reason I would do it is that we will be migrating to SQL 2008 soon.

Just want o make sure I am not endangering my environment with this configuration.

[AndreTheGiant]

I suggest to do not mix SQL part, but probably it will works without issue.

Migrate to SQL 2008 when you can

It is supported as SQL 2005:

http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

Andre

[vmproteau]

I still haven't fully decided what I'll do in production but, it seems that the 2008 or even the 2008 R2 Native Client should work fine connecting to an SQL 2005 database.

I verified with Micriosoft who said it is a supported configuration. Below is also a blurb which appears to validate as well. The same blurb is found with regards to the 2008 R2 Native client.

Microsoft SQL Server 2008 Native Client (SQL Server 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 Server 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 Server 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 Server Native Client API.

If anyone is running in this configuration, pleas comment as well. I'd like to hear from the VMware community for some real world evidence.

[BigHug]

We have been using mixed versions of sql native clients and sql servers for a long time. Have not seen a problem yet. I prefer to use latest and higer version of snc. However, some of our developers prefer to use lower version. Most apps like vCenter just uses odbc to connect and do simple things. Once it can connect, it should be fine. However, if you still don't feel comfortable, just re-install snc. Hope this helps.

[admin · Accepted solution]

There are absolutely no issues when using the sql2008 client driver to create dsn for sql2005 even in large environments. Another option you would have is to do an upgrade of your SQL2005 to SQL2008 using the Upgrade Advisor tool for assitance.

Thanks

sriram