Comments
3 comments
-
Hi @bkillen,
SQL Source Control isn't designed for this use case-- the files committed to the repo are designed to be purely the object definition rather than a deployment script.
Can I ask more about the use case / why this is important for the team?
Cheers,
Kendra -
Hello Kendra. I wish I knew the answer. From what I've been told the app developers want the ability to take a script that has that header and be able to run it over and over.
-
Ah, I see.
With SQL Source Control, the behavior is that it provides a standardized way of committing the files. But these are not designed to be deployment scripts -- for many object types (tables, etc), that wouldn't work at all.
There are a few options to configure deployments for SQL Source Control projects.
I don't know if your app development team holds licenses for SQL Compare or any other Redgate products, but if they do then there are options for them to create deployment scripts which include those re-runnable headers in them -- but this does require having SQL Compare or another tool to create those deployments.
Happy to help give more detail on those if that would be helpful.
Cheers,
Kendra
Add comment
Please sign in to leave a comment.
Any Advice?