Specifications

LSM USER MANUAL
Correct in: Juli 2010 v0.8
Page 34
4.0 DATABASE
The ADS multi-user version of the database engine is based on a client/server
architecture. This minimises the network traffic between the client and server and
controls transaction management. Each instance of database access is usually linked
to several actions, which together form a transaction. If the client computer which
runs the LSM software is interrupted during this type of transaction, the database can
be completely reverted to the status it was in before the transaction was started,
thereby retaining data consistency in full.
4.1. STRUCTURE
• Tables
The data is kept in the database in the form of tables.
• Indices
To speed up the search for certain entries, indices are created for the relevant
columns.
• Referential integrity
Relationships between the tables are set up. The database engine uses these
to ensure data consistency.
• Stored procedures
Stored procedures are functions which handle complex tasks. They are saved
directly in the database and can be called up by LSM with ease. This includes
e.g. the task of authorising a transponder for a lock.
4.2. SECURITY
• User-oriented access to data
Individual rights can be assigned to each software user. After logging on with
his or her database log-on name and password, the user can then access the
database with his or her individual rights.
• Encrypting tables and communication
The tables in the database and all application communication with the
database via the network is encrypted with a 160-bit password and data is
only transferred incrementally, so any data which is tapped is not useful.