Hi,
I ran the deployment scanner.
The only error referred to : SQL 2005
"""
At least one test for the SQL server collation has failed. SQL databases (shown below) contain entities with mixed collations. If they are Enterprise Vault Vault Store databases then they will prevent a successful upgrade. Please go to http://seer.entsupport.symantec.com/docs/293475.htm for more details.
SQLSERVER: Unmatched default SQL collation: Server: SQL_Latin1_General_CP1_CI_AS; EnterpriseVaultDirectory database: Latin1_General_CI_AS.
SQLSERVER: Database: EnterpriseVaultDirectory - no mixed collations found.
SQLSERVER: Unmatched default SQL collation: Server: SQL_Latin1_General_CP1_CI_AS; EnterpriseVaultMonitoring database: Latin1_General_CI_AS.
SQLSERVER: Database: EnterpriseVaultMonitoring, Table: MailboxSource , Column: SourceName ; Table: MonitoringConfig , Column: StringValue ; - mixed SQL collation found.
SQLSERVER: Unmatched default SQL collation: Server: SQL_Latin1_General_CP1_CI_AS; EVVault001 database: Latin1_General_CI_AS.
SQLSERVER: Database: EVVault001 - no mixed collations found.
"""
So I followed every steps in DOC: #293475
I downloaded the change_collation.sql script from microsoft.
When I run it on EnterpriseVaultDirectory database in report mode, it gives:
Msg 2714, Level 16, State 6, Line 248
There is already an object named 'udf' in the database.
When I run it on my EVVault001 database, in report mode, it gives:
Msg 2714, Level 16, State 6, Line 248
There is already an object named 'udf' in the database.
Any ideas?