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
Folks, for several weeks now I have been stuffing backups into cloud
storage. Simply because it's convenient in batch files, I have been using
PKZIPC V6 with switch like these -cryptalg=AES,256 -pass=MyL0ngSafePassw0rd
to prepare the files for backup. I mentioned this to my cat and he asked me
some
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.
That can work quite well but be careful if you're using the .nodes() method
in T-SQL to provide the table to join to. It doesn't have cardinality
estimates (actually it "guesses" 10,000 rows) and can end up with some
seriously badly performing query plans. Often we have to use it to extract
the dat
