Skip to main content

​
SQL Studio

SQL Studio is Collate’s integrated query execution environment that lets you run SQL queries directly against your configured database services. With SQL Studio, explore data, validate queries, and perform ad-hoc analysis without leaving the Collate platform.

​
What is SQL Studio?

SQL Studio provides a unified interface for executing SQL queries across multiple database services from within Collate. It eliminates the need to switch between different database clients and provides a consistent experience regardless of which database you’re querying.

​
Key Features

SQL Studio provides the following core capabilities:
  • Multi-Service Support: Execute queries across multiple database services from a unified interface.
  • Database Selection: Choose which ingested database a query runs against from the query toolbar.
  • SELECT Query Execution: Run SELECT queries and view results in the studio for different services in a single place.
  • Secure Authentication: Multiple authentication methods with encrypted credential storage.
  • Query Management: Save, organize, and reuse frequently-used queries.

​
How SQL Studio Works

SQL Studio follows a four-step workflow:
  1. Install the Application: Admins install the SQL Studio (Query Runner) application from the App Marketplace
  2. Configure Services: Admins configure SQL Studio for each database service and set authentication methods
  3. Authenticate: Users connect to services using the configured authentication method
  4. Execute Queries: Users write and run SQL queries, save queries, and explore data

​
Supported Database Services

SQL Studio currently supports:
  • BigQuery
  • Snowflake
  • Trino (Starburst)
  • Redshift
  • PostgreSQL
  • MSSQL
  • MySQL
  • Athena
  • Databricks
  • Unity Catalog
Each service supports different authentication methods and has service-specific configuration options. See Admin Configuration for detailed setup instructions.

​
Authentication Options per Service

AWS Identity and Access Management (IAM) authenticates connections to Athena, Redshift, and PostgreSQL.

​
Authentication Methods

SQL Studio supports four authentication methods for most services, each designed for different use cases. Databricks and Unity Catalog use a Personal Access Token or a Service Principal instead:

​
How to Configure Authentication Methods

​
Basic Authentication

Best for: Service accounts, automated access, or when OAuth is not available Basic Authentication lets you provide direct credentials such as Username + Password or Service Account fields. How it works: Admin Setup:
  • Admin selects authentication type as “Basic” in the database service configuration
  • Admin saves the configuration
User Connection:
  • Users enter their own credentials in SQL Studio
  • Credentials are encrypted and stored securely
  • Credentials remain valid until manually changed by the user
Supported services:
  • BigQuery (GCP Service Account fields)
  • Snowflake (Username + Password OR Username + Key Pair)
  • Trino (Username + Password)
  • Redshift (Username + Password)
  • PostgreSQL (Username + Password)
  • MSSQL (Username + Password)
  • MySQL (Username + Password)
Admin setup: Admins enable Basic Auth mode - users provide their own credentials.

​
External OAuth

Best for: Organizations that want OAuth authentication but use a different SSO provider or email & password for Collate login External OAuth lets you authenticate directly with the database service provider (Google (for BigQuery), Snowflake, Starburst (for Trino)) using OAuth 2.0, separate from their Collate login. How it works: Admin Setup:
  • Admin fills in the OAuth configuration fields:
    • Client ID (required)
    • Client Secret (required)
    • Redirect URL (optional)
    • Scope (optional)
  • Admin saves the configuration
User Connection:
  • Users click “Connect” in SQL Studio for the configured database service
  • Users are redirected to the database provider’s authentication page (Google for BigQuery, Snowflake for Snowflake, Azure AD for Trino)
  • Users authenticate with their database provider credentials
  • Access token exchange happens automatically
  • OAuth tokens are securely stored and used for query execution
Supported services:
  • BigQuery (Google OAuth)
  • Snowflake (Snowflake Security Integration - Custom OAuth)
  • Trino (Starburst OAuth Client)
Admin setup: Admins must configure OAuth client credentials (Client ID, Client Secret) for each service.

​
Collate SSO

Best for: Organizations using Google OIDC for Collate login Collate SSO uses your existing Google SSO configuration in Collate to authenticate with database services. Instead of configuring separate OAuth credentials, SQL Studio automatically uses already configured fields from Collate login. How it works: Admin Setup:
  • Admin selects authentication type as “Collate SSO” in the database service configuration
  • Fields in the UI (Client ID, Client Secret, Scope) are optional and not mandatory to fill
  • Once the admin saves the form, these fields are automatically prefetched from Collate’s SSO settings
  • Admin can then view the auto-enriched values
User Connection:
  • Users click “Connect” in SQL Studio for the configured database service
  • A popup opens for users to allow/grant permissions defined in the scope (e.g., BigQuery access)
  • OAuth tokens are securely fetched, stored, and automatically used for query execution
  • No additional credential entry required from users or admin
Tip: SSO Support: As of now, Collate SSO flow is only supported for Google OIDC (OpenID Connect).
Supported services:
  • BigQuery (with Google Workspace SSO)
Admin setup: Minimal or no configuration required - OAuth credentials (Client ID, Client Secret, Scope) are automatically pulled from Collate’s SSO settings.

​
AWS IAM

AWS IAM connections use your AWS credentials or an assumed role to authenticate with Athena, Redshift, or PostgreSQL. For more information, see AWS IAM for Redshift and PostgreSQL and Athena Configuration. For more information, see AWS IAM Authentication.

​
Getting Started

Ready to start using SQL Studio? Follow these guides:

​
Next Steps