cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade 2007 to 8. Collation problem

prodsac
Level 4
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?
1 ACCEPTED SOLUTION

Accepted Solutions

EVNoodles
Level 4
Employee
It sounds like the temp table needs a flush

Please read this part of the technote you were referencing

SQL 2005
 
The MSDN script does not drop the temporary tables created.
 
So if you run the script in normal mode, then try again in report mode, you will have errors saying that the tables already exists.

If you are still having issues I would recommend logging a case with us and we can help out.

If this has solved the issue please mark this post as solved.

Thanks for your time

EV Noodles

View solution in original post

3 REPLIES 3

EVNoodles
Level 4
Employee
It sounds like the temp table needs a flush

Please read this part of the technote you were referencing

SQL 2005
 
The MSDN script does not drop the temporary tables created.
 
So if you run the script in normal mode, then try again in report mode, you will have errors saying that the tables already exists.

If you are still having issues I would recommend logging a case with us and we can help out.

If this has solved the issue please mark this post as solved.

Thanks for your time

EV Noodles

EVNoodles
Level 4
Employee
Double Post Apols :)

prodsac
Level 4
perfect, it works.

thanks