Applies to: DNN430 / DNN330 (and probably previous versions too).
There are explicit "COLLATE" values on:
\DesktopModules\Feedback\Providers\DataProviders\SqlDataProvider\03.01.01.SqlDataProvider
\DesktopModules\Blog\Providers\DataProviders\SqlDataProvider\01.00.00.SqlDataProvider
\DesktopModules\Blog\Providers\DataProviders\SqlDataProvider\03.01.21.SqlDataProvider
\DesktopModules\Events\Providers\DataProviders\SqlDataProvider\03.02.00.SqlDataProvider
\DesktopModules\Feedback\Providers\DataProviders\SqlDataProvider\03.01.01.SqlDataProvider
\Providers\DataProviders\SqlDataProvider\02.01.01.SqlDataProvider

I think this may cause some problems when the server's default is set to another value.
May be, they should be removed from the scripts...

Sample problem (feedback module):
Note that only the "CreatedByEmail" column will have the SQL_Latin1_General_CP1_CI_AS collation, and the other "string" columns will have the server's default.

if not exists (select * from dbo.sysobjects where id = object_id(N'{databaseOwner}[{objectQualifier}Feedback]') and OBJECTPROPERTY(id, N'IsTable') = 1)
    BEGIN
        CREATE TABLE {databaseOwner}[{objectQualifier}Feedback] (
    [ModuleID] [int] NOT NULL ,
    [Status] [int] NOT NULL ,
    [Subject] nvarchar (200) NULL,
    [FeedbackGUID] [nvarchar] (50) NOT NULL ,
    [CreatedByEmail] [nvarchar] (200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [ApprovedBy] [int] NOT NULL DEFAULT (0) ,
    [Category] [int] NOT NULL ,
    [Message] [nvarchar] (1000) NOT NULL ,
    [DateCreated] [datetime] NOT NULL DEFAULT (getdate()),
    [FeedbackID] [int] IDENTITY (1, 1) NOT NULL ,
    CONSTRAINT [PK_{objectQualifier}Feedback] PRIMARY KEY  CLUSTERED
    (
        [FeedbackID]
    )  ON [PRIMARY]
) ON [PRIMARY]
    END
GO

I had this problem after restoring a production database to my local machine using sql express.

The problem was that 3 tables have all character columns with explicit collation settings.

After I changed the database settings and tempdb settings to be the same, I also had to manual change the column settings for the following tables to the database default (or explicit setting that matched the DB and tempdb).

The tables affecting my system were EventLog, EventLogConfig, and EventlogTypes.

---

Jim www.walkspoiled.com