This topic describes requirements for SQL Server target hosts, and Windows Domain or local users, for connecting with the Delphix Engine. The target host server, and the databases it contains, are collectively referred to as target environments. Windows target environments can be used for staging and/or provisioning of virtual databases (VDBs), as well as proxies for discovery of database instances on source environments. See the topic Setting Up SQL Server Environments: An Overview for more information. The requirements described in this topic apply equally to target environments used as staging environments and for provisioning VDBs.
Requirements for SQL Server Target Hosts
Each SQL Server target host must meet these requirements:
-
- The SQL Server instance on the target host should run as either domain users or local service accounts. Delphix does not support running SQL Server instances as local user accounts.
The SQL Server instance on the target host should be the same version or higher than the instance hosting the source database, with one exception. If a source database comes from a SQL Server 2005 instance, then the target hosts that will host VDBs from that source must be running either a SQL Server 2005 instance or a SQL Server 2012 instance or higher.
- The target host must have 64-bit Windows as the operating system. Delphix does not support 32-bit target systems.
- To add a Windows cluster as a target environment see the topic Adding a SQL Server Failover Cluster Target Environment.
- If the target host is a VMWare virtual machine, then the Windows Server operating system must be configured to use the VMXNET3 network driver.
- The operating system version on a target host that will be used for the provisioning of VDBs should be equal to or higher than the operating system on the target that is hosting the staging databases for the dSource from which the VDB is being provisioned. There is no OS compatibility requirement between source and target hosts. See the topic SQL Server Operating System Compatibility Matrices for more information.
- Windows PowerShell 2.0 or higher must be installed. To check the current version, type $PSVersionTable.PSVersion on a PowerShell Window.
- Execution of Windows PowerShell scripts must be enabled on the target host.
While running Windows PowerShell as an Administrator, enter this command to enable script execution: Set-ExecutionPolicy Unrestricted
. - For Windows 2003 target hosts, the following should be installed:
- WIndows Server iSCSI initiator (available for download).
- Hotfix documented in Microsoft Knowledge Base article KB 943043.
- The Windows iSCSI Initiator Service should have its Startup Type set to Automatic, and the service should be running. See the topic SQL Server Target Host iSCSI Configuration Parameter Recommendations for configuring the Windows iSCSI Initiator Service.
The Delphix Connector must be installed, as described in the topics Setting Up SQL Server Environments: An Overview and Adding a SQL Server Standalone Target Environment.
- Shared Memory must be enabled as a Network Protocol for the SQL instances on the target.
In SQL Server Config Manager, navigate to Client Protocols > Shared Memory to enable this. - TCP/IP access must be enabled for each SQL Server instance on the target host to allow remote connections to instances.
In SQL Server Config Manager, navigate to Network Configuration > Protocols > TCP/IP to enable TCP/IP access.
Windows User Requirements
There must be a Windows user (for example, delphix_trgt) for the target host that can be used by the Delphix Engine. This user can be a Windows domain user or a local user. However, using a local user account will prevent the target host from being used as a staging target. This user must meet these requirements:
- , and for mounting iSCSI LUNs presented by the Delphix Engine to the target host.
- Must have the server role sysadmin for each SQL Server instance that the Delphix Engine will communicate with.
In SQL Server Management Studio, navigate to Security > Logins >delphix_trgt > Server Roles to set this role for the user. - Must have Log on as a batch job rights so the Delphix Engine can remotely execute commands via Powershell.
Using the secpol.msc security policy editor, navigate to Local Policies > User Rights Assignment > Log on as a batch job to set this right.