Adding parameterized values. Which is more secure.

[Ryan Taylor]

Hello.

Adding some data to a sql server 2000 table. Is the later more secure than
the former? If so, why?

SqlCommand sqlCmd = new SqlCommand(update, sqlConn);

sqlCmd.Parameters.Add("@hashedPass", user.HashedPassword);



SqlCommand sqlCmd = new SqlCommand(update, sqlConn);

sqlCmd.Parameters.Add("@hashedPass", SqlDbType.NVarChar, 255).Value =
user.HashedPassword;



Thanks in advance.

Ryan Taylor

[Raterus]

You would get a better answer on microsoft.public.dotnet.framework.adonet, but I don't think it really matters. Adding the extra values just allows sql server to more efficiently process the parameters, it doesn't do anything more to secure it.

"Ryan Taylor" <rtaylor@stgeorgeconsulting.com> wrote in message news:OEXtPC1lEHA.896@TK2MSFTNGP12.phx.gbl...

> Hello.
>
> Adding some data to a sql server 2000 table. Is the later more secure than
> the former? If so, why?
>
> SqlCommand sqlCmd = new SqlCommand(update, sqlConn);
>
> sqlCmd.Parameters.Add("@hashedPass", user.HashedPassword);
>
>
>
> SqlCommand sqlCmd = new SqlCommand(update, sqlConn);
>
> sqlCmd.Parameters.Add("@hashedPass", SqlDbType.NVarChar, 255).Value =
> user.HashedPassword;
>
>
>
> Thanks in advance.
>
> Ryan Taylor
>
>