Microsoft SQL database considerations - Metasys - LIT-12011279 - General System Information - Metasys System - 13.0.50

All versions of SQL Server software must be set up in Mixed Mode Authentication and configured to use both the TCP/IP port 1433 and Named Pipes protocols. When upgrading to a new version of SQL Server software, you must preserve this configuration because the upgrade process turns off the network protocols.

Consider the following general database recommendations:

• The unified Metasys server is incompatible with server clusters. For a split Metasys server (ADX), the database server computer can be part of a server cluster.

• Run SQL Server databases in Simple Recovery mode to reduce the risk of system failure due to lack of disk space. Simple recovery mode allows you to restore from the previous night’s backup only. For point-in-time recovery, run the databases in Full Recovery mode and back up your transaction log at least every 24 hours. Failure to perform Transaction log backups at this interval eventually results in system failure due to lack of available disk space.

• Confirm that SQL Server database backups are being performed correctly and consistently to prevent data corruption. Check periodically to make sure the backups are present and restorable. Create backups using the Metasys Database Manager or the tools listed in Database management: SQL Server tools. Each backup should be saved in separate locations.

• Check periodically to make sure your database indexes are healthy because fragmented indexes greatly reduce database performance. Rebuild indexes as necessary using tools available from the IT department or the Metasys Database Manager. See Database management: Metasys Database Manager and Database management: SQL Server tools.

• Do not use third-party backup programs to backup the Metasys databases. Instead, use the tools provided by SQL Server software or use the Metasys Database Manager.

• To create and manage the Metasys Server databases and SQL Server user accounts that are used during Metasys Server runtime, the Metasys Server software installation program requires a user account with administrator access to SQL Server databases during installation. The account may be either a SQL Server user account or a Windows operating system user account that has the required privileges. After the installation program creates the Metasys Server databases and SQL Server user accounts, the administrator account is no longer used. You may remove SQL Server database administrator rights from this user account.

• During runtime, the Metasys Server software uses the SQL Server user accounts that were created by the Metasys Server installation program. For information about managing the SQL Server user accounts used by the Metasys Server (account rename and password changes), contact Johnson Controls technical support.

• SCT uses virtual service accounts with integrated authentication. Windows authentication is more secure than database authentication, as it uses a certificate based security mechanism. With virtual service accounts, the management of account credentials is handled by the Windows operating system so no manual management is required.

The default location for Metasys system databases is determined by database default locations setting in SQL Server. The following table lists the databases that the Metasys system creates.

In addition, the online archive, MetasysSCT, SCTTranslationDictionary, and any current Metasys SCT archive databases also may be present. SCT archive database names are user configured.

For information on installing SQL Server software for use with a Metasys system, refer to the SQL Server Installation and Upgrade Instructions (LIT-12012240), Metasys Server Installation and Upgrade Instructions (LIT-12012162), or Metasys Server Lite Installation and Upgrade Instructions (LIT-12012258).