← Back to the generator
Database naming FAQ
Short answers to the questions developers actually ask about naming databases.
| Question | Answer |
|---|---|
| snake_case or camelCase? | Lowercase snake_case. PostgreSQL folds unquoted identifiers to lowercase, so mixed case forces quoting everywhere. snake_case needs no quoting on any major engine. |
| How long can a database name be? | PostgreSQL: 63 bytes. MySQL/MariaDB: 64 characters. SQL Server: 128 characters. Keep names under 32 characters for readability. |
| Hyphens or spaces? | Only with quoting in every query — avoid them. Underscores are the safe separator. |
| Can a name start with a digit? | Technically possible with quoting on some engines, but avoid it. Start with a letter. |
| Which words must I avoid? | SQL reserved words: select, table, order, group, user, index, database, schema, and hundreds more per engine. |
| How do I name environments? | One base + suffix: shop_dev, shop_staging, shop_prod. Domain first, environment last. |
| Are generated names unique? | No — they are starting-point suggestions. Always verify availability on your own server. |
| Can I use these names commercially? | Yes. They are random word combinations; just confirm the name is free and does not collide with an existing trademark in your context. |
| Is anything sent to a server? | No. The generator runs 100% in your browser. No signup, no cookies, no tracking. |
| Does it work offline? | After the first page load, the tool itself runs entirely offline since it needs no network calls. |
For the deeper reasoning, see what makes a good database name and database naming conventions by engine.