ManojkMohan
Honored Contributor II

@donlxz 

Try improving the JDBC URL like 

jdbc:databricks://adb-1234567890123456.7.azuredatabricks.net:443/my_schema;
HttpPath=/sql/1.0/endpoints/abcd1234;
AuthMech=3;
UID=myuser;
PWD=mypassword;
Catalog=my_catalog;
Schema=my_schema;
RetryCount=5;
RetryInterval=2000;

On data bricks side

Workload design Separate concurrent ETL jobs into different schemas or catalogs Prevents two jobs from contending for locks on the same schema

ManojkMohan_0-1760633900284.png

SQL design best practice Use fully qualified table names instead of relying on USE Eliminates the need for schema context switching

ManojkMohan_1-1760634022800.png

Monitoring and troubleshooting Track queries causing deadlocks using Databricks system tables Helps identify which workflow/session caused the lock

ManojkMohan_2-1760634164823.png

Cache meta data as best practise

ManojkMohan_3-1760634260341.png

 

 

 

 

View solution in original post