http://blogs.msdn.com/b/nickmalik/archive/2005/09/08/462727.aspxI worry that we may have created a monster. The fact that you can now submit an XML document to SQL Server and it will break it apart for you, storing the parts into tables... it's a pretty compelling idea. However, it also ties the persistence mechanismen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/nickmalik/archive/2005/09/08/462727.aspx#463097Fri, 09 Sep 2005 23:03:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:463097Sean ChaseI like the fact that you can use XML to pass an array of values as a parameter to a stored proc. That's useful. Other than something like that, I'm not that excited about it.<div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=463097" width="1" height="1">http://blogs.msdn.com/b/nickmalik/archive/2005/09/08/462727.aspx#462772Fri, 09 Sep 2005 06:53:35 GMT91d46819-8472-40ad-a661-2c78acb4018c:462772feelitei don't think XML is transient while SQL is persistent as you seem to imply. The tight coupling is of a misuse of the feature. <br> <br>My reasons are at my blog <br> <br>&lt;a href = &quot;<a rel="nofollow" target="_new" href="http://blog.theintellect.net/?p=28&quot;&gt;">http://blog.theintellect.net/?p=28&quot;&gt;</a> <br><a rel="nofollow" target="_new" href="http://blog.theintellect.net/?p=28&lt;/a&gt;">http://blog.theintellect.net/?p=28&lt;/a&gt;</a><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=462772" width="1" height="1">