Create a sample SQL file for upload testing
Generate an SQL text fixture at your target size. Review its statements and database dialect before execution; comment padding only increases the file bytes.
1 MB = 1,000,000 B · 1 MiB = 1,048,576 B
Advanced: test an upload limit
Enter the byte limit above, then choose one byte below, the exact limit or one byte above. Each choice uses the same base: 10,485,760 B. Generate and download each file to test your endpoint.
What to test with a SQL fixture
Inspect the statements in a text editor and test the upload limit first. Use an isolated database and your own dialect-specific fixture for execution tests.
Choose a size here
These options set the generator above. Separate size guides explain how to test a particular upload boundary.
File structure and testing limits
A short SQL example with block-comment padding. Review the SQL before execution; dialect and permissions remain application-specific.
Format reference: PostgreSQL lexical structure.
This generator assembles the file in your browser; file content is not sent to a server. Site analytics may make network requests. Office ↔ PDF conversion uses a separate server workflow. Data processing and privacy.
Technical notes for every format · Guide to testing file upload limits
Questions
How small can an SQL file be?
About 126 bytes. Below that the format cannot carry its mandatory structure, let alone padding.
Does a larger SQL file contain more database records?
The sample includes a users table and one INSERT statement. Most additional bytes are inside a block comment; the file tests transport and import limits rather than realistic database volume.
Can I ask for an unusual size?
Any byte count above the minimum works — for example 3,145,728 bytes (exactly 3 MB) or 27.5 MB. Drag the caliper or type the number.
Noticed an issue with this test file? Report an issue →