CACrown ArchivesThe cinema collection
Menu
Research dossier · Science & Nature

XML database

data persistence software system that allows data to be specified, and sometimes stored, in XML format

Specimen drawers, botanical folios and brass scientific instruments under study light
Science and natureInterpretive dossier study · Crown Archives visual atlas
Record originEnglish Wikipedia
Text licenseCC BY-SA 4.0
Source revisionJul 10, 2026
Entity authorityQ357393
Source-derived summary

An XML database is a data persistence software system that allows data to be specified, and stored, in XML format. This 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 database.

Rationale for XML as a database format

Reasons to store data in XML format as an XML database include:

An enterprise may have numerous XML documents with similar data, but dispersed in different XML formats. Conglomerating this data into a singular, standardized XML database structure will avoid compatibility issues

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 parse 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

Provides a solution for Object-relational impedance mismatch

Compatibility with XML use on the data transport layer

XML-enabled databases

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

XML is stored into a CLOB (Character large object)

XML is "shredded" into a series of tables based on a schema

XML is stored into a native XML Type as defined by ISO Standard 9075-14

RDBMS that support the ISO XML Type are:

IBM DB2 (pureXML)

Microsoft SQL Server

Oracle Database

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

Native XML databases

Native XML databases are especially tailored for working with XML data. As managing XML as large strings would be inefficient, and due to the hierarchical nature of XML, custom optimized data structures are used for storage and querying. This usually increases performance both in terms of read-only queries and updates. XML nodes and documents are the fundamental unit of (logical) storage, just as a relational database has fields and rows. One important caveat to this is that native XML databases need more disk space to store both data and indexes than XML-enabled databases do.

Editorial summary

Begin with the source’s own compact description: “XML database” is data persistence software system that allows data to be specified, and sometimes stored, in XML format. The dossier treats that line as a proposition to test through database, data and persistence, not as a finished interpretation.

Editorial reviewUseful for establishing the present vocabulary of the subject while preserving a route back to the evidence on which that vocabulary rests. The current 390-word lead offers orientation but no explicit four-digit date, so chronology should not be assumed. The selected authority fields contribute no independent date. For this dossier, database, data and persistence is the immediate research focus.
Editorial analysis

Why this record matters

The phrase “data persistence software system that allows data to be specified, and sometimes stored, in XML format” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.

Evidence profile

Datasets, specimens, observations and peer-reviewed methods provide the appropriate test for the technical claims summarized here. The source revision retrieved here is dated Jul 10, 2026. The linked authority identifier is Q357393. None of the 0 selected statements returned an explicit reference.

Critical limits

Scientific names, classifications and consensus can change while older terminology persists in catalogues and historical literature. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.

How to read it

Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.

Best used for
  • Current terminology
  • Classification context
  • Finding cited technical literature
Verify next

Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.

Three-step research path

  1. Establish the record: confirm the title “XML database”, its source revision and the description used here.
  2. Expand the search: follow XML database primary sources, XML database archive and database research across catalogues and specialist indexes.
  3. Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.

Questions for further research

  1. Which source most directly establishes the central claim about “XML database”?
  2. Which observation, specimen, dataset or publication supports the account?
  3. Is the terminology current, historical or disputed?
Subject index

Search terms from this dossier

Source & attribution

This entry incorporates text from XML database” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.