Export (0) Print
Expand All

Setting up a remote SQL Server instance

DPM needs an instance of 64-bit SQL Server Enterprise or Standard Editions for its database. During installation you can specify that a local or remote SQL Server can be used. For DPM in System Center 2012 R2 you can use an instance of SQL Server running SQL Server 2008 R2 with SP2 or later, or SQL Server 2012 with SP1. This procedure describes how to set up a remote SQL Server running SQL Server 2008 R2 with SP2. The instructions are similar for SQL Server 2012 SP1 and R2.

To install and configure a remote SQL Server database for DPM

Configure SQL Server

  • On the Setup Role tab select SQL Server Feature Installation.

  • On the Feature Selection tab select Database Engine Services. Then in Instance Features, select Reporting Service - Native.

  • On the Instance Configuration tab specify the name of the instance that will be used for DPM. Note that using a remote SQL Server that has an underscore character in the name isn’t supported for DPM. If there is an underscore in the name the DPM installation might fail.

  • On the Server Configuration tab, in Service Accounts specify the account that the SQL Server services should run under:

    • We recommend that you use a single, dedicated domain user account to run the SQL Server services SQL Server Agent, SQL Server Database Engine, and SQL Server Reporting Services.

    • When you create a domain user account give it the lowest possible privileges, assign it a strong password that does not expire. You can give any name to the account. But give it a name that’s easily identifiable, such as DPMSQLSvcsAcc.

  • On the Database Engine Configuration tab, use Windows authentication mode as the authentication method. In Specify SQL Server administrators, add the account you specified to the administrators list.

  • In the Reporting Service Configuration tab, in Reporting Services Native Mode, select Install and configure to perform a default installation of reporting

  • If you want to configure DPM to use a remote instance of SQL Server, note the following:

    • To set up a remote SQL Server for DPM do the following. Note that the instructions are similar for both SQL Server 2008 R2 with SP2 and SQL Server 2012 SP1:

      1. Start SQL Server Setup.

      2. On the Installation tab, click New SLQ Server stand-alone installation or add features to an existing installation.

      3. On the Product Key tab enter a valid license key and accept the terms.

      4. On the Setup Support Files tab, click Install.

      5. On the Setup Support Rules tab, correct any failures before proceeding.

      6. On the Setup Role tab, select SQL Server Feature Installation.

      7. On the Feature Selection page select Database Engine Services and the subcategories SQL Server Replication and Full—Text Search. Select Reporting Services, Management Tools – Basic, and SQL Client Connectivity SDK.

      8. On the Installation Rules tab review the rules.

      9. On the Instance Configuration tab click Named Instance and specify a name to identify the SQL Server instance for DPM.

      10. On the Disk Space Requirements tab review the information.

      11. On the Server Configuration tab, specify account settings for the SQL Server services. Note the following:

        • We recommend that you use a single, dedicated domain user account to run the services SQL Server Agent, SQL Server Database Engine, and SQL Server Reporting Services.

        • Create a domain user account with the lowest possible privileges, assign it a strong password that does not expire, and then add it to both the local Administrators group and to the SQL Server Sysadmin fixed server role in a later step. You can name this user account anything that you want but for easy identification we suggest a meaningful name such as DPMSQLSvcsAcct.

        • All services except the SQL Full-text Filter Daemon Launcher should be set to Automatic.

    • On the Database Engine Configuration tab, accept the Windows authentication mode setting. In Specify SQL Server administrators, add the user account you’ll use to connect to the remote instance when you install DPM. To add your own user account, click Add Current User. You can add additional accounts if you need to.

    • Complete the rest of the wizard with the default settings, and on the Ready to Install tab, click Install.

Install DPM support files

On the remote SQL Server you’ll need to install the DPM support files (SQLprep). To do this, on the SQL Server computer insert the DPM DVD and start setup.exe. On the DPM installation menu select DPM remote SQL prep, and follow the wizard steps to install Microsoft Visual C++ 2012 Redistributable. The DPM support files will be installed automatically.

Setup firewall rules

DPM communicates with the remote SQL Server using TCP ports, and you’ll need to open the required ports in the Windows firewall. By default the following ports are used:

  • The report server listens for HTTP requests on port 80 for HTTP requests.

  • The default instance of the database engine listens on TCP port 1443. This setting can be modified.

  • To use the SQL Server Browser service to connect to instances that don’t listen on the default 1433 port, you’ll need UDP port 1434.

  • A named instance of SQL Server uses Dynamic ports by default. This setting can be modified.

You can see the current port number used by the database engine in the SQL Server error log. You can view the error logs by using SQL Server Management Studio and connecting to the named instance. You can view the current log under the Management – SQL Server Logs in the entry Server is listening on [‘any’ <ipv4> port_number]. For information about modifying default ports, see Configure a Widows Firewall for Database Engine Access in the SQL Server TechNet library.

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft