Specifications
LSM USER MANUAL 
Correct in: Juli 2010 v0.8 
Page 10 
3.0  INSTALLATION AND CONFIGURATION 
3.1. GENERAL 
3.1.1  DEFINITION OF “DATABASE-BASED SOFTWARE SYSTEMS” 
DATABASES 
Databases are structured memories for large quantities of data about objects in our 
environment. They are structured by arranging the data into tables which are made 
up of a certain number of data records. The data records are in turn made up of data 
fields. This allows the individual data to be queried, modified and compared with 
ease. 
Example 
The Deutsches Telefonverzeichnis (German phone directory) database is made up of 
a certain number of tables (local phone books), these tables are made up of data 
records (personal entries), the data records are in turn made up of data fields 
(surname, first name, address, phone number). 
DATABASE SYSTEMS 
Database systems are made up of the data (database) and a so-called database 
management system. 
Behind the database management system (or database engine) is a program which 
helps to create, modify and evaluate data. These types of systems include e.g. the 
Microsoft SQL Server, or, in the case of the LSM software system, the Advantage 
Database Server from Sybase. 
The interface to the user or to the user software (GUI in the case of the LSM software 
system), is a query language, e.g. SQL (Structured Query Language). This language 
allows databases to query and evaluate or modify content. 
The database contains the data itself. Relational databases, such as the Microsoft 
SQL Server or Sybase’s Advantage Database Server, store data in the form of tables. 
It is possible to create, link and query several tables. Together, these tables form the 
database. LSM, which manages a locking plan, has to write and link together in 
corresponding tables all the relevant data, such as transponder data, personal data 
and information about locks, doors, areas and groups. 
If a new person is created, all the detailed information such as employee number, 
name, date of birth etc. is entered as a new row in the corresponding Persons table 
and thereby adopted as a new data record. This data record is then of course 
available to the Transponder table as a new possible transponder owner. LSM will 
check that even though one person can own more than one transponder, one 
transponder can only have one owner. The relationship between the Transponder 
and Locks tables is different. On the one hand, one transponder can of course trigger 
several locks, but on the other hand one lock will of course respond to several 
transponders. LSM must therefore check the authorisations as well as the 
assignment. All of this happens automatically in the background and at first the user 










