April 17, 2003 at 3:12 pm
Has anyone else encountered the problem where long FOR XML return sets are broken into snippets, with carriage returns scattered throughout the return set? Is this something that only appears when I run it through QA? I've tried it as "Results in Text" and "Results to File".
Thanks for the help,
Rick
Rick Todd
April 21, 2003 at 8:00 am
This was removed by the editor as SPAM
April 21, 2003 at 9:14 am
There is a trace flag (257) that makes the output a little easier to work with.
Andy
April 21, 2003 at 9:29 am
quote:
There is a trace flag (257) that makes the output a little easier to work with.
I tried that Andy. Upon further investigation it appears that SQL Server is putting a carriage return in every 2035 characters, even when output to a file...
Rick Todd
April 21, 2003 at 9:48 am
From QA only? If you use an ADO stream, I don't think you'll have this issue.
Andy
April 29, 2003 at 3:27 pm
Andy is correct. I have used the ADO Stream object and returned very large XML results. I have had no problems with extra carriage returns.
Phil Cleveland
April 29, 2003 at 3:39 pm
Thanks for the input guys. I figured it was a lot easier to get feedback from you guys, than to either figure out to do it myself in code, or convince one of the developers to test it for me!
Rick
Rick Todd
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply