Skip to main content
A SQL Workspace is a managed environment for processing StreamNative streams with SQL. It owns the lifecycle and placement of a SQL Workspace engine and provides endpoints for SQL Studio and native PostgreSQL clients.

​
Engine

During Private Preview, every SQL Workspace uses RisingWave. You cannot select a different engine.

​
What a workspace contains

A SQL Workspace contains:
  • One managed SQL Workspace engine.
  • Zero or more SQL Catalog databases.
  • Managed source objects created for eligible topics within those databases.
  • SQL Studio and native PostgreSQL query paths.

​
Placement

When you create a workspace, select an eligible AWS hosted location or ready AWS BYOC Cloud Environment. The Cloud Console displays only placements available to your organization during Private Preview. During Private Preview, SQL Workspaces are supported only on AWS. Other cloud providers are not currently supported.

​
Lifecycle

A workspace must reach Ready before you can open SQL Studio, connect through the native endpoint, or use its catalogs. You can add SQL Catalogs during creation or after the workspace is ready. Before deleting a workspace, remove its SQL Catalog resources. Deleting a workspace removes the managed SQL runtime and makes its query endpoints unavailable, but workspace data is retained by default. It does not delete any connected Pulsar or Kafka cluster. See Data Retention.

​
Access

Cloud roles control who can manage the SQL Workspace resource. Engine permissions control what a user can do inside the workspace. During Private Preview, Organization Admin users can administer the engine. For details, see Access control overview.