Hi @data_learner1 ,

Audit logs focus on security and usage monitoring such as user access, table read/write events. They don't track schema level changes.

To track schema level changes, delta transaction logs will be the best to use. The transaction log files are typically stored in a _delta_log directory within the table's root directory. Here is a sample code snippet you can use to query the log files for a table.

df = spark.read.json("/path/to/your/delta/table/_delta_log/*.json")
df.select("commitInfo","metaData").display()

Hope this helps!

@KaranamS : for suppose, i have list of tables in databricks unity catalog, with the read access I wanted to find out if they are doing any renames to the existing tables? how can we do this?

Thank you for your suggestions.

@data_learner1 , Other alternative to track the table renames would be snapshots. You can run 'SHOW TABLES' on a catalog and save the output on daily basis and compare current vs previous to find out dropped or renamed tables

@data_learner1 

Unity Catalog logs all data access and metadata operations (including schema changes) into the audit logs — which are stored in the system catalog tables, such as:

system.access.audit

You mentioned you only have read access — and likely no access to system.access.audit, which is only visible to metastore admins or users with elevated privileges.