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
DuckDB DBA Cheat Sheet is one lab note for DuckDB. A cheat sheet is a short list of reads: version, size, sessions, and the one command you already use. It is not every statement the engine can run.
DuckDB is a file, not a server. There is no login and no listener. Restrict the file mode. Do not replace the only .duckdb file. Do not pipe a downloaded script to a shell. The file, when there is one, is one .duckdb file. There is no bind address. Do not invent a network listener for this file.
Do not paste a destructive statement onto the sheet. A sample password does not belong on it. The sheet names the client and one read, and it contains no secret.
The generator drafts text in the browser. It does not log in. A header on a script says to review it before running, and a destructive line is supposed to stay a comment. You still read the draft. 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.
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.
- Write the database name and confirm you administer it.
- Save a backup, a file, or a snapshot before any draft is applied.
- Read the draft and delete every line this ticket did not name.
- Replace a sample password, a bind to every address, and any secret.
- Apply one change only when the lab window is open.
- Read the result back and compare it with the ticket.
- Stop. The next change is a different page.
Mistakes that outlive the statement
DuckDB DBA Cheat Sheet goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- Pasting a draft you did not read.
- The wrong database.
- A secret or a sample password left in the note.
- A listen address of every interface left in the file.
- Two changes in one window.
- No copy saved before the change.
- Disabling authentication, a firewall, or TLS to make a check pass.
- Calling the generator output a finished production change.
- Do not paste a destructive statement onto the sheet. A sample password does not belong on it.
Decisions to write down
One decision for DuckDB DBA Cheat Sheet: The database is DuckDB. The change is only this cheat sheet. A sample password was replaced or was never present. A listen on every address was removed or was never present. Nothing was applied during the reading. And the proof you expect is: The sheet names the client and one read, and it contains no secret.
Checks before you call it done
Confirm this before you call the change done: The database name matches the ticket. The draft was read. No secret is in the note. Authentication was not disabled. The listen address is not every interface. And nothing was applied, or the lab window is still closed. If one of those fails, stop.
# DuckDB. cheat sheet.
# Review before you run.
# Replace a sample password.
# Delete a bind to every address.
# Do not disable authentication.
# 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.Before you leave the database
DuckDB DBA Cheat Sheet 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.
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.