Preparing the SQL Server database for Spotfire

You can use either scripts or command-line commands that are provided with Spotfire Server to configure your SQL Server database server to store your Spotfire database. First, prepare your SQL Server database, and then select the best method for your system to create the Spotfire database.

About this task

If you plan to use one of the provided scripts to configure an SQL Server database server for storing the Spotfire database, then configure the Spotfire database before running the Spotfire Server installer.
If you plan to create a Spotfire database using the CLI command create-db, first install the Spotfire Server. For more information about this option, see Creating a Spotfire database using the command create-db.

Note: If you plan to configure Integrated Windows authentication (IWA) between Spotfire Server and the Spotfire database in SQL, see Setting up the Spotfire database (SQL Server with Integrated Windows authentication).

Before you begin

You have downloaded and unzipped the Spotfire Server installation kit from the TIBCO eDelivery web site. For instructions, see Downloading installation software.

Note: To reduce the likelihood of encountering issues like

Transaction (Process ID 68) was deadlocked on lock resources
				with another process and has been chosen as the deadlock victim. Rerun the
				transaction

, apply MVCC/Row versioning mode by using the setting READ_COMMITTED_SNAPSHOT.

Procedure

User name and password authentication, if needed.
Download the command-line database tools (for example, sqlcmd) and place them in the system path.
Configure the TCP/IP port for listening on the port, and set up case-insensitive collation for the Spotfire database.

What to do next

You can create the Spotfire database using the provided script or the command-line command create-db.

Note: Databases with self-signed certificates

Set up your database server for encrypted connections, with a valid, not self-signed, server certificate. For more information see Fixing Microsoft SQL Server JDBC driver-related issues.