Before You Start

• Prepare the database address, port, database name, username, and password under Settings → Database Connections.
• Confirm that the account permissions match the task, prefer a read-only account, and never put the password in project files or prompts.
• State the target tables, field meanings, time range, filters, and expected output so the Agent does not scan unrelated data.
• Oracle users must configure Thick mode for the environment. For Oracle 11g compatibility issues, check the client and driver configuration first.

Steps

1. Open Settings → Database Connections, create a MySQL, Doris, or Oracle connection, complete the connection test, and save it.
2. Choose read-only or read-write access. Read-only is suitable for querying, sampling, and analysis; use read-write only when writing is explicitly needed and a backup exists.
3. Switch to the Remote Database workspace on the left and choose a saved connection from Select Remote Database Connection.
4. Click New SQL or describe the task to the Remote Database Agent at the bottom. Ask it to inspect the schema and a small sample before generating the query.
5. Before running read-write SQL, the software saves it to the current project's sql/remote_db_history/; execution stops if saving fails.
6. When reusing results, pass filtered, aggregated, and redacted data to the project database or export it to data_exports/ instead of copying the whole database.

Acceptance Checks

Results should state the connection, table and field scope, SQL definition, filters, returned row count, and data-quality warnings. Read-write tasks should have a pre-execution statement in the project SQL history. Redact personal or sensitive fields and review permissions.