SQL Clone 4

SQL Clone 4 release notes

September 20, 2019 - SQL Clone 4.0.4

This release of SQL Clone includes the following enhancements and bug fixes:

Features

Fixes

  • Fixed a deserialization error when using Get-SqlCloneTeam

September 18, 2019 - SQL Clone 4.0.3

This release of SQL Clone includes the following enhancements and bug fixes:

Features

  • SQL Clone now uses only FIPS compliant encryption and hashing algorithms

Fixes

August 28, 2019 - SQL Clone 4.0.2

This release of SQL Clone includes the following enhancements and bug fixes:

Features

  • Increases the size limit for image modification files in the UI, allowing e.g. larger masking sets to be uploaded

Fixes

  • The group icon is now shown again for Active Directory groups on the SQL Clone users page
  • Failure to clean up temporary users/logins when running SQL script modifications will now be logged and will not suppress reporting of any underlying error
  • The activity log and PowerShell cmdlets now show a reason for failure when an operation could not be started because the required agent is offline

August 20, 2019 - SQL Clone 4.0.1

This release of SQL Clone includes the following enhancements and bug fixes:

Features

  • You can now choose a color during team creation
  • PowerShell cmdlets now require .NET Framework 4.7.2

Fixes

  • Hotfix for taking a long time to get SQL Clone users (There is a current known issue that all users show a group icon in the SQL Clone users page)

July 30, 2019 - SQL Clone 4.0.0

This release of SQL Clone includes the following enhancements and bug fixes:

Features

SQL Clone 4 introduces Teams, allowing you to have more control over the instances, images and clones that users have access to.

  • Control which instances specific users can use to create clones and images, enabling safe self-service and delegation for DevOps and CI.
  • Maintain images with different levels of sensitivity or data masking for different users.
  • Allow people working on different projects to use the same SQL Clone installation without seeing instances, images and clones that aren't relevant to them.
  • Assign teams to new images as part of your automation scripts to make them available to the right users straight away.

Important notes

  • Upgrading to SQL Clone 4 will start a new trial. You will need to re-enter your SQL Clone serial number after upgrading. Provided you have a valid subscription (or support contract for legacy versions), your existing serial number from v1/v2/v3 will work.
  • SQL Clone Server now requires .NET Framework version 4.7.2 or later (was previously 4.6.1). If you are using an older version, you should update .NET before upgrading SQL Clone.
  • Existing PowerShell cmdlets will continue to work as normal after this upgrade. However, you should manually upgrade them to make use of the new Get-SqlCloneTeam cmdlet and the -Teams parameter in New-SqlCloneImage.

Fixes

  • Tooltips displayed on icons are now centered.
  • Fixed a UI crash in IE11 during the image creation workflow.
  • Size limit value not shown in total modification size exceeded error message in Create Templates form.

Didn't find what you were looking for?