Databridge Installation Guide > Setting Up a Relational Database > Setting Up a SQL Server Database

Setting Up a SQL Server Database

Use the following procedures to set up a Microsoft SQL Server database for use with Databridge Client for SQL Server.

Databridge Client uses only the ODBC data source parameter to connect to ODBC. The ODBC data source parameter provides the database and server parameters required to run BCP.

In addition, the following notes apply to Microsoft SQL Server:

  • The default schema for the Databridge user determines the ownership of tables.

  • Databridge Client for SQL Server uses ODBC, which places no restrictions on the user’s schema.

  • You can use primary keys with non-clustered indexes without having to edit the scripts generated by the client.

To set up a SQL Server 2016 database

NOTE:Starting with SQL Server 2016, SQL Server Management Studio no longer allows you to add “NT AUTHORITY\SYSTEM” to the sysadmin role.

The available options are:

  1. Run the service under the user account that is setup to run the command line client (dbutility) and use Integrated Windows authentication.

  2. Setup the database to use SQL Server authentication and run the service under the built-in system account.

To set up a SQL Server 2012 or 2012 R2 database

  1. If you use Integrated Windows Authentication with Databridge Client on Microsoft SQL Server 2012 and are running the service using the default account, you must add NT AUTHORITY\SYSTEM to the sysadmin Server Role. In the Microsoft SQL Server 2012 Management Studio, use the left pane to navigate to Security > Server Roles, right-click sysadmin, click Properties, then click the Add button.

  2. Create an ODBC data source, unless one already exists. See the following procedure for instructions.

    IMPORTANT:When creating ODBC data sources for Databridge Client, use the Microsoft SQL Server Native Client driver. The Microsoft SQL Server driver doesn't support columns longer than 32K, multi-threaded updates, and several other important Databridge features.

  3. Make sure that you have enough disk space free for the Microsoft SQL Server database.

  4. If your DMSII data sets contain case-sensitive ALPHA key items, using the default Microsoft SQL Server installation may result in duplicate keys. To avoid this, make certain the collating sequence for the client database is set to a case-sensitive or binary collation.