What SQL statements does this support?

Only INSERT INTO table (col, ...) VALUES (...), (...); statements. SELECT, CREATE TABLE, UPDATE, DELETE, and any other statement type aren't parsed, this is intentionally narrow, not a general SQL parser.

Can I convert multiple rows at once?

Yes, a single INSERT statement with multiple comma-separated value tuples (VALUES (1,'a'), (2,'b')) produces one XML per tuple.

How are NULL and quoted values handled?

NULL becomes an empty element, quoted strings ('...') have their SQL-escaped doubled quotes ('') unescaped back to a single quote, and unquoted numeric-looking values become plain numbers.

SQL to XML Converter - Convert INSERT Statements Online

Overview

Introduction

A handful of INSERT statements, say, from a database seed script or a support ticket, are sometimes easier to inspect or share as XML.

This tool converts them directly.

What Is SQL to XML Converter?

A narrowly-scoped SQL parser that recognizes only the INSERT INTO ... VALUES ... shape.

It converts each value tuple into an XML <row> element under a single <rows> root.

How SQL to XML Converter Works

The statement is matched against an INSERT INTO table (columns) VALUES (...) pattern.

The column list and each parenthesized value tuple are parsed, respecting quoted strings so commas inside a quoted value aren't mistaken for tuple separators, and each tuple becomes one <row> with columns mapped to child elements.

When To Use SQL to XML Converter

Use it to quickly turn a handful of INSERT statements from a seed script or support ticket into readable, shareable XML.

It's also useful for reviewing exactly what a generated INSERT statement contains before running it.

Often used alongside XML to SQL Converter and CSV to XML Converter.

Features

Advantages

Handles multiple value tuples from a single statement.
Respects quoted strings when splitting values, so commas inside data don't break parsing.
Runs entirely client-side.

Limitations

Only INSERT INTO ... VALUES ... is supported; every other SQL statement type will report an error rather than attempting a best-effort parse.
Column names come directly from the statement's column list, unusual or quoted identifiers may need cleanup after conversion.

Examples

Converting a multi-row INSERT

Input

INSERT INTO users (id, name) VALUES (1, 'Ada'), (2, 'Alan');

Output

<?xml version="1.0" encoding="UTF-8"?>
<rows>
  <row>
    <id>1</id>
    <name>Ada</name>
  </row>
  <row>
    <id>2</id>
    <name>Alan</name>
  </row>
</rows>

Each parenthesized value tuple becomes its own <row> element.

Best Practices & Notes

Best Practices

If parsing fails, confirm your statement is exactly INSERT INTO ... (columns) VALUES (...); with no other SQL mixed in.
Use XML to SQL Converter to check what a round trip does to your specific rows.
Strip trailing comments or a second statement from the pasted SQL before converting.

Developer Notes

Value-list splitting tracks quote state and parenthesis depth manually (not with a single regex) so that commas inside quoted strings or nested expressions don't split a value incorrectly.

SQL to XML Converter Use Cases

Turning a handful of seed-script INSERT statements into readable XML
Sharing example database rows from a support ticket as XML
Reviewing what a generated INSERT statement actually contains

Common Mistakes

Pasting a SELECT, UPDATE, or CREATE TABLE statement, only INSERT INTO ... VALUES ... is supported.
Including a trailing comment or a second statement in the same input, which breaks the pattern match.

Tips

Use XML to SQL Converter to check what a round trip does to your specific rows.
Check the FAQ above if the output doesn't look like what you expected.

SQL to XML Converter