Comments
Sort by recent activity
We ended up writing a script as a predeployment gated by the IsShadowDeployment environment variable. The script generates the dependencies off a conifg table on our shadow deployment server. So far, so good! / comments
We ended up writing a script as a predeployment gated by the IsShadowDeployment environment variable. The script generates the dependencies off a conifg table on our shadow deployment server. So fa...
Indeed, not too keen on the synonym approach even though it is quite creative. We will take a look at the /EXCLUDE switch. The main reason we do not want to source control is if procedural changes are made to those tables, then when we work off of a sanitized production restore and attempt to generate migration scripts, changes to that externally controlled schema will be picked up. Ultimately, it would be beneficial if we could exclude it from the script generation, but include it in the Schema-Model. Edit: Just to provide clarity, the procedurally controlled schema is an Operational Data Store that will automatically make additive changes to the tables representing the transactional system. The source controlled logic is the ELT into star schemas. We definitely understand that this particular use case is a corner case-- we will likely not use the script generation function, but take advantage of the rest of the features that come with Change Automation for this particular DB. / comments
Indeed, not too keen on the synonym approach even though it is quite creative. We will take a look at the /EXCLUDE switch.The main reason we do not want to source control is if procedural changes a...