Discover how to use RisingWave Console’s SQL Console to query your RisingWave data, explore schemas, view query history, and visualize streaming data flows.
RisingWave Console includes a powerful, web-based SQL Console that allows you to directly interact with the databases within your connected RisingWave clusters. You can execute queries, explore your database objects, view query history, and even visualize streaming data flows.
Before you can run queries, you need to tell the SQL Console how to connect to specific databases within your RisingWave instances. This involves defining a “database connection” which uses one of your already configured “cluster connections” (from RisingWave Console’s Clusters section) and adds specific database credentials.
< >
) in the sidebar.Primary App DB
, Analytics User on Prod RW
). This name will help you identify it in the SQL Console.root
, app_user
).dev
, postgres
, rw_db
).The SQL Console has several key areas:
rw (Default Local Cluster)
), this pane allows you to browse your connected RisingWave cluster’s databases, schemas, and objects like tables, views, materialized views (MVs), sources, and sinks. Expanding these items can show columns and their types.CREATE TABLE
) are executed, potentially allowing them to run as background tasks in RisingWave for long-running operations without blocking the console. (Consult RisingWave documentation for specifics on background DDL.)SELECT
queries in a tabular format, or success/error messages for DDL/DML statements.The SQL Console in RisingWave Console provides a convenient and integrated way to interact with your RisingWave data directly from your browser, enhancing your development and operational workflows.
Discover how to use RisingWave Console’s SQL Console to query your RisingWave data, explore schemas, view query history, and visualize streaming data flows.
RisingWave Console includes a powerful, web-based SQL Console that allows you to directly interact with the databases within your connected RisingWave clusters. You can execute queries, explore your database objects, view query history, and even visualize streaming data flows.
Before you can run queries, you need to tell the SQL Console how to connect to specific databases within your RisingWave instances. This involves defining a “database connection” which uses one of your already configured “cluster connections” (from RisingWave Console’s Clusters section) and adds specific database credentials.
< >
) in the sidebar.Primary App DB
, Analytics User on Prod RW
). This name will help you identify it in the SQL Console.root
, app_user
).dev
, postgres
, rw_db
).The SQL Console has several key areas:
rw (Default Local Cluster)
), this pane allows you to browse your connected RisingWave cluster’s databases, schemas, and objects like tables, views, materialized views (MVs), sources, and sinks. Expanding these items can show columns and their types.CREATE TABLE
) are executed, potentially allowing them to run as background tasks in RisingWave for long-running operations without blocking the console. (Consult RisingWave documentation for specifics on background DDL.)SELECT
queries in a tabular format, or success/error messages for DDL/DML statements.The SQL Console in RisingWave Console provides a convenient and integrated way to interact with your RisingWave data directly from your browser, enhancing your development and operational workflows.