Register | Log In
Store Download Support Blogs Forums Contact
Resources > Forums
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
8/8/2006 11:47 AM
 
User is offline Juan Pablo Schmiede


jschmiede.wordpress.com/
Joined: 8/20/2004
Posts: 1

This is a SQL Server problem not DNN, so i dont get why upgrading to 4.3 os superior will fix this problem.

What you need to do is configure your tables (EventLog in this case) to use a collation equal to your server (server, tempdb and DNN database), you do this by changing collation propertie of the column you are comparing (LogGuid).

If you use MS SQL Server Management Studio, you do this by right clicking over your table name and selecting "modify" and changing the "Collation" to the database default (or the one ou are using in all server tables).

Greetings,

JP.
 
New Post
8/31/2006 2:03 PM
 
User is offline Lorenzo

Joined: 8/24/2006
Posts: 1

Hello!

Of course I run into the same problem. The solution of changing the collation for the EventLog tables woked fine. However I found more coherent another solution, namely insert a collation on the LogGUI field on the temp table as follows:

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

and all works perfectly!

I was wondering if, in fact, that was a SQL problem or a DNN problem. Let's put the matter in this way:

DNN "forces" collation on the database. However when using a temp table, the stored proc doesn't "force" any collate on the text (varchar, nvarchar etc.) fields.

For the sake of coherence I would suggest that either the db shouldn't be forced with a collation or that on creation of a temp table should be forced with the correct collation.

Lorenzo
 
New Post
10/7/2006 1:49 PM
 
User is offline Frank Corrao

www.raiseepilepsy.org
Joined: 4/7/2005
Posts: 122
I totally agree.  Not good to assume anything in the db creation scripts.  Get rid of the collation in the create table(s).!!
Version: DNN 4.4.1
Hosting Provider: 1and1
RAISE
 
New Post
7/23/2007 4:04 AM
 
User is offline Simon Holman

expeed.com.au
Joined: 1/6/2006
Posts: 50

Nevermind, had a blonde moment
 
New Post
12/10/2008 2:53 AM
 
User is offline Michael Dohr

Joined: 3/24/2006
Posts: 32

I have the same problem:

acutall Collations:

DNN_DB: Latin1_General_CI_AS
TempDB: SQL_Latin1_General_CP1_CI_AS
Server-default: SQL_Latin1_General_CP1_CI_AS

I allready tried to change the collation of the EventLog-table-columns (as far as possible)
Next to this, i tried to add the table as described above to the tempdb:

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

Unfortunately none of the provided solutions worked out. Or maybe I've done something wrong. Wahts does the #PageIndex stand for in the tempdb?
 
 Page 3 of 12
Previous1234...12Next 
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"


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.
Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

DotNetNuke Scoop!

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.
Copyright © 2002-2012 DotNetNuke Corp. / Terms of Use / Privacy
Hosted by MaximumASP