Microsoft SQL Server

CloverDX Server > Configuration > System Database Configuration > Microsoft SQL Server

Creating Database

It is advised to use SQL Server Authentication instead of Windows Authentication. To enable it, select the server instance in Microsoft SQL Server Management Studio: go to Properties → Security → Server authentication and select the SQL Server and Windows Authentication mode. The server instance needs to be restarted.

	Note
	Make sure you have: TCP/IP `Enabled` in SQL Server Network Configuration → Protocols TCP Port set to 1433 in TCP/IP Properties → IP Addresses → IPAll

Create a new database
```
CREATE DATABASE clover_db;
```
Enable Read Committed Snapshot Isolation on the new database
```
ALTER DATABASE clover_db SET READ_COMMITTED_SNAPSHOT ON;
```

Create a new login role.

CREATE LOGIN clover WITH PASSWORD = 'clover', DEFAULT_DATABASE = clover_db;

Connect to the database.
```
USE clover_db;
```
Create a new database user.
```
CREATE USER clover FOR LOGIN clover;
```
Add a database role membership db_owner (Members of the db_owner fixed database role can perform all configuration and maintenance activities on the database, and can also drop the database).
```
EXEC sp_addrolemember 'db_owner','clover';
```

CloverDX Server Setup

Using MS SQL requires configuration of the database server:

Run Microsoft SQL Server Management Studio tool;
Create a new user under Security/Logins;
Under Databases create a new database (e.g. 'clover') for CloverDX Server, select the user from the previous step as owner of the database;
Under database Options, set the Is Read Committed Snapshot On option to True.

Example of a properties file configuration:

jdbc.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc.url=jdbc:sqlserver://localhost:1433;instance=SQLSERVERINSTANCE;database=clover_db
jdbc.username=clover
jdbc.password=clover
jdbc.dialect=org.hibernate.dialect.SQLServerDialect

Add a JDBC 4 compliant driver on the application server classpath. A JDBC driver that does not meet the JDBC 4 specifications will not work properly.

	Note
	Continue with: Encrypted JNDI or Activation