Using triggers to track Stored Procedure Changes or Options?

[whatwhat]

If you could please elaborate on the why SSDT will fall apart? The database design is handled by 2 devs while the other dev's use the stored procs.

Because SSDT relies on you having access to the production system to do checks against, and write the "upgrade" scripts. This is fine in a mom and pop shop when you have one box and two devs, but if you have many servers and many devs it just isn't sustainable.

In the real world, a developer does not have access to a production box unless they are needed to troubleshoot something.

It might seem a bit overkill, but it is always better to try and get a solid development platform going no matter how small the systems you are working on. If/When you ever apply for another job, I'd be much more impressed with someone who might not know MSDN Books Online definitions off by heart, but was able to put basic source control and other things in place in a smaller operation.

 

[Pho3nix]

Because SSDT relies on you having access to the production system to do checks against, and write the "upgrade" scripts. This is fine in a mom and pop shop when you have one box and two devs, but if you have many servers and many devs it just isn't sustainable.

In the real world, a developer does not have access to a production box unless they are needed to troubleshoot something.

It might seem a bit overkill, but it is always better to try and get a solid development platform going no matter how small the systems you are working on. If/When you ever apply for another job, I'd be much more impressed with someone who might not know MSDN Books Online definitions off by heart, but was able to put basic source control and other things in place in a smaller operation.

Agree with most of your points.
As mentioned previously corporate governance is something we have to deal with currently which means a lot of things that are obvious solution are not possible.
I am not working in a dev house and all previous ones I have worked in never used source control for SQL etc. thus the topic

Think a separate thread might be suited to discuss procedures used in "real" dev houses in in mom & pop shops as you put it. Thanks for your input here.

 

[Pho3nix]

The other thing I've seen done very effectively as an additional check to versioning is to hash the source code and use that to check that the version applied is correct.

/looks into this.

 

[patrict]

I'd also be interested in that separate thread discussing differences, always keen to see how others are handling the problems we all face