These pages cover SQL Clone Technical Preview 0.2 to 0.3, which is not the latest version. Help for other versions is also available.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Current »

Technical preview

The technical preview was a way to experiment with the core technology and gather feedback about what people want to use this technology for. The next step is to release an early beta in the run up to a V1 product release. The product will be a centralized management system for database provisioning with this technology built into an agent on each SQL Server being used. See the product page for more information on what's coming up: http://www.red-gate.com/products/dba/sql-clone/

 

Technical preview

This is only preview, not a fully supported product. Snapshots and clones will not be compatible with later versions. These builds will not work after December 14th. Contact us if this will cause you difficulties.

0.3.0 - October 10th, 2016

  • Delayed timebomb to December 14th to allow more time to transition to the upcoming beta for those dependent on the technical preview

0.2.5 - August 10th, 2016

  • Improved progress & error feedback in the installer
  • Explicitly set initial catalog to master in connection strings

0.2.4 - August 1st, 2016

  • Fixed a null reference error when VHD size could not be determined
  • Support for NT 6.1 (Windows 7, Windows Server 2008 R2)
  • Mention permissions needed during installer

0.2.3 - July 13th, 2016

  • SQL Clone now supports creating snapshots from backups taken using Redgate's SQL Backup tool

0.2.2 - June 28th, 2016

  • The application is now known as SQL Clone

    • This accomodates the broader long-term aims of the application
    • Powershell Cmdlet names haven't changed - but will in a later release
  • The installer for SQL Clone will now download and install pre-requisites if required

    • Currently .NET 4.5.2, VC++ 2015 x64 and VC++ 2013 x64
  • Removes the command line exe - the powershell cmdlets should be used in its place

  • No labels