This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
Untrusted input does not belong inside the SQL text. The converter replaces quoted text and numbers with placeholders. MySQL and SQLite use a question mark. SQL Server uses @p and a number. Oracle uses :p and a number. PostgreSQL uses $ and a number. The original values stay in the client, in the same order.
The escape tool doubles single quotes and says to prefer parameters. Manual escaping is not the design you keep. Do not concatenate a value into the statement to make a test pass. The page does not run the statement. Least privilege still applies to the account that sends the parameters.
192.0.2.10, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the database named in the ticket. Read the draft, then the database, then decide.
Rollback is the backup, the file, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Paste one statement you may hold.
- Read the placeholders.
- Keep the values in the client.
- Prefer parameters over quote doubling.
- Do not run the draft.
- Stop.
Mistakes that outlive the statement
Preventing SQL Injection with Parameterized Queries goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A value concatenated into SQL.
- The draft run during the reading.
- Manual escaping kept as the design.
- An account with more privilege than the statement needs.
Decisions to write down
One decision for Preventing SQL Injection with Parameterized Queries: Placeholders replaced the literals. Values stay in the client. Nothing was run. And the account is limited.
Checks before you call it done
Confirm this before you call the change done: The statement was read. The placeholder style matches the engine. Nothing was run. No value was concatenated. And the database is yours. If one of those fails, stop.
-- Parameters, not concatenation.
-- Keep values in the client, in the same order.
-- Do not run the draft during the reading.Before you leave the database
Preventing SQL Injection with Parameterized Queries ends when the database in the prompt is the database in the ticket. If it is not, you are on the wrong database. Stop.
The draft stays a draft until a person has read the names in it. A generator does not log into the database. You delete a line that names a host, a database, or an account you did not write down.
192.0.2.10, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a database because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. A sample password in a draft is replaced. It is not a password you keep.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the database name and the change aloud. If they cannot find them in the ticket, the note is not done.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a database you do not administer. You do not disable authentication, a firewall, or TLS to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.