-
Notifications
You must be signed in to change notification settings - Fork 129
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
[FEATURE] MS Fabric support #226
Comments
One idea could be to simply copy the dispatch logic from "sqlserver" and call it "fabric" and your good to go. Here is one example "type_timestamp.sql" {%- macro type_timestamp() -%} {%- macro default__type_timestamp() -%} {%- macro sqlserver__type_timestamp() -%} {%- macro fabric__type_timestamp() -%} If you use this approach everything works fine - except the dbt model versions ( https://docs.getdbt.com/reference/resource-properties/versions ) |
This is what I'm doing
That's how I do it Edit: |
Thank you for this request and sorry for the delayed response. MS Fabric and AWS Redshift are next on the roadmap for support. |
Are there any updates regarding AutomateDV supporting MS Fabric? |
Hello greetings,
I would like to evaluate dbtvault in MS Fabric environment. I was wondering if you already have a some idea of what is necessary to get dbtvault to run on MS Fabric or maybe already started working on this.
Depending on the effort, glad be able to help reach the support of Ms Fabric.
Best regards
AB#5347
The text was updated successfully, but these errors were encountered: