Selecting the Instance of SQL Server
Applies To: System Center Data Protection Manager 2007
A typical DPM installation includes an instance of SQL Server that is installed by DPM Setup. The instance of SQL Server that is installed by DPM Setup is included in the DPM software and does not require a separate SQL Server license.
However, when you install DPM 2007, you can specify a remote instance of SQL Server to be used by DPM instead of the default instance of SQL Server that is included with DPM.
To use a remote instance of SQL Server, the server running SQL Server and the DPM server should be located in the same domain. A specific instance of SQL Server can be used by only one DPM server. The remote instance of SQL Server cannot be on a computer that is running as a domain controller.
Note
If the remote instance of SQL Server is running as a domain account, you should enable the named pipes protocol for communication with the DPM server. For instructions on configuring the named pipes protocol, see Configuring Client Network Protocols (https://go.microsoft.com/fwlink/?LinkId=87976).
The remote instance of SQL Server must be running Internet Information Services (IIS) and SQL Server 2005 Standard or Enterprise Edition with SP2, including the following components:
SQL Server Database Engine
Reporting Services
We recommend you use the following settings on the remote instance of SQL Server:
Use the default failure audit setting.
Use the default Windows Authentication mode.
Assign a strong password to the sa account.
Enable password policy checking.
Install only the SQL Server Database Engine and Reporting Services components.
A remote instance of SQL Server should not run as Local System.
Run SQL Server by using a low-privileged domain user account.