> For the complete documentation index, see [llms.txt](https://docs.dwh.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dwh.dev/integrations/snowflake/snowflake-marketplace-native-app/ctas-logic-change-tracking.md). # CTAS logic change tracking {% embed url="" %} DWH.dev tracks logical changes in `CREATE TABLE AS SELECT` (CTAS) operations based on data from Snowflake’s `QUERY_HISTORY`.\ For every CTAS statement, the corresponding target object is identified, and its `query_hash` — the unique identifier of the compiled query generated by Snowflake — is extracted. If the current `query_hash` differs from the previously stored one, DWH.dev flags this as a **CTAS logic change** and automatically recalculates all dependent lineage relationships.\ This means that even when the table name remains unchanged, any modification in the SQL logic (such as added columns, altered joins, filters, or expressions) is immediately reflected in the lineage graph. #### Used for * Tracking the evolution of transformation logic over time. * Auditing business-logic changes without manually comparing SQL code. * Automatically updating lineage whenever CTAS logic changes. * Preventing silent downstream inconsistencies caused by logic drift. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dwh.dev/integrations/snowflake/snowflake-marketplace-native-app/ctas-logic-change-tracking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.