Setting up a SQL Server database and user for TrueSight Server Automation

Requirements and recommendations

• Click here for a list of supported SQL Server databases.

  • 2012 (EE, SE)
  • 2012 Cluster (EE,SE)
  • 2012 R2 (EE, SE)
  • 2014 (EE, SE)
  • 2016 (EE, SE)
  • 2017 (EE, SE)
  • 2019 (EE, SE)
    
    

  Note

  For SQL Server to support TLS 1.2, certain client components and driver updates are required, as discussed in the following Microsoft article: https://support.microsoft.com/en-us/kb/3135244

• You do not need to create the database schema if you are installing or upgrading using the unified product installer. The unified installer performs this task automatically. 

To set up a SQL Server database and user

.Failed to execute the [excerpt-include] macro.

_{Back to top}

To configure TrueSight Server Automation databases for a non-English locale (optional)

This is an optional step. To use TrueSight Server Automation in a locale other than English, follow these guidelines:

• Configure your TrueSight Server Automation databases using the settings recommended by your database vendor for that language.
•  If the database is configured for a multibyte locale or a non-LATIN-1 locale, when you set up the database schema, run the master script that corresponds to the nchar character set.

_{Back to top}

To install the SQL schema manually (not required when using unified product installer)

This section provides instructions for installing the SQL Server database schema manually.

1. Copy install scripts from the db_scripts directory in the main product .zip to a location that you can access from the SQL Server console. For information on the db_scripts directory, see Downloading-the-installation-files.
    The relevant scripts appear in the /files/configurations/dbscripts/sqlserver directory inside the TSSA<version>-<platform>64 installer zip package.
2. Open a command prompt window.
3. Change (cd) to /db_scripts/sqlserver.

4. Run the master script that corresponds to the character sets for which your database is configured, using the following syntax:
   <master_script.bat> <db_server> <db_name> <bl_user> <bl_pwd>
   For example:
   sqlserver_master.bat QLDS0002 BLADELOGIC BLADELOGIC bmcAdm1n
   Replace the variables with the following values:

   Variable	Value
   <master_script.bat>	sqlserver_master.bat if your database is configured for char/varchar character sets or sqlserver_nchar_master.bat if your database is configured for nchar/nvarchar character sets
   <db_server>	Name of the database server. If the server uses a nonstandard port, the server name and port number must be enclosed in quotation marks, as shown in the following example: "QLDS0002,1381" To use a named server instance, append the named instance, including the complete path, as shown in this example: sqlserver_master.bat <db_server>\<instance_name> <db_name> <db_user> <db_password>
   <db_name>	Name of the TrueSight Server Automation database that you created while setting up the database
   <bl_user>	Logon name for the TrueSight Server Automation database user
   <bl_pwd>	BMC  Server Automation database user password

_{Back to top}

SQL database maintenance: Recommendation for gathering statistics

As with other products which use Microsoft SQL database, some performance problems in a TrueSight Server Automation environment can be caused by stale SQL statistics on the TrueSight Server Automation schema, due to changing data volumes or changes in column values. BMC strongly recommends that you gather statistics for the core TrueSight Server Automation database one time per week.

Use the EXEC sp_updatestats command to run the SQL server built-in procedure against all tables in the schema, to gather statistics and optimize the database. For more information on gathering statistics, see Microsoft documentation.

You can also refer to the Health and Value Dashboard for additional statistics about the database server and information you can use for troubleshooting problems. To access the dashboard, see Using the Health and Value Dashboards.

_{Back to top}

Where to go from here

Configuring-the-file-server