This type of example is exactly the reason why I and many more or 'scared' (or at least concerned) about the CLR Integration in SQL Server 2005. I see absolutely no reason whatsoever to create UDTs that combine two scalar values (in fact I have yet to see any example of a good use for CLR UDTs). This gives no benefits at all, but a lot of problems will come from it. The complexity is much higher, for no reason. The portability is completely lost. Displaying the type will be difficult in many tools (probably will just show a binary). And it is a violation of 1NF, so one might wonder why a relational DBMS is used anyway?