Posted by Terri on 11/14/05 17:07

Thanks to those who replied, I'm going to investigate the ADO stream object.

"Erland Sommarskog" <esquel@sommarskog.se> wrote in message
news:Xns970CB19EE5537Yazorman@127.0.0.1...
> pb648174 (google@webpaul.net) writes:
> > If you are already calling this code from ADO, then instead of BCP and
> > all that you can just directly execute the FOR XML statement, loop
> > through each 2033 char return results and create the XML file from the
> > web server.
>
> Actually, if he would do it the simple-minded way, he would not get
> 2033-characters slices, as he is using SQLOLEDB(*) - he would get a binary
> thingie instead.
>
> I have not investigated it, but I believe the proper way to receive FOR
> XML in ADO with SQLOLEDB is to use the Stream object.
>
> But apart from that fine detail, I agree with you. Doing this from SQL
> Server will be diffictul.
>
> (*) If you use the MSDASQL provider, that is ODBC, then you would have
> to as you say. But I would not recommend that.

[Back to original message]