Show Contents / Index / Search

Setting Up a SQL Server Database

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

The 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.
  • The Databridge Client for SQL Server uses ODBC, which places no restrictions on the user’s schema when using SQL Server 2005 or later.
  • You can use primary keys with non-clustered indexes without having to edit the scripts generated by the client.
  • The Databridge Client for SQL Server supports the data type bigint and the SQL Server 2008 data types date, datetime2 and time. To maintain backward compatibility for these data types, enable the parameters use_bigint, use_date, use_datetime2 and use_time (respectively).

To set up a SQL Server database

  1. If you use Integrated Windows Authentication with the 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, select Properties, and 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 the 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, perform a custom installation of Microsoft SQL Server and set the Sort Order to Dictionary, case-sensitive. The only way you can change sort order case-sensitivity is via installation.