Currently, when using Copy Job to transfer Snowflake data into MS Fabric Lakehouse, we can use the variable library to parameterize the Snowflake connection but cannot parameterize the target Snowflake database. This issue arises when switching the Snowflake source system between DEV and PROD environments using the variable library, as these environments may have different database names.
Suggestion: Add this as a parameter in the Copy Job using a variable library to swap the database based on environments OR add a parameter to the Snowflake connection for the database (currently only includes the "warehouse" parameter).
No CommentsBe the first to comment
Recent ideas
Add "Add to Dictionary" and "Ignore All" Functionality to Power BI Text Boxes
When creating professional Power BI reports, legitimate company names, project names, industry-specific terms and technical terminology are sometimes incorrectly flagged as spelling errors with a red...mmartelozzo8 hours agoNew MemberNew4Views0likes0CommentsFix Direct Lake semantic model binding in Deployment Pipelines
When deploying Direct Lake semantic models via Deployment Pipelines, the Lakehouse source is incorrectly treated as an external SQL source. This results in broken lineage and prompts for credentials....lk12318 hours agoAdvocate INew1.5KViews27likes2Comments