Handle schema changes and upgrades
As Zenoti evolves, new columns, new tables, and modified schemas are periodically introduced to the Redshift data warehouse. This article explains how schema changes are managed and what you need to do as a Redshift Data Share customer.
Audience: Analytics engineers and BI developers who maintain queries, reports, or data pipelines against Zenoti's Redshift Data Share.
On this page
- How schema changes work
- What Zenoti may change in an upgrade
- Schema versioning
- Backward compatibility
- New table onboarding
- What you should do
- Quick reference
- Tips
- Troubleshooting
Before you begin
- You must have an active Redshift Data Share connection provisioned by Zenoti.
- Read access to the Redshift cluster is required to query the system catalog for new tables.
- No special permissions or DDL access are required — schema changes are applied by Zenoti, not by you.
How schema changes work
Unlike S3 Data Share (where you must apply schema changes to your own warehouse), Redshift Data Share schema changes are applied automatically by Zenoti. When Zenoti releases a schema update, the changes are applied directly to the Redshift cluster during a processing cycle. You do not need to run any DDL commands or alter tables yourself.
This means:
- New columns appear automatically in your queries after the next data refresh.
- New tables appear automatically and begin populating with data.
- Column type adjustments (rare) are applied without customer intervention.
What Zenoti may change in an upgrade
| Change type | Description | Impact on your queries |
|---|---|---|
| New columns on existing tables | Additional attributes added to a fact or dimension table | No impact — existing queries continue to work. New columns are available for use in future queries. |
| New tables | Entirely new fact, dimension, or consolidated tables for new subject areas | No impact — new tables are available alongside existing ones. |
| Data type changes | Column precision or type adjustments (rare) | Minimal impact — typically widening a column or increasing precision. |
Zenoti does not remove or rename existing columns during normal upgrades. This means your existing queries, reports, and integrations remain stable when new columns or tables are added.
Schema versioning
Zenoti maintains versioned schemas for the data warehouse. Each release that introduces schema changes is tracked internally. When a new schema version is deployed:
- The Redshift table definitions are updated during a processing cycle.
- The next data refresh populates any new columns with values.
- New tables (if any) begin receiving data from the next full or incremental load.
You do not need to track schema versions yourself. The changes take effect automatically.
Backward compatibility
Zenoti follows these principles for schema changes:
- Column names are kept stable. Existing columns are not renamed or removed.
- New columns are added, not substituted. If a new attribute is introduced, it is added as a new column rather than replacing an existing one.
- Existing queries continue to work. Because columns are only added (never removed or renamed), queries that reference existing columns are not affected by upgrades.
After a schema upgrade, new columns may initially contain NULL values for historical rows until the next data refresh cycle populates them.
New table onboarding
When Zenoti adds an entirely new table to the data warehouse:
- The new table is created in the Redshift cluster by Zenoti engineering.
- An initial data load populates the table with historical data (where applicable).
- Subsequent data refresh cycles keep the new table updated incrementally.
New tables appear automatically in your Redshift Data Share. You can discover them by querying the Redshift system catalog or by reviewing Zenoti release notes.
Note: Some new tables may not yet be populated for all organizations immediately after release. Data availability depends on whether your organization uses the corresponding Zenoti feature.
What you should do
Although schema changes are applied automatically, there are a few actions to take on your side:
Review Zenoti release notes when notified of a new release. Release notes describe any schema changes, including new columns, new tables, and changes to existing columns.
Update your queries and reports if new columns are relevant to your reporting needs. New columns are available immediately after the upgrade but are not automatically included in existing queries that use explicit column lists.
Check for new tables that may be useful for your business. New fact, dimension, or consolidated tables expand the range of reports you can build.
Update downstream integrations if you have automated pipelines that depend on a specific column list. Adding new columns to your
SELECTstatements or adjusting ETL logic in your downstream systems ensures you benefit from the new data.
Quick reference
| Question | Answer |
|---|---|
| Do I need to run DDL commands? | No — Zenoti applies schema changes automatically. |
| Will my existing queries break? | No — columns are only added, never removed or renamed. |
| When do new columns get data? | After the next data refresh cycle following the upgrade. |
| How do I discover new tables? | Review Zenoti release notes or query the Redshift system catalog. |
| What if a new column is NULL? | This is expected for historical rows until the next refresh populates values. |
Tips
- Use
SELECT *sparingly in production queries. While it will automatically include new columns after an upgrade, unexpected additional columns can break downstream consumers that expect a fixed column count or order. Prefer explicit column lists and update them intentionally when new columns are relevant. - Subscribe to Zenoti release notes. Schema changes are announced in release notes before they are deployed. Reviewing these in advance gives you time to update queries, reports, and pipelines before the upgrade takes effect.
- Test against the Redshift system catalog after each release. Running a query against the system catalog to compare the current column list on key tables against your documented baseline is a reliable way to detect schema additions early.
Troubleshooting
A column I expected to find is not appearing in query results.
New columns are added during a processing cycle and populated during the subsequent data refresh. If a release was recently deployed, wait for the next data refresh cycle (approximately every 1–2 hours) and re-run your query. If the column still does not appear after a full refresh cycle, contact Zenoti Support.
A new column is returning NULL for all historical rows.
This is expected behavior. When a new column is added to an existing table, historical rows do not have values for that column until the next data refresh cycle processes them. After the next incremental load completes, historical rows will be backfilled where applicable.
A query that previously worked is now returning an error after an upgrade.
Schema changes in Redshift Data Share are additive — columns are never removed or renamed. If a query is failing after an upgrade, verify that the column names referenced in your query match the current table definition. Check Zenoti release notes for any data type changes that may affect how your BI tool processes the column. If the issue persists, contact Zenoti Support with the query and the error message.