Current limitations of SQL Clone Beta
- You should explicitly launch the agent installer as an administrator (ctrl + shift + enter or ctrl + shift + click on the installer exe)
- The maximum size of an image (and therefore the maximum database size for cloning) is 2TB
- Databases with filestream and memory-optimized filegroups cannot be imaged
- Clones cannot be created on a SQL Server cluster
- CLR assemblies are not ported to other machines by SQL Clone. These may have to be registered in a post-clone step if they are required.
- SQL Clone does not currently support differential backups.
- Creating an image from a multi-database backup only creates an image for the first database in the backup.
- Clones and images cannot be deleted.
Things to be aware of during the beta
- Don't refresh the web app during wizards.
- Be careful to enter correct instance names and network share paths. There's no up-front validation, so operations will fail later on.
- Be patient waiting for list of databases (and everything else) to load.
- It is likely there will be breaking changes during the beta program.
- Uninstalling and reinstalling will require a cleanout of the %localappdata%\Red Gate\SQL Clone\clones directory.