I was finishing a design on a web service and at the review a question
was raised about my using a SQLParameter array as a parameter to a
method in the web service. The preference the person had was to use
xml instead. If I understood him correctly he indicated that DotNet
converts everything to xml anyways in a web service and so by using
the array I might be creating some unnecessary overhead?

I was curious about how I could determine the actual amount of
overhead that might be caused by something like this?

"Doogie" <dnlwhite (AT) dtgnet (DOT) com> wrote

It's not a matter of .NET doing the conversion. Web Services almost always
use XML.

You should not use platform-specific types in a web service if you intend
any other platform to understand them. A Java application will not
understand SQLParameter.

Out of curiosity, why are you passing SQLParameter values in a web service?

John

Hi John,
The short version is that we were planning a type of process to send
stored proc calls to a table in our database that are "process heavy"
and take a while to execute. A SQL job was going to pick them up and
actually run them. So we were sending the proc name, and info on the
parameters to the web service which would then insert that info into a
table that the SQL job would read and then execute accordingly. Thus
I need an array of some kind that users of the web service can shoot
me off their parameter info.

But, since I posted the question, the design was put on hold. Seems
they want to wait until we get SQL 2005 completely installed on all
our sql servers first.

Thanks though for the input!