SQL to AsciiDoc Converter

About SQL to AsciiDoc Converter

Convert SQL database dumps (CREATE TABLE and INSERT statements) to AsciiDoc table markup for technical documentation, books, and articles. AsciiDoc is a lightweight markup language widely used for technical writing and documentation.

Key Features

• Multiple Table Styles: Default, grid (all borders), and frame (outer border)
• Column Alignment: Auto-detect, left, center, or right alignment
• Header Support: Optional header row
• Table Titles: Automatically uses table name as title
• Column Specifications: Proper AsciiDoc column syntax
• Smart Parsing: Extracts column names and data from SQL dumps
• File Download: Save as .adoc file

How to Use

1. Input SQL Data: Paste your SQL CREATE TABLE and INSERT statements or upload a .sql file
2. Choose Table Style: Select default, grid, or frame style
3. Set Alignment: Choose auto-detect or specific alignment
4. Configure Header: Toggle header row display
5. Copy or Download: Use the Copy or Download button to save your AsciiDoc markup

Table Styles

Default:

• Clean, minimal table appearance
• No explicit borders in markup
• Relies on AsciiDoc processor defaults

Grid (all borders):

• Shows all cell borders
• Professional appearance
• Best for complex tables

Frame (outer border):

• Shows only outer table border
• Clean, modern look
• Good for simple tables

Example Conversion

SQL Input:

CREATE TABLE products (
  id INT,
  name VARCHAR(100),
  price DECIMAL(10,2),
  category VARCHAR(50)
);

INSERT INTO products VALUES (1, 'Laptop', 999.99, 'Electronics');
INSERT INTO products VALUES (2, 'Mouse', 24.99, 'Accessories');

AsciiDoc Output:

.products
[cols=">,<,>,<"]
|===
|id
|name
|price
|category

|1
|Laptop
|999.99
|Electronics

|2
|Mouse
|24.99
|Accessories

|===

Alignment Options

Auto-detect:

• Automatically detects numeric columns
• Right-aligns numeric data
• Left-aligns text data
• Recommended for most use cases

Left Alignment (<):

• Default alignment for text
• Best for names and descriptions

Center Alignment (^):

• Balanced visual appearance
• Good for headers and short values

Right Alignment (>):

• Perfect for numeric values
• Aligns decimal points naturally

Common Use Cases

• Technical Documentation: Include database schemas in technical docs
• Books: Write technical books with AsciiDoc and Asciidoctor
• API Documentation: Document database structures
• README Files: Create professional documentation
• GitHub Pages: Use with Jekyll-AsciiDoc plugin
• PDF Generation: Convert to PDF with Asciidoctor-PDF

AsciiDoc Syntax

• Table Delimiter: |=== marks table start and end
• Cell Separator: | character separates cells
• Column Specs: cols attribute defines alignment and width
• Table Title: . prefix creates table caption
• Alignment: < (left), ^ (center), > (right)

AsciiDoc Processors

• Asciidoctor: Modern AsciiDoc processor (Ruby)
• Asciidoctor.js: JavaScript implementation
• Asciidoctor-PDF: Direct PDF generation
• Asciidoctor-EPUB3: EPUB book generation

Supported SQL Syntax

• CREATE TABLE: Extracts column names for table headers
• INSERT INTO: Parses data values from INSERT statements
• Data Types: Handles all SQL data types (VARCHAR, INT, DECIMAL, etc.)
• Quoted Strings: Handles single and double quotes with proper escaping

Integration

The generated AsciiDoc markup works with:

• Asciidoctor: Convert to HTML, PDF, EPUB, and more
• GitHub: Render .adoc files in repositories
• GitLab: Native AsciiDoc support
• Static Site Generators: Jekyll, Hugo with plugins
• IDEs: IntelliJ IDEA, VS Code with extensions

Privacy & Security

All conversions happen locally in your browser. Your SQL data is never uploaded to any server, ensuring complete privacy and security.

FAQ

• Which AsciiDoc flavor is this compatible with? The output follows standard AsciiDoc syntax and works well with Asciidoctor and other common processors that support table markup.
• Why are pipes (|) escaped in cell content? The | character has special meaning in AsciiDoc tables, so the converter escapes it inside cell values to keep the table structure intact.
• Can I customize column widths as well as alignment? Yes. After export you can adjust the cols="..." specification to include widths or more advanced options if your AsciiDoc toolchain supports them.
• What if my SQL has no CREATE TABLE statement? The tool can still work from INSERT statements alone, but it will generate generic column names if it cannot infer them from an INSERT column list.
• Is it safe to mix these tables with existing AsciiDoc content? Yes. You can drop the generated table block into any AsciiDoc document; just ensure there is a blank line before and after the table for correct parsing.