Microsoft SQL Server Database Best Practices

For best results, configure and maintain your Microsoft SQL database according to the vendor's requirements and use the Jive best practices.

Installation

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 will 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 typing the following from a command line as the jive user:
```
jive set webapp.custom_classpath_additions path/JDBC_Driver.jar
```
where path/to/driver is the path to the jTDS JDBC driver and JDBC_Driver.jar is the name of the JAR file.

Note:

If you have implemented SSL to secure traffic between the web application nodes and the database, an issue with the jTDS driver will prevent the Jive application from starting. To work around this problem, 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"

Case Sensitivity

SQL Server instance default collation is case-insensitive, but accent-sensitive. If database collation is not specified, the instance collation will be 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 would be different logins), Latin1_General_CS_AI is required so that case sensitivity may be utilized in indexing and string searches.

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