XML Reader on SQL Table returning invalid XML?

It's to do with the XmlTextReader. Normalization property. This property is set to false when you explicitly create an XmlTextReader, so the "invalid" characters are decoded.

When the XmlTextReader is created implicitly, Normalization is set to true.

The exception is telling you the truth. SQL Server apparently permits the display of invalid XML. Try this.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.