Xml stored as varbinary I'm wondering if I have to 
store a XML information inside a column (just storing, not for querying ) (SQL SERVER)
which Datatype is better to use XML or Varbinary? I did an example:

DECLARE @ClientList XML
SET @ClientList =
'&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!-- A list of current clients --&gt;
&lt;People&gt;
&lt;Person id="1234"&gt;
&lt;FirstName&gt;Juan&lt;/FirstName&gt;
&lt;LastName&gt;Perez&lt;/LastName&gt;
&lt;/Person&gt;
&lt;Person id="98765"&gt;
&lt;FirstName&gt;Alfredo&lt;/FirstName&gt;
&lt;LastName&gt;Domiguez&lt;/LastName&gt;
&lt;/Person&gt;
&lt;/People&gt;'

Declare @ClientListBinary Varbinary(max)
set @ClientListBinary = CONVERT (varbinary(max),@clientlist,1)
print datalength(@ClientList)
print datalength(@ClientListBinary)


and the result is that Varbinary uses more space... any thoughts on that
If your RDBMS has an xml datatype, why would you not use it?

For example, in SQL Server, you should put XML data in an xml column, because:


The XML data can be compared to an XML Schema Collection, to give the functionality of typed XML.
The XML data can be shredded with XQuery later.
The XML data can be indexed with a number of different XML index types, which help the XQuery shredding.


As far as I can see, the only reason to use varbinary(max) over xml is if you expect to be putting more than 2GB of data into one field. (Of course, there may be other reasons, which I'm sure I'll learn from the posts here. :-).