XML database

An XML database is a data persistence software system that allows data to be specified, and sometimes stored, in XML format. These data can be queried, transformed, exported and returned to a calling system. XML databases are a flavor of document-oriented databases which are in turn a category of NoSQL database (meaning Not (only) SQL).

Rationale for XML in databases

There are a number of reasons to directly specify data in XML or other document formats such as JSON. For XML in particular, they include:

• An enterprise may have a lot of XML in an existing standard format
• Data may need to be exposed or ingested as XML, so using another format such as relational forces double-modeling of the data
• XML is very well suited to sparse data, deeply nested data and mixed content (such as text with embedded markup tags)
• XML is human readable whereas relational tables require expertise to access
• Metadata is often available as XML
• Semantic web data is available as RDF/XML

Steve O'Connell gives one reason for the use of XML in databases: the increasingly common use of XML for data transport, which has meant that "data is extracted from databases and put into XML documents and vice-versa". It may prove more efficient (in terms of conversion costs) and easier to store the data in XML format. In content-based applications, the ability of the native XML database also minimizes the need for extraction or entry of metadata to support searching and navigation.

XML Enabled databases

XML enabled databases typically offer one or more of the following approaches to storing XML within the traditional relational structure:

1. XML is stored into a CLOB (Character large object)
2. XML is `shredded` into a series of Tables based on a Schema
3. XML is stored into a native XML Type as defined by ISO Standard 9075-14

RDBMS that support the ISO XML Type are:

1. IBM DB2 (pureXML)
2. Microsoft SQL Server
3. Oracle Database
4. PostgreSQL

Typically an XML enabled database is best suited where the majority of data are non-XML. For datasets where the majority of data are XML, a native XML database is better suited.

Example of XML Type Query in IBM DB2 SQL

select
   id, vol, xmlquery('$j/name', passing journal as "j") as name
from
   journals
where 
   xmlexists('$j[licence="CreativeCommons"]', passing journal as "j")

Native XML databases

These databases are typically better when much of the data is in XML or other non-relational formats.

• BaseX
• Berkeley DB XML Edition
• eXist
• MarkLogic Server

All the above databases uses XML as an interface to specify documents as tree structured data that may contain unstructured text, but on disk the data is stored as "optimized binary files." This makes query and retrieval faster. For MarkLogic it also allows XML and JSON to co-exist in one binary format.

Key features of native XML databases include:

• Has an XML document as at least one fundamental unit of (logical) storage, just as a relational database has a row in a table as a fundamental unit of (logical) storage.
• Need not have any particular underlying physical storage model. For example, NXDs can use optimized, proprietary storage formats. This is a key aspect of XML databases. Managing XML as large strings is inefficient due to the extra markup in XML. Compressing and indexing XML allows the illusion of directly accessing, querying and transforming XML while gaining the performance advantages of working with optimized binary tree structures.

The standards for XML querying per W3C recommendation are XQuery 1.0 and XQuery 3.0. XQuery includes XPath as a sub-language and XML itself is a valid sub-syntax of XQuery.

In addition to XPath, XML databases support XSLT as a method of transforming documents or query-results retrieved from the database. XSLT provides a declarative language written using an XML grammar. It aims to define a set of XPath filters that can transform documents (in part or in whole) into other formats including plain text, XML, or HTML.

But big picture, XML persistence describes only one format in the larger, faster moving NoSQL movement at this time. Many databases support XML plus other formats, even if XML is internally stored as an optimized, high-performance format and is a first-class citizen within the database. (see Google Trends Link above to see relative popularity of terms).

Language features

Name	License	Native Language	XQuery 3.0	XQuery Update	XQuery Full Text	EXPath Extensions	EXQuery Extensions	XSLT 2.0
BaseX	BSD License	Java	Yes	Yes	Yes	Yes	Yes	Yes
eXist	LGPL License	Java	Partial	Proprietary	Proprietary	No	Yes	Yes
MarkLogic Server	Commercial	C++	Partial	Proprietary	Proprietary	No	No	Yes
Qizx	Commercial	Java	Yes	Yes	Yes	No	No	Yes

Supported APIs

Name	XQJ	XML:DB	RESTful	RESTXQ	WebDAV
BaseX	Yes	Yes	Yes	Yes	Yes
eXist	Yes	Yes	Yes	Yes	Yes
MarkLogic Server	Yes	No	Yes	Yes	Yes
Qizx	No	No	Yes	No	No
Sedna	Yes	Yes	No	No	No

References

External links

• DB-Engines Ranking of Native XML DBMS by popularity, updated monthly
• XML Databases - The Business Case, Charles Foster, June 2008 - Talks about the current state of Databases and data persistence, how the current Relational Database model is starting to crack at the seams and gives an insight into a strong alternative for today's requirements.
• An XML-based Database of Molecular Pathways (2005-06-02) Speed / Performance comparisons of eXist, X-Hive, Sedna and Qizx/open
• XML Native Database Systems: Review of Sedna, Ozone, NeoCoreXMS 2006
• XML Data Stores: Emerging Practices
• Bhargava, P.; Rajamani, H.; Thaker, S.; Agarwal, A. (2005) XML Enabled Relational Databases, Texas, The University of Texas at Austin.
• Initiative for XML Databases
• XML and Databases, Ronald Bourret, September 2005
• The State of Native XML Databases, Elliotte Rusty Harold, August 13, 2007
• Qualcomm Qizx Official website