Housing authority developers are creating a modern SQL Database Project for case-management schema in CI. Which project style should they choose?
Select an answer to reveal the explanation.
Short Explanation
SDK-style SQL Database Projects are the modern blueprint housing CI expects—buildable, diffable schema as code, not a mystery zip of binaries or a slide deck pretending to be DDL.
Full Explanation
Housing authority developers creating a modern SQL Database Project for case-management schema in CI should choose an SDK-style SQL Database Project. SDK-style projects integrate cleanly with contemporary MSBuild/SDK tooling, produce reviewable SQL objects as source, and build in standard pipelines—matching how municipal teams implement schema-as-code for case-management databases today. A legacy binary-only model that cannot build in standard pipelines blocks CI verification and obscures diffs. A single undocumented SQL script folder with no project file lacks build validation, object organization, and publish profiling that Database Projects provide. Checking in a PowerPoint architecture deck instead of schema objects documents intent but cannot deploy or verify case-management DDL. Exam caveat: SDK-style is the modern direction for SQL projects in Azure Data Studio/VS; older non-SDK SQL projects may still exist—know how to migrate rather than mix broken tooling. Project success still requires correct target platform settings (Azure SQL versus SQL Server version) so builds do not accept unsupported T-SQL. Operational check: create an SDK-style SQL Database Project, import or author case-management tables/procedures, build in CI on a pull request, publish to a scratch database, and confirm the pipeline artifact (dacpac) is produced from source—not from an opaque binary drop.