These pages cover SQL Clone 1, 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 4 Next »

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
  • Clones cannot be created on failover clusters or 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 differential backups.
  • 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, see Uninstalling SQL Clone
  • No labels

Visit the Redgate forums

Contact support

Mistake on this page? Email us