AI2sql Docs
Go to AppContact
  • 1. Introduction
    • 1.1. What is AI2SQL?
    • 1.2. Key features of AI2SQL
    • 1.3. How to get started with AI2SQL
    • 1.4. What Users Can Ask AI2SQL
  • 2. AI2SQL Dashboard
    • 2.1. Accessing the dashboard
    • 2.2. Generating SQL based on predefined datasets
    • 2.3. Exploring sample queries and use cases
  • 3. Managing Tables
    • 3.1. Importing tables using DDL
    • 3.2. Manually adding tables
    • 3.3. Editing, Updating, and Deleting Table Information
    • 3.4. Importing Database Schema via CSV
  • 4. AI2SQL Workspace
    • 4.1. Navigating the workspace
    • 4.2. Generating SQL for specific database engines
    • 4.3. Selecting tables for SQL generation
    • 4.4. Saving and organizing queries in the workspace
  • 5. Formatting SQL
    • 5.1. Accessing the SQL formatter
    • 5.2. Customizing formatting options
    • 5.3. Applying formatting to your SQL queries
  • 6. SQL Fixer
    • 6.1. Identifying SQL errors with SQL Fixer
    • 6.2. Understanding common SQL error messages
    • 6.3. Resolving SQL errors using AI2SQL's suggestions
    • 6.4. Handling Long SQL Queries
  • 7. Formula Generator
    • 7.1. Overview of Formula Generator
    • 7.2. Excel, Google Sheets, and regex formula translation
    • 7.3. Power BI DAX formula translation
    • 7.4. Airtable formula translation
    • 7.5. Using Formula Generator to enhance SQL queries
  • 8. CSV Analyzer
  • 9. Database Connectors
    • 9.1. Supported database connectors
    • 9.2. Setting up database connections (MySQL, SQL Server, or PostgreSQL)
    • 9.2.1. AI2sql Oracle Cloud Connector
    • 9.3. Setting up MongoDB Connectors
    • 9.4. Google BigQuery Setup and Service Account Key Creation
    • 9.5. Generating SQL queries for connected databases
    • 9.6. Setting up Snowflake Connectors
    • 9.7. Troubleshooting AI2sql Connector Issues: A Comprehensive Checklist
    • 9.8. Requesting new database connectors
    • 9.9. System Security Overview
  • 10. Dataset Questions Generation
  • 11. AI2SQL ChatGPT Plugin User Guide
    • 11.1. Introduction
    • 11.2. Getting Started
    • 11.3. Obtaining Your Token
    • 11.4. Using Your Token
    • 11.5. Connecting Your MSSQL (SQL Server) Database
    • 11.6. Connecting Your MySQL Database
    • 11.7. Connecting Your PostgreSQL Database
    • 11.8. Generating SQL Queries
    • 11.9. Troubleshooting
  • 12. Troubleshooting and Support
    • 9.1. Common issues and solutions
    • 12.2. Chat Support
    • 12.3. Contacting AI2SQL support
    • 12.4. Community resources and forums
  • 13. Templates
    • 13.1. Custom Template Creation
    • 13.2. Save the Template
    • 13.3. Generate SQL Using Template
  • 14. AI2sql: SQL Generation from Database ER Diagrams
    • 14.1. Introduction
    • 14.2. SQL Generation Process
    • 14.3. Troubleshooting & FAQs
  • 15. AI2sql API Integration
  • 16. AI2SQL Dictionary Template
  • 17. AI2sql GPTs
    • 17.1. Getting Started
    • 17.2. Obtaining Your Token
    • 17.3. Connecting Your MySQL Database
  • 18. Connecting Your Local Database
  • 19. SQL File Uploader
    • 19.1 Generating SQL queries
Powered by GitBook
On this page
  • Adding an ERD Diagram
  • How to Add an ERD Diagram
  • Best Practices for ERD Uploads
  • What Happens Next
  • Troubleshooting
  • Limitations
  1. 14. AI2sql: SQL Generation from Database ER Diagrams

14.2. SQL Generation Process

Previous14.1. IntroductionNext14.3. Troubleshooting & FAQs

Last updated 9 months ago

Adding an ERD Diagram

Our SQL generator tool allows you to upload an Entity-Relationship Diagram (ERD) to quickly generate SQL based on your database design. This feature is perfect for users who have already created their database schema visually and want to convert it into SQL code.

How to Add an ERD Diagram

  1. Navigate to the "Add ERD Diagram" screen in the tool.

  2. You'll see a form with the following fields:

    • Database Name*

    • Database Description

    • ER Diagram* (upload area)

  3. Fill in the fields as follows:

Database Name*

Enter a name for your database. For example: "customers"

  • Use lowercase letters, numbers, and underscores.

  • Avoid spaces and special characters.

  • The name should reflect the overall purpose of your database.

Database Description

Provide a brief description of your database. For example: "store information about customers"

  • This helps document your database for future reference.

  • Keep it concise but informative.

ER Diagram*

Upload your ER Diagram here.

  • Accepted formats: .jpg, .png, .bmp, or .svg

  • Ensure the image is clear and legible.

  • The diagram should show all tables, columns, and relationships.

  1. After filling in all the required information and uploading your ERD, click the "Finish" button to proceed.

Best Practices for ERD Uploads

  1. Image Quality: Ensure your ERD is high resolution and all text is readable.

  2. Complete Information: Your ERD should include all tables, columns, data types, primary keys, foreign keys, and relationships.

  3. Consistent Notation: Use standard ERD notation to ensure accurate interpretation.

  4. Legible Layout: Arrange your entities and relationships clearly to avoid confusion.

  5. Include Cardinality: Show the nature of relationships between entities (one-to-one, one-to-many, many-to-many).

  6. Color Coding: If used, ensure it adds clarity rather than complexity.

What Happens Next

After uploading your ERD:

  1. Our system will analyze the diagram to identify tables, columns, and relationships.

  2. SQL code will be generated based on the interpreted schema.

  3. You'll have the opportunity to review and edit the generated SQL.

  4. You can then use this SQL to create your database or make further modifications.

Troubleshooting

If the generated SQL doesn't match your expectations:

  • Check that your ERD is clear and follows standard notation.

  • Ensure all relationships are clearly marked.

  • Try uploading a higher resolution image if text is not being read correctly.

Limitations

Please note:

  • The accuracy of the SQL generation depends on the clarity and completeness of your ERD.

  • Complex constraints or database-specific features may not be fully captured from the diagram alone.

  • You may need to manually adjust the generated SQL for advanced features or optimizations.

Remember, while this feature can save significant time, it's always important to review and test the generated SQL to ensure it meets your specific requirements.