Duplicated storage location

[juanjomendez96]

Hello there!

After a year working with Databricks, we have found that we could improve our catalog and schemas organization, so we would like to perform a 'migration' process where we move tables, volumes, models, etc from one catalog to another.

The problem here is that we want to keep the old catalog storage connections during the process (for legacy purposes), and as far as we know, it seems that Databricks does not support this.

So I was wondering if anyone from the community has any idea how can we approach this.

Note that we have a plan for moving tables, models and functions, and also the new catalog organization is already defined. Our only problem is to have duplicated storage location in different catalogs.

Thanks in advance guys!

[-werners- · Accepted solution]

It is not possible to have overlap within/between catalogs.
So you should make sure that any path you define in your catalogs/schemas/tables isn´t already used in the old UC.

[WiliamRosa · Accepted solution]

Hi @-werners- 
Exactly, “It is not possible to have overlap within/between catalogs.” I’m sharing below the official documentation that confirms this behavior:
https://docs.databricks.com/aws/en/volumes/paths