Forum Discussion
Post ProdigyUnderstanding different connection methods to a lakehouse
Hi,
in a copy activity of a pipeline it is possible to connect a destination lakehouse in two manners:
- selecting an existing connection of lakehouse type and then selecting the destination lakehouse, or
- selecting the destination lakehouse searching it in the OneLake catalog.
Which are the differencies between these two connection methods, with a particular reference to the deployment operation (by deployment pipeline)?
Which of the two methods is better?
Thanks
Hi pmscorca. To optimize a connection configuration for usage with deployment pipelines you want to leverage the Variable Libraries in Fabric because they allow automatic parameter substitution per deployment stage.
For that you need to choose a "Use dynamic content" when selecting a connection from the dropdown list and then configure connection parameters using your variables (Variable Library or pipeline parameters):Connection is a GUID of a Lakehouse connection Id from the Settings/Connections and Gateways.
Connection type is a string, hardcoded as it's always the same for a chosen storage type (i.e Lakehouse)
Workspace ID is a GUID of a target Workspace ID. Hardcoded here but can be parameterized.
Lakehouse ID is a GUID of the target Lakehouse.
Table is a string, but be aware of a naming convention for schema-enabled vs not Lakehouses.
Hope this helps answer your question.
3 Replies
- apturlov
Super User
Hi pmscorca. To optimize a connection configuration for usage with deployment pipelines you want to leverage the Variable Libraries in Fabric because they allow automatic parameter substitution per deployment stage.
For that you need to choose a "Use dynamic content" when selecting a connection from the dropdown list and then configure connection parameters using your variables (Variable Library or pipeline parameters):Connection is a GUID of a Lakehouse connection Id from the Settings/Connections and Gateways.
Connection type is a string, hardcoded as it's always the same for a chosen storage type (i.e Lakehouse)
Workspace ID is a GUID of a target Workspace ID. Hardcoded here but can be parameterized.
Lakehouse ID is a GUID of the target Lakehouse.
Table is a string, but be aware of a naming convention for schema-enabled vs not Lakehouses.
Hope this helps answer your question.
v-aatheequeCommunity Support
Hi pmscorca
We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.- v-aatheeque
Hi pmscorca
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.