If any of these requirements are problematic for you (or your organisation), we'd love to hear about it by email.

These requirements apply to both parts of SQL Clone:

• Windows Server 2008 R2 or later, or Windows 7 or later (64-bit versions only)
• SQL Server 2008 or later (Express edition is sufficient)
• .NET 4.5.2 or later (part of installation)

SQL Clone management service requirements

A single central management service is required to use SQL Clone, it co-ordinates agents, and serves a web UI.

Requires:

• Access to a SQL Server (2008 or later) for storing configuration data
• If using Windows Server 2008r2 or Windows 7, installation upgrades security defaults to match later Windows versions:
  • TLS 1.2 enabled (part of installation)
  • SendTrustedIssuerList disabled (part of installation)

SQL Clone agent requirements

An agent should be installed on the same machine as any SQL Server you wish SQL Clone to use as a source of images, destination for clones, or temporary scratch space for restoring backups.

This requires a user account which has:

• Local admin privileges in order to use the Virtual Disk Service
• Read/write access to network locations where images will be stored
• If you wish to use Windows Authentication for SQL Server:
  • CREATE DATABASE on local SQL Server instances where clones will be created
  • VIEW ANY DEFINITION on local SQL Server instances where images will be created from