SQL - no mixed collations found.

[James_Herbert]

Hi All,

We are currently running EV2007 SP4 and looking to upgrade to EV8 SP3.  After running the deployment scanner we have come up with a error below regarding our SQL environment;

SV-LON-KVS-001: Database: EnterpriseVaultDirectory - no mixed collations found.
	SV-LON-KVS-001: Database: EnterpriseVaultMonitoring - no mixed collations found.
	SV-LON-KVS-001: Database: EVUKEmailStore - no mixed collations found.
	SV-LON-KVS-001: Database: EVUKPublicFolderStore - no mixed collations found.
	SV-LON-KVS-001: Database: EVUSPublicFolderStore - no mixed collations found.
	SV-NYC-KVS-001: Database: EVUSEmailStore - no mixed collations found.

Has anyone got any ideas whats needed to resolve this?  Also has anyone come across any issues upgrading from EV2007 SP4 to EV8 SP3?

Thanks
James

[MichelZ]

Hi No mixed collations is a good thing, you do not need to do anything. Cheers

[James_Herbert]

Sorry after looking again the error is Unable to connect to at least one of the SQL servers listed

	Failed
		Unable to connect to at least one of the SQL servers listed.   SV-LON-KVS-001: Database: EnterpriseVaultDirectory - no mixed collations found. SV-LON-KVS-001: Database: EnterpriseVaultMonitoring - no mixed collations found. SV-LON-KVS-001: Database: EVUKEmailStore - no mixed collations found. SV-LON-KVS-001: Database: EVUKPublicFolderStore - no mixed collations found. SV-LON-KVS-001: Database: EVUSPublicFolderStore - no mixed collations found. SV-NYC-KVS-001: Database: EVUSEmailStore - no mixed collations found.

However I can connect to all DB's via enerprise manager on both boxes.  We are currently running SQL 200 SP4

Any ideas?

[GertjanA]

Hi James

It looks like you are using a SQL-server in LON(den?) and N(ew)Y(ork)C(ity).
You might experience a delay whilst checking the collation.

If you have a vaultserver local to NYC, try running deploymentscanner from there.
If you do not have a vaultserver local, try running deploymentscanner again.

It might be connection was lost while checking.

and, in enterprise manager, how many ev databases do you have on the NYC sql server? Perhaps it is a mismatch in entries in DS, and reporting?

Gertjan

[James_Herbert]

Hi Gertjan,

Thats correct we have 5 DB's in London and one in NYC.  I ran the Deployment Scanner from the NYC vault serverand got exactly the same message about not being able to connect to one of the SQL servers.  Our links are pretty fast and stable so I don't think it's a Wan issue

Thanks
James

[JesusWept3]

yeah doesn't sound like a WAN issue to be honest, unless it was a Firewall/port issue
you don't per chance use Named Instances do you? maybe you just need to specifiy SQLServer\InstanceName?

[James_Herbert]

Nop we are just using the default SQL instance on both servers

[JesusWept3]

okey dokey, just try using the FQDN and not just netbios for the SQL server
other than that just continue, i wouldn't get caught up on this issue

[James_Herbert]

FQDN didn't seem to make any difference.  Sorry I forgot to mention that there are no firewalls between the sites.

Is the general opinion that this is a DS issue and I shouldn't have issues with the upgrade?

[JesusWept3 · Accepted solution]

you can do a quick check manually

on the sql server go to the properties of each EV Database and the Master database and make sure that the collation matches
if the collation matches then don't worry, as for connectivity, ive seen the DS bomb out for no reason yet EV functions 100% OK hence the dont spend too much time on it

[James_Herbert]

I think the issue is DS is looking for the SQL Collation of the EnterpriseVaultDirectory DB (which is based in London) from the NYC SQL server which holds one of our EV store DB's

All the DB's located in London are using Latin1_general_CI_AS and the NYC DB's are using SQL-Latin1_General_CP1_CI_AS

Thanks
James

[JesusWept3]

Yeah, i'd just move along then and not worry about it