SQL Server caring about case sensitivity
I'm in the process of setting up a load testing environment for my current app. As I'm moving my database over via T-SQL scripts and command files from my database project I've been running into really strange issues. It appears that some of our scripts don't have the same casing as the parameters and/or column names do and as I'm running my scripts on the database server (Windows 2003) my scripts are failing because of the mis-match. As an example I had a stored procedure that was doing a join to another table which had an alias set to "D", however, below in the query it referred to this alias as "d". When running the command file I was getting an error saying that the "d" alias was invalid. I've run these scripts hundreds of times on other databases and never received this error, what gives? Why would SQL Server start caring about case sensitivity in column names, aliases, and parameters?