What is it?

1

Separates ‘old’ data

Separates ‘Old’ infrequently used data from main Operational data

2

Archive database

Data is moved into a customer archive database at regular intervals

3

Resources

Frees resources and improves system performance

4

Efficiency

Your BisTrack database is maintained as ‘lean’ as possible

5

Database size

Reduces databases size by 25% to 50% - customer defined

6

Consultation

Guidance and recommendations are provided

Benefits

 

Faster SQL server responses

  • SQL Server will service its requests from a smaller set of data

  • SQL Server will scan smaller index and table data

Faster hardware responses

  • SQL Server will store more of the relevant BisTrack data in memory

  • Accessing data in memory is significantly faster than accessing data on physical storage

Reduced hardware requirements

  • By keeping BisTrack database growth in check, the need to increase memory, CPU and disk storage will be reduced

Configuration


BisTrack tables

Archiving module can operate on 80+ BisTrack tables.

Configuration tables

Table configuration specifies: 

  • Table “active” flag

  • Data retention period

  • Archive/Deletion method

Process

 

Step 1

CUSTOMER SPECIFIC ARCHIVING DATABASE IS CREATED

Step 2

AGREE CONFIGURATION STRUCTURE

  • Define customer specific formats for emailing invoices, credit notes & statements (optional)

  • Improved efficiency, auditing  and processing time

Step 3

INITIAL ARCHIVE RUN AND ONGOING QUARTERLY ARCHIVES

FAQs

Can I access the data within the archive database?

Yes – archived data is accessible, but for the benefit of performance, the appropriate retention levels should be set to make this unnecessary.

Can the archive process be run against a table that is not in sync?

No – the pre-processing archive checks prevent an archive process occurring against a table if the file structures do not match.

 

Are table structures maintained to match changes in BisTrack?

Yes – archive table structures are verified before each archive run and modified where necessary.

How frequently should the archive routine be run?

Quarterly – to keep both the files sizes and process times to a manageable level.

Pricing

 

Archive module (OTLF)

£3,000

Module cost & Installation

Full implementation in Azure or On-Premise infrastructure environment

Initial setup & archive

£2,394

Configuration table setup

Agree configuration structure of tables, along with initial archive.

Quarterly archive fee

£798

Commitment

Module to be implemented for a minimum of twelve months.

Summary

 

Step 1

CONSIDERATIONS

  • Do I have more than three years of BisTrack data?

  • Are my BisTrack responses becoming slower? 

Step 2

WHAT IS ARCHIVING?

  • Frees resources and improves system performance 

  • Reduces database size by 25% to 50% - customer defined

Step 3

BENEFITS

  • Faster SQL server responses

  • Faster hardware responses

  • Reduced hardware requirements