Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Upgrade Vault from v9.0.2 to v10.0.2: SQL collation detected by Deployment scanner but unable to correct

Created: 25 Feb 2013 • Updated: 02 Mar 2013 | 2 comments
This issue has been solved. See solution.

Hi,

We're preparing upgrade of our Vault (for Ms Exchange 2003/2010 and file archiving) from v9.0.2 to v10.0.2.

Deployment scanner has detected a collation with 2 DBs: EnterpriseVault FSAReporting and EnterpriseVaultFSAReportingTempDB.

Our SQL admin has executed following command below:

USE master

GO

ALTER DATABASE EnterpriseVaultFSAReportingTempDB

COLLATE SQL_Latin1_General_CP1_CI_AS

GO

Result of this command is indicated below:

Msg 5075, Level 16, State 1, Line 1

The object 'Positive_StartByte' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

Msg 5075, Level 16, State 1, Line 1

The object 'Positive_LogicalByteCount' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

Msg 5075, Level 16, State 1, Line 1

The object 'Positive_ActualByteCount' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

Msg 5072, Level 16, State 1, Line 1

ALTER DATABASE failed. The default collation of database 'EnterpriseVaultFSAReporting' cannot be set to SQL_Latin1_General_CP1_CI_AS.

Msg 5075, Level 16, State 1, Line 1

The object 'Positive_StartByte' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

Msg 5075, Level 16, State 1, Line 1

The object 'Positive_LogicalByteCount' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

Msg 5075, Level 16, State 1, Line 1

The object 'Positive_ActualByteCount' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.

Msg 5072, Level 16, State 1, Line 1

ALTER DATABASE failed. The default collation of database 'EnterpriseVaultFSAReportingTempDB' cannot be set to SQL_Latin1_General_CP1_CI_AS.

After executing the SQL command, DS gives same result.

Important note: I precise we do not want to use FSA reporting anymore but I don't know how to disengage this reporting.

Kr,

Operating Systems:

Comments 2 CommentsJump to latest comment

Advisor's picture

If its going to be dedicated SQL Server, you might want to alter master db collation to match other database collation, just detach other DB's, change master DB collation and attach them back.