This is a repost from the sql 2000 forums. dineshasanka has replied and pointed me to some articles, and I am reading this at present. But is any one out there already using this datatype and how are they finding it. Background: I work for a software development house where I am the technical dba for sql server and others. Today a developer came to me and asked me if I thought that having address information stored in an xml datatype would be a good idea. My reaction to this was to say the least negative for the following reasons: denormalising the address to a single line would cause problems in validating components of the address object. extracting data for sorting would involve string operations causing slow processing. instinct leads me to believe that this is not a good idea and while it would save development time it would cause problems with trying to make use of the data later on. However I try and get our developers to ask questions - but beyond the above listed I cannot see provide more. I confess to not knowing anything about the xml datatype and its intended uses. Can anyone out there please itemise advantages or disadvantages of using the xml datatype to store an address - ie "23 nowhere street, bristol, united kingdom, dgr 435" would be store in a single column. How would you use the xml datatype?