Updating the Microsoft SQL Server database

When you update your Spotfire Server to a newer version, any user action database logging you have configured earlier will most likely continue to work. If there are new views available, you might want to add them.

About this task

See also Update action logs and system monitoring.

Using a text editor, open the file create_actionlog_db.sql.
Remove the lines above use $(ACTIONDB_DBNAME) and change this line to use spotfire_actionlog. The script will only create the views that do not already exist.

Tip: If you are familiar with SQL tools, it is probably the fastest to log in to the database spotfire_actionlog and run the SQL in your edited create_actionlog_db.sql.

Otherwise, you can tweak the existing scripts to run the SQL.

Before you begin

You must have credentials to the action log database.

Procedure

In the new installation kit directory, browse to \scripts\mssql_install\actionlog.
Using a text editor, open the script file create_actionlog_db.sql and edit it as described above.
Using a text editor, open the script file create_actionlog_db.bat (on Windows) or .sh (on Linux).
In the file, remove the section "Create the Spotfire Action log database user". Then, enter the information for DBSERVER_CONNECTIDENTIFIER, ACTIONDB_USERNAME, and ACTIONDB_PASSWORD.
Run the edited script the same way as when you enabled the database logging.

What to do next

The installation kit also includes a library import file, which contains information links for logging categories, as well as a sample Spotfire analysis file, which you can use to gain insight about your system. This import file might be updated with a new release and, if so, you can import it again. See Importing a library for analyzing action logs in Spotfire Analyst for more information.