Collation error - Enterprise Vault

[LukasM]

Deployment scanner display this error

How do I change de collation lenguage?

[JesusWept3]

You can try these:
 

An Enterprise Vault (EV) upgrade fails due to SQL collation issues

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

Theres also these forum posts:
https://www-secure.symantec.com/connect/forums/unmatached-default-sql-collation-deployment-scanner
https://www-secure.symantec.com/connect/forums/errors-changing-sql-collation
https://www-secure.symantec.com/connect/forums/collation-change-ev-sql-databases
https://www-secure.symantec.com/connect/forums/upgrade-vault-v902-v1002-sql-collation-detected-deployment-scanner-unable-correct
 

[GabeV]

Hello LukasM,

Are you moving the Enterprise Vault databases to a new SQL server? If that's the case, an option (and I think it would be the easy one) could be to change the collation in the SQL server to match the collation in the EV databases. This link might help:

http://www.mssqltips.com/sqlservertip/2901/how-to-change-server-level-collation-for-a-sql-server-instance/

[Ben_Watts]

It would be worth contacting Support as this is something we deal with on a regular basis, as there are constraints etc to be thought about and dealt with, or as Gabe says, if you are on a new SQL server then you can change the Master collation.

As it mentions in the technote that JesusWept linked, if you do want to change the Master DB Collation then that is something you need to ask your DBA to deal with as Support are only able help with the EV DBs.

EV doesnt care which collation is in use, so long as we match the Master DB Collation.

[JesusWept3]

well EV does care what collation you use, if you put in a Case sensitive collation then EV would fall over pretty quick, regardless of whether it matched the master or not

[GabeV · Accepted solution]

From the Installation and Configuration guide: "The SQL installation must be case-insensitive, as case-sensitive SQL installations are not supported". If this is a new SQL server, reinstalling the instance with the correct collation would be the fastest solution. However, the recommendation is that the user's DB collation matches the Master DB collation.

Here is a Microsoft blog with some SQL queries to change the database collation, but this is something you need to review with your DBA since the steps involve in the process are complex:

http://blogs.msdn.com/b/ikovalenko/archive/2006/12/03/alter-database-alter-collation-forced.aspx

[LukasM]

Thx for the answers, I will investigate with the KB that you send me and see how it goes.