I am part of a dev group that works with ASP.Net/C#, and we are having a problem. We create lots of stored procedures in the datacenter (they run SQL 2000, in 6.5 compatibility mode), and they work as they should.
But sometimes we need to alter these procedures (successfully), including the number of parameters that they receive. If the procedure was executed several times, and the number of parameters that it receive was changed the application returns an error:
We have a workaround to it, drop the old procedure and recreate it, with a new name. It works, but it's not practical and the client don't like to wait.
The developer of the "Connection" class says that it's a problem with the database (some kind of strange unknown cache).
Somebody have a clue to what is the problem and how to solve it? It's definitelly a problem with the database or the application is the one to blame?