SqlParameter object: Why do I need to mess with all the options?

Question

When I call a stored procedure from .NET code, I could you this to specify a param value:

sqlCommand.Parameters.AddWithValue("@param1", myvalue1);

If I am calling a SQL Server stored procedure, is there ever a need to specify other optional SqlParameter property values such as Length, datatype, precision, etc, when I am calling a SQL Server stored procedure?

When is it necesary?

Oded · Accepted Answer · 2012-01-14 22:32:39Z

1

You need to declare the extra parameters when you are dealing with a datatype that requires them.

For example - you can't use the simple overload with floating point data types, as you must specify the precision and scale as defined on the server.

When not specifying them on a type that requires them, you will get a SqlException with a descriptive message to this effect.

In such cases, you can't use AddWithValue, but need to use Add passing in a SqlParameter object.

edited Jan 14, 2012 at 22:32

answered Jan 14, 2012 at 22:27

Oded

501k102 gold badges900 silver badges1k bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

SqlParameter object: Why do I need to mess with all the options?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related