Forum Discussion
Questions on Git Integration Behavior and Semantic Model Connector in Fabric
Hi AdarshChekodu,
Thanks for the additional questions.
Now, there isn’t an automated migration path available to switch an existing semantic model from the SQL Endpoint connector to the new Lake-based connector. Moving to the new connector typically requires creating a new semantic model based on the Lakehouse. We understand this can require planning from a deployment and governance perspective.
Regarding support going forward, both connectors continue to be supported today. The new Lake-based connector is part of the long-term direction in Fabric, especially for Direct Lake and Lake-centric scenarios, but there has not been an announcement about deprecating the SQL-endpoint connector. If there are any changes to support policies in the future, those will be communicated through the usual Microsoft channels and documentation.Thank you again for using the Microsoft Fabric Community Forum.
Hi AdarshChekodu,
Thanks for getting back and glad to hear the suggestion shared earlier by Srisakthi, helped with your first point.
Regarding your second question about the connector change: In Fabric, semantic models created from a Lakehouse are gradually moving to use the Azure Data Lake based connection (including Direct Lake scenarios), instead of the older SQL connector approach. This is expected behaviour as Fabric is shifting towards a more lake-native architecture for semantic models.
This shouldn’t negatively impact your existing models but depending on how your current CI/CD process is set up, you may need to review and update any scripts or deployment steps that assume the older SQL connector.
Refer these links:
1. https://learn.microsoft.com/en-us/fabric/data-warehouse/semantic-models
2. https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview
If you have any concerns around how this affects your current deployment workflows, feel free to share more details and we can help investigate on that.
Thank you.
v-kpoloju-msft
Thanks alot for the response.
Is there a plan from microsoft to help us migrate from the old Connector "SQL Endpoint" to the new one? Or will we have to re-create the entire semaic model with the new connector?
Also in future will there be features that will support only the new connectors? Or will the old connector be "Out of Support"?
Thanks,
Adarsh
Hi AdarshChekodu,
Thanks for the additional questions.
Now, there isn’t an automated migration path available to switch an existing semantic model from the SQL Endpoint connector to the new Lake-based connector. Moving to the new connector typically requires creating a new semantic model based on the Lakehouse. We understand this can require planning from a deployment and governance perspective.
Regarding support going forward, both connectors continue to be supported today. The new Lake-based connector is part of the long-term direction in Fabric, especially for Direct Lake and Lake-centric scenarios, but there has not been an announcement about deprecating the SQL-endpoint connector. If there are any changes to support policies in the future, those will be communicated through the usual Microsoft channels and documentation.Thank you again for using the Microsoft Fabric Community Forum.
Hi AdarshChekodu,
Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.Thank you.