Fusion Servicing Director SQL server required configuration settings

Fusion Servicing Director SQL server required configuration settings

Fusion Servicing Director requires Microsoft SQL Server for the database server, and the Microsoft SQL Server software must be configured with the settings described below.

You must manually install SQL Server and the appropriate service pack before you install the Servicing Director databases. For detailed information about installing, configuring, and managing SQL Server, see your Microsoft SQL Server product documentation and support resources.

Review the following:

General SQL Server information:

  • You can use Servicing Director on the Microsoft SQL Server full editions Standard, Enterprise, or DataCenter. You can also use Servicing Director on the free to download, but limited, Microsoft SQL Server Express edition. The Microsoft product bundle SQL Server Express with Advanced Services is the recommended SQL Server Express installation to use. SQL Server Express can be a good choice for a test server.

    Note: SQL Server Express has important limitations.

  • SQL Server Express is limited to lower processor usage, 1GB of RAM memory, and maximum database sizes of 4GB for SQL Server 2008 and 10GB for SQL Server 2008 R2 and SQL Server 2012. SQL Server Express does not provide the SQL Agent service often used to perform scheduled database backups, requiring you to use another database backup solution. Depending on your business use of Servicing Director, these limitations may make SQL Server Express inadequate for your business. SQL Server Express will have slower performance, so while you do not have a user limit, the more users you have, the slower SQL Server Express will perform, especially during high demand periods such as during extensive reporting and calculations. Also, with SQL Server Express, the database sizes will eventually stop new loan transactions from being added to the system when the database limit is reached.
  • You can estimate using about 1GB of database space per 1000 Servicing Director loans. Your usage may vary. Most Servicing Director data accumulates over time, providing a full audit and historical record on every loan, permanently storing most data whether or not a loan is actively being serviced or not. Using Servicing Director will typically cause the database size to grow over time, and there are no significant product provided methods to reduce the size of the database. Therefore, leave the SQL Server default setting enabled to allow databases to automatically grow or manage the disk space available to allow for the growing database size.
  • Servicing Director databases are installed with the SQL Server Simple recovery model. You can change the recovery model, but you will be required to manage the transaction log created by other recovery models. For more information about recovery models and database backups, see your Microsoft SQL Server documentation.
  • Servicing Director databases will be installed with SQL Server compatibility level 100 (SQL Server 2008). This is the required level for Servicing Director, and higher levels are not supported at this time.
  • SQL Server named instances can be used for the Servicing Director databases.
  • SQL Server Cluster servers are not supported for Servicing Director. The Servicing Director database is not tested or designed for a SQL Server Cluster server.SQL Server database replication is not supported for Servicing Director.
  • The Servicing Director database product is not tested or designed for a database with replication enabled. If replication is enabled, the Servicing Director database upgrades may fail to upgrade the replicated parts of Servicing Director without displaying an error, and report the upgrade was successfully completed. Also, some Servicing Director SQL Server transactions fail when replication is enabled on some Servicing Director tables.
  • You should apply the latest Microsoft recommended Service Packs and Microsoft Updates to your SQL Server as required by your business needs.
  • Virtual Windows servers qualify as Windows servers and are supported for your Servicing Director SQL Server. However, many customers achieve faster performing SQL Servers when their Windows platform is a dedicated physical server rather than a virtual server.

When you install SQL Server, you must select the following SQL Server configuration settings:

  • Management Tools: Servicing Director rarely requires you to use the SQL Server Management tool called SQL Server Management Studio, but you may need it at some point. Therefore, install the SQL Server management tools. 

    For full editions of SQL Server, during the SQL Server Setup Feature Selection, select the Management Tools - Complete feature to install the SQL Server Management Studio and other tools.

    For SQL Server Express, the Microsoft product bundle SQL Server Express with Tools provides the Management Tools feature, which installs the limited SQL Server Management Studio Express application. During the SQL Server Setup Feature Selection, select the Management Tools - Basic feature to install the SQL Server Management Studio Express. You can also download SQL Server Management Studio Express from the Microsoft support downloads web site.
     
  • Client Tools SDK: During the SQL Server Setup Feature Selection, select the Client Tools SDK shared feature. The Servicing Director database installation program uses SQL Server Management Objects (SMO) to communicate with your SQL server. The Client Tools SDK is one way to install SMO on your server when you install SQL Server. You can also install SMO from a related SQL Server feature pack. The Servicing Director database installation program will install SMO if it is not present.
  • Windows service account: Select a Windows service logon account with elevated privileges such as the local system account or a suitable domain account. Servicing Director will use SQL Server to access the Windows registry or other areas requiring elevated privileges. When using SQL Server 2012, the default NT Service account created by the SQL Server installation is preferred. For older versions of SQL Server, the Local System account is preferred.
  • Collation sequence: The collation of SQL_Latin1_General_CP1_CI_AS is required and will be set by default. Do not select any other collation.  Once the collation sequence is set during the SQL Server installation, it cannot be changed unless the SQL Server software is uninstalled and installed again.
  • Authentication mode: Select Mixed Mode (SQL Server authentication and Windows authentication). The SQL Server and Windows authentication mode is required for Servicing Director. With SQL Server and Windows authentication, you will be prompted to enter your choice of the SQL Server system administrator "sa" login password. Save this "sa" login password for later use, because the Servicing Director database installation and upgrades, as well as other SQL Server administrator tasks will require this login and password.

After you have installed SQL Server or SQL Server Express, you must do the following:

  1. Enable SQL OLE Automation Procedures. The current values for these options can be viewed and changed by using the sp_configure system stored procedure. For detailed information about configuring SQL Server, see the Microsoft documentation. Perform this procedure once for a new installation of SQL Server.
  2. Enable SQL CLR for hosting Microsoft .NET. The current values for these options can be viewed and changed by using the sp_configure system stored procedure. For detailed information about configuring SQL Server, see the Microsoft documentation. Perform this procedure once for a new installation of SQL Server.
  3. Confirm the SQL Server Network Configuration enables the TCP/IP protocol.
    • If you have more than one SQL Server instance on the server, you may need the SQL Server Browser service to be started and configured with startup type automatic.
    • If the SQL Server is SQL Express, then use Microsoft SQL Server support recommended procedures to disable the SQL databases "auto-close" feature on all the databases.

You should also do the following after the Servicing Director database is installed on the SQL Server:

  • Configure your backup tools to back up the Servicing Director databases. The default database names are Service and SvcEventMgr.
  • Complete a new set of backups on the new server.

ArticleNumber:

000054377

    • Related Articles

    • Upgrading SQL Server for Fusion Servicing Director 19.1

      Fusion Servicing Director 19.1 requires you to have Microsoft SQL Server version 2014 or 2016 on your server. Previous versions of Servicing Director could use older versions of SQL Server, but older versions are not supported with 19.1. The version ...
    • Upgrading Windows Server for Fusion Servicing Director

      Fusion Servicing Director is supported only on Microsoft Windows Server versions listed on the Servicing Director System Requirements. If you are not sure of your Servicing Director Windows Server version, search the Knowledge Center for the related ...
    • Fusion Servicing Director 19.1 Windows and SQL Version FAQ

      Below are selected Fusion Servicing Director 19.1 Release Windows and SQL Version frequently asked questions (FAQ). To upgrade to 19.1, is Windows Server 2016 required? No. All versions of Windows server from 2008 through Windows 2016 are supported ...
    • Preparing a Fusion Servicing Director Disaster Recovery Server

      Use this article to prepare a Servicing Director server as a recovery server before your existing production server suffers a disaster or failure. Once the disaster recovery server is prepared, it can remain offline, until you need to update it with ...
    • Creating a Servicing Director test server

      You want to create a Servicing Director test server with a copy of your production server data, and after making all the required changes, use the test server for testing and training. The procedure below is for your local IT or system administrator ...