Hi ..

I am discovering, whilst rebuilding DNN after reinstalling SQL Svr 2005, that case sensitivity is an issue with DNN. I am getting failures due silly things, such as

---< cut >---

System.Data.SqlClient.SqlException: Must declare the scalar variable "@moduleid".
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)



CREATE procedure dbo.GetModuleSetting

@ModuleId int,
@SettingName nvarchar(50)

as

select
'SettingValue' = case when Files.FileName is null then ModuleSettings.SettingValue else Files.Folder + Files.FileName end

from ModuleSettings
left outer join Files on ModuleSettings.SettingValue = 'fileid=' +
convert(varchar,Files.FileID)
where SettingName = @SettingName and moduleid=@moduleid

---< cut >---

(the "error" is that the last "@moduleid" should be the same as the "@ModuleId" in the param list)

So, this being the case,
what is the assumed or "correct" collation for DNN under SQLSvr?
Or is this a "make sure you install SQL Server right" kind of problem.

Many thanks,

-mark.

hi, sebastian



no kidding! .. lol

are there plans for future? seems like it would just take a code cleanup to do it ..

also, is there a prefered collation for DNN under SQLSvr? Or will -any- case insensitive collation work?

thanks,

-mrk.