Forum Discussion
Updating a Semantic Model to use a different Workspace
- 11 months ago
I had a call with Microsoft and resolved this issue.
Open Deployment Pipeline’s “Rules”
Chose “Data source rules”
“Server”
Navigate to the Workspace you want the Semantic Model’s data to come from
Click the three dots against the Lakehouse you need to use > Settings
Copy the SQL analytics endpoint > SQL connection string into the “Server” section of the Data source rule
“Database”
Navigate to the Workspace you want the Semantic Model’s data to come from
Click into the SQL analytics endpoint of the Lakehouse you need to use
Copy the GUID after mirroredwarehouse in the URL into the “Database” section of the Data source rule, i.e. the "Artifact ID" in a URL that looks like this https://app.fabric.microsoft.com/groups/<Workspace ID>/<Artifact type>/<Artifact ID>/
1. A semantic model (in Fabric) can be built in Direct Lake mode (where tables are read directly from a lakehouse via parquet/Delta) or in Import / DirectQuery modes via SQL analytics endpoints.
2. The model’s data sources (gateway / cloud connection settings) are managed under Settings → Gateway & cloud connections in the semantic model item.
3. You can script or copy a semantic model via APIs or external tools (e.g. Semantic Link Labs) to another workspace. The copy may preserve metadata/logic, but you’ll likely need to reconfigure the connection sources / credentials.
4. For Direct Lake models, the data connection metadata includes a pointer to the SQL analytics endpoint of the lakehouse. The model “database” ID is tied to that endpoint.
Microsoft Learn
rajeshgumpena wrote:1. A semantic model (in Fabric) can be built in Direct Lake mode (where tables are read directly from a lakehouse via parquet/Delta) or in Import / DirectQuery modes via SQL analytics endpoints.
2. The model’s data sources (gateway / cloud connection settings) are managed under Settings → Gateway & cloud connections in the semantic model item.
3. You can script or copy a semantic model via APIs or external tools (e.g. Semantic Link Labs) to another workspace. The copy may preserve metadata/logic, but you’ll likely need to reconfigure the connection sources / credentials.
4. For Direct Lake models, the data connection metadata includes a pointer to the SQL analytics endpoint of the lakehouse. The model “database” ID is tied to that endpoint.
Microsoft Learn
How do I find the database ID? My connection string looks like this:
SqlServer{"server":"aaaaaaaaa-111111111111.datawarehouse.fabric.microsoft.com","database":"b2-c3-d4"}
I've been able to find the "server" string (it's the SQL connection URL for the Lakehouse), but I can't figure out how to identify where the "database" GUID has come from.