To ensure best performance of the database, Softrip includes a tool to delete old data. This process deletes Reservation, Product, and Accounting data based on their relevant dates. This process removes old data, ensuring that the main production database only includes data that is relevant to daily operation of the system.

Inputs

The archiving process is a stored procedure named proc_ArchiveAllData. This stored procedure should be run on the main production database.

• @Server: The database server that hosts the archive database (e.g. MSSQL-ARCHIVE). Archived /deleted records will be copied to this database before they are deleted from the main production database.

• @DBName: The database name for the archive database (e.g. SoftripNetArchive). Archived /deleted records will be copied to this database before they are deleted from the main production database.

• @ResCutoffDate: The last departure date for which to keep reservation data. Reservations departing before this date will be deleted.

• @ProdCutoffDate: The last product date for which to keep Product data. Products that end before this date will be deleted.

• @MrkCutoffDate: The last date for which to keep CRM/Marketing data.

• @AccCutoffDate: The last date for which to keep Accounting data. Accounting data for dates before this date will be deleted.

Process

Input Validation

1. Make sure there's no outstanding contingent liability in the period we last closed, for bookings in the archived period.

   1. Process stops here if we have outstanding contingent liability.

...

1. Delete transaction detail (AccTransDetail) records whose transaction date is before the @AccCutoffDate from the main production database

2. Delete transactions (AccTrans) records whose transaction date is before the @AccCutoffDate from the main production database

3. Delete month end (AccMonthEnd) records whose transaction date is before the @AccCutoffDate from the main production database

Notes

• The archive process can take a VERY long time, especially if it is run for a large date range (for example, running it for the first time with cutoff dates that include many years of data). While this process is running, your Softrip applications may run into timeout errors and other errors or performance issues.

• Once the archive process has completed, we recommend that SQL maintenance tasks are run:

  • Back up and truncate the main production database’s SQL transaction log file

  • Rebuild all table indexes on the main production database