"Applies to" label

The SQL reference encompasses both Databricks SQL and Databricks Runtime. It also includes some content that applies only to Unity Catalog. Near the top of each article is a label that indicates which products and versions are supported for that article.

For example, this article applies to all versions for both Databricks SQL and Databricks Runtime:

Applies to: check marked yes Databricks SQL check marked yes Databricks Runtime

In this example, the article applies to all versions of Databricks SQL and Databricks Runtime versions 11.1 and above:

Applies to: check marked yes Databricks SQL check marked yes Databricks Runtime 11.3 LTS and above

In this example, the article just applies to Databricks SQL and is not supported in Databricks Runtime:

Applies to: check marked yes Databricks SQL

In this example, the article applies only Unity Catalog, to all versions of Databricks SQL, and to Databricks Runtime versions 11.1 and above:

Applies to: check marked yes Databricks SQL check marked yes Databricks Runtime 11.3 LTS and above check marked yes Unity Catalog only

In some cases, an article mostly applies to a product, but certain parameters within an article are only supported by one product or specific versions of a product. In this case, the Applies to label is inserted into the appropriate parameter in the body of the article. For example:

The top of an article might state: Applies to: check marked yes Databricks SQL check marked yes Databricks Runtime

One specific parameter within the article might indicate Applies to: check marked yes Databricks SQL check marked yes Databricks Runtime 11.3 LTS and above. This means that most of the document is supported by all versions of both Databricks SQL and Databricks Runtime, and that specific parameter is supported by all versions of Databricks SQL and only Databricks Runtime versions 11.1 and above.

Another specific parameter within the article might indicate Applies to: check marked yes Databricks Runtime 11.3 LTS and above. This means that most of the document is supported by all versions of Databricks SQL and Databricks Runtime, but that specific parameter is not supported by Databricks SQL and is only supported in Databricks Runtime versions 11.1 and above.