XML support has been significantly extended for SQL Server 2005. In this article, Tim Chapman takes a look at how you can shred XML data into a relational format with SQL Server's OPENXML function.
2007-02-22
4,779 reads
Tim Chapman discusses new functionality in SQL Server 2005 that allows you to shred XML data into a relational format without the intensive memory operations. He also explains how using XQuery rather than OPENQUERY can lead to performance gains.
2007-02-20
3,813 reads
XML is becoming more and more prevalent in applications and more SQL Server DBAs are learning to work with this data structure. Raj Vasant brings us part 2 of his series on using OPENXML inside SQL Server, looking at passing XML into your stored procedures this time.
2006-02-16
8,418 reads
2005-05-30
13 reads
SQL Server 2000 added XML support awhile back, though it was limited in what is offered and can be a little confusing. SQL Server 2005 will add many more features and functions, but in the meantime, if you are looking to add some XML support to your 2000 server, new author Raj Vasant brings us some basics on using OpenXML.
2007-02-23 (first published: 2005-05-12)
43,020 reads
Want to take advantage of some of the benefits of using XML for data exchange, take a look at 'FOR XML' in SQL 2000.
2001-05-10
6,150 reads
By Steve Jones
I caught this interesting item over on Pinal Dave’s blog: Eleven Interview Questions that...
By Hemantgiri
I use color-coded connections in SSMS to distinguish Production, Pre-Production, UAT, and Development. But...
Comments posted to this topic are about the item Split Large Queries in Athena...
Comments posted to this topic are about the item Finding Trailing Spaces
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers