Analytics β Redshift Data Share overview
Analytics β Redshift Data Share is Zenoti's direct SQL query access to the business intelligence data warehouse. With Redshift Data Share, you connect any SQL-compatible BI tool (such as Tableau, Power BI, DBeaver, or a custom application) directly to an Amazon Redshift cluster and run queries against your organization's analytics data in real time.
On this page
- What is Redshift Data Share
- Before you begin
- How it works
- Redshift Data Share vs S3 Data Share
- What data is available
- Data scoping
- Star schema data model
- Related articles
What is Redshift Data Share
Redshift Data Share gives you a live SQL connection to the Zenoti analytics data warehouse. Unlike file-based delivery, you do not download or manage data files. Instead, you connect your BI tool to a Redshift endpoint provided by Zenoti and query the data directly using standard SQL.
The data warehouse contains a complete star schema of your business data, refreshed approximately every 1β2 hours with incremental updates from your Zenoti operational system. You can query dimension tables, fact tables, and pre-joined consolidated tables to build reports, dashboards, and custom analytics.
All data is read-only. You cannot modify, insert, or delete records in the data warehouse.
Before you begin
Verify the following before connecting a BI tool to Redshift Data Share.
| Prerequisite | Why it matters |
|---|---|
| Analytics Plus tier enabled for your organization | Required for all Zenoti analytics features, including Redshift Data Share. Zenoti sets this tier at the organization level β it is not a setting you configure yourself. |
| Redshift Data Share add-on enabled by Zenoti | A paid add-on that must be provisioned by your Zenoti account representative; it is not self-serve. |
| Cluster access credentials | Zenoti provisions a Redshift endpoint, database name, user, and password during onboarding. Without these, your BI tool cannot connect. |
| Data scope confirmed (organization / zone / center) | Each scope creates a separate data share endpoint. Confirm the right scope before onboarding because changing scope requires a new subscription. |
Availability: Redshift Data Share requires the Analytics Plus tier, which Zenoti enables at the organization level. It is also a paid add-on that Zenoti provisions separately. There is no in-product page, menu, or toggle to activate it β contact your Zenoti account representative to request access.
Data is read-only; the Redshift Data Share role cannot modify the data warehouse.
How it works
Redshift Data Share is provisioned and managed entirely by Zenoti. There is no configuration page or menu in the Zenoti application for this feature. During onboarding, Zenoti:
- Provisions your access to either a shared cluster or a dedicated cluster, depending on your subscription.
- Creates your Redshift endpoint, database name, username, and password.
- Scopes the data share to your chosen level (organization, zone, or center).
- Delivers your credentials so you can connect a BI tool of your choice.
Once provisioned, data flows from your Zenoti operational system through automated processing stages to the Redshift data warehouse. You do not need to manage, monitor, or interact with this pipeline β Zenoti handles all processing automatically.
At a high level, the pipeline works as follows:
- Extraction β Changed records are identified in the Zenoti operational system based on what has been created, updated, or deleted since the last cycle.
- Transformation β Business logic is applied to structure the data into the star schema format with dimension and fact tables.
- Loading β Transformed data is loaded into the Redshift data warehouse, updating dimension records and inserting new fact records.
- Export β For organizations that also subscribe to S3 Data Share, the same data is exported as CSV files to their S3 bucket.
The pipeline produces:
- A full load during initial onboarding, containing all historical data.
- Incremental updates approximately every 1β2 hours after that, containing only records that have changed since the last cycle.
For organizations with a dedicated Redshift cluster, Zenoti processes data to both the shared and dedicated clusters in parallel, so your dedicated cluster stays current.
See Data freshness and refresh cycles for details on how data refreshes work.
Redshift Data Share vs S3 Data Share
Zenoti offers two data delivery mechanisms that share the same underlying data warehouse. Choose the one that best fits your analytics workflow, or use both.
| Feature | Redshift Data Share | S3 Data Share |
|---|---|---|
| Access method | Direct SQL queries via a Redshift endpoint | CSV files delivered to your Amazon S3 bucket |
| Query language | Standard SQL (Redshift-compatible) | N/A β you load CSV files into your own data platform |
| Data format | Live database tables | CSV files (UTF-8, comma-delimited, no headers) |
| Schema | Star schema with dimension, fact, and consolidated tables | Same star schema, delivered as flat files with schema definitions |
| Data freshness | Approximately every 1β2 hours | Approximately every 1β2 hours |
| Best for | Ad-hoc querying, BI tool connections, real-time dashboards | Loading into your own data warehouse, archival, custom ETL pipelines |
| Infrastructure you manage | BI tool connection only | S3 bucket access, file ingestion pipeline |
Both products deliver the same table schemas and the same data. The table structures, column names, and data types are identical. Per-table column reference documentation is shared between both products and kept in one place β see the consolidated tables reference and the dimension and fact table references linked from Understand the star schema and data model for column-level details.
For S3 Data Share configuration, folder structure, and CSV format details, see the Analytics β Amazon S3 category.
What data is available
The Redshift data warehouse contains three categories of tables:
| Category | Description |
|---|---|
| Dimension tables | Descriptive attributes β names, codes, categories, and reference data for guests, centers, employees, services, products, and more. Prefixed with Bi_Dim*. |
| Fact tables | Measurable events and transactions β sale amounts, appointment counts, payment details, and other numeric metrics. Prefixed with Bi_Fact*. |
| Consolidated tables | Pre-joined combinations of fact and dimension data, ready to query without writing JOIN statements. Named by subject β for example, Sales_Fact_Consolidated. |
These tables cover all major Zenoti business domains:
- Guests and guest profiles
- Centers and locations
- Employees and staff
- Services and appointments
- Products and retail
- Memberships and packages
- Gift cards
- Campaigns and promotions
- Issues and feedback
- Loyalty programs
- Training and classes
- Inventory
Note: Per-table column reference articles β including dimension tables, fact tables, consolidated tables, views, and ETL metadata β are maintained exclusively in the Analytics β Amazon S3 category. Do not look for a separate table reference section in this category.
Data scoping
Your Redshift Data Share subscription can be scoped to one of three levels:
| Scope | What data you receive |
|---|---|
| Organization | All data across all centers in your organization |
| Zone | Data for the centers in a specific zone |
| Center | Data for a single center |
Each scope level creates a separate data share endpoint. If you need data at multiple scope levels, each requires its own subscription. Confirm the right scope with your Zenoti account representative before onboarding, because changing scope requires a new subscription.
Star schema data model
The data warehouse uses a star schema design:
- Fact tables sit at the center and contain measurable events (invoice amounts, appointment durations, membership charges).
- Dimension tables surround the facts and provide descriptive context (guest names, center details, service categories).
- Consolidated tables combine pre-joined fact and dimension data, eliminating the need for complex JOIN queries.
All joins between fact and dimension tables use surrogate keys called WIDs (Warehouse IDs). For example, centerwid in a fact table links to centerwid in Bi_DimCenter.
See Understand the star schema and data model for a full explanation of the data model, WID keys, and how to write join queries.