I would like to ask some sql profi for help…

I am trying to install DotNetNuke in scenario as follows:

• Hosting platform: Win 2003 + SQL2005, Dnn version 4.9.2
• Bad news: SQL server collation is …_CS_AS (case sensitive and accent sensitive)
• Dnn database has collation …_CI_AI (both aspects insensitive)

As you probably knows DNN db install scripts are generated in case insensitive manner. Install wizard ends on db install stage in infinite loop with db forever growing …

Classic install method gets errors in "DotNetNuke.Schema.SqlDataProvider" and in some other scripts. The cause is the character case problem. I edited those scripts where I saw some error message.

Next install try ends on “Configuring SuperUser” stage with exception: Could not find stored procedure dbo.aspnet_CheckSchemaVersion

I checked database and there in none of “aspnet_...“ procedures. I am wondering now – is this result of case problem or is it another problem with db user permission?

Makes it ever sense to try install on SQL server with “_CS_AS” collation?

Missing aspnet membership tables is result of previous problem, which is character case in scripts as follows:

• 04.05.00.SqlDataProvider
• 04.06.00.SqlDataProvider
• 04.07.00.SqlDataProvider
• DotNetNuke.Schema.SqlDataProvider (this script was created by SQL Compare from Red Gate Software)

At first I modified the scripts listed above, reseted web.config, emptied the database and ran the installation again. Installation failed and the result was the error message mentioned above. During the control of the database I noticed that some objects had not been created (eg. aspnet tables and roles). This was probably caused by limited permissions of db user. I ran manually the scripts, which had not been executed as result of previous error:

• InstallCommon.sql
• InstallMembership.sql
• InstallRoles.sql
• InstallProfile.sql

Directly in database I corrected the owner of aspnet objects, then I deleted the content of Version table and ran the installation again. The result of these actions is fully functional installation of DotNetNuke portal.

It seems that the whole problem was caused by character case errors in the scripts mentioned above.

Yes, it is mentioned in the first article. To be exact, here is the summary:

• Server default collation: …_CS_AS
• DNN database collation: …_CI_AI

The above is valid for my host database server. I tested the same install on my own intranet using SQL server with collation: …_CI_AS and everything is working fine.