cancel
Showing results for 
Search instead for 
Did you mean: 
Administration & Architecture
Explore discussions on Databricks administration, deployment strategies, and architectural best practices. Connect with administrators and architects to optimize your Databricks environment for performance, scalability, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

Enable Predictive optimization

AnkurMittal008
New Contributor II

 In case to use predictive optimization we should first enable this at account level ? If this is the case then by doing this each of the catalogue/schema/table in Account will start using predictive optimization by default? should we first disable this for list of catalogues where we do not want this to be used using "ALTER CATALOG [catalog_name] DISABLE PREDICTIVE OPTIMIZATION;"" before enabling at Account level ? 

1 REPLY 1

SparkJun
Databricks Employee
Databricks Employee

Yes, you must enable predictive optimization at the account level. Once enabled, predictive optimization will be applied by default to all catalogs, schemas, and tables within the account. To prevent predictive optimization from being applied to specific catalogs, you should disable it for those catalogs before enabling it at the account level. You can do this using the following command:

ALTER CATALOG [catalog_name] DISABLE PREDICTIVE OPTIMIZATION;
This way, when you enable predictive optimization at the account level, it will not be applied to the catalogs where you have explicitly disabled it.
 

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group