Dbt Sqlserver Versions Save

dbt adapter for SQL Server and Azure SQL

v1.3.0

1 year ago

What's Changed

v1.3.0

Features

  • Support for dbt-core 1.3
    • Python models are currently not supported in this adapter
    • The following cross-db macros are not supported in this adapter: bool_or, array_construct, array_concat, array_append

Fixes

  • The macro type_boolean now returns the correct data type (bit)

Chores

  • Update adapter testing framework
  • Update dependencies and pre-commit hooks

Complete changelog

All commits: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.2.0...v1.3.0

v1.3.0rc1

1 year ago

Changelog

v1.3.0 (pre-releases)

Features

  • Support for dbt-core 1.3
    • Python models are currently not supported in this adapter
    • The following cross-db macros are not supported in this adapter: bool_or, array_construct, array_concat, array_append

Fixes

  • The macro type_boolean now returns the correct data type (bit)

Chores

  • Update adapter testing framework
  • Update dependencies and pre-commit hooks

Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.2.0...v1.3.0rc1

v1.2.0

1 year ago

v1.2.0

Make sure to read the updated documentation about:

Changelog

Possibly breaking change: connection encryption

For compatibility with MS ODBC Driver 18, the settings Encrypt and TrustServerCertificate are now always added to the connection string. These are configured with the keys encrypt and trust_cert in your profile. In previous versions, these settings were only added if they were set to True.

The new version of the MS ODBC Driver sets Encrypt to True by default. The adapter is following this change and also defaults to True for Encrypt.

The default value for TrustServerConnection remains False as it would be a security risk otherwise.

This means that connections made with this version of the adapter will now have Encrypt=Yes and TrustServerCertificate=No set if you are using the default settings. You should change the settings encrypt or trust_cert to accommodate for your use case.

Features

  • Support for dbt-core 1.2
    • Full support for the new grants config
    • New configuration option: auto_provision_aad_principals - setting this to true will automatically create contained database users linked to Azure AD principals or groups if they don't exist yet when they're being used in grant configs
  • Support for MS ODBC Driver 18
  • Support automatic retries with new retries setting introduced in core
  • The correct owner of a table/view is now visible in generated documentation (and in catalog.json)
  • A lot of features of dbt-utils & T-SQL utils are now available out-of-the-box in dbt-core and this adapter. A new release of T-SQL utils will follow.
    • Support for all type_* macros
    • Support for all cross-database macros, except:
    • bool_or
    • listagg will only work in SQL Server 2017 or newer or the cloud versions. The limit_num option is unsupported. DISTINCT cannot be used in the measure.

Fixes

  • In some cases the TIMESTAMP would be used as data type instead of DATETIMEOFFSET, fixed that

Chores

  • Update adapter testing framework to 1.2.2
  • Update pre-commit, tox, pytest and pre-commit hooks
  • Type hinting in connection class
  • Automated testing with SQL Server 2017, 2019 and 2022
  • Automated testing with MS ODBC 17 and MS ODBC 18

Commit changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.1.0...v1.2.0

v1.2.0rc1

1 year ago

What's Changed

Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.2.0b2...v1.2.0rc1

v1.2.0 (pre-releases)

Possibly breaking change: connection encryption

For compatibility with MS ODBC Driver 18, the settings Encrypt and TrustServerCertificate are now always added to the connection string. These are configured with the keys encrypt and trust_cert in your profile. In previous versions, these settings were only added if they were set to True.

The new version of the MS ODBC Driver sets Encrypt to True by default. The adapter is following this change and also defaults to True for Encrypt.

The default value for TrustServerConnection remains False as it would be a security risk otherwise.

This means that connections made with this version of the adapter will now have Encrypt=Yes and TrustServerCertificate=No set if you are using the default settings. You should change the settings encrypt or trust_cert to accommodate for your use case.

Features

  • Support for dbt-core 1.2
    • Full support for the new grants config
    • New configuration option in the target: auto_provision_aad_principals - setting this to true will automatically create contained database users linked to Azure AD principals or groups if they don't exist yet when they're being used in grant configs
  • Support for MS ODBC Driver 18
  • Support automatic retries with new retries setting introduced in core
  • The correct owner of a table/view is now visible in generated documentation (and in catalog.json)
  • A lot of features of dbt-utils & T-SQL utils are now available out-of-the-box in dbt-core and this adapter. A new release of T-SQL utils will follow.
    • Support for all type_* macros
    • Support for all cross-database macros, except:
    • bool_or
    • listagg will only work in SQL Server 2017 or newer or the cloud versions. The limit_num option is unsupported. DISTINCT cannot be used in the measure.

Fixes

  • In some cases the TIMESTAMP would be used as data type instead of DATETIMEOFFSET, fixed that

Chores

  • Update adapter testing framework to 1.2.1
  • Update pre-commit, tox, pytest and pre-commit hooks
  • Type hinting in connection class
  • Automated testing with SQL Server 2017, 2019 and 2022
  • Automated testing with MS ODBC 17 and MS ODBC 18

v1.3.0b1

1 year ago

First beta version with support for dbt 1.3.0 No new features/bugfixes which were not already included in v1.2.0b2

v1.2.0b2

1 year ago

Possibly breaking change: connection encryption

For compatibility with MS ODBC Driver 18, the settings Encrypt and TrustServerCertificate are now always added to the connection string. These are configured with the keys encrypt and trust_cert in your profile. In previous versions, these settings were only added if they were set to True.

The new version of the MS ODBC Driver sets Encrypt to True by default. The adapter is following this change and also defaults to True for Encrypt.

The default value for TrustServerConnection remains False as it would be a security risk otherwise.

This means that connections made with this version of the adapter will now have Encrypt=Yes and TrustServerCertificate=No set if you are using the default settings. You should change the settings encrypt or trust_cert to accommodate for your use case.

This behaviour might still change in the final release of 1.2.0 based on feedback gathered during the beta phase.

Features

  • Support for dbt-core 1.2
  • Support for MS ODBC Driver 18
  • Support automatic retries with new retries setting introduced in core
  • The correct owner of a table/view is now visible in generated documentation (and in catalog.json)
  • A lot of features of dbt-utils & T-SQL utils are now available out-of-the-box in dbt-core and this adapter. A new release of T-SQL utils will follow.
    • Support for all type_* macros
    • Support for all cross-database macros, except:
    • bool_or
    • listagg will only work in SQL Server 2017 or newer or the cloud versions. The limit_num option is unsupported. DISTINCT cannot be used in the measure.

Fixes

  • In some cases the TIMESTAMP would be used as data type instead of DATETIMEOFFSET, fixed that

Chores

  • Update adapter testing framework to 1.2.1
  • Update pre-commit, tox, pytest and pre-commit hooks
  • Type hinting in connection class
  • Automated testing with SQL Server 2017, 2019 and 2022
  • Automated testing with MS ODBC 17 and MS ODBC 18

Outstanding work for official release

  • Add documentation about new features to official dbt docs pages

v1.2.0b1

1 year ago

Features

  • Support for dbt-core 1.2
  • Support automatic retries with new retries setting introduced in core
  • The correct owner of a table/view is now visible in generated documentation (and in catalog.json)
  • A lot of features of dbt-utils & T-SQL utils are now available out-of-the-box in dbt-core and this adapter. A new release of T-SQL utils will follow.
    • Support for all type_* macros
    • Support for all cross-database macros, except:
    • bool_or
    • listagg will only work in SQL Server 2017 or newer or the cloud versions. The limit_num option is unsupported. DISTINCT cannot be used in the measure.

Fixes

  • In some cases the TIMESTAMP would be used as data type instead of DATETIMEOFFSET, fixed that

Chores

  • Update adapter testing framework to 1.2.1
  • Update pre-commit, tox, pytest and pre-commit hooks
  • Type hinting in connection class

Outstanding work for next beta release

  • Native dbt support for GRANTs as configs
  • Add documentation about new features to official dbt docs pages

Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.1.0...v1.2.0b1

v1.1.0

2 years ago

v1.1.0

See changes included in v1.1.0rc1 below as well

Full changelog can be found here

Fixes

Chores

v1.1.0.rc1

Features

  • update to dbt 1.1

Fixes

  • #194 uppercased information_schema (@TrololoLi)
  • #215 Escape schema names so they can contain strange characters (@johnf)

Chores

  • Documentation on how to contribute to the adapter
  • Automatic release process by adding a new tag
  • Consistent code style with pre-commit
  • #201 use new dbt 1.0 logger (@semcha)
  • #216 use new dbt testing framework (@dataders & @sdebruyn)

List of PRs

New Contributors

Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.0.0...v1.1.0

v1.1.0.rc1

2 years ago

What's Changed

Summary

Full changelog can be found here

Features

  • update to dbt 1.1

Fixes

  • #194 uppercased information_schema (@TrololoLi)
  • #215 Escape schema names so they can contain strange characters (@johnf)

Chores

  • Documentation on how to contribute to the adapter
  • Automatic release process by adding a new tag
  • Consistent code style with pre-commit
  • #201 use new dbt 1.0 logger (@semcha)
  • #216 use new dbt testing framework (@dataders & @sdebruyn)

Commits & PRs

New Contributors

Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.0.0...v1.1.0.rc1

v1.0.0

2 years ago

Please see dbt-core v1.0.0 release notes for upstream changes

Fixes

  • fix index naming when columns contain spaces #175

Under the Hood

  • re-organize macros to match new structure #184