Current limitations of SQL Clone Beta

• 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.
• Images cannot be deleted within the application (the workaround is to be manually delete them from disk once all related clones are deleted).

Things to be aware of during the beta

• Progress indications are very inaccurate, just because the progress bar stops, it doesn't mean the operation won't succeed.
• It is likely there will be breaking changes during the beta program, requiring a full uninstall/reinstall of management service and agents.
• If you delete or switch your configuration database, you must also cleanout of the %localappdata%\Red Gate\SQL Clone\clones directory manually.