Greg Using xml (tables/parameters) in sql databases should be your final last ditch choice, they perform woefully badly.
What exactly are you trying to do that can't be done with 1. Repeatable calls to the same prepared sp. 2. Sql in clause generated in code? 3. Sqlcmd query? 4. Bulk loading data. Xml in databases will bite you in the ass later. .02c Davy "When all you have is a hammer, every problem looks like a nail." I feel much the same way about xml -----Original Message----- From: "Greg Keogh" <[email protected]> Sender: [email protected] Date: Thu, 30 Jun 2011 09:45:16 To: <[email protected]>; 'ozDotNet'<[email protected]> Reply-To: ozDotNet <[email protected]> Subject: RE: SQL CLR table as function parameter Chaps, in future, I think I'll consider feeding XML into user-defined procs and functions (especially those written in managed code). I personally have only needed to do the most simple parsing of XML in T-SQL using the "SelectNodes" lookalike techniques, but I knows there's a lot more you can do. I'll probably be forced to return to this subject soon. In the meantime I hard-coded a few CLR functions with different numbers of parameters to suit our needs. The general purpose method taht I planned can come later. - Greg
