Migration of File Tracking entries after upgrade to ST 5.3.3 for Microsoft SQL database

Due to a structural change of database tables related to File Tracking, the data related to transfers, made before upgrade, should be migrated to the new tables created on upgrade in order to be visible in SecureTransport 5.3.3 File Tracking. If the migration is skipped all the details related to transfers made before upgrade will NOT be visible on the File Tracking page.

If migration is NOT needed, skip the migration instructions and go directly to section Dropping the old tables.

For instructions regarding File Tracking migration on Microsoft SQL or the embedded MySQL DB, refer to the following articles:

• for embedded MySQL DB
• for Oracle DB

Prerequisites

IMPORTANT NOTE: Make a backup of your database before proceeding with the migration.

Make sure that all SecureTransport services are stopped.

Execute the following command to stop all services:

<FILEDRIVEHOME>/bin/stop_all

Migrating the File Tracking records

1. As MSSQL database admin execute the following statement ([schemaName] is the database user SecureTransport is running with):

ALTER DATABASE [schemaName] SET RECOVERY SIMPLE

2. Connect to database with the user SecureTransport is running with.

3. Open the filetracking-migration-mssql.sql migration script that can be found attached to this article and copy its contents.

4. Paste it as a new single query in Microsoft SQL Server Management Studio.

5. Change the following line from the script code to point to the database user name SecureTransport is running with:

SET @schemaName = 'TODO: enter schema name here';

6. Execute the script with the permissions of the database user SecureTransport is running with.

7. Wait for the migration to complete (there should be an output in the Management Studio Console).

8. As the MSSQL database admin execute the following statement ([schemaName] is the database user SecureTransport is running with):

ALTER DATABASE [schemaName] SET RECOVERY FULL

Old tables should be dropped using the instructions in the next section.

Dropping the old tables

As the old tables won’t be used after upgrade they should be dropped using the attached filetracking-migration-mssql_drop-old.sql script.

1. Connect to database with the user SecureTransport is running with.

2. Open the filetracking-migration-mssql_drop-old.sql script and change the first line by entering the name of the user SecureTransport is running at the place of [YOUR_DATABASE_NAME_HERE].

3. Copy the script and execute it as a single query in Microsoft SQL Server Management Studio.