https://www.adathedev.co.uk/tags/xml/Recent content in XML on AdaTheDev BlogHugo -- gohugo.ioadathedev@gmail.com (Adrian Hills)adathedev@gmail.com (Adrian Hills)Mon, 16 Jan 2012 10:36:00 +0000https://www.adathedev.co.uk/2012/01/modifying-xml-data-before-returning.htmlMon, 16 Jan 2012 10:36:00 +0000adathedev@gmail.com (Adrian Hills)https://www.adathedev.co.uk/2012/01/modifying-xml-data-before-returning.htmlThis post follows on from a question I recently replied to, for how to exclude a specific node from an XML column value before returning it, using TSQL. Example setup CREATE TABLE Example ( ID INTEGER IDENTITY(1,1) PRIMARY KEY, XmlField XML ) INSERT Example (XmlField) VALUES ('<Root><ChildA>Value I want to see</ChildA><ChildB>Value I do not want to see</ChildB></Root>') So if you want to return the XML minus the ChildB node, how do you do it?https://www.adathedev.co.uk/2010/06/sql-server-xml-datatype-with-cdata.htmlMon, 14 Jun 2010 14:06:00 +0100adathedev@gmail.com (Adrian Hills)https://www.adathedev.co.uk/2010/06/sql-server-xml-datatype-with-cdata.htmlSo today I learnt something new - it turns out the XML datatype in SQL Server does not preserve CDATA sections. e.g. DECLARE @XML XML SET @XML = '<Test><NodeA><![CDATA[Testing cdata section <woop!>]]></NodeA></Test>' SELECT @XML Results ------------------------------------------------------------------ <Test><NodeA>Testing cdata section <woop!></NodeA></Test> After a quick dig around, I found this MS Connect case. I personally would like to see it accept whatever you pass in without silently altering it, as long as it’s well-formed XML of course.https://www.adathedev.co.uk/2010/02/sql-server-2008-table-valued-parameters.htmlThu, 11 Feb 2010 20:38:00 +0000adathedev@gmail.com (Adrian Hills)https://www.adathedev.co.uk/2010/02/sql-server-2008-table-valued-parameters.htmlThe scenario is, you want to create a stored procedure that returns the records relating to a finite set of keys/IDs that you pass in to it. How do you do it? Well you could use dynamic SQL, but for the purpose of this article I’m going to ignore that option. Test scenario -- Create basic customer table CREATE TABLE [dbo].[Customer] ( Id INTEGER IDENTITY(1,1) PRIMARY KEY, Name NVARCHAR(50) NOT NULL ); GO -- Populate Customer table with 100,000 sample records DECLARE @Counter INTEGER SET @Counter = 1 WHILE (@Counter <= 100000) BEGIN INSERT Customer (Name) VALUES ('Test Customer #' + CAST(@Counter AS VARCHAR(10))) SET @Counter = @Counter + 1 END Option 1 - CSV list of keys In SQL Server 2000, you would most likely have ended up passing in a CSV list of keys, splitting that out into a table, and then joining that on to your real data table to match the records to return.