You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog.
You have a connection to a Microsoft SQL Server database named DB1.
You need to expose the schemas and tables of DB1 to meet the following requirements:
* The schemas and tables can be queried in Databricks.
* The schemas and tables appear alongside other Unity Catalog objects.
* The data is NOT copied into Databricks-managed storage.
Solution: You create a foreign catalog in Catalog Explorer.
Does this meet the goal?
CORRECT ANSWE R: A - Yes.
According to Microsoft Learn on Lakehouse Federation and Unity Catalog foreign catalogs, a foreign catalog is a Unity Catalog object that represents an external database (such as SQL Server) through a registered connection. Creating a foreign catalog in Catalog Explorer using an existing connection to DB1 exposes all schemas and tables from DB1 as queryable objects within Unity Catalog. These objects appear alongside native Unity Catalog objects in Catalog Explorer. Crucially, Lakehouse Federation queries the external database in place --- the data is never copied into Databricks-managed storage. This satisfies all three requirements: schemas and tables can be queried in Databricks, they appear alongside other Unity Catalog objects, and the data is not copied. The foreign catalog is created under the registered connection to DB1.
Currently there are no comments in this discussion, be the first to comment!