SQL database in Fabric: how do you manage schema changes across dev, test and prod?

Hi everyone,

We are evaluating SQL database in Fabric for a small transactional workload and need a repeatable way to promote schema changes between environments. Today our idea is a SQL project built in CI and deployed as a dacpac, with idempotent scripts for data fixes such as:

IF NOT EXISTS (
    SELECT 1 FROM sys.columns
    WHERE object_id = OBJECT_ID(N'dbo.Orders') AND name = N'Channel'
)
    ALTER TABLE dbo.Orders ADD Channel varchar(20) NULL;

What I would like to know

• Do you use SQL projects with deployment pipelines, Git integration in the workspace, or a mix of both?
• How do you handle environment-specific settings and permissions so a deploy does not overwrite them?
• Any problems with large table alterations or rollback plans on this service?

Real examples of the promotion flow would be very helpful. Thanks in advance!