Use AI to accelerate operator judgment, not replace it.

Ask for SQL in plain language

AI "show the top ten customers by revenue in the last thirty days"
AI NEXT "show only active customers"
AI CONTEXT SHOW;

Review generated SQL against the connected database schema, target scope, expected row count, and permission model before execution. Do not treat generated output as an authorization to query or modify data.

Request database-specific syntax help

AI "syntax of create user"
AI "how to create a table with foreign key"

Use this as a research aid and verify the result against the target database version and organizational standards, especially for grants, DDL, or production data changes.

Keep control boundaries explicit

• Configure and own the AI provider credentials in your approved environment.
• Do not include secrets, credentials, or unnecessary sensitive data in prompts.
• Use a least-privileged database identity for all connections.
• Prefer a read-only validation query before a modifying command.
• Clear or manage conversation context when the topic or data boundary changes.