You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Home > Access It! Universal.NET > Access It! Universal.NET Database Sizing Estimates
Access It! Universal.NET Database Sizing Estimates
print icon

Overview

The AIUniversal and AIUEvent databases differ in their size growth based on how the system is utilized. For example, a system utilizing cardholder images would be much larger in size compared to a system not using cardholder images. The data outlined below was calculated from an in-house test. It should only be used as an estimate and not used for any exact approximations.

AIUniversal Table Size Estimates

Cardholders

1000 cardholders, with every possible field containing the maximum length resulted in a table size of 4.5MB.

Images

1000 cardholder images, utilizing the default size of 400x320 resulted in a table size of 320MB.

Cards

1000 cards, utilizing both an active and expire date resulted in a table size of 1MB.

CardAccessLevel

1000 cards, with each card having a single access level assigned resulted in a table size of 0.4MB.

Reader

64 readers, with each configured at the default values resulted in a table size of 0.6MB.

Input

128 inputs, with each configured at the default values resulted in a table size of 0.2MB.

Output

126 outputs, with each configured at the default values resulted in a table size of 0.1MB.

AIUEvents

A typical AIUEvent database will grow to between 135-160MB in size for every 1 million records. By default, Access It! Universal.NET performs a system archive every time the AIUEvent database reaches 1 million events. This value can be modified using the database configuration utility (Start | Programs | Access It! Universal.NET | Utilities | Database Configuration Utility). On an hourly basis the Access It! Universal.NET service will compare the number of rows within the AIUEvents database to the configured Archive Settings. If the threshold is reached an archive is performed and the following steps are taken.

  1. A brand new AIUEvents database is created
    The AIUEvents database is named after the year, month, day, hour, minute, second it was created.
  2. The stored procedure within the AIUniversal database is rebuilt so any new events are placed in the newly created database 
  3. The views vwEvents and vwEvents_composite are rebuilt so that the Access It! Universal service queries the old and new AIUEvents database 

scroll to top icon