I just wanted to take a moment to share and see if anyone has a work around. Installation is failing with errors in Schema log and others. I have a sqlserver with an existing production instance on it from another vendor that requires case sensitive collation. This is a Server Wide setting and cannot be changed after the sqlserver install. I have a requirement to use this server.

Ultimately that means that all object names defined in the database are case sensitive.  The schema log is showing errors in two flavors. 1) local variable names are mismatched. e.g. the declaration is @Id and later in the script it is referenced as @ID as well as many other variations of UserName and username etc..  After changing all of those I started running into issues between the database table case and the case in the stored procedures, it has to match. I resolved all of those so that the installation runs. ( This took about 16 hours of editing ). Now that the install runs I am running into issues with the dataprovider source code for the application as it is also case sensitive, the variable names must match in case to the variable names in  the stored procedures.  Unfortunately, once I finish this editing and have a functional server I wont be able to upgrade until this is resolved :\(.

The issue around case sensitivity is listed as reported and unnassigned.

I am continuing to find and resolve all these differences, I am hoping that someone out there has run into this and created a script that resolves these issues perhaps a 04.05.02 :\). Or has gone through and edited all the provider files with the correct case as driven by the databasecolumn names and the application stored procedure calls. 

Thank you for your consideration.

John

FYI you can change the collation in sql 2000/sql 2005 at a column, table or database level - you do not need to alter the server collation - see http://www.databasejournal.com/features/mssql/article.php/10894_3302341_2 for more details on how to use the ALTER statement.

Cathal