Unanswered: Stored procedure performance when attaching parameters?
About 75% of my stored procedures can possibly produce an "output message" which is sent back to the client via an OUTPUT parameter
CREATE PROCEDURE myProc
My client-code is written such that I never call the SqlCommand.ExecuteReader() directly; everything is encapsulated with an "ExecuteCommand" routine. Within the "ExecuteCommand" routine, I automatically attach an output parameter called "outputMsg" since 75% of my procs use it.
The problem: Only 75% use it, the other 25% don't need it. If don't include that outputMsg parameter in those procedures, then my "ExecuteCommand" routine generates an error saying something like "No parameters were expected by 1 was found" -- which is correct, because the procedure does not take any paramters, but my "ExecuteCommand" method is set up to automatically include that "outputMsg" parameter since 75% of the procedures use it.
As a workaround, I just included that "outputMsg" to EVERY stored procedure even though 25% of them don't need it.
My question: Would this produce a noticible performance difference? By "this" I mean the fact that I'm attaching output parameters to procedures for procedures that don't even use them.