Hi @dev_puli, In Azure Databricks, you can trace the history of table modifications, including the user responsible and the timestamp.
Here’s how you can achieve this:
Delta Lake Table History:
Comparison and Deployment:
Workspace Files and Notebooks:
Remember to adapt these steps based on your specific use case and requirements.
By leveraging Delta Lake history and workspace file details, you can gain insights into modifications and compare performance effectively. 🚀
Thanks for your response! I used "describe history table_name" before as you specified above. I am fairly new to Databricks. Can you provide more insights about the workflow? How to trace the history of a workflow like tracing the history of a table(using a command like describe) or a notebook (using git options)? I am not sure of the possibilities of deploying the workflows from lower environments to higher environments. I had challenges in changing the owner of a workflow when I created a workflow. I ended up in seeking the help from another user with admin privileges to change the owner.
Sorry! I added another issue at the end without mentioning it was a new issue I encountered. I had challenges in changing the owner of a workflow when I created a workflow. I ended up seeking help from another user with admin privileges to change the owner. Is there a way to choose a service principle as the default owner every time a workflow gets created by any user?
Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections.
Click here to register and join today!