dbt adapter for SQL Server and Azure SQL
bool_or
, array_construct
, array_concat
, array_append
type_boolean
now returns the correct data type (bit
)All commits: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.2.0...v1.3.0
bool_or
, array_construct
, array_concat
, array_append
type_boolean
now returns the correct data type (bit
)Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.2.0...v1.3.0rc1
Make sure to read the updated documentation about:
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.
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 configsretries
setting introduced in coretype_*
macrosbool_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.TIMESTAMP
would be used as data type instead of DATETIMEOFFSET
, fixed thatCommit changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.1.0...v1.2.0
Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.2.0b2...v1.2.0rc1
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.
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 configsretries
setting introduced in coretype_*
macrosbool_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.TIMESTAMP
would be used as data type instead of DATETIMEOFFSET
, fixed thatFirst beta version with support for dbt 1.3.0 No new features/bugfixes which were not already included in v1.2.0b2
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.
retries
setting introduced in coretype_*
macrosbool_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.TIMESTAMP
would be used as data type instead of DATETIMEOFFSET
, fixed thatretries
setting introduced in coretype_*
macrosbool_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.TIMESTAMP
would be used as data type instead of DATETIMEOFFSET
, fixed thatFull Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.1.0...v1.2.0b1
See changes included in v1.1.0rc1 below as well
Full changelog can be found here
Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.0.0...v1.1.0
Full changelog can be found here
Full Changelog: https://github.com/dbt-msft/dbt-sqlserver/compare/v1.0.0...v1.1.0.rc1
Please see dbt-core v1.0.0 release notes for upstream changes