When you encounter this error, it's because you can't use a masking set that has multiple rule controllers with SQL Clone's imaging workflow currently. This is documented here.
The workaround is normally to put each Rule Controller into its own separate masking set and supply each as a separate file to SQL Clone in the web UI.
If you are using the Powershell, bellow is a sample script to do it:
$mask1 = New-SqlCloneMask -Path \\red-gate\masking-sets\production1.DMSMaskSet
$mask2 = New-SqlCloneMask -Path \\red-gate\masking-sets\production2.DMSMaskSet
$mask3 = New-SqlCloneMask -Path \\red-gate\masking-sets\production3.DMSMaskSet
$ImageOperation = New-SqlCloneImage -Name $name `
-SqlServerInstance $SqlServer `
-BackupFileName @('\\red-gate\backups\AdventureWorks-201701012210.bak') `
-Destination $ImageDestination `
-Modifications @($mask1, $mask2,$mask3)
0
0
Was this article helpful?
0 out of 0 found this helpful
Articles in this section
- Changes to SQL Clone In-Product Updates and Notifications
- What resources are required for involved machines using SQL Clone
- Where is the log out button in SQL Clone?
- Only one Rule Controller can be present if the SIMPLELOGINSUB is used
- SQL Clone Download URLs
- SQL Clone performance experiences delays while running simple queries
- Changing the default location of SQL Clone files
- SQL Clone throws "Could not get list of clones" error due to Newtonsoft.Json.JsonSerializationException
- Silent Install Clone Agent
- Error 21 message when trying to use a cloned database