| Microsoft Jet Database Engine |
Article Index for Microsoft |
Website Links For Microsoft |
Information AboutMicrosoft Jet Database Engine |
| CATEGORIES ABOUT MICROSOFT JET DATABASE ENGINE | |
| database engines | |
| microsoft database software | |
|
The Microsoft Jet Database Engine is a Database Engine on which several Microsoft products were built. A database engine is the underlying component of a Database , a collection of information stored on a computer in a systematic way. The first version of Jet was developed in 1992 , consisting of three Modules which could be used to manipulate a database. JET stands for ''Joint Engine Technology'', sometimes being referred to as ''Microsoft JET Engine'' or simply ''Jet''. Microsoft Access , Microsoft Exchange Server and Visual Basic use or have used Jet as their underlying database engine. It has since been superseded, however, by Microsoft Desktop Engine (MSDE) and no longer exists as a component of Microsoft Data Access Components (MDAC). Jet databases can be upgraded (or in Microsoft parlance, "up-sized") to an MSDE database. ARCHITECTURE Jet allowed the manipulation of Relational Database and was part of a Relational Database Management System (RDBMS). It offered a single Interface that other software could use to access Microsoft databases and provided support for security, Referential Integrity , Transaction Processing , Index ing, Record , page locking and data replication. In later versions, the engine was extended to be able to run SQL queries, store character data in Unicode format, create Database Views and allowed bi-directional replication with Microsoft SQL Server. There were three modules to Jet. One was the ''Native Jet ISAM Driver'', a Dynamic Link Library (DLL) that could directly manipulate Microsoft Access database files (MDB), which was a modified form of an Indexed Sequential Access Method (ISAM) database. Another one of the modules were the ''ISAM Drivers'', DLLs that allowed access to ISAM databases, among them being Xbase , Paradox , Btrieve and FoxPro files. The final module was the ''Data Access Objects'' (DAO) DLL, DAO allowed programmers access to the Jet engine. It was basically an Object-oriented data language used by Access Basic and Visual Basic programmers to access Jet. Locking Jet allowed multiple users to access the database concurrently. To prevent that data from being corrupted or invalidated when multiple users tried to write to the database, Jet employed a data write locking policy. Any single user could only modify those Database Record s (that is, items in the database) to which they had applied a Lock that gave them exclusive access to the record until the lock was released. Up to Jet 4, a page locking model was used, and in Jet 4 a record locking model was employed. Microsoft databases are organised into data "pages", which are fixed length (2 KB ) data structures that divide up the database. Data is stored in "records", but these are of variable length and so may take up less or more than one page. The page locking model worked by locking the pages, instead of individual records, which though less resource intensive also meant that more than one record might be locked at any one time. Record locking was introduced in Jet 4. There were two mechanisms that Microsoft used for Locking : ''pessimistic locking'', and ''optimistic locking''. With pessimistic locking, the record or page is locked immediately when the lock is requested, while with optimistic locking, the synchronization is delayed for transactions until the operations are actually performed. Conflicts are less likely to occur with optimistic locking; since the record is locked for a shorter duration of time, there is a lesser chance of someone needing to access it while it is locked. However, it cannot be certain that the update will succeed because another user could potentially update the record first. With pessimistic locking, the update is guaranteed to succeed once the lock is obtained, but other users are unable to make their own changes until the lock is released. Lock conflicts, which either require the user to wait, or cause the request to fail (usually after a timeout) are more common with this policy. Transaction processing Jet supported Transaction Processing for database systems that had this capability (ODBC systems had one level transaction processing, while several ISAM systems like Paradox did not have transaction processing capability). Transactions are a series of operations performed on a database that must be done together — this is known as Atomicity and is a part of ACID (Atomicity, Consistency, Isolation, and Durability), concepts considered to be the key transaction processing features of a Database Management System . For transaction processing to work (until Jet 3.0), the programmer needed to begin the transaction manually, perform the operations needed to be performed in the transaction, and then commit (save) the transaction. Until the transaction is committed, changes are made only in memory and not actually written to disk . Transactions have a number of advantages over independent database updates. One of the main advantages is that transactions can be abandoned if a problem occurs during the transaction. This is called rolling back the transaction, or just rollback, and it restores the state of the database records to precisely the state before the transaction began. Transactions also permit the state of the database to remain consistent if a system failure occurs in the middle of a sequence of updates required to be atomic. There is no chance that only some of the updates will end up written to the database; either all will succeed, or the changes will be discarded when the database system restarts. With ODBC's in-memory policy, transactions also allow for many updates to a record to occur entirely within memory, with only one expensive disk write at the end. Implicit transactions were supported in Jet 3.0 onwards. These are transactions that are started automatically after the last transaction was committed to the database. Implicit transactions in Jet occurred when an SQL DML statement was issued. However, it was found that this had a negative performance impact, so in Jet 3.5 Microsoft removed implicit transactions when SQL DML statements were made. Data integrity . In this example, there is a foreign key (artist_id) value in the album table that references a non-existent artist — in other words there is a Foreign Key value with no corresponding Primary Key value in the referenced table. What happened here was that there was an artist called "Aerosmith", with an artist_id of "4", which was deleted from the artist table. However, the album ''Eat the rich'' referred to this artist. With referential integrity enforced, this would not have been possible.]] Jet enforces Entity Integrity and Referential Integrity . Entity integrity is one of the key concepts of Relational Database s, and ensures that no record is able to be duplicated and also ensures that no field (or group of fields) that identify the record (the Primary Key ) are NULL . Thus, Jet supports primary keys. Referential integrity is where the fields that identify data that exists in a database tables (the Foreign Key ) must correspond with an existing primary key in that database. If a foreign key value exists that does ''not'' have a corresponding primary key in the referenced table, then the referential integrity is broken and the data between tables will no longer be synchronised. For instance, a music lover may have a database that stores information about his record collection, and need to store data about an artist and his/her music. In this example, the artist can record many albums, but the album is only recorded by one artist, so two database tables are created: Artist and '''Album'''. The ''Artist'' table uses the field ''artist_id'' as its primary key, and the ''Album'' table uses ''album_id''. The album table references the artist table using ''artist_id'' as a foreign key. If, for some reason, an artist is deleted and there is an album in the system that contains a reference to that artist then the referential integrity of this record would become broken. Jet will by default prevent this from happening. Jet is also capable of doing cascading updates and deletes. With cascading deletes enabled for the ''Album'' table, if the artist in the previous example were deleted, then all the artists' albums would also be deleted. Jet also supports "business rules" (also known as "constraints"), or rules that apply to any column to enforce what data might be placed into the table or Column . For example, a rule might be applied that does not allow a date to be entered into a date_logged column that is earlier than the current date and time, or a rule might be applied that forces people to enter a positive value into a numeric only field. Security Access to Jet databases is done on a per user-level. The user information is kept in a separate system database, and access is controlled on each object in the system (for instance by table or by query). In Jet 4, Microsoft implemented functionality that allowed database administrators to set security via the SQL commands CREATE, ADD, ALTER, DROP USER and DROP GROUP. These commands were a subset of ANSI SQL 92 standard, and they also applied to the GRANT/REVOKE commands. When Jet 2 was released, security could also be set programmatically through DAO . Queries Queries are the mechanisms that Jet uses to retrieve data from the database. They can be defined in Microsoft QBE (Query By Example), through the Microsoft Access SQL Window or through Access Basic's Data Access Objects (DAO) language. These are then converted to an SQL SELECT statement. The query is then Compile d — this involves parsing the query (involves syntax checking and determining the columns to query in the database table), then converted into an internal Jet query object format, which is then Tokenized and organised into a tree like structure. In Jet 3.0 onwards these were then optimised using the Microsoft Rushmore query optimisation technology. The query is then executed and the results passed back to the application or user who requested the data. Jet passes the data retrieved for the query in a Dynaset . This is a set of data that is dynamically linked back to the database. Instead of having the query result stored in a temporary table, where the data cannot be updated directly by the user, the dynaset allows the user to view and update the data contained in the dynaset. Thus, if a university lecturer queried all students who received a distinction in their assignment and found an error in that student's record, they would only need to update the data in the dynaset, which would automatically update the student's database record without the need for them to send a specific update query after storing the query results in a temporary table. HISTORY
|
|
|