-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Azure SQL, Synapse, and Microsoft Fabric and extend support for SQL Server #2160
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, the authentication work is very much appreciated! I just bumped tbump/version, ran sqlserver tests locally and this LGTM, merging!
Quality Gate passedIssues Measures |
This PR adds support for Microsoft Fabric Lakehouses and Data Warehouses as a data source and along with it extends support for the existing SQL Server data source.
What this PR does/includes:
Extend authentication methods for SQL Server
This should make a lot of T-SQL users happy. I am also one of the lead maintainers for the dbt adapters which do the same thing. So basically I added the features which the dbt adapters support to this data source as well.
The data source now supports all the common authentication methods users of SQL Server (on-prem), Azure SQL DB, and Azure SQL Server Managed Instance use. This has probably also opened the door to compatibility with Azure Synapse Dedicated SQL Pools (because of the data types they probably should use the dbt-fabric adapter).
Create a new Fabric data source as a child of the SQL Server data source
The Fabric data source is different from the one for SQL Server in which data types are allowed. Furthermore it inherits from SQL Server.
No failing tests :)
Fabric T-SQL surface area is a bit smaller than the one in SQL Server. SQL Server was skipped on a lot of tests and this will unfortunately be the same for Fabric at this moment.
I'd be happy to work with you to add this to your CI but then we'd need to work together through Slack to configure the cloud infrastructure.