ZenotiHelp

Analytics — Redshift data share FAQ

ZTZenoti Docs Team Updated October 7, 2026 9 min readFAQ

Find answers to common questions about Analytics -- Redshift Data Share.


Index

  1. What is Redshift Data Share?
  2. What license do I need?
  3. How is Redshift Data Share different from S3 Data Share?
  4. How do I connect to the Redshift cluster?
  5. What tables are available?
  6. What are dimension, fact, and consolidated tables?
  7. What is a WID column and how do I use it?
  8. How often is data refreshed?
  9. How do I check when data was last updated?
  10. What is the void column?
  11. How do I filter data by my organization or center?
  12. What are ETL metadata columns?
  13. Can I write data back to the data warehouse?
  14. What happens during a schema upgrade?
  15. What should I do if data appears stale?
  16. What is a monthly snapshot?
  17. Do I need to handle incremental loads?
  18. What SQL clients can I use?
  19. Where can I find column-level table schemas?
  20. What is the difference between a shared and dedicated cluster?

1. What is Redshift Data Share?

Redshift Data Share is a Zenoti analytics delivery mechanism that provides direct SQL query access to a data warehouse hosted on Amazon Redshift. The data warehouse contains a star schema with dimension tables, fact tables, and consolidated tables covering your Zenoti business data -- appointments, sales, employees, memberships, inventory, marketing, and more.

With Redshift Data Share, you connect a SQL client or BI tool directly to the Redshift cluster and run standard SQL queries against your data. There is no need to export, download, or stage files.


2. What license do I need?

You need an Analytics Plus subscription with the Redshift Data Share add-on enabled. Redshift Data Share is a paid add-on that must be activated by Zenoti. Contact your Zenoti account representative to confirm your entitlements or to add Redshift Data Share to your plan.


3. How is Redshift Data Share different from S3 Data Share?

Both products use the same underlying data warehouse with identical table schemas. The difference is in how you access the data:

Feature Redshift Data Share S3 Data Share
Access method SQL queries via a Redshift client Read CSV files from your S3 bucket
Query capability Run SQL directly against the data Load CSVs into your own warehouse first
Schema management Automatic -- Zenoti applies changes Manual -- you apply schema upgrades yourself
Infrastructure Zenoti-managed Redshift cluster Your own S3 bucket
Best for Teams that want direct SQL access without managing infrastructure Teams that want full control over their data warehouse

Table schemas, column names, and data content are identical between Redshift Data Share and S3 Data Share. Per-table column reference documentation applies to both products.


4. How do I connect to the Redshift cluster?

During onboarding, Zenoti provides you with:

  • Cluster endpoint (host and port)
  • Database name
  • Username and password

Use these credentials in any SQL client or BI tool that supports Amazon Redshift connections (JDBC or ODBC). Common tools include Tableau, Power BI, DBeaver, and the Amazon Redshift Query Editor.

See Query Redshift Data with SQL for connection guidance by tool.


5. What tables are available?

The data warehouse includes three kinds of tables:

  • Dimension tables -- reference data for centers, employees, services, guests, products, memberships, packages, and more
  • Fact tables -- transactional data for appointments, invoices, commissions, memberships, packages, gift cards, campaigns, inventory, and more
  • Consolidated tables -- pre-joined versions of the most commonly used subject areas

Coverage spans appointments, sales, employee commissions, memberships, packages, gift cards, marketing campaigns, inventory, guest personas, daily traffic, and more. The full list of tables, with their columns, is in the Analytics — Amazon S3 table reference pages, which apply to Redshift Data Share as well -- see question 19.


6. What are dimension, fact, and consolidated tables?

The data warehouse uses a star schema design with three types of tables:

  • Dimension tables (Bi_Dim* prefix) contain descriptive attributes. Examples: Bi_DimCenter, Bi_DimEmployee, Bi_DimService. Dimension tables are the "who, what, where" of your data.

  • Fact tables (Bi_Fact* prefix) contain measurable events and transactions. Examples: Bi_FactAppointment, Bi_FactInvoiceItem, Bi_FactEmployeeCommission. Fact tables are the "how much, how many, when" of your data. They connect to dimension tables via WID surrogate key columns.

  • Consolidated tables are pre-joined tables that combine fact and dimension data into a single flat structure, named by subject. Examples: Sales_Fact_Consolidated, Appointment_Fact_Consolidated. They contain the same data as the corresponding star schema tables but do not require JOIN statements, making queries simpler.


7. What is a WID column and how do I use it?

WID stands for Warehouse ID. It is a surrogate key -- an auto-generated integer used as the primary key in all dimension and fact tables. WID columns are the designated join keys between fact and dimension tables.

For example, Bi_FactAppointment.centerwid joins to Bi_DimCenter.centerwid. The WID is not the same as the natural business key (such as a center code or employee GUID). Natural keys are preserved in separate columns for cross-referencing with the source Zenoti system.

-- Join using WID columns
SELECT f.*, c.CenterName
FROM Bi_FactAppointment f
JOIN Bi_DimCenter c ON f.centerwid = c.centerwid
WHERE f.void = 0 AND c.void = 0;

Always use WID columns for joins. They are optimized for query performance in the star schema.


8. How often is data refreshed?

Data is refreshed approximately every 1 to 2 hours through incremental data refresh cycles. The exact timing depends on data volume and processing conditions. This is not a fixed schedule -- it is an approximate cadence.

During each refresh cycle, only records that were created, updated, or deleted since the previous cycle are processed. This keeps the data warehouse current without reprocessing the entire data set.


9. How do I check when data was last updated?

Query the table's load or update timestamp. Fact tables usually carry etlCreatedDate, and dimension tables usually carry EtlLastUpdatedOn:

SELECT MAX(etlCreatedDate) AS last_load
FROM Bi_FactAppointment;

You can also check the Bi_DimETLRefreshLog table, which records when data was last refreshed for each center and organization:

SELECT *
FROM Bi_DimETLRefreshLog
ORDER BY EtlLastUpdatedOn DESC
LIMIT 10;

10. What is the void column?

The void column is a soft-delete flag present in dimension tables. It indicates whether a record is active or has been deleted:

void value Meaning
0 Active, current record
Non-zero Deleted or voided record

Always filter WHERE void = 0 in your queries to return only active records. Omitting this filter may cause inflated counts or include records that no longer exist in the source system.

Fact tables use a delete-insert pattern for data updates: deleted and updated records are removed from the table, and new or updated records are inserted.


11. How do I filter data by my organization or center?

Every table includes an organizationid column (a GUID identifying your organization). If your data share is scoped to a single organization, all records already belong to you. If your data share includes multiple organizations or you want to filter by center, use these patterns:

-- Filter by organization
SELECT * FROM Bi_FactAppointment
WHERE organizationid = 'your-org-guid' AND void = 0;

-- Filter by center (join to Bi_DimCenter)
SELECT f.*
FROM Bi_FactAppointment f
JOIN Bi_DimCenter c ON f.centerwid = c.centerwid
WHERE c.CenterName = 'Downtown Spa'
  AND f.void = 0
  AND c.void = 0;

Data can be scoped at three levels: organization, zone, or center. Each scope level creates a separate data share endpoint. Contact your Zenoti Implementation team if you are unsure of your subscription scope.


12. What are ETL metadata columns?

Most tables include some standard metadata columns used for tracking data freshness and multi-tenant isolation:

Column Description
podname Source identifier for the data origin
organizationid Organization GUID for multi-tenant filtering
groupid Tenant/group identifier in multi-tenant deployments
etlCreatedDate Timestamp when the record was first created by the data pipeline
EtlLastUpdatedOn Timestamp of the most recent update to the record

Which of these columns a table has varies: dimension tables usually carry EtlLastUpdatedOn, and fact tables usually carry etlCreatedDate. Check the table's column reference -- see question 19 -- before you rely on one. Use the timestamp the table carries to check data freshness, and organizationid for multi-tenant filtering.


13. Can I write data back to the data warehouse?

No. The Redshift Data Share is read-only. You can query and read data, but you cannot insert, update, delete, or create objects in the data warehouse. All data is managed and refreshed by Zenoti through automated data processing pipelines.


14. What happens during a schema upgrade?

Schema changes (new columns, new tables, type adjustments) are applied automatically by Zenoti to the Redshift cluster. You do not need to run any DDL commands. Your existing queries continue to work because Zenoti does not remove or rename existing columns during normal upgrades.

After an upgrade:

  • New columns appear in your queries and may initially contain NULL for historical rows.
  • New tables appear and begin populating with data.
  • Review Zenoti release notes to learn about new columns or tables you may want to use.

See Handle Schema Changes and Upgrades for more detail.


15. What should I do if data appears stale?

If your data looks outdated:

  1. Check the last load timestamp by querying MAX(etlCreatedDate) on your primary fact table.
  2. Check Bi_DimETLRefreshLog to see whether recent refresh cycles completed for your organization.
  3. Allow up to 2 hours between refresh cycles during normal operation. Slight delays are normal during periods of high data volume.
  4. Contact Zenoti Support if data has not been refreshed for 6 or more hours. Provide the latest timestamp you can see and the table you checked.

See Troubleshoot Redshift Data Issues for a detailed troubleshooting guide.


16. What is a monthly snapshot?

A monthly snapshot is a point-in-time copy of the data warehouse state, preserved for historical comparison. Snapshots allow you to compare data across periods -- for example, comparing membership counts at the end of March versus April.

Monthly snapshots are generated automatically by Zenoti on a scheduled basis.


17. Do I need to handle incremental loads?

No. With Redshift Data Share, incremental data processing is handled entirely by Zenoti. Each refresh cycle automatically processes only records that changed since the previous cycle and updates the Redshift data warehouse in place. You always query the current state of the data.

This is a key difference from S3 Data Share, where you must manage incremental file loading yourself.


18. What SQL clients can I use?

Any SQL client or BI tool that supports Amazon Redshift connections is compatible. Common options include:

  • Tableau -- Amazon Redshift connector
  • Power BI -- Amazon Redshift connector
  • DBeaver -- Redshift connection type
  • Amazon Redshift Query Editor -- Browser-based, accessed from the AWS console
  • DataGrip -- Redshift data source
  • SQL Workbench/J -- JDBC connection to Redshift
  • Python (psycopg2, SQLAlchemy, redshift_connector) -- Programmatic access

See Query Redshift Data with SQL for connection guidance.


19. Where can I find column-level table schemas?

Per-table column reference articles are maintained in one place, the table reference in the Analytics — Amazon S3 section of the help site. Start from the consolidated tables reference or the dimension and fact table references it sits beside. These references apply to both Redshift Data Share and S3 Data Share, since both products share the same table schemas.

You can also discover table structures directly in Redshift by querying the system catalog:

-- List all columns for a specific table
SELECT column_name, data_type
FROM information_schema.columns
WHERE table_name = 'bi_dimcenter'
ORDER BY ordinal_position;

20. What is the difference between a shared and dedicated cluster?

Zenoti offers two Redshift cluster options:

  • Shared cluster: Your data resides on a Redshift cluster shared with other Zenoti customers. Data is isolated by organization -- you can only query your own data. This is the default option.

  • Dedicated cluster: Your data resides on a Redshift cluster provisioned exclusively for your organization. This provides isolated compute resources and may be recommended for organizations with large data volumes or specific compliance requirements.

Both cluster types use the same star schema, the same table structures, and the same data refresh process. The data content and query experience are identical. The choice between shared and dedicated is typically made during onboarding based on your organization's needs.

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