If one has a big database, it will be very slow to build. Especially if one has a lot of stored procedures and unit tests.
One option would be to have two SQL projects that are responsible for different aspects of the database. Then each build could deploy separately. In this case one would have the DropObjects flag to false.
Has anyone encountered this approach or used any other method of working with a large database in SSDT?
If one had multiple SQL projects - how could you break concerns apart?
So far I have a huge build which takes hours including unit tests when I put the SQL project in a pipeline
I've done this and I'm actually working on another project much smaller that's broken into 5 DB projects and will produce 2 dbs. However, I'm here because I forgot how to do it but I think it was done with project variables as I recall. I remember there was a website that showed how to do it and that's why I'm here. If I find it I'll share it.
The reason we do it is it's easier to break the parts to reusable parts in other db projects. Build once and share.