# Coordinator Database

> Super simple SQL database built for a trillion values. Plain SQL from the first row to the last — embedded in your app or on a server.

- [Full text](https://coordinatordb.com/llms-full.txt): Public documentation, examples and pages.

## Documentation

- [CoordinatorDB documentation](https://coordinatordb.com/docs): Start, query and operate CoordinatorDB through its public interfaces.
- [Concepts](https://coordinatordb.com/docs/concepts): CoordinatorDB interfaces, data operations and configuration.
- [Practical choices](https://coordinatordb.com/docs/concepts/best-practices): CoordinatorDB type, key and input choices.
- [Choose a primary key](https://coordinatordb.com/docs/concepts/best-practices/choosing-a-primary-key): Declare a stable row identity and enforce alternate unique keys.
- [Choose JSON declarations](https://coordinatordb.com/docs/concepts/best-practices/json-type): Validate selected object fields while retaining the rest of a JSON document.
- [Check joins](https://coordinatordb.com/docs/concepts/best-practices/minimize-optimize-joins): Make join keys and result multiplicity explicit before measuring a query.
- [Choose a data type](https://coordinatordb.com/docs/concepts/best-practices/select-data-type): Match numeric, temporal and structured declarations to the values you need.
- [Choose an insert method](https://coordinatordb.com/docs/concepts/best-practices/selecting-an-insert-strategy): Select literal, query, client-file, HTTP or server-file input.
- [Core concepts](https://coordinatordb.com/docs/concepts/core-concepts): Understand the state and names used by SQL connections.
- [Glossary](https://coordinatordb.com/docs/concepts/core-concepts/glossary): Understand databases, connections, namespaces, requests and settings.
- [Query Parallelism](https://coordinatordb.com/docs/concepts/core-concepts/query-parallelism): Set and observe the thread limit for CoordinatorDB queries.
- [Features](https://coordinatordb.com/docs/concepts/features): CoordinatorDB interfaces, configuration and data operations.
- [Local database copy](https://coordinatordb.com/docs/concepts/features/backup-restore/local-disk): Write a database copy and open it as an independent instance.
- [Database copies](https://coordinatordb.com/docs/concepts/features/backup-restore/overview): Create a consistent independent database with VACUUM INTO.
- [Configuration files](https://coordinatordb.com/docs/concepts/features/configuration/server-config/configuration-files): Server XML, user credentials, paths and startup in CoordinatorDB.
- [Server ceilings](https://coordinatordb.com/docs/concepts/features/configuration/settings/constraints-on-settings): Apply the stricter nonzero server and database resource limits.
- [Settings](https://coordinatordb.com/docs/concepts/features/configuration/settings/overview): Understand server, database and one-statement setting scope.
- [Request limits](https://coordinatordb.com/docs/concepts/features/configuration/settings/query-complexity): Bound elapsed time, accounted memory, returned rows and encoded response bytes.
- [Admission limits](https://coordinatordb.com/docs/concepts/features/configuration/settings/server-overload): Understand requests refused before SQL execution.
- [Statement settings](https://coordinatordb.com/docs/concepts/features/configuration/settings/settings-query-level): Apply format parsing or output options to one statement.
- [Connection limits](https://coordinatordb.com/docs/concepts/features/configuration/settings/tcp-connection-limits): Configure shared connection admission, incoming bytes and socket timeouts.
- [Command-line interface](https://coordinatordb.com/docs/concepts/features/interfaces/cli): Start the server or run interactive and scripted native SQL.
- [Native client](https://coordinatordb.com/docs/concepts/features/interfaces/client): Run interactive SQL, exact-byte queries and attached input through native TCP.
- [HTTP interface](https://coordinatordb.com/docs/concepts/features/interfaces/http): SQL requests, authentication, uploads and responses over HTTP.
- [Client interfaces](https://coordinatordb.com/docs/concepts/features/interfaces/native-clients-interfaces-index): Choose the supplied native client, HTTP or the browser workspace.
- [Interfaces](https://coordinatordb.com/docs/concepts/features/interfaces/overview): Compare native sessions, HTTP requests and browser SQL tools.
- [File schemas](https://coordinatordb.com/docs/concepts/features/interfaces/schema-inference): Supply explicit column types and recognize the two schema-providing file formats.
- [SQL console](https://coordinatordb.com/docs/concepts/features/interfaces/sql-console): Run and inspect a SQL request in the browser Playground.
- [Native TCP interface](https://coordinatordb.com/docs/concepts/features/interfaces/tcp): Use an authenticated connection that retains SQL session state.
- [Browser SQL workspace](https://coordinatordb.com/docs/concepts/features/interfaces/web-sql): Use connections, SQL tabs, table pages, notebooks and dashboards.
- [SQL and Markdown notebooks](https://coordinatordb.com/docs/concepts/features/interfaces/web-ui-notebook): Organize SQL requests and notes into independently runnable cells.
- [Shape result views](https://coordinatordb.com/docs/concepts/features/interfaces/web-ui-result-shaping): Search, filter, sort, copy and export rows already loaded in the browser.
- [Deleting rows](https://coordinatordb.com/docs/concepts/features/operations/delete): Remove selected rows or an entire table definition.
- [Delete data](https://coordinatordb.com/docs/concepts/features/operations/delete/overview): Remove selected rows while retaining the table, or drop the table itself.
- [Batch inserts](https://coordinatordb.com/docs/concepts/features/operations/insert/bulkinserts): Send several rows in one statement and group related statements in a transaction.
- [Insert data](https://coordinatordb.com/docs/concepts/features/operations/insert/inserting-data): Choose literal, query, formatted or file input for a table.
- [Transactions](https://coordinatordb.com/docs/concepts/features/operations/insert/transactions): Commit or roll back related changes and use savepoints for partial undo.
- [Joining tables](https://coordinatordb.com/docs/concepts/features/operations/select/joining-tables): Combine matching rows and choose which unmatched rows to retain.
- [Updating rows](https://coordinatordb.com/docs/concepts/features/operations/update): Change existing data with UPDATE or upsert.
- [Update data](https://coordinatordb.com/docs/concepts/features/operations/update/overview): Change stored values or update a row on an insert conflict.
- [Query observation](https://coordinatordb.com/docs/concepts/features/performance): Inspect plans, active requests, finished queries and request limits.
- [Authentication and network access](https://coordinatordb.com/docs/concepts/features/security): Configure explicit users and choose how clients reach the service.
- [Network ports](https://coordinatordb.com/docs/concepts/features/security/network-ports): Configure native TCP and optional HTTP listener addresses.
- [Get started with CoordinatorDB](https://coordinatordb.com/docs/get-started): Install the executable, connect and run a first SQL workflow.
- [Deployment modes](https://coordinatordb.com/docs/get-started/about/deployment-modes): Choose a managed server connection or an embedded database connection.
- [Features](https://coordinatordb.com/docs/get-started/about/distinctive-features): Explore implemented SQL, typed values, data formats and server interfaces.
- [What is CoordinatorDB?](https://coordinatordb.com/docs/get-started/about/intro): Query relational data with typed SQL and embedded, native or HTTP interfaces.
- [Create a table](https://coordinatordb.com/docs/get-started/quickstarts/creating-tables): Define typed columns, insert sample events and read them back.
- [Quickstarts](https://coordinatordb.com/docs/get-started/quickstarts/home): Run independent examples for tables, input, queries and row changes.
- [Insert with the native client](https://coordinatordb.com/docs/get-started/quickstarts/insert-data-using-clickhouse-client): Insert rows or load a local CSV file using the CoordinatorDB client.
- [Update and delete rows](https://coordinatordb.com/docs/get-started/quickstarts/mutations): Apply related row changes in a transaction.
- [Work with Map values](https://coordinatordb.com/docs/get-started/quickstarts/working-with-the-map-type): Construct, inspect and replace typed key/value pairs.
- [Write queries](https://coordinatordb.com/docs/get-started/quickstarts/writing-queries): Filter order rows, calculate grouped totals and order the result.
- [Install CoordinatorDB](https://coordinatordb.com/docs/get-started/setup/install): Install and start CoordinatorDB with its supplied configuration.
- [Self-managed CoordinatorDB](https://coordinatordb.com/docs/get-started/setup/self-managed/overview): Run the supplied server with explicit files, credentials and listeners.
- [Guides](https://coordinatordb.com/docs/guides/clickhouse): Step-by-step CoordinatorDB data and SQL guides.
- [Arrow and Avro](https://coordinatordb.com/docs/guides/clickhouse/data-formats/arrow-avro-orc): Choose an Arrow IPC layout or an Avro schema-based exchange format.
- [Binary file exchange](https://coordinatordb.com/docs/guides/clickhouse/data-formats/binary): Preserve exact output bytes and load them into an explicit typed schema.
- [CSV and TSV](https://coordinatordb.com/docs/guides/clickhouse/data-formats/csv-tsv): Import and export delimited files with the CoordinatorDB client.
- [Load and export data](https://coordinatordb.com/docs/guides/clickhouse/data-formats/intro): Choose a format and distinguish client input from server-side files.
- [Export JSON](https://coordinatordb.com/docs/guides/clickhouse/data-formats/json/exporting): Return named or positional JSON rows while preserving numeric digits.
- [JSON format choices](https://coordinatordb.com/docs/guides/clickhouse/data-formats/json/formats): Compare named, positional, column-oriented and string-only layouts.
- [JSON data](https://coordinatordb.com/docs/guides/clickhouse/data-formats/json/intro): Choose row, column or whole-document JSON exchange.
- [Load JSON rows](https://coordinatordb.com/docs/guides/clickhouse/data-formats/json/loading): Insert named JSON rows into a typed CoordinatorDB table.
- [Expand JSON into rows](https://coordinatordb.com/docs/guides/clickhouse/data-formats/json/other): Turn JSON members or typed records into ordinary query sources.
- [Validate JSON fields](https://coordinatordb.com/docs/guides/clickhouse/data-formats/json/schema): Distinguish row-column validation from typed paths inside a document.
- [Parquet exchange](https://coordinatordb.com/docs/guides/clickhouse/data-formats/parquet): Export typed rows, import a file and inspect its footer metadata.
- [SQL row exchange](https://coordinatordb.com/docs/guides/clickhouse/data-formats/sql): Distinguish executable INSERT SQL from a literal-values data format.
- [Templates and regular expressions](https://coordinatordb.com/docs/guides/clickhouse/data-formats/templates-regex): Decode captured line fields or write a custom escaped row layout.
- [Data modelling](https://coordinatordb.com/docs/guides/clickhouse/data-modelling): CoordinatorDB schemas, copies, prepared statements and test data.
- [Backfill a table](https://coordinatordb.com/docs/guides/clickhouse/data-modelling/backfilling): Copy existing rows through an explicit destination value contract.
- [Combine related data](https://coordinatordb.com/docs/guides/clickhouse/data-modelling/denormalization): Store a verified join result as an independent snapshot table.
- [Generate test data](https://coordinatordb.com/docs/guides/clickhouse/data-modelling/generating-test-data): Populate a repeatable numeric fixture with generate_series.
- [Design a schema](https://coordinatordb.com/docs/guides/clickhouse/data-modelling/schema-design): Declare identity, required values, exact amounts and foreign-key relationships.
- [Prepared statements](https://coordinatordb.com/docs/guides/clickhouse/data-modelling/stored-procedures-and-prepared-statements): Bind positional parameters through the embedded CoordinatorDB API.
- [Distinct array aggregation](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/array-agg-distinct): Collect one copy of each value while controlling array order and NULLs.
- [avg_if](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/avg-if): Calculate the average amount of paid orders.
- [avg_merge](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/avg-merge): Combine batch average states without losing their observation counts.
- [avg_merge_state](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/avg-merge-state): Combine average states while retaining a state for the next stage.
- [avg_state](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/avg-state): Store the information needed to calculate and combine averages.
- [count_if](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/count-if): Count orders whose status is paid.
- [max_simple_state](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/max-simple-state): Store and combine scalar partial max values.
- [min_simple_state](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/min-simple-state): Store and combine scalar partial min values.
- [sum_if](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/sum-if): Calculate revenue only from paid orders.
- [sum_simple_state](https://coordinatordb.com/docs/guides/clickhouse/examples/aggregate-function-combinators/sum-simple-state): Store and combine scalar partial sum values.
- [Inspect query history](https://coordinatordb.com/docs/guides/clickhouse/performance-and-monitoring/diagnose-slow-queries): Find completed request duration and errors using query IDs.
- [Inspect query measurements](https://coordinatordb.com/docs/guides/clickhouse/performance-and-monitoring/isolate-query-bottlenecks): Compare elapsed time, row and byte counters and analyzed plans.
- [Check a query change](https://coordinatordb.com/docs/guides/clickhouse/performance-and-monitoring/optimization-approaches): Verify results before comparing access plans and execution measurements.
- [Inspect and index a query](https://coordinatordb.com/docs/guides/clickhouse/performance-and-monitoring/query-optimization): Use a concrete predicate, statistics and EXPLAIN QUERY PLAN.
- [Index a filtered query](https://coordinatordb.com/docs/guides/clickhouse/performance-and-monitoring/query-optimization-example): Check a predicate result before and after creating an index.
- [Work with arrays](https://coordinatordb.com/docs/guides/clickhouse/working-with-arrays): Create typed collections, select elements, expand rows and collect results.
- [Work with joins](https://coordinatordb.com/docs/guides/clickhouse/working-with-joins): Combine customer orders while retaining customers without matches.
- [Data types](https://coordinatordb.com/docs/reference/data-types): Choose native types, declare value constraints and convert SQL values.
- [AggregateFunction](https://coordinatordb.com/docs/reference/data-types/aggregatefunction): Store typed intermediate results that can be merged later.
- [Array](https://coordinatordb.com/docs/reference/data-types/array): Store an ordered collection of values with one element type.
- [Bool](https://coordinatordb.com/docs/reference/data-types/bool): Store true and false values.
- [Date](https://coordinatordb.com/docs/reference/data-types/date): Store a calendar date without a time or timezone.
- [Date32](https://coordinatordb.com/docs/reference/data-types/date32): Store a calendar date without a time or timezone.
- [DateTime](https://coordinatordb.com/docs/reference/data-types/datetime): Store a timestamp with whole-second precision and a declared timezone.
- [DateTime64](https://coordinatordb.com/docs/reference/data-types/datetime64): Store timestamps with fractional-second precision from 0 through 9.
- [Decimal](https://coordinatordb.com/docs/reference/data-types/decimal): Store exact fixed-point numbers with up to 76 decimal digits.
- [Domain types](https://coordinatordb.com/docs/reference/data-types/domains): Use identifiers, network addresses and geometry with dedicated value contracts.
- [Dynamic](https://coordinatordb.com/docs/reference/data-types/dynamic): Retain the concrete type of each value without a fixed alternative list.
- [Enum8 and Enum16](https://coordinatordb.com/docs/reference/data-types/enum): Store a value from a named set of labels and numeric codes.
- [FixedString](https://coordinatordb.com/docs/reference/data-types/fixedstring): Store a fixed number of bytes with zero padding.
- [Float32, Float64 and BFloat16](https://coordinatordb.com/docs/reference/data-types/float): Store approximate floating-point numbers.
- [Geometry types](https://coordinatordb.com/docs/reference/data-types/geometry-types): Represent coordinates, paths and polygons with typed collections.
- [Int and UInt](https://coordinatordb.com/docs/reference/data-types/int-uint): Store signed and unsigned integers with checked ranges.
- [IPv4](https://coordinatordb.com/docs/reference/data-types/ipv4): Store IPv4 addresses with numeric address ordering.
- [IPv6](https://coordinatordb.com/docs/reference/data-types/ipv6): Store IPv6 addresses in normalized compressed form.
- [JSON](https://coordinatordb.com/docs/reference/data-types/json): Store validated JSON with optional typed paths.
- [LowCardinality](https://coordinatordb.com/docs/reference/data-types/lowcardinality): Wrap repeated scalar values while preserving their value semantics.
- [Map](https://coordinatordb.com/docs/reference/data-types/map): Store ordered key/value pairs, including duplicate keys.
- [Nested](https://coordinatordb.com/docs/reference/data-types/nested-data-structures): Store an array of named records in one column.
- [Nullable](https://coordinatordb.com/docs/reference/data-types/nullable): Allow NULL values inside typed collections.
- [QBit](https://coordinatordb.com/docs/reference/data-types/qbit): Store fixed-dimensional numeric vectors and choose probe precision.
- [SimpleAggregateFunction](https://coordinatordb.com/docs/reference/data-types/simpleaggregatefunction): Store directly readable scalar partial sums or extrema.
- [Special data types](https://coordinatordb.com/docs/reference/data-types/special-data-types): Use typed intervals and understand unsupported special declarations.
- [Interval](https://coordinatordb.com/docs/reference/data-types/special-data-types/interval): Represent a signed quantity with a calendar or elapsed-time unit.
- [String and VARCHAR](https://coordinatordb.com/docs/reference/data-types/string): Store UTF-8 text with an optional character limit.
- [Time](https://coordinatordb.com/docs/reference/data-types/time): Store signed whole seconds without a calendar date or timezone.
- [Time64](https://coordinatordb.com/docs/reference/data-types/time64): Store signed elapsed seconds with fractional precision.
- [Tuple](https://coordinatordb.com/docs/reference/data-types/tuple): Store a fixed set of positional or named fields.
- [UUID](https://coordinatordb.com/docs/reference/data-types/uuid): Store validated UUID values in canonical form.
- [Variant](https://coordinatordb.com/docs/reference/data-types/variant): Store one value from a declared set of alternative types.
- [Error codes](https://coordinatordb.com/docs/reference/errors): Permanent CoordinatorDB error numbers and symbolic names.
- [Formats](https://coordinatordb.com/docs/reference/formats): Supported input and output formats in CoordinatorDB.
- [arrow](https://coordinatordb.com/docs/reference/formats/arrow/arrow): Use this file layout when the consumer expects an Arrow IPC file with a footer.
- [arrow_stream](https://coordinatordb.com/docs/reference/formats/arrow/arrow-stream): Use this layout with consumers expecting sequential Arrow IPC messages rather than a seekable IPC file.
- [avro](https://coordinatordb.com/docs/reference/formats/avro/avro): The root schema must be a record.
- [avro_confluent](https://coordinatordb.com/docs/reference/formats/avro/avro-confluent): Every record carries a schema identifier rather than an embedded object-container schema.
- [bson_each_row](https://coordinatordb.com/docs/reference/formats/bson-each-row): Each row is one BSON document with a length and terminator.
- [csv](https://coordinatordb.com/docs/reference/formats/csv/csv): Fields follow the result projection or INSERT column order.
- [csv_with_names](https://coordinatordb.com/docs/reference/formats/csv/csv-with-names): The first record contains column names; all later records contain values using the ordinary CSV quoting rules.
- [csv_with_names_and_types](https://coordinatordb.com/docs/reference/formats/csv/csv-with-names-and-types): Two records precede the values: column names, then type names.
- [custom_separated](https://coordinatordb.com/docs/reference/formats/custom-separated/custom-separated): Choose this format when the source has fixed delimiters but is not ordinary CSV or TSV.
- [custom_separated_with_names](https://coordinatordb.com/docs/reference/formats/custom-separated/custom-separated-with-names): The first record identifies the fields, followed by value records with the configured delimiters.
- [form](https://coordinatordb.com/docs/reference/formats/form): The input represents one row of key/value pairs, rather than a stream of several records.
- [geo_json](https://coordinatordb.com/docs/reference/formats/geo-json): Output detects exactly one column containing a native geometry alias; there is no geometry-column setting.
- [hash](https://coordinatordb.com/docs/reference/formats/hash): The fingerprint covers values in row and column order; column labels do not enter it.
- [hive_text](https://coordinatordb.com/docs/reference/formats/hive-text): Fields are positional.
- [json](https://coordinatordb.com/docs/reference/formats/json/json): The document contains column metadata, a data array of named row objects and a row count.
- [json_as_object](https://coordinatordb.com/docs/reference/formats/json/json-as-object): Each source object is the complete value of one JSON column.
- [json_as_string](https://coordinatordb.com/docs/reference/formats/json/json-as-string): Each source object becomes the complete text value of one selected String column.
- [json_columns](https://coordinatordb.com/docs/reference/formats/json/json-columns): Each object key names a column, and its value is an array containing that column's rows.
- [json_compact](https://coordinatordb.com/docs/reference/formats/json/json-compact): The document contains ordered column metadata and positional row arrays, plus a row count.
- [json_compact_columns](https://coordinatordb.com/docs/reference/formats/json/json-compact-columns): The outer array contains one value array per column.
- [json_compact_each_row](https://coordinatordb.com/docs/reference/formats/json/json-compact-each-row): Every row is an independent JSON array with fields in projection or INSERT-column order.
- [json_compact_each_row_with_names_and_types](https://coordinatordb.com/docs/reference/formats/json/json-compact-each-row-with-names-and-types): The first array contains names, the second contains runtime type names, and subsequent arrays contain values.
- [json_compact_strings_each_row](https://coordinatordb.com/docs/reference/formats/json/json-compact-strings-each-row): Position identifies each column, but every field is a JSON string containing the complete native text value.
- [json_each_row](https://coordinatordb.com/docs/reference/formats/json/json-each-row): Every row is a named JSON object.
- [JSON format settings](https://coordinatordb.com/docs/reference/formats/json/json-format-settings): JSON input and output options in CoordinatorDB.
- [json_object_each_row](https://coordinatordb.com/docs/reference/formats/json/json-object-each-row): The document's outer keys identify rows; each associated object holds that row's fields.
- [json_strings_each_row](https://coordinatordb.com/docs/reference/formats/json/json-strings-each-row): Objects retain named fields, but every value is a JSON string containing complete native text.
- [line_as_string](https://coordinatordb.com/docs/reference/formats/line-as-string/line-as-string): Input takes a whole line as one String field, without splitting the line into columns.
- [markdown](https://coordinatordb.com/docs/reference/formats/markdown): The first row contains column labels and the next row defines table alignment.
- [msg_pack](https://coordinatordb.com/docs/reference/formats/msg-pack): Fields are consecutive MessagePack objects in column order; every target column count groups the next objects into one row.
- [npy](https://coordinatordb.com/docs/reference/formats/npy): Exactly one selected or target column is required.
- [null_output](https://coordinatordb.com/docs/reference/formats/null-output): No result payload is written, but SQL still executes.
- [parquet](https://coordinatordb.com/docs/reference/formats/parquet/parquet): The file stores a column schema, row groups, data pages and a footer.
- [parquet_metadata](https://coordinatordb.com/docs/reference/formats/parquet/parquet-metadata): The input is a complete Parquet file, but the output relation describes its footer rather than its data rows.
- [png](https://coordinatordb.com/docs/reference/formats/png): Rows describe pixels through x and y coordinates and grayscale, RGB or RGBA channel values.
- [pretty_compact](https://coordinatordb.com/docs/reference/formats/pretty/pretty-compact): A Unicode border surrounds a table with a name header and one display row per SQL row, followed by the row count.
- [protobuf](https://coordinatordb.com/docs/reference/formats/protobuf/protobuf): Each row is a length-prefixed Protocol Buffers message.
- [regexp](https://coordinatordb.com/docs/reference/formats/regexp): One complete physical line is matched at a time.
- [row_binary](https://coordinatordb.com/docs/reference/formats/row-binary/row-binary): Rows contain only positional field bytes.
- [row_binary_with_names](https://coordinatordb.com/docs/reference/formats/row-binary/row-binary-with-names): A column count and name strings precede the ordinary row_binary payload.
- [row_binary_with_names_and_types](https://coordinatordb.com/docs/reference/formats/row-binary/row-binary-with-names-and-types): The header carries a column count, names and types before the row_binary values.
- [sql_insert](https://coordinatordb.com/docs/reference/formats/sql-insert): The output is executable SQL with column names and literal row values.
- [sql_values](https://coordinatordb.com/docs/reference/formats/sql-values): Each row is a parenthesized list of SQL literals; commas separate the rows.
- [sqlite](https://coordinatordb.com/docs/reference/formats/sqlite): Input selects one user table by sqlite_read_table, or the first table in catalog order by default.
- [tab_separated](https://coordinatordb.com/docs/reference/formats/tab-separated/tab-separated): Fields use literal tabs as separators and one line per row.
- [tab_separated_raw](https://coordinatordb.com/docs/reference/formats/tab-separated/tab-separated-raw): The outer field values are written without tab-separated escaping.
- [tab_separated_with_names](https://coordinatordb.com/docs/reference/formats/tab-separated/tab-separated-with-names): The first escaped tab-separated row contains names, followed by ordinary data rows.
- [tab_separated_with_names_and_types](https://coordinatordb.com/docs/reference/formats/tab-separated/tab-separated-with-names-and-types): Names and runtime types occupy the first two escaped tab-separated rows.
- [tskv](https://coordinatordb.com/docs/reference/formats/tab-separated/tskv): Each row contains escaped name=value fields separated by tabs.
- [template](https://coordinatordb.com/docs/reference/formats/template/template): A template combines literal bytes with zero-based positional or named placeholders.
- [vertical](https://coordinatordb.com/docs/reference/formats/vertical): Each result row is numbered and displayed as a sequence of labelled values.
- [xml](https://coordinatordb.com/docs/reference/formats/xml): One document contains runtime column metadata, nested value representations and the result row count.
- [yaml](https://coordinatordb.com/docs/reference/formats/yaml): Read and write a YAML sequence of named row mappings.
- [Functions](https://coordinatordb.com/docs/reference/functions): Scalar, aggregate, table and window functions in CoordinatorDB.
- [Aggregate Functions](https://coordinatordb.com/docs/reference/functions/aggregate-functions): Aggregate functions, NULL processing, and aggregate modifiers in CoordinatorDB.
- [any_value](https://coordinatordb.com/docs/reference/functions/aggregate-functions/any-value): Select one non-NULL value from a group.
- [array_agg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/array-agg): Collect values into a typed array.
- [avg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/avg): Calculates the arithmetic mean.
- [avg_if](https://coordinatordb.com/docs/reference/functions/aggregate-functions/avg-if): Average non-NULL values from rows whose condition is SQL true.
- [bit_and](https://coordinatordb.com/docs/reference/functions/aggregate-functions/bit-and): Apply bitwise AND across integer values.
- [bit_or](https://coordinatordb.com/docs/reference/functions/aggregate-functions/bit-or): Apply bitwise OR across integer values.
- [bit_xor](https://coordinatordb.com/docs/reference/functions/aggregate-functions/bit-xor): Apply bitwise XOR across integer values.
- [bool_and](https://coordinatordb.com/docs/reference/functions/aggregate-functions/bool-and): Return whether every non-NULL boolean input is true.
- [bool_or](https://coordinatordb.com/docs/reference/functions/aggregate-functions/bool-or): Return whether any non-NULL boolean input is true.
- [Aggregate combinators](https://coordinatordb.com/docs/reference/functions/aggregate-functions/combinators): Calculate conditional aggregates and store mergeable aggregate states.
- [corr](https://coordinatordb.com/docs/reference/functions/aggregate-functions/corr): Calculates the Pearson correlation coefficient.
- [count](https://coordinatordb.com/docs/reference/functions/aggregate-functions/count): Counts rows or non-NULL values.
- [count_if](https://coordinatordb.com/docs/reference/functions/aggregate-functions/count-if): Count rows whose condition is SQL true; skip false and NULL conditions.
- [covar_pop](https://coordinatordb.com/docs/reference/functions/aggregate-functions/covar-pop): Calculates the population covariance.
- [covar_samp](https://coordinatordb.com/docs/reference/functions/aggregate-functions/covar-samp): Calculates the sample covariance.
- [group_concat and string_agg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/group-concat): Concatenate non-NULL values with a separator.
- [json_agg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-agg): Collect group inputs, including NULL, into a JSON array.
- [json_agg_strict](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-agg-strict): Collect rows into a native JSON array.
- [json_group_array](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-group-array): Collect values into a JSON text array, including NULL values.
- [json_group_object](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-group-object): Collect name/value pairs into a JSON text object.
- [json_object_agg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-object-agg): Aggregate key/value pairs into native JSON, including NULL values and retaining duplicate keys.
- [json_object_agg_strict](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-object-agg-strict): Collect rows into a native JSON object.
- [json_object_agg_unique](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-object-agg-unique): Collect rows into a native JSON object.
- [json_object_agg_unique_strict](https://coordinatordb.com/docs/reference/functions/aggregate-functions/json-object-agg-unique-strict): Collect rows into a native JSON object.
- [jsonb_agg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/jsonb-agg): Aggregate values into a canonical native JSON array.
- [jsonb_agg_strict](https://coordinatordb.com/docs/reference/functions/aggregate-functions/jsonb-agg-strict): Collect rows into a native JSON array.
- [jsonb_object_agg](https://coordinatordb.com/docs/reference/functions/aggregate-functions/jsonb-object-agg): Aggregate key/value pairs with final-key-wins semantics.
- [jsonb_object_agg_strict](https://coordinatordb.com/docs/reference/functions/aggregate-functions/jsonb-object-agg-strict): Collect rows into a native JSON object.
- [jsonb_object_agg_unique](https://coordinatordb.com/docs/reference/functions/aggregate-functions/jsonb-object-agg-unique): Collect rows into a native JSON object.
- [jsonb_object_agg_unique_strict](https://coordinatordb.com/docs/reference/functions/aggregate-functions/jsonb-object-agg-unique-strict): Collect rows into a native JSON object.
- [max](https://coordinatordb.com/docs/reference/functions/aggregate-functions/max): Calculate the maximum value.
- [min](https://coordinatordb.com/docs/reference/functions/aggregate-functions/min): Calculate the minimum value.
- [mode](https://coordinatordb.com/docs/reference/functions/aggregate-functions/mode): Select the most frequent non-NULL native value using the selected collation.
- [percentile_cont](https://coordinatordb.com/docs/reference/functions/aggregate-functions/percentile-cont): Calculate a continuous numeric percentile.
- [percentile_disc](https://coordinatordb.com/docs/reference/functions/aggregate-functions/percentile-disc): Select an input value at a discrete percentile.
- [Aggregate Function Reference](https://coordinatordb.com/docs/reference/functions/aggregate-functions/reference-index): All supported CoordinatorDB aggregate functions.
- [regr_avgx](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-avgx): Calculates the mean of the independent variable over complete pairs.
- [regr_avgy](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-avgy): Calculates the mean of the dependent variable over complete pairs.
- [regr_count](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-count): Count observations with both regression variables present.
- [regr_intercept](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-intercept): Calculates the intercept of a least-squares regression line.
- [regr_r2](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-r2): Calculates the coefficient of determination of a linear regression.
- [regr_slope](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-slope): Calculates the slope of a least-squares regression line.
- [regr_sxx](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-sxx): Calculates the sum of squared deviations of the independent variable.
- [regr_sxy](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-sxy): Calculates the sum of products of centered input pairs.
- [regr_syy](https://coordinatordb.com/docs/reference/functions/aggregate-functions/regr-syy): Calculates the sum of squared deviations of the dependent variable.
- [stddev_pop](https://coordinatordb.com/docs/reference/functions/aggregate-functions/stddev-pop): Calculates the population standard deviation.
- [stddev_samp](https://coordinatordb.com/docs/reference/functions/aggregate-functions/stddev-samp): Calculates the sample standard deviation.
- [sum](https://coordinatordb.com/docs/reference/functions/aggregate-functions/sum): Calculates the sum of numeric values.
- [sum_if](https://coordinatordb.com/docs/reference/functions/aggregate-functions/sum-if): Sum non-NULL values from rows whose condition is SQL true.
- [total](https://coordinatordb.com/docs/reference/functions/aggregate-functions/total): Calculate a floating-point total, returning zero for empty input.
- [var_pop](https://coordinatordb.com/docs/reference/functions/aggregate-functions/var-pop): Calculates the population variance.
- [var_samp](https://coordinatordb.com/docs/reference/functions/aggregate-functions/var-samp): Calculates the sample variance.
- [Arithmetic functions](https://coordinatordb.com/docs/reference/functions/regular-functions/arithmetic-functions): Add, subtract, multiply and divide numeric values.
- [Array functions](https://coordinatordb.com/docs/reference/functions/regular-functions/array-functions): Array functions supported by CoordinatorDB.
- [Bit functions](https://coordinatordb.com/docs/reference/functions/regular-functions/bit-functions): Apply integer bit operations and inspect binary strings.
- [Comparison functions](https://coordinatordb.com/docs/reference/functions/regular-functions/comparison-functions): Comparison functions supported by CoordinatorDB.
- [Conditional functions and CASE](https://coordinatordb.com/docs/reference/functions/regular-functions/conditional-functions): Choose a value from conditions or missing-value fallbacks.
- [Date and time functions](https://coordinatordb.com/docs/reference/functions/regular-functions/date-time-functions): Date and time functions supported by CoordinatorDB.
- [Vector distances](https://coordinatordb.com/docs/reference/functions/regular-functions/distance-functions): Compare QBit vectors with an Array reference at a chosen precision.
- [Encoding and binary functions](https://coordinatordb.com/docs/reference/functions/regular-functions/encoding-functions): Encoding and binary functions supported by CoordinatorDB.
- [Functions for NULL values](https://coordinatordb.com/docs/reference/functions/regular-functions/functions-for-nulls): Functions for NULL values supported by CoordinatorDB.
- [Geographic functions](https://coordinatordb.com/docs/reference/functions/regular-functions/geo): Construct geometry, measure spherical distances and test containment.
- [Geographic distances](https://coordinatordb.com/docs/reference/functions/regular-functions/geo/coordinates): Calculate spherical distance between longitude/latitude coordinates.
- [Geometry construction](https://coordinatordb.com/docs/reference/functions/regular-functions/geo/geometry): Construct points and coordinate collections with typed casts.
- [point_in_polygon](https://coordinatordb.com/docs/reference/functions/regular-functions/geo/polygon): Test containment with explicit outer- and hole-boundary rules.
- [Hash and digest functions](https://coordinatordb.com/docs/reference/functions/regular-functions/hash-functions): Hash and digest functions supported by CoordinatorDB.
- [IP address and network functions](https://coordinatordb.com/docs/reference/functions/regular-functions/ip-address-functions): IP address and network functions supported by CoordinatorDB.
- [JSON functions](https://coordinatordb.com/docs/reference/functions/regular-functions/json-functions): JSON functions supported by CoordinatorDB.
- [Logical expressions](https://coordinatordb.com/docs/reference/functions/regular-functions/logical-functions): Combine SQL truth values with AND, OR and NOT.
- [Mathematical functions](https://coordinatordb.com/docs/reference/functions/regular-functions/math-functions): Mathematical functions supported by CoordinatorDB.
- [Utility functions](https://coordinatordb.com/docs/reference/functions/regular-functions/other-functions): Utility functions supported by CoordinatorDB.
- [Scalar functions](https://coordinatordb.com/docs/reference/functions/regular-functions/overview): CoordinatorDB scalar function reference.
- [Random functions](https://coordinatordb.com/docs/reference/functions/regular-functions/random-functions): Random functions supported by CoordinatorDB.
- [Rounding functions](https://coordinatordb.com/docs/reference/functions/regular-functions/rounding-functions): Round, raise, lower or truncate numeric values.
- [Splitting and joining strings](https://coordinatordb.com/docs/reference/functions/regular-functions/splitting-merging-functions): Splitting and joining strings supported by CoordinatorDB.
- [String functions](https://coordinatordb.com/docs/reference/functions/regular-functions/string-functions): String functions supported by CoordinatorDB.
- [String replacement functions](https://coordinatordb.com/docs/reference/functions/regular-functions/string-replace-functions): String replacement functions supported by CoordinatorDB.
- [String search and full-text functions](https://coordinatordb.com/docs/reference/functions/regular-functions/string-search-functions): String search and full-text functions supported by CoordinatorDB.
- [Tuple functions](https://coordinatordb.com/docs/reference/functions/regular-functions/tuple-functions): Construct fixed records and select positional or named fields.
- [Map functions](https://coordinatordb.com/docs/reference/functions/regular-functions/tuple-map-functions): Construct ordered maps and inspect keys, values and missing entries.
- [Type conversion functions](https://coordinatordb.com/docs/reference/functions/regular-functions/type-conversion-functions): Convert values explicitly and inspect their native type.
- [UUID functions](https://coordinatordb.com/docs/reference/functions/regular-functions/uuid-functions): UUID functions supported by CoordinatorDB.
- [Table functions](https://coordinatordb.com/docs/reference/functions/table-functions): Produce query rows from series, arrays, JSON, text or confined files.
- [file](https://coordinatordb.com/docs/reference/functions/table-functions/file): Read a confined server-side file as a typed SQL relation.
- [generate_series](https://coordinatordb.com/docs/reference/functions/table-functions/generate-series): Generate inclusive numeric or calendar values as a table source.
- [Window functions](https://coordinatordb.com/docs/reference/functions/window-functions): Calculate rankings, adjacent values and aggregates without collapsing rows.
- [cume_dist](https://coordinatordb.com/docs/reference/functions/window-functions/cume-dist): Calculate the cumulative distribution within a partition.
- [dense_rank](https://coordinatordb.com/docs/reference/functions/window-functions/dense-rank): Rank rows within a partition without gaps after ties.
- [first_value](https://coordinatordb.com/docs/reference/functions/window-functions/first-value): Read the first value in a window frame.
- [lag](https://coordinatordb.com/docs/reference/functions/window-functions/lag): Read a value before the current row in an ordered partition.
- [last_value](https://coordinatordb.com/docs/reference/functions/window-functions/last-value): Read the last value in a window frame.
- [lead](https://coordinatordb.com/docs/reference/functions/window-functions/lead): Read a value after the current row in an ordered partition.
- [nth_value](https://coordinatordb.com/docs/reference/functions/window-functions/nth-value): Read the nth value in a window frame.
- [ntile](https://coordinatordb.com/docs/reference/functions/window-functions/ntile): Divide an ordered partition into numbered buckets.
- [percent_rank](https://coordinatordb.com/docs/reference/functions/window-functions/percent-rank): Calculate the relative rank of a row within its partition.
- [rank](https://coordinatordb.com/docs/reference/functions/window-functions/rank): Rank rows within a partition, leaving gaps after ties.
- [row_number](https://coordinatordb.com/docs/reference/functions/window-functions/row-number): Number rows within each partition, starting at one.
- [Reference](https://coordinatordb.com/docs/reference/home): CoordinatorDB SQL, types, functions, formats, settings and system tables.
- [Operators](https://coordinatordb.com/docs/reference/operators): Combine SQL values with arithmetic, comparisons, logic, membership and search.
- [Settings](https://coordinatordb.com/docs/reference/settings): Database, format and server options in CoordinatorDB.
- [Format settings](https://coordinatordb.com/docs/reference/settings/formats): Statement-scoped format options and defaults in CoordinatorDB.
- [Delimited format settings](https://coordinatordb.com/docs/reference/settings/formats/format): Tab-separated and Hive text delimiters, headers, defaults, and row boundaries.
- [Avro settings](https://coordinatordb.com/docs/reference/settings/formats/format-avro): Configure Avro containers and schema-registry records.
- [RowBinary settings](https://coordinatordb.com/docs/reference/settings/formats/format-binary): Configure binary row headers, JSON representation and string limits.
- [CSV format settings](https://coordinatordb.com/docs/reference/settings/formats/format-csv): CSV separators, quotes, headers, and input defaults.
- [CustomSeparated format settings](https://coordinatordb.com/docs/reference/settings/formats/format-custom): Custom text row, field, and result delimiters.
- [Regular-expression input settings](https://coordinatordb.com/docs/reference/settings/formats/format-regexp): Match complete lines and decode capture groups into fields.
- [Protobuf schema settings](https://coordinatordb.com/docs/reference/settings/formats/format-schema): Choose literal message schemas, inferred fields, wrappers and oneof behavior.
- [Template settings](https://coordinatordb.com/docs/reference/settings/formats/format-template): Define row/result templates, separators and JSON integer quoting.
- [Shared input settings](https://coordinatordb.com/docs/reference/settings/formats/input-format): Control unknown named fields for the formats that support name binding.
- [Other format settings](https://coordinatordb.com/docs/reference/settings/formats/other): BSON strings, GeoJSON validation, and MessagePack UUID encoding.
- [Output settings](https://coordinatordb.com/docs/reference/settings/formats/output-format): Control display, image dimensions and generated SQL statements.
- [Server settings](https://coordinatordb.com/docs/reference/settings/server-settings/settings): CoordinatorDB server XML reference.
- [http_port](https://coordinatordb.com/docs/reference/settings/server-settings/settings/http): Enable HTTP on a port from 0 through 65535.
- [listen_host](https://coordinatordb.com/docs/reference/settings/server-settings/settings/listen): Bind configured listeners to a numeric IPv4 or IPv6 address.
- [Request and admission limits](https://coordinatordb.com/docs/reference/settings/server-settings/settings/max): Configure processing ceilings, connection admission and socket timeouts.
- [Logger and file paths](https://coordinatordb.com/docs/reference/settings/server-settings/settings/other): Configure diagnostic log destinations, rotation and confined file sources.
- [tcp_port](https://coordinatordb.com/docs/reference/settings/server-settings/settings/tcp-port): Choose the native TCP port, defaulting to 7400.
- [users_config](https://coordinatordb.com/docs/reference/settings/server-settings/settings/users): Locate the required explicit user credential file.
- [Database settings](https://coordinatordb.com/docs/reference/settings/session-settings): Persistent database settings, defaults and values in CoordinatorDB.
- [Query logging settings](https://coordinatordb.com/docs/reference/settings/session-settings/log-queries): Enable structured request history and choose a minimum recorded duration.
- [max_execution_time](https://coordinatordb.com/docs/reference/settings/session-settings/max-execution): Bound request processing time in seconds.
- [max_memory_usage](https://coordinatordb.com/docs/reference/settings/session-settings/max-memory-usage): Bound accounted live SQL memory across a request.
- [max_result_rows and max_response_bytes](https://coordinatordb.com/docs/reference/settings/session-settings/max-result): Bound cumulative returned rows and complete encoded response bytes.
- [max_threads](https://coordinatordb.com/docs/reference/settings/session-settings/max-threads): Choose a ceiling on total threads used by an eligible query.
- [foreign_keys, recursive_triggers, user_version, application_id](https://coordinatordb.com/docs/reference/settings/session-settings/other): Set connection flags and application-managed header values with PRAGMA or validated catalog writes.
- [SQL statements](https://coordinatordb.com/docs/reference/statements): CoordinatorDB statement and SELECT-clause reference.
- [ALTER TABLE](https://coordinatordb.com/docs/reference/statements/alter): Add, drop or rename columns and rename an existing table.
- [ALTER TABLE columns](https://coordinatordb.com/docs/reference/statements/alter/column): Add, drop and rename columns while preserving a valid table definition.
- [ATTACH](https://coordinatordb.com/docs/reference/statements/attach): Attach another database namespace to an embedded connection.
- [CREATE INDEX](https://coordinatordb.com/docs/reference/statements/create/create-index): Index columns or expressions, with optional uniqueness and a row predicate.
- [CREATE DATABASE](https://coordinatordb.com/docs/reference/statements/create/database): Create a named persistent database on the server.
- [CREATE TABLE](https://coordinatordb.com/docs/reference/statements/create/table): Define typed columns, constraints and generated values.
- [Temporary tables](https://coordinatordb.com/docs/reference/statements/create/table/temporary-table): Create connection-local tables in the temp namespace.
- [CREATE VIEW](https://coordinatordb.com/docs/reference/statements/create/view): Name a SELECT definition that is evaluated when queried.
- [DELETE](https://coordinatordb.com/docs/reference/statements/delete): Remove matching rows and optionally return their deleted values.
- [DETACH](https://coordinatordb.com/docs/reference/statements/detach): Remove an attached namespace without deleting its database file.
- [DROP](https://coordinatordb.com/docs/reference/statements/drop): Remove tables, views, indexes and triggers.
- [EXPLAIN](https://coordinatordb.com/docs/reference/statements/explain): Inspect a planned statement or execute it with runtime measurements.
- [IN](https://coordinatordb.com/docs/reference/statements/in): Test membership in a value list, subquery or table.
- [INSERT INTO](https://coordinatordb.com/docs/reference/statements/insert-into): Insert literal rows, query results, defaults or formatted input.
- [Rename a table](https://coordinatordb.com/docs/reference/statements/rename): Give an existing table a new name with ALTER TABLE.
- [SELECT](https://coordinatordb.com/docs/reference/statements/select): Read rows, evaluate expressions and calculate aggregate or window results.
- [ALL](https://coordinatordb.com/docs/reference/statements/select/all): Retain duplicate rows in SELECT and UNION ALL results.
- [DISTINCT](https://coordinatordb.com/docs/reference/statements/select/distinct): Remove duplicate projected rows.
- [EXCEPT](https://coordinatordb.com/docs/reference/statements/select/except): Return distinct left-side rows absent from the right-side result.
- [FORMAT](https://coordinatordb.com/docs/reference/statements/select/format): Encode a server query result in a registered output format.
- [FROM](https://coordinatordb.com/docs/reference/statements/select/from): Read rows from tables, views, subqueries and table functions.
- [GROUP BY](https://coordinatordb.com/docs/reference/statements/select/group-by): Calculate aggregates independently for rows with equal grouping keys.
- [HAVING](https://coordinatordb.com/docs/reference/statements/select/having): Filter groups using aggregate results.
- [INTERSECT](https://coordinatordb.com/docs/reference/statements/select/intersect): Return distinct rows present in both query results.
- [JOIN](https://coordinatordb.com/docs/reference/statements/select/join): Combine related rows and retain unmatched rows with outer joins.
- [LIMIT](https://coordinatordb.com/docs/reference/statements/select/limit): Return a bounded number of rows after sorting and skipping an offset.
- [OFFSET](https://coordinatordb.com/docs/reference/statements/select/offset): Skip rows before returning a limited result.
- [ORDER BY](https://coordinatordb.com/docs/reference/statements/select/order-by): Sort query results and choose the placement of NULL values.
- [UNION](https://coordinatordb.com/docs/reference/statements/select/union): Combine query results with optional duplicate elimination.
- [WHERE](https://coordinatordb.com/docs/reference/statements/select/where): Filter input rows before grouping and aggregation.
- [WITH](https://coordinatordb.com/docs/reference/statements/select/with): Name reusable subqueries and define recursive common table expressions.
- [SET](https://coordinatordb.com/docs/reference/statements/set): Persist a validated database setting for subsequent requests.
- [SHOW](https://coordinatordb.com/docs/reference/statements/show): List databases, tables, effective settings and system relations.
- [UPDATE](https://coordinatordb.com/docs/reference/statements/update): Change matching rows immediately and optionally return their new values.
- [USE](https://coordinatordb.com/docs/reference/statements/use): Select the server database used by later native requests.
- [SQL syntax](https://coordinatordb.com/docs/reference/syntax): Write identifiers, literals, expressions, statement batches and control statements.
- [system.columns](https://coordinatordb.com/docs/reference/system-tables/columns): Inspect declared column types, positions, defaults and key membership.
- [system.databases](https://coordinatordb.com/docs/reference/system-tables/databases): Read the managed database inventory and validated management fields.
- [system.formats](https://coordinatordb.com/docs/reference/system-tables/formats): Discover format names and their input/output directions.
- [system.functions](https://coordinatordb.com/docs/reference/system-tables/functions): Read descriptive metadata for documented scalar and aggregate overloads.
- [System tables](https://coordinatordb.com/docs/reference/system-tables/overview): CoordinatorDB server catalogs and request observations.
- [system.processes](https://coordinatordb.com/docs/reference/system-tables/processes): Observe active TCP and HTTP requests independently of query logging.
- [system.query_log](https://coordinatordb.com/docs/reference/system-tables/query-log): Read structured request events, errors and terminal resource counters.
- [system.settings](https://coordinatordb.com/docs/reference/system-tables/settings): Inspect effective database values and read-only format defaults.
- [system.tables](https://coordinatordb.com/docs/reference/system-tables/tables): Inspect table/view definitions and available size estimates across databases.
- [About Coordinator DB](https://coordinatordb.com/docs/resources/about): Choose a Coordinator DB connection and find its public SQL and interface documentation.
- [Adopting Coordinator DB](https://coordinatordb.com/docs/resources/about/adopters): Evaluate Coordinator DB with an application's queries, connection requirements and recovery procedure.
- [Coordinator DB support](https://coordinatordb.com/docs/resources/about/support): Prepare a reproducible Coordinator DB support request using public request diagnostics and a minimal dataset.
- [Changelog](https://coordinatordb.com/docs/resources/changelog): Example release notes for Coordinator DB, grouped by version and change type.
- [Development and contributing](https://coordinatordb.com/docs/resources/develop-contribute): Develop and verify Coordinator DB applications, integrations and documentation.
- [Verify a local build](https://coordinatordb.com/docs/resources/develop-contribute/build/build): Check a Coordinator DB executable, configuration and first SQL result on its intended host.
- [Validate an ARM distribution](https://coordinatordb.com/docs/resources/develop-contribute/build/build-cross-arm): Verify a Coordinator DB distribution on its intended ARM machine and application workload.
- [Validate a LoongArch distribution](https://coordinatordb.com/docs/resources/develop-contribute/build/build-cross-loongarch): Check a LoongArch-targeted executable with explicit paths, configuration and SQL fixtures.
- [Validate a macOS cross build](https://coordinatordb.com/docs/resources/develop-contribute/build/build-cross-osx): Separate build-host results from runtime verification of a macOS-targeted executable.
- [Validate a RISC-V distribution](https://coordinatordb.com/docs/resources/develop-contribute/build/build-cross-riscv): Collect target-side startup and application compatibility evidence for RISC-V.
- [Validate an s390x distribution](https://coordinatordb.com/docs/resources/develop-contribute/build/build-cross-s390x): Verify text, numeric and binary application results on an s390x target.
- [Validate an Elbrus distribution](https://coordinatordb.com/docs/resources/develop-contribute/build/build-e2k): Record executable startup and application compatibility checks on an Elbrus environment.
- [Verify a macOS build](https://coordinatordb.com/docs/resources/develop-contribute/build/build-osx): Check Coordinator DB startup, local paths and native queries on macOS.
- [Compatibility fixes and backports](https://coordinatordb.com/docs/resources/develop-contribute/contribute/backports): Describe affected versions and verify a narrowly scoped integration fix against each target.
- [Benchmark compressed input](https://coordinatordb.com/docs/resources/develop-contribute/contribute/building-and-benchmarking-deflate-qpl): Measure application-side compressed file loading with equivalent rows and reproducible conditions.
- [Continuous integration checks](https://coordinatordb.com/docs/resources/develop-contribute/contribute/continuous-integration): Run reproducible Coordinator DB application checks in an automated job.
- [Third-party integration dependencies](https://coordinatordb.com/docs/resources/develop-contribute/contribute/contrib): Review the observable behavior and distribution requirements of application-side dependencies.
- [Integrate the embedded API](https://coordinatordb.com/docs/resources/develop-contribute/contribute/integrating-rust-libraries): Define connection ownership, parameter binding and typed result behavior for embedded applications.
- [Measure application workloads](https://coordinatordb.com/docs/resources/develop-contribute/contribute/profile-guided-optimization): Use repeatable end-to-end measurements to assess Coordinator DB integration changes.
- [Integration code style](https://coordinatordb.com/docs/resources/develop-contribute/contribute/style): Make application examples and adapters readable through explicit SQL, types and ownership.
- [Regression tests](https://coordinatordb.com/docs/resources/develop-contribute/contribute/tests): Describe Coordinator DB behavior with small deterministic input, output and session checks.
- [Integration development](https://coordinatordb.com/docs/resources/develop-contribute/integrations): Choose the public Coordinator DB interface and contract for an application adapter.
- [Build an integration](https://coordinatordb.com/docs/resources/develop-contribute/integrations/building-integrations): Implement explicit request, result and error handling at the public Coordinator DB boundary.
- [Document your integration](https://coordinatordb.com/docs/resources/develop-contribute/integrations/documenting-your-integration): Write runnable Coordinator DB adapter documentation with explicit behavior and tested limits.
- [Test your integration](https://coordinatordb.com/docs/resources/develop-contribute/integrations/testing-your-integration): Verify authentication, sessions, values, writes and failures in a Coordinator DB adapter.
- [Public connection model](https://coordinatordb.com/docs/resources/develop-contribute/introduction/architecture): Understand API boundaries, session ownership and database access in Coordinator DB applications.
- [Developer guide](https://coordinatordb.com/docs/resources/develop-contribute/introduction/developer-instruction): Prepare reproducible Coordinator DB integration and documentation contributions.
- [Native result and input formats](https://coordinatordb.com/docs/resources/develop-contribute/native-protocol/format): Select and verify row formats without confusing them with the native transport protocol.
- [Native transport integrity checks](https://coordinatordb.com/docs/resources/develop-contribute/native-protocol/hash): Separate transfer verification, result comparison and documented native client behavior.
- [Native protocol](https://coordinatordb.com/docs/resources/develop-contribute/native-protocol/protocol): Use the public Coordinator DB native connection contract through the supplied client.
- [Roadmap and feature proposals](https://coordinatordb.com/docs/resources/develop-contribute/roadmap): Evaluate documented Coordinator DB capabilities and make concrete proposals without release assumptions.
- [Support center](https://coordinatordb.com/docs/resources/support-center/home): Find Coordinator DB answers by topic: SQL, imports, connections, configuration, diagnostics and recovery.
- [Connect ingestion clients over a private network](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/aws-privatelink-setup-for-clickpipes): Place an external importer on a trusted route to the SQL endpoint.
- [Import from a private managed Kafka source](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/aws-privatelink-setup-for-msk-clickpipes): Run a separate consumer with access to both the broker and Coordinator DB.
- [Plan a private route for a broker consumer](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/aws-privatelink-vpc-endpoint-service-for-msk-cluster): Verify independent broker and database routes before continuous ingestion.
- [Update an infrastructure billing contact](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/change-billing-email): Locate billing ownership outside the database SQL interface.
- [Automate Coordinator DB SQL over HTTP](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/clickhouse-cloud-api-usage): Use the documented request endpoint instead of a cloud management API.
- [Connect a private Confluent consumer to SQL](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/confluent-cloud-private-connectivity-for-clickpipes): Keep external broker connectivity separate from destination ingestion.
- [Use a custom DNS name for SQL access](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/custom-dns-alias-for-instance): Point a client hostname at the configured listener or external proxy.
- [Inspect service metadata with system tables](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/execute-system-queries-in-cloud): Use documented read only relations rather than administrative SYSTEM commands.
- [Check service readiness and SQL access](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/how-to-check-my-clickhouse-cloud-sevice-state): Distinguish a listening endpoint from a usable authenticated database.
- [Reach SQL through an SSH tunnel](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/how-to-connect-to-ch-cloud-using-ssh-keys): Forward a local port while keeping database authentication separate.
- [Diagnose ingestion failures after an upgrade](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/ingest-failures-23-9-release): Compare the input contract and capture an exact failing request.
- [Move a verified database copy to another region](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/multi-region-replication): Treat a remote copy as an independent dataset with an explicit cutover.
- [Control diagnostic artifacts in your deployment](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/opt-out-core-dump-collection): Review host crash collection and share redacted request evidence.
- [Restore access to a SQL endpoint](https://coordinatordb.com/docs/resources/support-center/knowledge-base/cloud-services/unable-to-access-cloud-service): Check routing, listeners, authentication and request admission in order.
- [Apply request budgets without per-user quotas](https://coordinatordb.com/docs/resources/support-center/knowledge-base/configuration-settings/about-quotas-and-query-complexity): Use server ceilings and database limits with their actual scope.
- [Replace an unsupported ALTER USER setting change](https://coordinatordb.com/docs/resources/support-center/knowledge-base/configuration-settings/alter-user-settings-exception): Manage credentials in XML and request defaults through SET.
- [Use native client commands and connection options](https://coordinatordb.com/docs/resources/support-center/knowledge-base/configuration-settings/change-the-prompt-in-clickhouse-client): Identify the active database without relying on a custom prompt setting.
- [Configure a database request default](https://coordinatordb.com/docs/resources/support-center/knowledge-base/configuration-settings/configure-a-user-setting): Set a supported value with awareness that it affects other clients.
- [Correct an unknown or invalid setting](https://coordinatordb.com/docs/resources/support-center/knowledge-base/configuration-settings/ignoring-incorrect-settings): Use strict validation to find misspellings and wrong configuration scope.
- [Plan the number of tables and databases](https://coordinatordb.com/docs/resources/support-center/knowledge-base/configuration-settings/maximum-number-of-tables-and-databases): Inspect the current inventory and verify growth with representative workloads.
- [Commit related inserts atomically](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/achieving-atomic-inserts): Use a transaction for related SQL writes and respect connection scope.
- [Add data to a Parquet export safely](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/cannot-append-data-to-parquet-format): Create a new complete file instead of concatenating binary exports.
- [Export query results to a client file](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/file-export): Redirect exact result bytes from the native client and verify the artifact.
- [Work with arrays of JSON objects](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/importing-and-working-with-json-array-objects): Expand a JSON array into explicitly typed rows for SQL processing.
- [Import GeoJSON features with nested properties](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/importing-geojason-with-nested-object-array): Validate geometry separately from flexible JSON feature properties.
- [Import Parquet downloaded from object storage](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/ingest-parquet-files-in-s3): Fetch a file with external tooling and load it through the native client.
- [Extract values from a JSON document](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/json-extract-example): Use explicit JSON paths and distinguish missing fields from JSON null.
- [Choose the right JSON input format](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/json-import): Match row oriented JSON and whole documents to their documented formats.
- [Load and query a small JSON dataset](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/json-simple-example): Create explicit columns, insert row objects and verify their values.
- [Load JSON records from an external Kafka consumer](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/kafka-clickhouse-json): Translate decoded messages into validated row uploads.
- [Set up a repeatable external Kafka import](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/kafka-to-clickhouse-setup): Test the consumer, SQL destination and recovery policy independently.
- [Exchange MySQL query results through files](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/mysql-to-parquet-csv-json): Use an external export and explicit Coordinator DB destination types.
- [Convert Parquet rows to CSV or JSON](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/parquet-to-csv-json): Load a typed file and export a deliberate consumer representation.
- [Exchange PostgreSQL results through files](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/postgresql-to-parquet-csv-json): Keep source export rules and destination type validation explicit.
- [Organize exports in year and month folders](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-import-export/s3-export-data-year-month-folders): Let an external export job choose filenames and upload completed artifacts.
- [Preserve a selected date range](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/backing-up-a-specific-partition): Copy selected rows for an archive and distinguish that export from a database backup.
- [Measure zeros and missing values](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/calculate-ratio-of-zero-sparse-serialization): Calculate a column value distribution before changing its representation.
- [Keep lookup data consistent](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/dictionaries-consistent-state): Store lookup values in a table and commit related changes together.
- [Use string-keyed lookup data](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/dictionary-using-strings): Choose a keyed table or a typed map for string lookups.
- [Read related data in one transaction](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/read-consistency): Choose a connection scope that keeps related read and write steps together.
- [Distinguish tables from interchange formats](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/understanding-part-types-and-storage-formats): Use table metadata for stored data and formats for import and export.
- [Apply an explicit retention cutoff](https://coordinatordb.com/docs/resources/support-center/knowledge-base/data-management/when-is-ttl-applied): Preview and delete expired rows with a reviewed date predicate.
- [General Coordinator DB questions](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs): Start with the query model, public interfaces and documented capability boundaries.
- [Choose SQL by the reader task](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/columnar-database): Evaluate filters, aggregates and lookups through documented query behavior.
- [Connect concurrent applications safely](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/concurrency): Use one server for multiple clients and respect database file-sharing limits.
- [Inspect the chosen query plan](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/cost-based): Use EXPLAIN and measured executions instead of assuming optimizer behavior.
- [Query and import a local data file](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/datalake): Read supported formats with an explicit schema and confined server file paths.
- [Name databases and SQL objects](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/dbms-naming): Choose stable identifiers and select the intended managed database explicitly.
- [Prepare the files and credentials a service needs](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/dependencies): Identify the documented runtime inputs without assuming external services.
- [Join related data in Coordinator DB](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/distributed-join): Bring related rows into documented SQL sources before joining them.
- [Coordinator DB frequently asked questions](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/faq-index): Find practical answers about SQL, deployment, data changes and reader tasks.
- [Query available data sources deliberately](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/federated): Use managed databases and explicit file sources without assuming remote federation.
- [Prepare a useful Coordinator DB contribution](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/how-do-i-contribute-code-to-clickhouse): Make a public behavior change easy to reproduce, test and review.
- [Store and update keyed records](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/key-value): Use a primary-key table for exact lookups and repeatable upserts.
- [Express grouped calculations in SQL](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/mapreduce): Use filtering and aggregation for row-to-summary transformations.
- [Investigate a slow query step by step](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/ne-tormozit): Check correctness, selected work and limits before changing configuration.
- [Build analytical reports with SQL](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/olap): Use grouped aggregates, joins and window functions for reports.
- [Operate a Coordinator DB service](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/operations-index): Find the public procedures for configuration, monitoring, copies and maintenance.
- [Choose database paths and independent copies](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/separate-storage): Keep database ownership separate from configuration and file-input locations.
- [Use Coordinator DB SQL deliberately](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/sql): Find supported statements, expressions and interface-specific commands.
- [Query dated measurements](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/time-series): Define time boundaries, group observations and maintain retention explicitly.
- [Update existing rows transactionally](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/updates): Use UPDATE and upserts with explicit keys and predicates.
- [Coordinator DB use cases](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/use-cases-index): Choose a practical SQL workflow for lookups, reports, events or vectors.
- [Analyze application event logs](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/use-clickhouse-for-log-analytics): Query event counts and structured attributes after explicit ingestion.
- [Compare fixed-dimensional vectors](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/vector-search): Rank stored QBit vectors with documented distance functions.
- [Evaluate Coordinator DB for your workload](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/who-is-using-clickhouse): Test a representative reader task without relying on unverified customer claims.
- [Choose a single-server application connection](https://coordinatordb.com/docs/resources/support-center/knowledge-base/general-faqs/why-recommend-clickhouse-keeper-over-zookeeper): Use documented database access without adding an assumed coordination service.
- [Integrate an application with Coordinator DB](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations): Choose native TCP, HTTP or embedded access for the application task.
- [Move SQL Server data into a containerized SQL service](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/how-to-set-up-ch-on-docker-odbc-connect-mssql): Separate container routing from external source export and row loading.
- [Run a SQL request from Node.js](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/node-js-example): Use HTTP fetch with explicit authentication and error handling.
- [Connect reporting tools without assuming ODBC compatibility](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/odbc-authentication-failed-error-using-powerbi-ch-connector): Verify the SQL endpoint independently and use file exchange when necessary.
- [Import Oracle query results through a file](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/oracle-odbc): Use an external Oracle export instead of a server ODBC data source.
- [Use Python without a product specific database driver](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/python-clickhouse-connect-example): Choose standard HTTP requests for the documented SQL interface.
- [Send Python HTTP queries and parse JSON rows](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/python-http-requests): Read status and query identifiers before decoding response data.
- [Manage deployment configuration with external automation](https://coordinatordb.com/docs/resources/support-center/knowledge-base/integrations/terraform-example): Keep infrastructure provisioning separate from SQL and startup XML.
- [Choose live views or stored query results](https://coordinatordb.com/docs/resources/support-center/knowledge-base/materialized-views/are-materialized-views-inserted-asynchronously): Distinguish ordinary views from explicitly maintained result tables.
- [Inspect requests that query a view](https://coordinatordb.com/docs/resources/support-center/knowledge-base/materialized-views/how-to-display-queries-using-mv): Find view queries in request history and verify their access plan.
- [Filter an ordinary view with query parameters](https://coordinatordb.com/docs/resources/support-center/knowledge-base/materialized-views/how-to-use-parametrised-views): Combine reusable view definitions with caller-supplied predicates.
- [Use a targeted index for repeated queries](https://coordinatordb.com/docs/resources/support-center/knowledge-base/materialized-views/projection-example): Create and verify an index that matches an application lookup.
- [Check report data after a restart](https://coordinatordb.com/docs/resources/support-center/knowledge-base/materialized-views/what-happens-to-refreshable-materialized-views-when-the-server-restarts): Verify ordinary views and application-maintained report tables after restarting.
- [Investigate repeated-query performance](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/check-query-cache-in-use): Use request measurements without assuming an undocumented query cache.
- [Build a request timeline from query history](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/collect-and-draw-traces): Correlate request start, completion and failure events by query ID.
- [Capture a browser request for diagnosis](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/generate-har-file): Collect useful Playground request details while removing credentials and private data.
- [Choose request metrics for external monitoring](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/mapping-of-system-metrics-to-prometheus-metrics): Map documented query counters into an application-owned monitoring view.
- [Write diagnostic logs to a file](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/outputsendlogsleveltracestofile): Configure log destinations and rotation through the server XML file.
- [Profile SQL with analyzed execution plans](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/profiling-clickhouse-with-llvm-xray): Measure an actual SQL statement using EXPLAIN ANALYZE and query history.
- [Choose diagnostic and query logging levels](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/send-logs-level): Configure diagnostic verbosity independently from structured SQL history.
- [Monitor active data-changing requests](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/view-number-of-active-mutations): Observe writes directly rather than looking for a background mutation queue.
- [See currently active requests](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/which-processes-are-currently-running): Read system.processes and distinguish active execution from request history.
- [Reduce diagnostic log verbosity](https://coordinatordb.com/docs/resources/support-center/knowledge-base/monitoring-debugging/why-default-logging-verbose): Choose a supported server level while keeping useful query evidence.
- [Choose an explicit result order](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/async-vs-optimize-read-in-order): Use ORDER BY for a stable result and inspect the cost of sorting.
- [Measure query processing time](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/check-query-processing-time-only): Distinguish SQL processing measurements from client and response time.
- [Find expensive completed queries](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/find-expensive-queries): Rank successful requests by duration and inspect their resource counters.
- [Find queries with high memory usage](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/finding-expensive-queries-by-memory-usage): Compare terminal peak memory measurements and identify wide query results.
- [Choose between Map fields and typed columns](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/improve-map-performance): Make frequently queried fields explicit and retain flexible key value data.
- [Tune INSERT SELECT requests](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/insert-select-settings-tuning): Measure and bound a query that copies rows between tables.
- [Resolve a query memory limit error](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/memory-limit-exceeded-for-query): Inspect effective ceilings and reduce a request before changing its budget.
- [Resolve duplicate rows with explicit SQL](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/optimize-final-vs-final): Use keys and documented conflict handling instead of background finalization.
- [Set a query execution deadline](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/query-max-execution-time): Apply a persisted processing time limit and distinguish it from network timeouts.
- [Choose precise basic data types](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/tips-tricks-optimizing-basic-data-types-in-clickhouse): Use declared ranges and value semantics when selecting a table schema.
- [Investigate a primary key access plan](https://coordinatordb.com/docs/resources/support-center/knowledge-base/performance-optimization/why-is-my-primary-key-not-used): Compare the query predicate with the declared key and inspect EXPLAIN output.
- [Calculate pi with SQL](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/calculate-pi-using-sql): Use a constant and a converging series to check numeric SQL calculations.
- [Compare two query result sets](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/compare-resultsets): Find missing rows and distinguish set differences from duplicate-count differences.
- [Compare query measurements](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/comparing-metrics-between-queries): Compare equivalent executions using terminal query events and analyzed plans.
- [Calculate filtered aggregates](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/filtered-aggregates): Compute several conditional totals from the same input rows.
- [Filter rows by an array member](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/how-to-filter-a-clickhouse-table-by-an-array-column): Use has and array positions to filter typed array values.
- [Insert rows from another table](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/how-to-insert-all-rows-from-another-table): Copy a selected relation with explicit destination columns and constraints.
- [Pivot a known set of categories](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/pivot): Turn selected categories into columns using conditional aggregation.
- [Useful diagnostic SQL queries](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/useful-queries-for-troubleshooting): Inspect the selected database, active requests and recent errors.
- [Expand JSON attributes into rows](https://coordinatordb.com/docs/resources/support-center/knowledge-base/queries-sql/using-array-join-to-extract-and-query-attributes): Use json_each for row-oriented analysis of JSON objects and arrays.
- [Check configured users and active identities](https://coordinatordb.com/docs/resources/support-center/knowledge-base/security/check-users-roles): Review explicit credentials and observe the identity used by a request.
- [Plan access without database roles](https://coordinatordb.com/docs/resources/support-center/knowledge-base/security/common-rbac-queries): Apply explicit credentials and application controls instead of unsupported grants.
- [Remove empty-password default access](https://coordinatordb.com/docs/resources/support-center/knowledge-base/security/remove-default-user): Replace the sample default account with explicit named credentials.
- [Design row and column access boundaries](https://coordinatordb.com/docs/resources/support-center/knowledge-base/security/row-column-policy): Keep application filters separate from database-enforced permissions.
- [Understand browser request identity and state](https://coordinatordb.com/docs/resources/support-center/knowledge-base/security/set-role-not-persisting-in-sql-console): Use configured authentication rather than session roles in browser SQL.
- [Connect application identity to database access](https://coordinatordb.com/docs/resources/support-center/knowledge-base/security/windows-active-directory-to-ch-roles): Separate external user login from Coordinator DB service credentials.
- [Verify the executable you are running](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/difference-between-official-builds-and-3rd-party): Keep executable provenance, configuration and verification steps together.
- [Use HTTPS in front of the HTTP interface](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/enabling-ssl-with-lets-encrypt): Plan external TLS termination around the documented HTTP listener rules.
- [Choose and verify a query thread limit](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/how-to-increase-thread-pool-size): Use max_threads as a ceiling and observe actual query usage.
- [Plan a Windows client connection](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/install-clickhouse-windows10): Separate the client environment from the documented server installation workflow.
- [Check installation prerequisites](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/llvm-clang-up-to-date): Follow the documented installation requirements and preserve the first installation error.
- [Prepare a persistent Coordinator DB service](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/production): Review credentials, listeners, limits and recovery before serving application traffic.
- [Use documentation safely with a SQL assistant](https://coordinatordb.com/docs/resources/support-center/knowledge-base/setup-installation/set-up-clickhouse-documentation-mcp-server): Give an assistant public references and review the SQL it proposes.
- [Add a column to an existing table](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/add-column): Choose a definition that remains valid for rows already stored.
- [Delete rows older than a chosen boundary](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/delete-old-data): Preview a retention predicate and commit the intended deletion.
- [Switch a table name with explicit renames](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/exchangestatementtoswitchtables): Validate a replacement table and change names in a controlled transaction.
- [Combine data from independent SQL services](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/how-to-create-table-to-query-multiple-remote-clusters): Gather remote results in a client workflow and join explicit local tables.
- [Use a shared persistent table across client sessions](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/recreate-table-across-terminals): Distinguish persistent objects from connection scoped temporary tables.
- [Validate a JSON schema change with a small runbook](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/runbook-json): Test typed paths, missing values and imports before changing live writes.
- [Choose a schema migration workflow](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/schema-migration-tools): Use explicit supported DDL and record migration state outside assumptions.
- [Find tables with a name pattern](https://coordinatordb.com/docs/resources/support-center/knowledge-base/tables-schema/search-across-node-for-tables-with-a-wildcard): Search registered metadata and distinguish local inventory from remote discovery.
- [Resolve certificate verification failures at the TLS boundary](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/certificate-verify-failed-error): Check the external HTTPS endpoint without disabling certificate validation.
- [Review container permissions before adding capabilities](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/configure-cap-ipc-lock-and-cap-sys-nice-in-docker): Diagnose the actual startup or access failure with minimal privileges.
- [Diagnose remote SQL connection timeouts](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/connection-timeout-remote-remotesecure): Test the documented client protocol and distinguish timeout stages.
- [Inspect table counts and size estimates](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/count-parts-by-type): Use public table metadata instead of physical part diagnostics.
- [Diagnose pressure from many small inserts](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/exception-too-many-parts): Batch related rows and inspect documented admission and processing errors.
- [Handle a macOS executable verification warning](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/fix-developer-verification-error-in-macos): Verify the executable source before allowing it through host security controls.
- [Resolve overlapping data import ranges](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/part-intersects-previous-part): Reconcile duplicate or intersecting batches using application identifiers.
- [Recover data from a verified independent copy](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/recovering-from-corrupt-keeper-snapshot): Preserve the damaged source and validate a clean replacement before use.
- [Restore an independent service after storage failure](https://coordinatordb.com/docs/resources/support-center/knowledge-base/troubleshooting/restore-replica-after-storage-failure): Reopen a verified copy and make the recovery boundary explicit.
- [Practical habits for reliable SQL work](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/community-wisdom): Keep small examples, explicit state and measured evidence with everyday queries.
- [Reduce unnecessary query and data work](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/cost-optimization): Measure useful work before changing schema, limits or retention.
- [Keep a focused SQL debugging record](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/debugging-insights): Capture the smallest failing case, exact request and relevant observations.
- [Choose a view or a report table](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/materialized-views): Make report freshness explicit when stored results are maintained by an application.
- [Optimize a measured reader task](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/performance-optimization): Verify results and use query plans before selecting indexes or limits.
- [Write a reproducible workload result](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/success-stories): Describe observed improvements with public tasks and verifiable measurements.
- [Improve a workload with many small writes](https://coordinatordb.com/docs/resources/support-center/tips-and-tricks/too-many-parts): Batch related input deliberately without relying on part-merge tuning.
- [Troubleshooting overview](https://coordinatordb.com/docs/resources/support-center/troubleshooting): Choose a focused diagnostic path for connection, SQL and ingestion errors.
- [Build a reproducible diagnostic case](https://coordinatordb.com/docs/resources/support-center/troubleshooting/troubleshooting): Reduce a failure and verify one explanation at a time.

## Optional

- [Sitemap](https://coordinatordb.com/sitemap.xml): Canonical page URLs.