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
5/20/2010 4:07 PM
 
David OLeary wrote:
We were able resolve this by scripting out the entire database with data (and without the Collation settings).

David,

I'm not a SQL guy, is it possible to dumb that answer down a bit?  Is this a simple script, or does it involve migrating the entire database?

Cheers


-----
Cheers
Dave
 
New Post
5/20/2010 4:08 PM
 
Laurence Neville wrote:
Are you absolutely sure that the 3 values returned by this query are the same? SELECT DATABASEPROPERTYEX( 'DotNetNuke or whatever your DNN database is called' , 'Collation' ) AS DotNetNukeDB_Collation, DATABASEPROPERTYEX( 'tempdb' , 'Collation' ) AS TempDB_Collation, SERVERPROPERTY( 'Collation' ) AS Server_Default_Collation

 Sorry it took so long to get back to you.  Yes, all three were identical.

DotNetNukeDB_Collation                     TempDB_Collation                                 Server_Default_Collation
SQL_Latin1_General_CP1_CI_AS     SQL_Latin1_General_CP1_CI_AS     SQL_Latin1_General_CP1_CI_AS

Cheers


-----
Cheers
Dave
 
New Post
5/21/2010 5:23 PM
 
David, I was under the impression that the eventlog issue has been fixed in DNN5, but haven't validated this yet. the problem here is a wrong data type being used to store the GUID (text instead of GUID for SQL Server 2005 and up).

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/17/2010 12:28 AM
 
Sebastian, Is there anything I can do about it? My SQL Server is 2008. Cheers

-----
Cheers
Dave
 
New Post
7/12/2010 7:35 PM
 
Just for fun, I tried to do an update to 5.4.4 and things started out crappy immediately with colation conflicts. So, now I would really like to fix this. Does anyone have a clue on how to resolve the issue?

-----
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