X-Men Code 127
One of the more interesting things about SQL Server 2005 is the support for the XML datatype. Instead of playing around with wierd and funky stored procedures to manipulate XML, you get validation and a bunch of other features just by specifying a field or a parameter as XML. Now, as nice as it is to be able to serialize a .net object and store the entire thing in one field in the database, I have my feelings that there is significant overhead to querying into that XML on a more than ad-hoc basis. So, you *might* want to add some additional fields to the table containing the xml. For example if you had the following XML: <OrderID>0a4fc0f8-6106-467f-ae10-45dcbfe4cefa</OrderID> <CustomerNumber>1234</CustomerNumber> <Status>Active</Status><Lines> <OrderLine ItemId="123" Quantity="2" Taxable="false" Price="12.34" DateChanged="2006-04-20T12:16:20.8942144-06:00" IsReadOnly="false"><...