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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Cannot resolve the collation conflict between "Latin1_General_CI_AS"Cannot resolve the collation conflict between "Latin1_General_CI_AS"
Previous
 
Next
New Post
12/10/2008 8:11 AM
 

Michael,

you should use

CREATE TABLE #PageIndex
   (
      IndexID int IDENTITY (1, 1) NOT NULL,
      LogGUID varchar(36) COLLATE Database_default
   )

This should have been fixed by one of the 4.x upgrade scripts...


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/10/2008 8:19 AM
 

if your specific database collation is different from the server, chances are the db was created on a different server, and moved to the current server. In order to prevent future issues, it is probably easiest to change the collation of the database to that of the server. A long time ago i blogged about that: http://www.apollo-software.nl/Blog/tabid/169/EntryId/2/Language-and-Collation-in-SQLServer.aspx


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
12/10/2008 8:56 AM
 

unfortunately it seems as if its not that easy to change the collation of a data-containing DNN-database. When trying to alter it says that it is not possible because of dependencies on the database collation of some objects and functions (fn_split, CK_C5SLLC_form_FromAction,...).

I also tried to add the #PageIndex-table with database collation as described by Sebastian,.. no success either.
FYI, i did this way:
CREATE TABLE #PageIndex
(
IndexID int IDENTITY (1, 1) NOT NULL,
LogGUID varchar(36) COLLATE Latin1_General_CI_AS //<- dnn-database collation
)

is this how it should work?

 
New Post
12/10/2008 1:11 PM
 

Erik, this is a dicrepancy between DNN database collation and collation of the temp DB, which can be prevented by using database default collation - which has been taken care of by an updated sproc in DNN 4.x (unfortunately, Michael had difficulties upgrading his site, I assume, this script did not run completely).


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/28/2010 11:41 PM
 

I'm dragging this thread back to life...

I am getting this errror, my specific one is:

 Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP850_CI_AI" in the equal to operation.

I have done the transact SQL and all the results show SQL_Latin1_General_CP1_C1_AS as the collation on all three.

i tried running the Create #Pageinfo table, however even though the command appears to have completed successfully, I cannot seem to find the new table and the Log Viewer is still broken.

Where should I go from here,,,


-----
Cheers
Dave
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Cannot resolve the collation conflict between "Latin1_General_CI_AS"Cannot resolve the collation conflict between "Latin1_General_CI_AS"


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