question

ReluctantPhilosopher avatar image
ReluctantPhilosopher asked

I'm in a SSDT development shop that sets ALL db objects in ALL projects to Build Action=None - this is crazy, right?

I work in a db development shop where it is common practice to disable the building of SQL code in SSDT projects. In other words, I have a stored procedure called sp1.sql, and I set the BuildAction to None. Object is never seen by the IDE, never gets compiled, and its only put into a DACPAC if the developer manually includes that script into the deployment script.

This is nuts, right?

They can't use schema compare. DACPACs are empty except for the manual scripts they create. Target databases must be in a known state before deploying a project since it can't use the delta magic of the DACPAC. So much SSDT capability is lost.

As a consultant, I feel obligated to guide the team towards best practices, but as an outsider I don't want to rock the boat.

Has anyone ever seen this done before? Are there profound benefits of leveraging (deleveraging?) Visual Studio and SSDT in this way? I think they could use pkzip and it would be even simpler and about the same capability.

Any thoughts or opinions are greatly appreciated.


ssdt
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

0 Answers

·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.