EV Upgrade from 7.5 to EV 8.0.5 - deployment scanner SQL

[adebola24]

Hi Guys

Upgrading the above using SQL Express 2005 - getting the attached error message in the deployment scanner

Has anyone come across this before ? there are some forum threads about it which are over 6months old so am starting a new thread

Thanks

Chris

SQL Collation

Back To Top

	Information
		Information: no mixed collations found in Enterprise Vault SQL databases.   SQL-02: Unmatched default SQL collation: Server: Latin1_General_CI_AS; EnterpriseVaultAudit database: . SQL-02: Database: EnterpriseVaultAudit - no mixed collations found. SQL-02: Database: EnterpriseVaultDirectory - no mixed collations found. SQL-02: Database: EnterpriseVaultMonitoring - no mixed collations found. SQL-02: Database: EVMailboxVaultStore - no mixed collations found.

[JesusWept3]

You really aren't going to use SQL express are you? There are some heavy limitations you may want to consider first, anywho, my suggestion would be to look at the collations of your existing EV databases and then make sure the master db and default collations on the new SQL server match the collation of the original server

[adebola24]

Thanks -- no we're not going to be using SQL express in the long term this is a temporary measure used to move them from EV 7.0 to EV9.0.2

They have an SQL 2008 x64 R2 server which they want to use for EV9, the customer was using SQL 2000 sp3 on EV 7.0  - since SQL 2008 x64 R2 is not supported on EV 2007 or EV 8 we decided that as they have a SQL Express 2005 server available (supported on EV 8 and 9)  (there is no reporting in use here) that the databases were to be moved to SQL 2005 express with idea to get to EV 9 - then move the databases to the SQL 2008 x64 R2 server

All of the databases match the same collation and the default too - even tried creating a new database to see what collation it would be etc

Now we have the error and the support team havent as yet come up with a fix we are thinking of installing a full SQL 2005 server in the environment and moving databases to that and attempting from there, but concious that SQL 2005 express and full have the same DB engine so it may be a waste of time and get the same error

Chris

[FreKac2 · Accepted solution]

I would go through the following technote, a database could have a table or even a column that doesn't match the DB collation.

http://www.symantec.com/business/support/index?page=content&id=TECH55063&actp=search&viewlocale=en_U...

So start with the checks and if you find any mixed collations you could use the scripts to change the collation. Read the whole document first if you haven't and make sure you have backups before doing anything.