# Connect reporting tools without assuming ODBC compatibility

An ODBC authentication error can occur before a query reaches Coordinator DB. The documented Coordinator DB interfaces are native TCP and HTTP SQL; they do not promise compatibility with a reporting tool's database-specific ODBC connector.

## Verify database access separately

Run a small authenticated HTTP SELECT from the reporting host. If it succeeds, the credentials and HTTP route are usable. It does not prove that the ODBC driver speaks the same protocol. Do not change server passwords repeatedly to fix a driver or protocol mismatch.

Confirm the connector's actual destination, port, protocol and expected product. A connector labeled for another database can assume unsupported login exchanges, metadata tables or SQL settings.

## Use a supported exchange path

When the reporting tool can import CSV or Parquet, export explicit columns through native `--query` and load that artifact into the tool. Validate timestamp, decimal and null interpretation with a small sample. For an application-controlled integration, use the HTTP interface and parse a supported result format.

There is no documented Coordinator DB ODBC driver or built-in reporting connector to configure. Keep a failed integration report specific: include the driver name, redacted endpoint, error stage and result of the independent HTTP check.

See [HTTP authentication](https://coordinatordb.com/docs/concepts/features/interfaces/http), [native exports](https://coordinatordb.com/docs/concepts/features/interfaces/client) and [formats](https://coordinatordb.com/docs/reference/formats).