Databricks Query History

Share

           Databricks Query History

Databricks provides several ways to access and manage your query history:

1. Query History UI

  • Location: Click “Query History” in the sidebar of your Databricks workspace.
    • Features: View a list of executed SQL queries.
    • Sort by duration, start time, or other criteria.
    • Filter by user, date range, SQL warehouse, and query status.
    • Click on a query to see detailed information (SQL command, execution time, resources used).
  • Benefits: Easy to use, provides a quick overview of your query history.

2. Query History API

3. Serverless Compute Query History

  • Availability: If your workspace is enabled for serverless computing.
  • Features: Includes both SQL and Python queries run in notebooks and jobs.
  • Benefits: Comprehensive view of query history across different execution environments.

4. Table Access Control (TAC) Logs

  • Location: “DatabricksTableAccessControl” log table.
  • Features: Tracks table usage and access.
  • Benefits: It provides insights into how tables are used and who is accessing them.

Retention Period

Query history data is typically retained for 30 days and then automatically deleted.

Databricks Training Demo Day 1 Video:

 
You can find more information about Databricks Training in this Dtabricks Docs Link

 

Conclusion:

Unogeeks is the No.1 IT Training Institute for Databricks Training. Anyone Disagree? Please drop in a comment

You can check out our other latest blogs on Databricks Training here – Databricks Blogs

Please check out our Best In Class Databricks Training Details here – Databricks Training

 Follow & Connect with us:

———————————-

For Training inquiries:

Call/Whatsapp: +91 73960 33555

Mail us at: info@unogeeks.com

Our Website ➜ https://unogeeks.com

Follow us:

Instagram: https://www.instagram.com/unogeeks

Facebook:https://www.facebook.com/UnogeeksSoftwareTrainingInstitute

Twitter: https://twitter.com/unogeeks


Share

Leave a Reply

Your email address will not be published. Required fields are marked *