Skip to content

Releases

v0.5.1

Choose a tag to compare

@karthikbd karthikbd released this 19 Nov 15:49
dad8628

Security

  • mssql-migrate schema -o FILE wrote each certificate's private key together with the one-time password
    protecting it into the script, so anyone who could read the file could recover the key. The script
    now leaves private keys out and says how to move them (migrate copies them over the connection as
    before). If you wrote a schema script with copy_certificates on, delete it, and consider the
    certificates' private keys exposed to whoever could read it. Found while writing the threat model.

Added

  • GOVERNANCE.md, CODE_OF_CONDUCT.md, ROADMAP.md; a security assurance case (threat model, trust
    boundaries, countermeasures) and a dependency and scanning policy in the developer documentation;
    support and end-of-life policy, vulnerability response process and secrets policy in SECURITY.md;
    an OpenVEX document (vex.openvex.json).
  • Reproducible builds: wheel and sdist are byte-identical when rebuilt from the same commit
    (ci/reproducible_sdist.py, checked in CI).
  • CI: statement-coverage floor of 80%, DCO sign-off check, dependency review on pull requests, mypy --strict
    and the Bandit-derived ruff security rules; errors that were silently ignored are now logged at debug level.

v0.5.0

Choose a tag to compare

@karthikbd karthikbd released this 19 Nov 07:08
b925918

Same quality and supply-chain checks as lodestream.

Fixed

  • Full validation could miss a difference. Row fingerprints joined column values with a
    separator byte that the values themselves may contain, so two different rows could fingerprint the
    same (e.g. text "x\x1esy", "z" and "x", "y\x1esz"), and two different keys could collide. Each value
    is now length-prefixed. Found by fuzzing.
  • A configuration value of the wrong type (port = "1433", include = "dbo.*", source = 5, ...)
    failed later with a Python error, or not at all; it is now rejected at start-up with a message that
    names the setting and the expected type. compatibility_level takes a number or text. Found by fuzzing.
  • pymssql (found by the new end-to-end runs with each driver): binary values sent through INSERT
    arrived as text and were rejected (pymssql 2.4 quotes bytes as a string literal); UTF-8 varchar
    values were mangled on read; FreeTDS bulk copy dropped the connection on long (max) values. Binary
    parameters are now sent as binary, UTF-8 varchar is read as nvarchar, and (max), datetime and
    UTF-8 columns load with INSERT.
  • pyodbc: text/ntext/image columns failed with MemoryError and CLR / hierarchyid columns
    with a cast error (fast_executemany sized its buffers from the target column; parameters now carry
    the transport type); a failed chunk left IDENTITY_INSERT on for the next table; ODBC connection
    pooling handed validation a connection still inside a worker's transaction, which failed on
    memory-optimized tables (pooling is now off); UTF-8 varchar values were mangled both ways (now
    read and sent as nvarchar).

Added

  • ClusterFuzzLite (Atheris) fuzzing of config loading, row fingerprints, chunk predicates and
    identifier quoting, on every pull request, push and daily
  • End-to-end CI runs every version pair with all three drivers: bundled pytds, pyodbc + ODBC
    Driver 18, and pymssql
  • ruff and mypy in CI (both clean); CONTRIBUTING.md; private vulnerability reporting;
    OpenSSF Best Practices badge

Docs: https://mssql-ocp-migrate.readthedocs.io/en/latest/whatsnew/

v0.4.0

Choose a tag to compare

@karthikbd karthikbd released this 18 Nov 21:13

Know before you copy, and catch up after. 0.4.0 closes the gaps found by comparing with dbatools, Microsoft's migration tooling (DMA, Azure DMS, SqlPackage) and the list of features SQL Server on Linux doesn't support.

  • mssql-migrate assess: a readiness assessment for SQL Server on Linux / OpenShift. It flags xp_cmdshell, OLE Automation, Windows paths, Database Mail, Windows logins, FILESTREAM, CLR, replication and Agent job steps Linux can't run, plus version, edition, collation, time zone, sp_configure and free-space differences. It also runs before migrate and in lift plan; copy blockers stop the run.
  • mssql-migrate sync: change-tracking catch-up after migrate, with --follow, and --final for the cut-over (foreign keys re-trusted, identities and sequences aligned, validation).
  • Exact objects: modules keep their ANSI_NULLS / QUOTED_IDENTIFIER settings and are copied byte for byte; trigger firing order, object owners, disabled indexes, ROWGUIDCOL and NOT FOR REPLICATION are kept.
  • Data types: sql_variant keeps each value's base type, precision, scale and collation; SQL Server 2025 json and vector.
  • Server level: custom error messages, login default languages, user-defined server roles, server-level permissions, Agent operators; optionally server configuration and server triggers. lift re-encrypts the database master key with the target's service master key.
  • Validation now compares module definitions and settings, object owners, and references that no longer resolve on the target.

Fixed: tables with text, ntext or image columns failed to load with the bundled driver.

The end-to-end suite now runs across versions in CI: 2022 → 2022, 2019 → 2022, 2022 → 2025 and 2025 → 2025.

Full details: release notes · CHANGELOG

v0.3.0

Choose a tag to compare

@karthikbd karthikbd released this 17 Nov 05:27

migrate now copies everything inside a SQL Server database, and validation checks each item.

  • Columns: dynamic data masking (stops without UNMASK), sparse columns and column sets, typed XML, CLR types, Always Encrypted (copied as ciphertext)
  • Tables: temporal (versioning restored), memory-optimized, partitioned with per-partition compression, change tracking, CDC
  • Indexes: storage options and compression, statistics, XML, spatial and full-text indexes
  • Objects: table types, XML schema collections, partition functions/schemes, CLR, Always Encrypted keys, rules/defaults, DDL triggers, plan guides, Service Broker
  • Security and settings: users, roles, permissions, certificates and signatures, row-level security (switched on after validation), extended properties, every database option, scoped configurations, Query Store, compatibility level
  • Server level: logins (same SID and password hash); optionally SQL Agent jobs (created disabled) and linked servers, for migrate and lift

The end-to-end suite now runs in CI against two SQL Server 2022 containers, and fixing what it found made the bulk-insert path correct for varbinary(max), binary(n), char/nchar, xml, column sets and hierarchyid. Worker processes are now spawned, so Python API scripts need an if __name__ == "__main__": guard.

Full details: release notes · CHANGELOG

Wheel, sdist and CycloneDX SBOM are Sigstore-signed and attached by the publish workflow.

v0.2.1

Choose a tag to compare

@karthikbd karthikbd released this 16 Nov 21:58

Supply-chain hardening; no functional changes. pip install mssql-ocp-migrate (no runtime dependencies).

Security

  • Every CI pip install hash-locked (ci/requirements-*.txt, --require-hashes); package installed with --no-deps
  • New vulnerability-audit.yml: pip-audit of the vendored python-tds and all CI tooling on every change and weekly
  • This release's wheel, sdist and CycloneDX SBOM (declaring the vendored python-tds 1.17.1) are Sigstore-signed and attached below
  • Dependabot updates grouped

Added

  • Installation docs for Windows and corporate networks (JFrog Artifactory / Curation), signature verification
  • Supply-chain and vulnerability-management section in the security docs; setup.py shim; .codacy/cli.sh

See CHANGELOG.md.

v0.2.0

Choose a tag to compare

@karthikbd karthikbd released this 16 Nov 21:45

First public release. pip install mssql-ocp-migrate (no runtime dependencies).

Added

  • Physical migration (mssql-migrate lift) for very large databases: striped, compressed, copy-only backups; restore WITH NORECOVERY across several volumes; continuous log catch-up that also applies log backups taken by existing jobs (from msdb, with path_map) and refuses broken chains (gaps, NUL, third-party VDI backups); minutes-long cut-over with a tail-log backup; logins copied with the same SID and password hash; TDE certificates copied over the connection; plan from real msdb history; verify; ag-script for availability-group seeding
  • Logical migration (mssql-migrate migrate): chunked, parallel, resumable copy with identity preservation and lossless temporal/CLR transport; schema, indexes, constraints and programmable objects; scale-out across pods with --shard and finalize; minimally logged loads
  • Validation: schema parity, row counts, server-side checksums, SHA-256 row comparison naming the exact keys that differ; HTML and JSON reports
  • Drivers: bundled pure-Python TDS driver (python-tds 1.17.1, MIT) with TLS on the standard library; optional pymssql and pyodbc when already installed
  • OpenShift manifests, Sphinx documentation, CI (tests on 3.10–3.13, docs, CodeQL, Scorecard) and PyPI Trusted Publishing

See CHANGELOG.md.