by Jason Baile » Wed, 22 Aug 2001 04:25:55
Thanks,
Jason
by Bryant Like » Wed, 22 Aug 2001 06:16:16
Do all 255 columns have values in them? When using for xml columns with NULLQuote:> I have found that SQL Server 2000 only returns 87 columns out of a
possible
> 255 in a large table we have. I am using "select * from table_x for xml
> auto, elements". Is there a limitation to SQL that doesn't have a
> workaround or a configuration property I need to set?
--
Bryant
http://sqlxml.org
1. limitations of FOR XML - saving xml message to message queue
Does anyone know a way to have a stored procedure
save an xml result set as a message queue?
Currently I am kludging it by appending xml tags
to my result set, then looping through the result
set / cursor. It is working but but I am wondering
if there is a way to do it using FOR XML AUTO. It
seems that FOR XML AUTO returns a stream object,
and this stream cannot be converted to a string
in the stored procedure. It seems that FOR XML
is only good if you are going to be manipulating
the STREAM with VB or .NET. I have to have the
stored procedure save the FOR XML stream directly
to the message queue. If anyone know a good way
please let me know.
I found this free extended procedure that saves messages to the
message queue.
http://www.sqlservercentral.com/products/xp_msmq/default.asp?scriptid=5
If you've tried doing this with sp_OACreate, you'll have a sorry tale
to tell. You get all the way to setting the body of the message, then
it all goes wrong because the data type (variant) of the message body
property is incompatible with OLE Automation.
2. Indexes & Cluster - more information.
3. how to overcome ResultSet limitations in DB2?
4. DBA position open in San Francisco
5. Newbie: SQL Aggregate Functions????
7. Size limitation of the resultset?
8. SQLXMLBulkLoad size limitation for XML file
10. Relational Queries Against XML Data - 8K Limitation?
11. Stored procedure XML output limitation