I need to write a table-valued function to query a web service and return the
contents of a DataTable.  the trick though, is that I don't know what the
table looks like at compile time, so I cannot write a proper
FillRowMethodName method, which needs apriori knowledge of the data ...

Can anyone list the advantages and disadvantages of CLR Stored
Procedures vs. sp_OACreate 'MSXML2.ServerXMLHttp' in SQL2005 for
calling .NET webservices?   Aside from a bit nicer programming model,
that is. I'm considering spending time converting existing sp_OACreate