In SQL Server 2005, XML was a new data type introduced in order to store XML documents and fragments in a SQL Server database. While this data type is most definitely useful, one of the main questions that you need to ask yourself before using it is "Should I store this data as XML?"
Based on what data should be stored and/or the processing that the data will participate in later, the shredding the XML data to store the data in a relational form (if it is possible) may be the better than storing it as XML to avoid possible storage and performance issues in the future. If the data is going to be used as XML for later processing then storing it as XML is beneficial to avoid extra processing once you consider the cost for storage as being minimal compared to the processing cost. If you are unsure of when or why to use the XML data type then I suggest you read Tim Anderson's interview with Dr Micheal Rys which highlights the thinking behind some features that were introduced and provides some guidance on how to use them. Please note that this article is based on SQL Server 2005, new and improved XML features for SQL Server 2008 will appear in a later post.
Subscribe to:
Post Comments (Atom)
Categories
Analytics
Azure
B2B
Big Data
Business Intelligence
Conferences
CTP
Database Design
Developer
Fun facts
GUI
How-To
Hyper-V
Interview
MCSA
MCSE
Mobile Reporting
NoSQL
O365
PASS
PD
Presentation
Programming
Publication
RLS
SAGO
SBCS
Security
SoftwareONE
SolidQ
SolidQ Journal
SP1
SQL Azure
SQL Database
SQL Database V12
SQL in the City
SQL MVP
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014
SQL Server 2016
SQL Server 2017
SQLSaturday
SSMS
SSRS
St Lucia
T-SQL
T-SQL Tuesday
TechEd 2013
Training
Trinidad & Tobago
TTSAC
TTSSUG
Upgrade
VDI
VHD
Virtual Machines
What's New
Win10
Windows 2012
Windows 2012 R2
XML
0 comments:
Post a Comment