Overview

For best results and to optimize the features of the Jive installation, configure and maintain the Microsoft SQL Server database based on the vendor's requirements and apply these Jive best practices.

Information

Installing Microsoft SQL Server DB

• SQL Server installations may be standalone instances or clustered. Mirrors with automatic-failover are not supported, but you can use mirrors for redundancy or DR purposes.
• The core application and the Activity Engine run using the jTDS MSSQL Driver version 1.3.x or higher. The Analytics database is not supported on MSSQL.

• Set your classpath to include the jTDS Driver by running the following from a command line as the jive user:

  jive set webapp.custom_classpath_additions path/JDBC_Driver.jar

  where path is the path to the jTDS JDBC driver and JDBC_Driver.jar is the name of the JAR file.

  Reminder:

  If SSL is implemented to secure traffic between the web application nodes and the database, an issue with the jTDS driver can prevent the Jive application from starting. As a workaround for this issue, run the following commands on each web application node:

  jive set webapp.custom_jvm_args " -Djsse.enableCBCProtection=false"
  jive set eae.custom_jvm_args " -Djsse.enableCBCProtection=false"

Recommendation for Typical Installations

SQL Server instance default collation is case-insensitive and accent-sensitive. If database collation is not specified, the instance collation is used. Latin1_General_CI_AS is recommended for typical installations. In special cases where the Jive platform is configured to allow case-sensitive user names (for example, where jsmith and JSmith are different logins), Latin1_General_CS_AI is required so that case sensitivity may be utilized in indexing and string searches.

You can find more information on adjusting SQL Server settings in the SQL Server documentation: Setting and Changing the Server Collation Setting and Setting and Changing the Database Collation.