You can always store XML as NVARCHAR, and then use the XML functions in the view against this column, which first converts the data to XML. However, you will have to weigh how much the work while compensating for the benefits of compression (the processor load will be significant, proportional to the amount of compression that you actually achieve). I can understand the desire to do such things on an I / O-linked system, but I suspect that XML columns are not candidates for compression for precisely this reason - the costs will outweigh the benefits more often than not. If you really intend to store data as compressed, and your biggest problem is storage space, I would think about letting your application do compression (C # here is much more flexible than T-SQL, and I suppose and also let your application deal with XML functions.
source share