Comments
1 comment
-
Hi, thank you for your forum post.
SCA PowerShell version does not make use of the ComparisonOptions.xml created using SQL Source Control.
The user needs to set the required SQL Compare options within the cmdlet they are using, for example the New-DatabaseArtifact -<table><tbody><tr><td><code>New-DatabaseReleaseArtifact -Source <Object> -Target <Object> [-FilterPath <string>] [-IgnoreStaticData] [-SQLCompareOptions <string>] [-SQLDataCompareOptions <string>] [-IgnoreAdditional] [-TransactionIsolationLevel <TransactionIsolationLevel>] [-IncludeIdenticalsInReport] [-AbortOnWarningLevel <WarningSeverity>] [-IgnoreParserErrors] [-SqlCmdVariables <hashtable>] [-CodeAnalysisSettingsPath <string>] [-DriftFiltering <DriftFiltering>] [<CommonParameters>]
<br>Many Thanks<br>Eddie
Add comment
Please sign in to leave a comment.
I set the <IgnoreDynamicDataMasking>True</IgnoreDynamicDataMasking> in the ComparisonOptions.xml.
I can see that sql source control in the SSMS is ignoring the mask. But the DevOps 'Create a database release artifact' step still generating the sql with alter table.
Am I doing a wrong practice or the DevOps plugin doesn't support the feature?
SQL Change Automation: Release, version 4.2.2
Many thanks,
Weinan