Nested or non standard directories within database repo?
Is it possible to still use SQL Source Control through SSMS effectively with having some Stored Procedure stored in a different directory or in a nested directory within the Stored Procedures directory that SQL Source Control uses by default? I need a way to mark certain stored procedures as "Do not deploy" but I also need to keep them in version control and exclude them entirely. The build pipeline right now creates one sql file for deploying to customers, but I would like a way of being able to tell which sprocs to include in the final sql file that will be generated. I'm open to alternative ideas if anyone has them.
0 · Share on Twitter