Coordinator DB frequently asked questions ​

Use these questions to choose the public documentation for the task at hand. Coordinator DB supports relational SQL, typed values, transactions and server or embedded connections. Feature names from another database should be checked against the reference before their syntax is used.

For the general query model, start with SQL, analytical queries and data changes. For application connections, read concurrency and integration choices.

For a concrete reader task, the use-case guides show key lookups, time series, log analysis and vector distances. These describe supported SQL workflows rather than a managed service or an automatic ingestion promise.

When an answer depends on the interface, state whether the query runs through native TCP, HTTP or an embedded connection. Session lifetime, parameter binding and server commands differ. Include the selected database and exact error when asking for help; remove credentials and private input values.

See deployment modes and the statement reference.