Split SCA generated sql package in two

fforgoso · March 9, 2020 1:43PM

Hi all.

We are working with SQL Change Automation and our client is wondering if we could deploy schema changes one day and data changes another day.

I'd like to know if it is possible to split the generated sql package in two. One file for schema changes and another for data changes. As far as I see, looks like we can't, but would like to confirm that.
Maybe you could suggest another way to address this problematic.

Thanks in advance.

Kendra_Little · March 9, 2020 2:32PM

Hi @fforgoso ,

The best way to do this is to create multiple deployments. Each deployment can contain the exact combination of changes that you would like.

There are a couple of different techniques you could use to selectively split migrations (of any kind) into multiple deployments.

Are you currently using a practice of branching and merging? If so, that type of strategy helps you control the flow of changes into your release pipeline. An example is described here: https://littlekendra.com/2020/01/10/why-i-like-the-release-flow-branching-strategy-with-git-for-database-devops/

Hope this helps,
Kendra

fforgoso · March 10, 2020 12:45PM

Good morning @Kendra_Little. Thanks for your answer.

Off the top of your head, can you think of an alternative than this suggested branching strategy?
Does the tool provide any settings to accomplish our client needs?

Split SCA generated sql package in two

Answers

Product Learning

Community Forums

Events & Friends

Simple Talk