ZenotiHelp

Get started with Redshift data share

ZTZenoti Docs Team Updated October 7, 2026 3 min readGuide

This article walks you through the prerequisites, first connection, and initial steps for querying your Analytics β€” Redshift Data Share data warehouse.

What you need before you start

Before you can connect and run queries, confirm the following:

  • Analytics Plus license β€” your Zenoti organization must have an active Analytics Plus license
  • Redshift Data Share add-on β€” this paid add-on must be enabled by Zenoti for your organization; contact your Zenoti account representative to request it
  • Cluster credentials β€” during onboarding, the Zenoti Implementation team provisions your Redshift cluster access and provides a host endpoint, port, database name, username, and password
  • SQL client β€” have a SQL client ready for connecting (for example, DBeaver, Tableau, Power BI, or the Amazon Redshift Query Editor)

Connecting to the Redshift cluster

Once the Zenoti Implementation team has provisioned your access, use the connection details they provided to connect from any SQL client that supports Amazon Redshift.

Connection details you will receive:

Field Description
Host The Redshift cluster endpoint
Port The port number (typically 5439)
Database The database name assigned to your data share
Username Your provisioned username
Password Your provisioned password

Enter these values in your SQL client's connection dialog. Most tools that support PostgreSQL or Amazon Redshift connections will work β€” including DBeaver, Tableau Desktop, Power BI Desktop, and the Amazon Redshift Query Editor in the AWS Console.

Important: Your access is read-only. You can query all tables in the data warehouse, but you cannot create, modify, or delete any data.

Your first query

Once connected, run a simple query to verify that everything is working:

SELECT * FROM Bi_DimCenter LIMIT 10;

This returns the first 10 rows from the center dimension table (Bi_DimCenter), which contains descriptive information about each center in your organization. If you see results, your connection is working correctly.

Understanding what you see

The Redshift Data Share data warehouse uses a star schema design. The tables are organized into three types:

Dimension tables

Dimension tables (prefixed with Bi_Dim) contain descriptive attributes β€” information about centers, guests, employees, services, products, and other business entities. Think of these as the "who, what, where" of your data.

Fact tables

Fact tables (prefixed with Bi_Fact) contain measurable events and transactions β€” appointments, invoices, payments, and other business activities. Think of these as the "what happened and when."

Consolidated tables

Consolidated tables are pre-joined tables that combine fact and dimension data into a single table for simplified querying. They are named by subject β€” for example Sales_Fact_Consolidated β€” and do not require any joins, so you can query them directly for common reporting scenarios. The consolidated tables reference lists them with their columns.

Joining dimensions to facts

Dimension and fact tables are joined using surrogate keys β€” columns ending in wid (Warehouse ID). For example, to connect appointment data with center information, you join centerwid in Bi_FactAppointment to centerwid in Bi_DimCenter.

Each table also contains natural keys (typically GUIDs) that correspond to identifiers in the Zenoti operational system, which you can use for cross-referencing.

The void column

Dimension tables include a void column that acts as a soft-delete flag. A value of 0 means the record is active; a non-zero value means the record has been voided or deleted. Fact tables carry a void column too. Filter on void = 0 when you want only active records.

Data scoping

Depending on how your subscription is configured, your data may be scoped at one of three levels:

Scope What you see
Organization All data across every center in your organization
Zone Data for all centers in a specific zone
Center Data for a single center

If you have an organization-level subscription and want to filter results to a specific center or group of centers, use the organizationid column (present in every table) along with centerwid to narrow your queries.

Data freshness

After your initial onboarding load completes with all historical data, incremental data refreshes run automatically every 1-2 hours. Query results reflect the state of your Zenoti data as of the most recent refresh. You do not need to trigger or schedule refreshes β€” they happen automatically.

Next steps

Was this article helpful?
Your feedback helps us improve our documentation.