Mariano,

As far as I can tell the SQL installation scripts used by the DNN installer are not consistent in their case use, for example procedures, columns and scalars are inconsistently spelled as 'PortalID', 'PortalId', '@PortalID', '@PortalId', 'GetPortalID', 'getPortalId' etc. When your SQL server system is using a case sensitive collation, its internal system tables are accessed using case sensitive routines.
Changing the case sensitivity/collation of your own databases does not help here. The only way is to change SQL server's system collation. You could do this by reinstalling SQL Server using a case insensitive system collation, e.g. English 437, or try the method as noted in: http://msdn2.microsoft.com/en-us/library/ms179254.aspx. Of course, with a case insensitive system collation you would have to override the collation for all your user databases.

I think the right way to deal with this should be a refactoring the DNN installer scripts to get their naming consistent.

Hope this helps.

WW

Hey!
First of all - I´m no expert on databases, I just use them for my applicatoins :)

I´m really comfused. "As far as I can tell the SQL installation scripts used by the DNN installer are not consistent in their case use" Why? There ar no case-sensitive script generation tools?
I have my own SQL2005 development server that is useless (in this case) because of inconsistent scripts? Just don´t get it...

I found så few questions obout this in the forum. Is case-sensitive collations unusual in database servers? I´m thinking this might cause problem when I vant to deploy on a webhost.

Thanks in advance...