Skip to content

SQL Server

To connect to SQL Server, the solution uses the Microsoft JDBC driver for SQL Server.

Installing the driver

This driver is included in the distribution, there are no additional steps required.

Configuration

ParameterValue
cfg.server.local.config.urljdbc:sqlserver://<server>:<port>;databaseName=<database>;encrypt=true;sendStringParametersAsUnicode=false
cfg.server.local.config.userYour SQL Server username
cfg.server.local.config.passwordYour SQL Server password
cfg.server.local.config.drivercom.microsoft.sqlserver.jdbc.SQLServerDriver

The URL must include sendStringParametersAsUnicode=false to prevent SQL Server from converting the parameters to Unicode and greatly improve performance.

Using a specific instance

If you are using a specific instance of SQL Server, you can specify it in the URL by adding instanceName=<instanceName> to the end of the URL.

Example: jdbc:sqlserver://localhost:1433;instanceName=SQLEXPRESS;databaseName=SFiler;encrypt=true;sendStringParametersAsUnicode=false

Using Windows Authentication

If you are using Windows Authentication, you can set the integratedSecurity property to true in the URL. This will cause the driver to use the current Windows user credentials to connect to the database.

This requires additional DLLs to be installed on the machine where S-Filer Portal is running. You should download the sqljdbc_auth.dll file from the Microsoft website and copy it to the [Install folder]/server/ext/lib folder.

Example: jdbc:sqlserver://localhost:1433;integratedSecurity=true;databaseName=SFiler;encrypt=true;sendStringParametersAsUnicode=false