About LLDBs
LeasePak Documentation Suite NETSOL website
Overviews

Overviews

About LeasePak Logical Databases (LLDBs)

About LLDBs - LeasePak Logical Databases
A LeasePak Logical Database (LLDB) is a an instance of a relational database. It contains Tables, Indexes, Views, Stored Procedures, and Triggers.
  • Tables have columns and rows, each row consisting of the same set of columns as every other row in the same table, but between rows, the different columns may contain different data, or the same data, or no data at all.
  • Indexes are made of certain columns from the table, selected to allow the retrieval of a single row using a minimum of identifying data, and also keeping the rows sorted according to a set of columns.
  • Views simply present subsets of the columns of a table as if they were a table themselves.
  • Stored procedures are programs written in the database's own SQL programming language dialect, which can be called by application code.
  • Triggers are programs that run when certain tables are modified by applcation code; in order to maintain integrity of the LLDB data, they perform maintenance on the table and related tables in response to these modifications.
LeasePak uses one of two alternative Database Management Systems (DBMS)es: Oracle or Sybase.
While these two systems are very different in many ways in their organization and terminology, they are both relational database systems, and that means they ultimately support the basic concepts outlined above.
These basic concepts allow LeasePak to deal with both DBMSes using a common metaphor, and thus the application code of the LeasePak server is only occasionally concerned with which DBMS is in use.

In Oracle, the entire DBMS is considered a "database", while in Sybase, the DBMS encompasses many "databases".
Under Oracle, a collection of tables, indexes, procedures and triggers devoted to a particular use is called a "schema". In Sybase, this is called a "database".
In LeasePak, they are both called "LeasePak Logical DataBases", or LLDBs. They both contain the same tables, indexes, and views, and many equivalent procedures and triggers.
In addition to the data maintained by the DBMS, there are certain LeasePak tables that are considered unsuitable for a relational database system; these, and other ASCII-based data files, are kept in the $udata directory of the LeasePak database environment in question. These are intrinsic parts of the LLDB, and must be backed up with the contents of the DBMS portion of the LLDB.
Together with certain basic structures in the LeasePak drivers, these all combine to form a single API, against which the LeasePak server is implemented.