![WellDatabase-Rect-1000x159-1.png]](https://support.welldatabase.com/hs-fs/hubfs/WellDatabase-Rect-1000x159-1.png?height=40&name=WellDatabase-Rect-1000x159-1.png){kind=small}
What is the difference between Header and Well tables in Snowflake?
Understand how legacy Header tables relate to standardized Well table naming in Snowflake and why both currently exist.
To improve naming consistency between Snowflake record types, certain legacy table names are being standardized across Snowflake, the API, and platform terminology.
Standardized Table Naming
| Legacy Table | Standardized Table |
|---|---|
| Header | Well |
| HeaderLocation | WellLocation |
Compatibility Note
Existing Header and HeaderLocation tables will continue to be maintained for compatibility with current workflows and integrations. No immediate action is required for existing queries or development work.
Recommended Approach
For new Snowflake development work, WellDatabase recommends using:
WellWellLocation
Frequently Asked Questions
Q: Why is this change being made?
A: The Snowflake database uses Well-based naming conventions across related record types and datasets. Standardizing legacy Header naming improves consistency between Snowflake, the API, and platform terminology.
Q: Are the Header and Well tables different datasets?
A: No. These tables represent the same underlying well record structures using updated naming conventions.
Q: Will the API naming change from Wells to Well?
A: No. Existing API naming will remain unchanged.
Explore additional articles by searching the topics on the left. If you have any questions, feel free to email support@welldatabase.com