Current known limitations of SQL Clone

• The source of an image cannot:
  • Have a total combined file size (mdf+ldf) of over 2TB.
  • Contain filestream or memory-optimized tables/filegroups.
  • Be a SQL Server database snapshot.
  • Be a differential backup.
  • Be a multi-database backup (only the first database within the backup will be imaged)
  • Be a live database currently part of a failover cluster.
    • Images can be created using backups of such a database.
    • Images can be created from availability groups.

• Clones cannot be created on failover clusters or availability groups.

• SQL Clone does not currently support running under a group managed service account.

• 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.

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.