Support center
Find a Coordinator DB guide by the task you need to complete. The knowledge base covers queries, schema changes, imports and exports, connection setup, settings, diagnostics and recovery. Each article links to the relevant public reference so you can check exact syntax and limits.
If you are starting with a new database, follow installation, create a table and run a query. For an existing application, choose its connection interface and the topic below that matches the observed behavior.
The Cloud category covers deploying your own server and connecting external network, broker and infrastructure services. Provider account operations and external importers remain separate from the SQL interface.
Use the sidebar to open a category or follow the article links below. General questions also group related guides by use case, integration and operating task.
Performance & optimization
- Tune INSERT SELECT requests
- Choose an explicit result order
- Measure query processing time
- Find expensive completed queries
- Find queries with high memory usage
- Choose between Map fields and typed columns
- Resolve a query memory limit error
- Resolve duplicate rows with explicit SQL
- Set a query execution deadline
- Choose precise basic data types
- Investigate a primary key access plan
Cloud
- Connect ingestion clients over a private network
- Import from a private managed Kafka source
- Plan a private route for a broker consumer
- Update an infrastructure billing contact
- Automate Coordinator DB SQL over HTTP
- Connect a private Confluent consumer to SQL
- Use a custom DNS name for SQL access
- Inspect service metadata with system tables
- Check service readiness and SQL access
- Reach SQL through an SSH tunnel
- Diagnose ingestion failures after an upgrade
- Move a verified database copy to another region
- Control diagnostic artifacts in your deployment
- Restore access to a SQL endpoint
Data import & export
- Commit related inserts atomically
- Add data to a Parquet export safely
- Export query results to a client file
- Import GeoJSON features with nested properties
- Work with arrays of JSON objects
- Import Parquet downloaded from object storage
- Choose the right JSON input format
- Extract values from a JSON document
- Load and query a small JSON dataset
- Load JSON records from an external Kafka consumer
- Set up a repeatable external Kafka import
- Exchange MySQL query results through files
- Convert Parquet rows to CSV or JSON
- Exchange PostgreSQL results through files
- Organize exports in year and month folders
Configuration & settings
- Apply request budgets without per-user quotas
- Replace an unsupported ALTER USER setting change
- Use native client commands and connection options
- Configure a database request default
- Correct an unknown or invalid setting
- Plan the number of tables and databases
Integrations & client libraries
- Run a SQL request from Node.js
- Connect reporting tools without assuming ODBC compatibility
- Import Oracle query results through a file
- Move SQL Server data into a containerized SQL service
- Use Python without a product specific database driver
- Send Python HTTP queries and parse JSON rows
- Manage deployment configuration with external automation
Troubleshooting & errors
- Troubleshooting overview
- Build a reproducible diagnostic case
- Resolve certificate verification failures at the TLS boundary
- Review container permissions before adding capabilities
- Diagnose remote SQL connection timeouts
- Inspect table counts and size estimates
- Diagnose pressure from many small inserts
- Handle a macOS executable verification warning
- Resolve overlapping data import ranges
- Recover data from a verified independent copy
- Restore an independent service after storage failure
Tables & schema
- Add a column to an existing table
- Delete rows older than a chosen boundary
- Switch a table name with explicit renames
- Combine data from independent SQL services
- Use a shared persistent table across client sessions
- Validate a JSON schema change with a small runbook
- Choose a schema migration workflow
- Find tables with a name pattern
Queries & SQL
- Calculate pi with SQL
- Compare two query result sets
- Compare query measurements
- Calculate filtered aggregates
- Filter rows by an array member
- Insert rows from another table
- Pivot a known set of categories
- Useful diagnostic SQL queries
- Expand JSON attributes into rows
Materialized views & projections
- Choose live views or stored query results
- Inspect requests that query a view
- Filter an ordinary view with query parameters
- Use a targeted index for repeated queries
- Check report data after a restart
Monitoring & debugging
- Investigate repeated-query performance
- Build a request timeline from query history
- Capture a browser request for diagnosis
- Choose request metrics for external monitoring
- Write diagnostic logs to a file
- Profile SQL with analyzed execution plans
- Choose diagnostic and query logging levels
- See currently active requests
- Monitor active data-changing requests
- Reduce diagnostic log verbosity
Security & access control
- Check configured users and active identities
- Plan access without database roles
- Remove empty-password default access
- Design row and column access boundaries
- Understand browser request identity and state
- Connect application identity to database access
Data management
- Preserve a selected date range
- Measure zeros and missing values
- Keep lookup data consistent
- Use string-keyed lookup data
- Read related data in one transaction
- Distinguish tables from interchange formats
- Apply an explicit retention cutoff
Setup & installation
- Verify the executable you are running
- Use HTTPS in front of the HTTP interface
- Choose and verify a query thread limit
- Plan a Windows client connection
- Check installation prerequisites
- Prepare a persistent Coordinator DB service
- Use documentation safely with a SQL assistant
General & FAQs
General
- General Coordinator DB questions
- Choose SQL by the reader task
- Connect concurrent applications safely
- Inspect the chosen query plan
- Query and import a local data file
- Name databases and SQL objects
- Prepare the files and credentials a service needs
- Join related data in Coordinator DB
- Query available data sources deliberately
- Prepare a useful Coordinator DB contribution
- Express grouped calculations in SQL
- Investigate a slow query step by step
- Build analytical reports with SQL
- Use Coordinator DB SQL deliberately
- Update existing rows transactionally
- Evaluate Coordinator DB for your workload
- Choose a single-server application connection
Use cases
- Coordinator DB use cases
- Store and update keyed records
- Query dated measurements
- Analyze application event logs
- Compare fixed-dimensional vectors
Integration
- Integrate an application with Coordinator DB
- Choose the right JSON input format
- Import Oracle query results through a file
Operations
- Operate a Coordinator DB service
- Delete rows older than a chosen boundary
- Move a verified database copy to another region
- Prepare a persistent Coordinator DB service
- Choose database paths and independent copies
Tips & tricks
- Practical habits for reliable SQL work
- Reduce unnecessary query and data work
- Keep a focused SQL debugging record
- Choose a view or a report table
- Optimize a measured reader task
- Write a reproducible workload result
- Improve a workload with many small writes
Prepare a reproducible support report
Record the SQL, selected database, interface, output format and relevant settings. Include a small synthetic dataset and the actual result or error. For server requests, preserve the query identifier so it can be matched with the public request history.
Remove credentials and application data before sharing a reproduction. Follow Coordinator DB support for the report contents and HTTP diagnostics for response headers and status codes.