Connection

A connection manages access to a data warehouse. It uses the credentials you register to run SQL and fetch table information. You can create and edit connections from global nav > Workspace settings > Data management > Connections. To check synced tables, use the catalog.

Key features

• Running SQL: Notebooks, reports, and saved queries can all run SQL using the registered credentials.
• Aggregating metadata: Table metadata sync syncs table schemas and other metadata to the catalog.
• Permissions: Access level and resource roles control who can run SQL and retrieve results. For resource role details, see Connection permissions.
• Supported warehouses: BigQuery / Snowflake / Redshift / Databricks / PostgreSQL.
  • Codatum is adding support for more warehouses over time. To request a connection to a warehouse not listed above, contact Codatum support.
• Demo connection: A sample connection you can use to try the product before setting up your own warehouse.
• Codatum Data Connection: A connection for analyzing AI agent conversation history and usage with SQL.
• Job label: Metadata that identifies where SQL was issued from (added automatically).
• Outbound IP addresses: The fixed IP addresses that Codatum uses to connect to databases for some connections.

Creating and managing connections

1. Open global nav > Workspace settings > Data management > Connections.
2. Select a warehouse from New connection.
3. Enter Connection name, Access level, and the connection settings for the warehouse.
4. Run Test connect to verify connectivity, then select Save.

The list is split into the following sections.

• Available connections: Connections you can use.
• Restricted Connections: Connections you don't have access to. If you can edit permissions, select Edit permissions to grant access.

The maximum number of connections depends on your contract (Limits).

Detail screen

The detail screen lets you check and operate the following.

• View on catalog: Opens the catalog filtered to this connection.
• General: Edit the name and connection options (not available for the demo connection).
• Access level and permissions: Check and edit the access level and resource roles (not available for the demo connection).
• Query jobs: The query job history for this connection (View history / Last run). This is a separate entry point from the Query jobs tab on the table/query detail in the catalog.
• Table sync settings: Last sync job, Sync targets, Resync Immediately, and Sync history. See Table metadata sync for details.
• Danger zone: Delete connection (also deletes related catalog data and saved queries; not available for the demo connection).

The same restrictions apply to Codatum Data Connection: you can't edit General or Access level and permissions, and you can't Delete connection.

Demo connection

The demo connection is a sample connection you can use to try out Codatum's features.

• You can experience Codatum's features before setting up your own warehouse.
• It includes typical business data (sales, customers, products, and so on).
• You can immediately run SQL against the demo connection when creating a notebook or report.

Item	Value
Connection name	Demo Connection
Type	BigQuery
Access level	Workspace
Editing	You can't edit the general settings, sync targets, or access level and permissions
Deletion	You can't delete it

The sync targets are fixed (a sample dataset provided by Codatum and some public BigQuery datasets). You can't change the sync targets manually. You can still run Resync Immediately.

Codatum Data Connection Beta

Codatum Data Connection is a Codatum-managed connection for analyzing AI agent conversation history, tool executions, and token usage with SQL. You can check the views and columns in the catalog, then select this connection in a SQL block or other SQL editor to analyze the data.

INFO

This feature is in beta. The specification might change without notice.

This feature is available when it's enabled for your workspace. Codatum automatically prepares the connection for new workspaces. Once it's ready, users with the required permissions can use it.

If the feature isn't available in an existing workspace, contact Codatum support.

Available views

You can access the following views through this connection.

View	Contents
agent_sessions	Conversation session periods, status, creators, and titles.
agent_turns	Conversation turns from user input to the end of the AI agent's response.
agent_messages	Message types, states, character counts, and whether message content is stored.
agent_tool_executions	Tool approval and execution states, start and end times, and duration.
agent_usage	LLM input and output token counts associated with sessions and conversation turns.
agent_turn_scores	The latest evaluation status and numeric scores per rubric for a conversation turn (task achievement, execution quality, difficulty, and so on).

Message content storage follows the Save conversations to logs setting in the AI profile at the time of execution. For messages whose content isn't stored, the content column doesn't include the message text.

These views don't include columns for the LLM provider name (provider) or model name (model).

Settings and constraints

• You can't edit the general settings, access level and permissions, or sync targets.
• You can't delete it.
• You can run Resync Immediately.
• It doesn't count toward the connection limit.

For the permissions needed to use this connection, see Connection permissions. Fixed constraints are also listed in Limits.

Analytics data coverage

• Execution history from before collection started or while collection was stopped isn't added automatically.
• Past turns, messages, and token usage copied when a conversation is forked aren't recorded as new executions in the fork.
• Collected analytics data remains after the conversation history expires.

Access level

You select the access level when you create a connection. The default is Workspace. Protected and Private might not be available, depending on your contract. For the meaning of each access level and the operations allowed for each resource role, see Connection permissions. You can add up to 3 Connection Owners to a regular connection (Limits).