· · (0) · ·

i actualy forgot you can do this (got used to stuffing paramters in order!)...

you can explicitly name your parameters inline (in the TSQL exec string).

EXEC SampleProcedure @EmployeeIDParm = 9, @MaxQuantity = @MaxQtyVariable OUTPUT

with the return code...

EXEC @ReturnCode = SampleProcedure @EmployeeIDParm = 9, @MaxQuantity = @MaxQtyVariable OUTPUT

let's you get away from order dependent parameters, letting you override just one if all the others have defaults etc.

probably why .net ado functions have you specify the input vars by name each time, including the @ symbol reference. it just builds the exec string up internally using that form.