I have a really weird issue here. I have two server setups, one here and one at a customer. The two setups are pretty alike - same OS/SQL server version etc. On our end everything is working fine, but on the customer end they were getting really weird issues. After setting up a trace and looking through it I noticed that there was a stored procedure that wasn't getting called with all the parameters it needs, where on our end all parameters where there, except one of them was an empty string ('').
So my question is - is there a configuration setting in SQL server that has to do with how stored procedures handle empty/blank parameter values? It seems the parameter is dropped completely on the customer's server.
I know about setting default values on parameters, but since I'm passing in an empty string, I would expect this to work.