There's been a brief discussion on the SQL Server 2005 XML newsgroup regarding RSS and the XML type on SQL, encoding and schema. In keeping with my recent series of code-heavy examples, here's the guts of a primvative little VB.NET console app that sucks feeds into a table.
The basic gist of the problem is that the XML type doesn't look at the content to determine encoding unless the source that being converted from is binary, but if an encoding is given in the prolog other than UTF-16 (in most cases), SQL complains that it can't switch the encoding. That's seldom the case with client side code where we are using SqlXml typed parameters. It seems the trick is to parse off the document prolog so that we're just feed the typed column data and not encoding information.
Continues at http://sqljunkies.com/WebLog/ktegels/articles/5013.aspx
You'll notice that a lot of recently posted comments in this blog has been deleted. Why? While they looked like they we're on topic, they we're simply junk trying to use my Google rankings to draw folks to their spam sites. Fancy!
FWIW, if you are postings with a source IP of two-zero-three-dot-one-zero-one-do-three-one-dot-eight-two, yep, purge them. You might also want to consider block at the firewall. It's an address in New Delhi...
IMHO, ISP have no reason to do anything about abusers until they start losing business; they start losing business when people can't use their service to reach the content the want. I know its punative, but sometimes you got to work from the bottom up.