Opinionated T-SQL formatter using Microsoft ScriptDom for safe CI/CD use
Formats T-SQL by parsing code with Microsoft ScriptDom and re-parsing output to ensure no syntax or comment loss, ideal for enforcing style in automated pipelines. Page Brooks provides this Windows utility as a single static binary with JSON-configurable rules and CI-friendly exit codes. The tool targets SQL Server developers, DBAs, and DevOps engineers who need a verifiable, zero-dependency formatter that can run in local editors and build systems.
What does maxdop actually change and why that matters?
The tool reformats T-SQL using Microsoft's ScriptDom parser, so it recognises stored procedures, GO batches, and legacy syntax the same way SQL Server does. Configuration lives in a .maxdop.json file that teams can commit to source control. The app runs as a single static binary on Windows x64, producing formatted files that reflect the configured style while operating without external runtimes.
How reliable is the formatting and verification process?
Verification is safety-first: every formatted file is re-parsed and compared against the original token stream. If the re-parse detects mismatched tokens, comments, or a differing syntax tree, the tool refuses to overwrite the original file. That behaviour prevents accidental corruption of logic or comments during automated formatting runs.
Is it safe to use in automated pipelines and what are the operational signals?
CI/CD integration is a design goal: the tool emits distinct exit codes for mismatches or errors, so pipeline steps can fail explicitly when formatting would alter semantics. The static binary form removes dependency installation from build agents, and the win-get install command simplifies deployment to Windows environments.
Do non-experts need deep SQL knowledge to operate the tool?
Operation is configuration-driven rather than manual editing, so typical users apply a repository .maxdop.json and run the binary. Familiarity with T-SQL structure helps when resolving verification failures, because the tool refuses to save changes on parse mismatches; that behaviour requires the user or maintainer to adjust style or address syntax that triggers the safeguard.
Who should adopt maxdop and when to be cautious
maxdop suits teams that require enforced, verifiable T-SQL formatting in Windows-based development and CI/CD workflows; its use of Microsoft's parser and the re-parse safeguard reduce risk of semantic change. Expect to intervene when verification blocks a format pass, since the tool intentionally prevents uncertain edits. Recommended.
