FOR XML data vs Recordset

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mahesh.aloysius@gmail.com - 03 Jul 2008 15:47 GMT

Hello,

I have an option to return data from a stored procedure using XML or
recordset. I do not intend to do any sort of XSL or anything but would
be transforming them into typed objects in the Data access layer.

Does anyone know of the performance differences when a stored
procedures returns XML data using "FOR XML" and one returning
recordset?

Any advice would be greatly appricated. Thanks in advance for your
help.

Regards,
Mahesh

Reply to this Message

Rick Sawtell - 03 Jul 2008 16:24 GMT

> Hello,
>
[quoted text clipped - 11 lines]
> Regards,
> Mahesh

It depends. The big difference is in the amount of data moving between
the db and the data access layer of the application. XML adds a lot of
overhead to that transfer of information. If this is a small set of data,
that is not called a whole lot, then XML may work well for you. If this is
a high volume transaction with large data sets, then this may really slow
things down for you.

Rick Sawtell

Reply to this Message