Test database read workloads and connection demand on approved resources. Compare operation rate, response times and failures as concurrency changes.
Business customers request a server connection using SSH key or password. Administrator approval and setup come before testing. Use a dedicated database account with permission for the databases and reads you intend to assess.
Saving a connection starts discovery. Select from the database names visible to that account. MySQL, PostgreSQL and SQL Server are supported; the account permissions determine what can be listed and queried.
Use connection churn to examine repeated connections, table reads for a selected table, or a custom SELECT workload. Start with modest concurrency and a short duration before increasing demand.
Compare completed operations, response times, failures and available engine counters. After-test connectivity provides another signal. A website 500 error alone does not prove the database caused it.
These are bounded read and connection tests. They do not reproduce every InnoDB crash, write lock, transaction deadlock, disk-full condition or failover event. The selected workload and data set determine what the result can explain.
Review available evidence and technical guidance, download the permitted report or email it to your verified account address. Repeat with the same query, data and settings after an infrastructure or indexing change.
Connect an approved resource and choose a database visible to your test account.