SQL Server provides a variety of ways to tune XML so that it provides consistent performance, consumes less space, all while ensuring efficient access to critical data. At its core, the metadata-styled XML format runs counter to the data that SQL Server is optimized to manage.
2024-07-15
XML is a common storage format for data, metadata, parameters, or other semi-structured data. Because of this, it often finds its way into SQL Server databases and needs to be managed alongside other data types.
2024-06-24
2022-01-28
577 reads
Determining the property syntax when modifying XML values in SQL Server can be time consuming if you don’t work with XML regularly. SQL Server includes a very flexible XML...
2019-05-15
Learn how to use T-SQL to fix contents of an XML document using FLWOR
2019-01-17
2,558 reads
What is the most efficient way to modify XML values? To allow for precise modification of XML nodes and values, the XQuery XML query language employs an extension known as the XML Data Modification Language (DML). The XML DML uses the XML modify() method, which makes use of three operational keyword sets: insert, replace value of, and delete. Seth Delconte takes a closer look.
2018-07-11
2,712 reads
Free download to all Simple Talk users. XML has been part of the SQL Standard since 2003, and is essential for any DBA because so many of the dynamic management views return XML data. Now that the industry is more used to data defined by document markup, it is becoming more important than ever for Database Developers and DBAs to understand the technology and to know where it makes sense to use XML.
2017-06-02
6,152 reads
Source xml is a rendition of a cross-tab report. I show the evolution of a Spackle solution for import as a SQL resultset.
2017-06-08 (first published: 2017-06-01)
489 reads
2017-01-20
1,017 reads
2016-08-25
1,136 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Comments posted to this topic are about the item The AI Bubble and the...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers