MSSQL Setup

Warning

This article is for general guidance. Always work with your DBA when setting up a production database. If you have any questions, contact Senzing Support. Support is 100% FREE!

Info

When upgrading from Senzing v3 to Senzing v4, there are changes made to the entity repository database schema. See Upgrading the Senzing Repository Schema To V4

Prerequisites

A user, password, IP or hostname, and database from your DBA that has DDL and DML permissions to an MSSQL database you have created
A MSSQL database tuned for Senzing
The MSSQL Linux client/driver installed

Info

See https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server

Add the Senzing Schema

Info

If applicable, your DBA should set up the database schema. If you have any questions, contact Senzing Support. Support is 100% FREE!

sqlcmd -U g2user -S 127.0.0.1 -d G2 -i <senzing_project_path>/resources/schema/szcore-schema-mssql-create.sql

Info

<senzing_project_path> refers to the path specified with the /opt/senzing/er/bin/sz_create_project command when creating a project.

Configure odbc.ini

Edit the /etc/odbc.ini file and add the following entry:

[MSSQL]
Driver = ODBC Driver 18 for SQL Server
Database = <your database name>
Server = <your database IP address>, 1433

Info

1433 is the default MSSQL port number, you need to change this is your port value differs.

Configure the CONNECTION string

Edit your SENZING_ENGINE_CONFIGURATION_JSON environment variable or sz_engine_config.ini file:

Edit the new CONNECTION mssql://username:password@server:port:database/?driver=mssqldriver entry where:

username = MSSQL username
password = password for the above username
server = IP address or hostname of the MSSQL Server
port = port number of the MSSQL Server
database = actual database name (not the DSN)
/?driver=mssqldriver = remove unless using custom driver

Update Database with the Senzing ER Configuration

A Senzing instance is configured with a Senzing Entity Resolution configuration. On a fresh installation this configuration needs to be registered in the Senzing database.

See Updating Database with Senzing ER Configuration

Info

If you have any questions, contact Senzing Support. Support is 100% FREE!