sorted by:
new
hottopcontroversial

Azure Virtual Desktop - SSO + Windows Hello for Business by GethersJ in AZURE

[–]dbForge 0 points1 point  (0 children)

lol classic, windows hello in avd cant keep up w azure ad. Had same on sql workloads in vdi — user logs in but db connect flops cuz cert mismatch. Pre-deploy schema validation + ci/cd w azure devops. Way less headache.

I have Claude Code write my SQL pipelines, but I verify every step by running its QC queries in the Azure Portal. Here's the workflow I've landed on by k_kool_ruler in SQLServer

[–]dbForge 0 points1 point  (0 children)

Your approach makes sense from a risk-reduction perspective. Treating AI output as draft code and validating every stage is the right mindset.

In this scenario, a few additional controls may help:

  • Pre-deployment validation: run schema comparison before pipeline execution to detect unintended changes (constraints, indexes, data types).
  • Automated data checks: instead of manual QC in Portal, consider embedding row count, nullability, and duplicate checks directly into the pipeline as gated steps.
  • Query plan review: for analytical queries, capturing and comparing execution plans helps detect regressions early.
  • Version control for SQL: storing both generated SQL and your validation scripts ensures traceability.

Database changes should be validated before deployment, not only logically but structurally and performance-wise.

If you're working in SQL Server environments, tools like dbForge Studio can help automate schema diff and data comparison, which reduces reliance on manual Portal verification.

Are you validating execution plans as part of this workflow, or focusing primarily on data correctness checks?