Corrupt an SQL File Online
Corrupt a .sql dump online for free. Breaks statement structure and encoding so imports fail instead of loading partial data.
- Nessun caricamento
- Nessun limite di dimensione
- Nessuna registrazione
Corrompi il tuo file SQL
Calibrato per .sql, .dump, e funziona altrettanto bene con qualsiasi altro formato.
Perché i file SQL sono difficili da corrompere per bene
An SQL dump is a text file of statements executed in order. That makes partial corruption genuinely dangerous in the real world, an import can succeed for thousands of rows and then fail halfway, leaving a database in an inconsistent state. Reproducing that on demand is exactly what this is for.
Cosa distrugge questo strumento
- Statement terminators. Semicolons and line breaks are overwritten, so statements run together into unparseable input.
- String literal quoting. Quotes are broken up, leaving literals unterminated and swallowing subsequent statements.
- The dump header. The opening bytes containing the client and server version comments are destroyed.
- Encoding validity. Invalid UTF-8 sequences make the file fail on import before any statement executes.
Cosa vedrai dopo
| Applicazione | Comportamento |
|---|---|
mysql < dump.sql | "ERROR 1064 (42000): You have an error in your SQL syntax" and the import aborts. |
psql -f | Reports invalid byte sequence for the encoding and stops. |
| phpMyAdmin / Adminer | Import fails with a syntax error and a line number. |
| Light level | Import may run partway before failing, the realistic partial-restore scenario. |
Motivi comuni per farlo
- Rehearsing a restore from a damaged backup before it happens for real.
- Verifying an import runs inside a transaction and rolls back cleanly on failure.
- Testing that a migration tool reports the failing statement rather than continuing.
- Demonstrating why backups must be verified, not just taken.
Come corrompere un file SQL
- Trascina il tuo file .sql nel riquadro qui sopra, oppure fai clic per sfogliare.
- Lascia il livello su Standard, a meno che tu non voglia un danno parziale (Light) o debba sconfiggere un software di recupero (Heavy).
- Premi Corrompi file. L'elaborazione avviene sul tuo dispositivo, quindi termina quasi subito.
- Scarica il risultato. Per impostazione predefinita mantiene il nome file e la lunghezza in byte originali.
Domande frequenti su SQL
Can I simulate a partial restore?
Yes, and this is the most useful case. Light level leaves most statements intact, so an import typically runs for a while before failing, which is precisely the scenario that catches missing transaction handling.
Does it work on compressed dumps?
A .sql.gz file is handled as a gzip archive instead, which breaks the whole thing at once. Decompress first if you want statement-level damage.
Will it break a specific table?
Not deterministically, damage is scattered, not targeted at named objects.
Is the original dump modified?
No. The corruption is applied to a copy in memory and downloaded separately.