Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...SQL Collation issue on upgrade after host migrationSQL Collation issue on upgrade after host migration
Previous
 
Next
New Post
2/16/2014 2:53 PM
 

Hi all

I have been using DNN since the iBuySpy portal and it has served me well over the years.

I currently have 4 instances, all with multiple portals.

In December, I migrated them from a datacentre hosting them on a local SQL server to Windows Azure. and until now I have had only minor issues.

The migration was performed by using the SQL database migration wizard from codeplex to move the databases up. copying up my source directories, changing the web.config connection strings and it all worked great.

at the time of migration, I had 1 instance on 7.1.something and 3 instances on 6.2.2. All of these instances were created in somewhere around DNN v3 and upgraded all the way till now.

Last week, I upgraded the 7.1.x instance and the first of the 6.2.2 instances with no issues. This weekend, I started an upgrade of the other 2 instances and have hit problems which are beyond my TSQL skills.

the error I am getting is:

Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "Latin1_General_CI_AI" in the equal to operation.

This error occurs while running the 6.2.3 upgrade script (at least).

if I run the upgrade script manually, it completes with no errors.

I would appreciate any assistance anyone can provide

thanks

 
New Post
2/17/2014 2:41 AM
 
you need to adjust default collation of the database and of all existing text columns (e.g. with a script like http://www.sqlservercentral.com/scrip...)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/17/2014 2:47 PM
 
as Sebastian suggests the problem is the database has different collations for certain objects/columns and that sql server does not like queries which contain data from different collations. At a guess your migration wizard set some column with a different collation (AFAIR azure does not allow database or table collations to be set), so you will have to ensure that the column has it's collation cleared/changes to the database default.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...SQL Collation issue on upgrade after host migrationSQL Collation issue on upgrade after host migration


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out