- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2026 07:40 AM
From time to time i read articles such as here which suggest to use a unity catalog schema management tool. All table schema changes should be applied via this tool.
Usually SPs (or users) have the "Modify" Permission on tables. This allows to them to "update/insert/delete" some data and hence they need it. However, it also allows to update the schema (e.g. add new columns). Hence, such a schema managed tool can be easily bypassed right? I know there are options such as mergeSchema but at the end the visison of "all schema changes can only be done via a schema management tool" is not feasible as long as users have the modify permission.
- Labels:
-
Delta Lake
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2026 07:13 AM
I tend to mostly agree with you. Trying to do table-schema management like I would have done while developing ETL flows in an RDBMS world is quite different from trying to do this in a fast-moving "new-sources-all-the-time" data engineering world.
There have been feature requests from customers to split the MANAGE into a DML vs DDL privilege. If that happens then your "data engineering" user/SP can be given the DML, while another "schema management" SP does the Liquibase-type schema management.
Note: This is more of a confusing overlap in lower environments. In higher environments you would be able to make sure that whatever gets deployed by the "data engineering SP" does not include DDL commands. In lower environments it becomes more of a "monitor and correct" motion to ensure your devs follow the best practice for table-schema management.
~Mohan Mathews.
