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
7/13/2010 9:07 PM
 
Sebastian Leupold wrote:
Dave, I assume this is default collation and i.e. the results are fine. in most cases, joins are using integer columns, which are not affected by collation at all. Only there seems to be a single sproc, which joins with a table from temp database, which might use a different collation.

 The results are fine.  The server, database and tempdb all list the same.


-----
Cheers
Dave
 
New Post
7/13/2010 9:08 PM
 
Sebastian,

Here is the SP from the database (5.1.4)

USE [mbgt]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO

ALTER PROCEDURE [dbo].[GetEventLog]
 @PortalID int,
 @LogTypeKey nvarchar(35),
 @PageSize int,
 @PageIndex int
AS

 DECLARE @PageLowerBound int
 DECLARE @PageUpperBound int
 -- Set the page bounds
 SET @PageLowerBound = @PageSize * @PageIndex
 SET @PageUpperBound = @PageLowerBound + @PageSize + 1

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

 INSERT INTO #PageIndex (LogGUID)
 SELECT EventLog.LogGUID
 FROM EventLog
 INNER JOIN EventLogConfig
  ON EventLog.LogConfigID = EventLogConfig.ID
 WHERE (LogPortalID = @PortalID or @PortalID IS NULL)
  AND (EventLog.LogTypeKey = @LogTypeKey or @LogTypeKey IS NULL)
 ORDER BY LogCreateDate DESC

 SELECT EventLog.*
 FROM EventLog
 INNER JOIN EventLogConfig
  ON EventLog.LogConfigID = EventLogConfig.ID
 INNER JOIN #PageIndex PageIndex
  ON EventLog.LogGUID = PageIndex.LogGUID
 WHERE PageIndex.IndexID   > @PageLowerBound 
  AND PageIndex.IndexID   < @PageUpperBound 
 ORDER BY
  PageIndex.IndexID 

 SELECT COUNT(*) as TotalRecords
 FROM #PageIndex


-----
Cheers
Dave
 
New Post
7/14/2010 3:16 AM
 
Dave,
I just revisited all your posts in this thread.
the main problem is between default collations:
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

and actual collation of all the tables:
 Table Name  Column Name
 Collation Name
 AllDnn_More_item   Description  SQL_Latin1_General_CP850_CI_AI
 ...    

i.e. someone altered default collation of the database. I suggest switching either database default collation or collation of all tables to current default collation, which should solve the conflict.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/14/2010 9:14 AM
 
The collation is ok for some columns, and in fact the collation is different for different columns in the same table:

vw_Tabs Url SQL_Latin1_General_CP850_CI_AI
vw_Tabs HasChildren SQL_Latin1_General_CP1_CI_AS
vw_Tabs RefreshInterval NULL
vw_Tabs PageHeadText SQL_Latin1_General_CP850_CI_AI
vw_Tabs IsSecure NULL

I found out that when Webhost4Life moved the database to their new platform, they scripted the move of the data which is where the issue entered the picture.  Unfortunately the move happened months ago, and we have too much data in it now to go back.  I have to try and fix this moving forward.

Cheers

-----
Cheers
Dave
 
New Post
7/14/2010 9:27 AM
 
vw_Tabs is a view, combining columns from multiple tables. However, you should adjust all collations to follow database default collation.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
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