VMware Cloud Community
axle201110141
Contributor
Contributor

ODBC DSN for VCenter 4.1

Hi

2 Questions from a newbie.

SCENARIO

I have VCenter 4.1 (A)  installed on a Windows 2008 R2 64bit server for a datacenter and I'm connecting to an external SQL Server 2005 database on a win 2003 server. I configured an ODBC DSN from c:\windows\SysWOW64\odbcad32.exe and it connects OK to the external SQL 2005 database. The version is 2005.90.1399.0.

We have another VCenter 4.1 (B) that was earlier installed on a Windows 2008 R2 64bit server for a different datacenter that connects to a different SQL Server 2005 database on a win 2003 server. A sqlncli_x64.msi was downloaded and installed on the VCenter 4.1 server, when looking at that ODBC DSN, the SQL Native client installed on that server is version 2005.90.3042.00.

QUESTION1

We are looking at linking both VCenters, do I need to change the SQL Native client version on the VCenter 4.1 (A) server ( 2005.90.1399.0) to match that of  VCenter 4.1 (B) server  (2005.90.3042.00)?

Is the SQL Native client version 2005.90.1399.0 used by VCenter 4.1 (A) server, the correct version to be used for a VCenter database v4.1, or will it cause problems later on?

QUESTION 2

The VCenter 4.1 databases mentioned in the above scenario have different SQL collations VCenter 4.1 (A) has collation of Latin1_General_CI_AS and VCenter 4.1 (B) has a collation of SQL_Latin1_General_CP_CI_AS. The Server system databases on both external SQL 2005 Servers have a collation of Latin1_General_CI_AS.

Do I need to change the collation of the VCenter database used by VCenter 4.1 (B) server to Latin1_General_CI_AS so it matches the collation of the VCenter database used by VCenter 4.1 (A) server?

Will there be any consequences if the collations are not the same?

Thanks in advance.

Regards

Reply
0 Kudos
0 Replies