Comments
Sort by recent activity
Looks to be related to the Default option set including dependencies. I've removed that so we'll see how things go now. / comments
Looks to be related to the Default option set including dependencies. I've removed that so we'll see how things go now.
I think one issue is that the options weren't being set correctly. According to the documentation the tool should detect that I'm running against an SSDT project and ignore permissions. That wasn't the case. Since I've set those options myself, I'm not seeing permissions being dropped anymore. However sequences are still getting altered even after adding "/exclude:Sequence"
/ comments
I think one issue is that the options weren't being set correctly. According to the documentation the tool should detect that I'm running against an SSDT project and ignore permissions. That wasn't...
To summarize what I think happened:
Permissions were dropped because there were some that existed in the target but not the source. It's confusing that /exclude:Additional didn't prevent this.
Sequences were altered because objects were deployed that had sequences that were dependencies. Again it's confusing (and I think undocumented) that IncludeDependencies overrides /excludes.
/ comments
To summarize what I think happened:
Permissions were dropped because there were some that existed in the target but not the source. It's confusing that /exclude:Additional didn't prevent this.
Sequ...