Hi @szymon_dybczak 

Yes on dedicated access mode it works fine, because we have access to /databricks/native/proj-data. From a cost perspective we want to stay on standard/shared cluster.

Pushing proj.db to UC volume and change the environment path is what I meant with hack/workaround 1. 

I still do not get it why the "proj-data" is in a path, where we have no "read" access from a standard cluster?