Telemetry Update: New kbc_sql_workspace Table

What's changing

We migrated SQL Workspaces to a new underlying service. As a result, kbc_workspace no longer receives new data for SQL Workspaces and will be deprecated in the future. Going forward, it will be updated only with Data Science and Data Apps workspaces until it is fully replaced. We will communicate both the deprecation timeline and the replacement details in the coming days.

For a full description of the new kbc_sql_workspace table and its columns, please refer to the documentation.

Columns not included in the new table

Some columns from kbc_workspace are not present in kbc_sql_workspace. These columns either are not yet supported by the new underlying service, or did not provide meaningful analytical value for SQL Workspaces:

• workspace_user — always a system user, not a real person; does not represent a meaningful actor
• workspace_active — reflects the state at the time of extraction from the backend database, but on our side it takes several hours before this data becomes available to users, making it an unreliable indicator
• workspace_hostname — a generic Snowflake URL associated with the project; in multi-tenant environments, it is the same for all workspaces within a stack and is typically identical across the entire organization. It does not change over time and does not provide any additional analytical value
• workspace_expire_hours — a platform-level setting that is not configurable or influenced by the user, not meaningful for SQL Workspaces
• workspace_start — a timestamp that differs from workspace_created by only a few seconds, effectively redundant

Need help migrating?

If you have kbc_workspace linked in existing pipelines and need help relinking to kbc_sql_workspace, Kai can assist you with the transition.

We believe the new kbc_sql_workspace table will provide a more reliable and focused data source for your SQL Workspace analytics.