Dbt-sqlserver

Latest version: v1.8.3

Safety actively analyzes 682387 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 6

0.20.0

Not secure
features:

- dbt-sqlserver will now work with dbt `v0.20.0`. Please see dbt's [upgrading to `v0.20.0` docs](https://docs.getdbt.com/docs/guides/migration-guide/upgrading-to-0-20-0) for more info.
- users can now declare a custom `max_batch_size` in the project configuration to set the batch size used by the seed file loader. [127](https://github.com/dbt-msft/dbt-sqlserver/issues/127) and [#151](https://github.com/dbt-msft/dbt-sqlserver/pull/151) thanks [jacobm001](https://github.com/jacobm001)

under the hood

- `sqlserver__load_csv_rows` now has a safety provided by `calc_batch_size()` to ensure the insert statements won't exceed SQL Server's 2100 parameter limit. [127](https://github.com/dbt-msft/dbt-sqlserver/issues/127) and [#151](https://github.com/dbt-msft/dbt-sqlserver/pull/151) thanks [jacobm001](https://github.com/jacobm001)
- switched to using a `MANIFEST.in` to declare which files should be included
- updated `pyodbc` and `azure-identity` dependencies to their latest versions

0.19.2

Not secure
fixes

- fixing and issue with empty seed table that dbt-redshift already addressed with [fishtown-analytics/dbt2255](https://github.com/fishtown-analytics/dbt/pull/2255) [#147](https://github.com/dbt-msft/dbt-sqlserver/pull/147)
- drop unneeded debugging code that only was run when "Active Directory integrated" was given as the auth method [149](https://github.com/dbt-msft/dbt-sqlserver/pull/149)
- hotfix for regression introduced by [126](https://github.com/dbt-msft/dbt-sqlserver/issues/126) that wouldn't surface syntax errors from the SQL engine [#140](https://github.com/dbt-msft/dbt-sqlserver/issues/140) thanks [jeroen-mostert](https://github.com/jeroen-mostert)!

under the hood:

- ensure that macros are not recreated for incremental models [116](https://github.com/dbt-msft/dbt-sqlserver/issues/116) thanks [infused-kim](https://github.com/infused-kim)
- authentication now is case-insensitive and accepts both `CLI` and `cli` as options. [100](https://github.com/dbt-msft/dbt-sqlserver/issues/100) thanks (JCZuurmond)[https://github.com/JCZuurmond]
- add unit tests for azure-identity related token fetching

0.19.1

Not secure
features:

- users can now delcare a model's database to be other than the one specified in the profile. This will only work for on-premise SQL Server and Azure SQL Managed Instance. [126](https://github.com/dbt-msft/dbt-sqlserver/issues/126) thanks [semcha](https://github.com/semcha)!

under the hood

- abandon four-part version names (`v0.19.0.2`) in favor of three-part version names because it isn't [SemVer](https://semver.org/) and it causes problems with the `~=` pip operator used dbt-synapse, a pacakge that depends on dbt-sqlserver
- allow CI to work with the lower-cost serverless Azure SQL [132](https://github.com/dbt-msft/dbt-sqlserver/pull/132)

0.19.0.2

Not secure
fixes

- solved a bug in snapshots introduced in v0.19.0. Fixes: [108](https://github.com/dbt-msft/dbt-sqlserver/issues/108), [#117](https://github.com/dbt-msft/dbt-sqlserver/issues/117).

0.19.0.1

Not secure
fixes

- we now use the correct connection string parameter so MSFT can montior dbt adoption in their telemetry. [98](https://github.com/dbt-msft/dbt-sqlserver/pull/98)

under the hood

- dbt-sqlserver's incremental materialization is now 100% aligneed logically to dbt's global_project behavior! this makes maintaining `dbt-sqlserver` easier by decreasing code footprint. [102](https://github.com/dbt-msft/dbt-sqlserver/pull/102)
- clean up CI config and corresponding Docker image [122](https://github.com/dbt-msft/dbt-sqlserver/pull/122)

0.19.0

Not secure
New Features:

- dbt-sqlserver's snapshotting now 100% aligneed logically to dbt's snapshotting behavior! Users can now snapshot 'hard-deleted' record as mentioned in the [dbt v0.19.0 release notes](https://github.com/fishtown-analytics/dbt/releases/tag/v0.19.0). An added benefit is that it makes maintaining `dbt-sqlserver` by decreasing code footprint. [#81](https://github.com/dbt-msft/dbt-sqlserver/pull/81) [fishtown-analytics/dbt#3003](https://github.com/fishtown-analytics/dbt/issues/3003)

Fixes:

- small snapshot bug addressed via [81](https://github.com/dbt-msft/dbt-sqlserver/pull/81)
- support for clustered columnstore index creation pre SQL Server 2016. [88](https://github.com/dbt-msft/dbt-sqlserver/pull/88) thanks [alangsbo](https://github.com/alangsbo)
- support for scenarios where the target db's collation is different than the server's [87](https://github.com/dbt-msft/dbt-sqlserver/pull/87) [alangsbo](https://github.com/alangsbo)

Under the hood:

- This adapter has separate CI tests to ensure all the connection methods are working as they should [75](https://github.com/dbt-msft/dbt-sqlserver/pull/75)
- This adapter has a CI job for running unit tests [103](https://github.com/dbt-msft/dbt-sqlserver/pull/103)
- Update the tox setup [105](https://github.com/dbt-msft/dbt-sqlserver/pull/105)

Page 4 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.