What problem does it solve? Writing and testing MS SQL Server scripts in Windmill requires knowing the correct parameter syntax, preview workflow, and metadata regeneration steps, and mistakes like deploying untested code or leaving stale lock files cause spurious diffs and broken runs. ## Core Features & Use Cases - MSSQL Parameter Binding: Declares named script arguments using @P1, @P2 placeholders with typed comments such as -- @P1 name1 (varchar). - Preview vs Run Guidance: Distinguishes wmill script preview for local iteration from wmill script run for deployed versions, preventing accidental deploys of untested code. - S3 Integration: Receives S3Object parameters decoded via OPENJSON and streams large result sets to S3 with the -- s3 directive in JSON, Parquet, or CSV format. - Use Case: Write a query filtering users by name and age, preview it locally with sample arguments, then regenerate metadata so the lock file and input schema stay in sync. ## Quick Start Write a Windmill MSSQL script that selects users by name and minimum age, then preview it locally with sample arguments.