Job description

Title SQL Server/Azure SQL Managed Instance Engineer to Baseline DB into SSDT + CI/CD + Row-Level Security (Short Timeline) Project Overview We have an existing SQL Server database (~54 tables, ~209 stored procedures) backing a .NET MVC app. The scope for this engagement is already fully defined. We are not looking for someone to create their own project plan or redesign the approach. Instead, we need an experienced engineer to execute the following step-by-step deliverables within a strict short timeframe (1–2 business days): Scope of Work 1.Schema Recreation – Recreate the schema on Azure SQL Managed Instance (fresh deployment, no data or login migration). 2. SSDT Project – Create an SSDT SQL Database Project (.sqlproj) as the single source of truth: o Import from source DB or DACPAC. o Set target platform (SQL Server 2019/2022, MI-compatible). o Resolve build warnings and unresolved references. 3. Row-Level Security (RLS) – Implement isolation on companyId: o Predicate function using SESSION_CONTEXT('CompanyId'). o Apply security policies to tenant-scoped tables. o Provide a short integration note/snippet for the app to set SESSION_CONTEXT. 4. Post-Deployment.sql – Author with: o Idempotent lookup seeds (MERGE). o Roles/users/grants (contained users/AAD preferred). o Optional DB-scoped settings. 5. Publish Profiles – Provide Dev/Test/Prod .publish.xml profiles with safe defaults (e.g., block data loss by default). 6. CI/CD Setup – Configure pipeline (GitHub Actions or Azure DevOps): o Build .sqlproj to DACPAC. o Generate DeployReport (preview). o Publish to MI Dev with secure authentication (AAD/Managed Identity preferred). 7. First Deployment – Deploy to MI Dev and perform smoke tests on key stored procedures/views. 8. Runbook & Guide – Deliver a short runbook covering: o Connectivity/authentication setup. o Pipeline usage. o Rollback guidance. Constraints • Azure SQL Managed Instance is the definite target. • No cross-database calls, CLR, linked servers, or SQL Agent jobs. • No legacy data or login migration. • Stored procedures remain intact. Deliverables • Clean SQL Database Project (.sqlproj) in our Git repo. • Post-Deployment.sql (with roles, grants, seeds, optional DB settings). • RLS function and policies applied to agreed tables. • Dev/Test/Prod publish profiles (safe defaults). • CI/CD pipeline YAML (GitHub Actions or Azure DevOps). • Short runbook: connectivity/auth, pipeline usage, rollback guidance. Timeline • Strict: 1–2 business days (8–14 hours for an experienced engineer). • Due to downstream dependencies, timely completion is essential. Required Experience • SQL Server & Azure SQL MI in production. • SSDT/sqlproj, DACPACs, and SqlPackage deployments. • RLS implementation on SQL Server. • Database CI/CD (GitHub Actions or Azure DevOps). • Writing idempotent T-SQL seeds (MERGE). Nice to Have • Multi-tenant database design/isolation experience. • Azure networking/MI connectivity. • Drift detection or static analysis experience. Proposal Requirements • Short summary of relevant projects. • Confirmation of ability to deliver in the required timeframe. • Step-by-step plan to complete the scope above. • Preferred CI/CD tool (GitHub Actions vs Azure DevOps). • Fixed price or estimated hours, earliest start date. • (Optional) Example pipeline YAML or Post-Deployment.sql snippet.

Requirements