Connection testing
The Test Connection button checks whether STYD can reach and sign in to your database with the details you entered, before you save.
What testing checks
A test confirms that, at that moment, STYD can reach the host and port and authenticate with the database, user, and password provided (and, for PostgreSQL, the schema). A successful test shows a clear success message.
A test may also warn you that a matching connection already exists in the workspace. In that case, use the existing connection rather than creating a duplicate. If the matching connection is archived, saving restores it with its history.
What a successful test means — and does not mean
It means
STYD could connect with those credentials right now.
STYD could connect with those credentials right now.
It does not guarantee
That every table is readable, that the AI Guide analysis has been done, or that future answers will be correct.
That every table is readable, that the AI Guide analysis has been done, or that future answers will be correct.
After a successful test
Save the connection.
STYD offers to analyse it with the AI Guide. Your first analysis is included while your workspace has an AI Guide setup left (see Pricing) and starts by itself; otherwise STYD shows its price in prompts and an owner or admin confirms it.
Start a chat thread on the connection. You do not have to wait for the analysis.
After a failed test
STYD shows one of four plain messages and what to do about it. Re-check the server address, port, database name, username, and password, and make sure the database is reachable at a public address (not localhost or a private network address). If it only accepts approved addresses, allow STYD’s: 109.123.235.222 and 2407:3640:2324:5796::1. The Common connection errors page explains each message.
If you change your database structure later, analyse the database again so STYD can pick up the new tables and columns. After the first analysis, every new one costs prompts, and STYD shows the price first.