Safety and limits
The server is built so a mistake, yours or the assistant's, cannot damage anything.
Read-only, by design
- The database logins used here can only read. Even if something slipped past the checks, the database would refuse a write.
- Only a single
SELECT(orWITH ... SELECT) runs. No inserts, updates, deletes, creating or dropping, stored procedures, or system views. - System databases are never reachable, on any connection.
- All data is synthetic, so there is no real person's information in it.
Limits
| Statements | One SELECT (or WITH ... SELECT) at a time. |
| Rows returned | Up to 200. Use WHERE, TOP/LIMIT or GROUP BY. |
| Time | A query that runs longer than about 10 seconds is stopped. |
| Speed | About 30 queries a minute per person. |
| Never allowed | Changing data, creating or dropping anything, stored procedures, system views, other databases. |
These are current settings and may change. They keep the shared servers fast for everyone.
Lock a connection to one database
Add /db/<name> to the server address and the connection only knows that database: https://learnsql.cpetoday.com/mcp/db/world. Everything else is invisible, and a query that names another database is refused.
It is handy for a class exercise ("everyone works in world today"). You can add several locked connections side by side. Each database page shows how.
What is logged
Queries are limited and logged so the service can be kept healthy and abuse can be stopped. Do not paste passwords or other secrets into a chat, because the assistant's app, not this server, keeps your chat.
Your sign-in
The shared login is for learning. Do not share it publicly. Repeated wrong attempts temporarily block a network address.