>>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) ?
>
>When we faced that, we had to resinstall SQL Server.

Thanks for your input on this. Being a rather drastic measure, I'll have to check with customer to see if they're using SQL Server for anything else than our software. If we're the only one software it'll be easier to talk the customer into doing the reisntall of SQL Server. If not, it's probably a "no go" on this option (we could break something else in the process).