>>>Recently ran into problem at customer site where a database built with case-insensitive was attached to server configured with case sensitive as the default. Now we're getting a errors left and right with scripts and such because of non-matching case on identifiers. Any suggestions aside from having to edit of all the scripts (case wasn't always consistent due to several people being involved) to have consistent case, and all SQL-passthru within application to be similarly consistent (again, because several people were involved, we didn't always have consistency in case) ?
>>
>>I agree with Michel. The only solution is either re-install or have everything match (all identifiers be in right case).
>
>Thanks for your input on this --- reinstallation however is likely to be a "no go" especially if the customer is using SQL Server for some other application (customer hasn't replied to my query regarding this as of yet).

Check also this thread about collations at MSDN.