Avoid deploying partition boundary definitions?
I've inherited the responsibility of DB deployment for several legacy databases. I see that partitioned tables, along with their schemes and functions are checked in to source control. When I try to compare/deploy I see that the old partition boundaries (dates) are being pushed in the deployment. Obviously I don't want to replace my 2017 boundaries in prod with 2015 dates! I want the scheme/function structure in source control, but do not want to change the boundaries. I can exclude these object types, of course, but then any NEW partition development that SHOULD be deployed would be missed. I should note that we are working on automated deployment thru DLM Automation, it's still a work in progress. Is there a best practice documented for this scenario using automation, or is this a manual step? I can't be the first one to encounter this? Thanks in advance for any input.
0 · Share on Twitter