case sensitive stored procedure

[dido]

When trying to import a SP it fails and says 'must declare the variables @day @month @year'. If I change these to @Day, @Month @Year then it's ok. However this procedure is still giving me problems that lead me to believe it is case sensitive. I had changed the collation of the db to SQL_Latin1_general_CPI_CI_AS which helped for all the tables and most of the SP's except a rogue few. What could be the problem?

 

[nigelrivett]

Try recompiling the SPs I guess.
Might be worth dropping them with the old case first if it has changed.

The first thing that happens when you call an SP (or query) is that it looks for the sp name to see if a plan is already cached - this is always case sensitive. If not then it looks for the SP to get the ID - this is not case sensitive - and uses any plan for that id. If still not found it generates a new plan.

I would guess you are getting caught in the middle.
dbcc freeproccache and dbcc DROPCLEANBUFFERS might help too.

Have you rebooted?

If none of this helps check the spelling.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.