Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Collation Change for EV SQL Databases

Created: 27 Nov 2012 • Updated: 17 Dec 2012 | 2 comments
syfan's picture
This issue has been solved. See solution.

Hello all,

I'm planning an upgrade of an EV 8 server to EV 9.0.4 and currently I have EV SQL databases with collation that does not match the collation of SQL master database. According to http://www.symantec.com/docs/TECH55063, all EV SQL databases should have a uniform collation (same as the SQL master DB) otherwise the upgrade to EV9 will fail.

I'm trying to figure out what are the exact steps to change the collation of EV DBs to match the SQL master collation. The articles provides 2 SQL queries in order to check collation status:

1) The first query checks if there any DBs with different collation (there are such DBs in my case)

2) the second query checks within each database to see if there is a mismatch with the columns of the database (db) for the EnterpriseVaultDirectory and each vault store database (this query does not report a problem in my case)

While the article provides a rather long procedure to change collation of problematic EV DB, it states that "Other solutions exists if only a mismatch exists from the first query where the collation can be changed at the database level itself, or install a new instance of SQL, create new databases with the proper collation and then restore the EV databases"

In the installation I'm checking, only the first query returns a mismatch so I wonder if I can only use the "collation change at database level" approach that the article mentions. If yes, does the "collation change at database level" approach includes only running the MSDN query referenced by the KB article without the extra steps (running parts of EV programmability scripts etc.) ?

Thank you very much in advance!

Comments 2 CommentsJump to latest comment

AndrewB's picture

i think GertjanA just went through something similar. his post is here: https://www-secure.symantec.com/connect/forums/fix...

if not, then look here for reference: https://www-secure.symantec.com/connect/search/apa...

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

SOLUTION
GertjanA's picture

Hi Syfan,

The tool I used changed the collation wonderfully, no SQL/EV issues.

Exactly what error do you get. I have seen in the past that sometimes collation is different on only 1 column, this can then be changed by hand.

 

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision