Current known limitations of SQL Clone

• The maximum size of an image (and therefore the maximum database size for cloning) is currently 2TB.
• Databases with filestream and memory-optimized tables/filegroups cannot be imaged.
• Database snapshots cannot be imaged.
• Clones cannot be created on failover clusters or availability groups. Images cannot be created directly from failover clusters but can be created using backups of the databases. Images can be created from availability groups.
• 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 creating an image from a differential backup.
• Creating an image from a multi-database backup only creates an image for the first database in the backup.
• SQL Clone does not currently support running under a group managed service account.

Known issues

• Progress indications for creating images from backups are very inaccurate.
• If you delete or switch your configuration database, you must also cleanout of the %localappdata%\Red Gate\SQL Clone\clones directory manually.

Images cannot be created directly from failover clusters but can be created using a backup from one. Images can be created directly from availability groups.