0% found this document useful (0 votes)
83 views3 pages

Embedded Database Management Systems

The document discusses embedded databases, which are tightly integrated with application software and require minimal maintenance, making them suitable for devices like mobile phones and medical equipment. It highlights the characteristics of embedded DBMS, including small footprint, automatic management, and portability, while contrasting them with traditional databases. The conclusion emphasizes the growing importance and future potential of embedded databases in various industries.

Uploaded by

icmlfc23
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
83 views3 pages

Embedded Database Management Systems

The document discusses embedded databases, which are tightly integrated with application software and require minimal maintenance, making them suitable for devices like mobile phones and medical equipment. It highlights the characteristics of embedded DBMS, including small footprint, automatic management, and portability, while contrasting them with traditional databases. The conclusion emphasizes the growing importance and future potential of embedded databases in various industries.

Uploaded by

icmlfc23
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

International Journal of Computer Science & Emerging Technologies (E-ISSN: 2044-6004) 124

Volume 1, Issue 4, December 2010

A Step To Embedded Database


A Techno Change
Manik Sharma
Assistant Professor & Head, PG Deptt. of computer Science and Applications
Sewa Devi SD College Tarn Taran
Manik_sharma25@[Link]

Abstract— Recent advances in device tools and and connectivity have paved the way for next
connectivity have tiled the way for next generation generation applications that are data-driven, where data
applications that are data-driven, where data can reside can reside anywhere, can be accessed at any time, from
anywhere, can be accessed at any time, from any any client. Embedded systems are computers
client. Embedded systems are computers (microprocessors) that are enclosed (embedded) in
(microprocessors) that are enclosed (embedded) in customized hardware. Examples of embedded systems
customized hardware. An embedded database system are portable medical equipment, cellular phones, or
is a database management system which is closely consumer electronics items. An embedded database
coupled with application software that requires access system is a database management system which is
closely tied with application software that requires
to stored statistics or data, such that the database
access to stored data, such that the database system is
system is ―hidden‖ from the application’s end-user and ―hidden‖ from the application’s end-user and requires
requires little or no ongoing maintenance. More than little or no ongoing maintenance [2]. More than 20 years
20 years one could argue that since the beginning of one could argue that since the beginning of software,
software, embedded databases have been in existence. embedded databases have been in existence.
The operations of the embedded database are invoked
by the application. The embedded database is
embedded within an application either as in-line code FLAT FILES
DISTRIBUTED (1960-1980)
or linked libraries unlike the traditional general DATABASE
(2000 Onwards)
purpose enterprise relational databases such as Oracle,
DB2, and SQL Server etc which normally run as the
separate applications that are independent of the
system application. The key operational advantage of
OBJECT
the embedded database is that using the embedded RELATIONAL HIERARCHICAL
database the users and administrators are not burdened (1990-Present) DATABASE
(1970-1990)
with time-consuming installations or maintenance as DATABASE
the database is packaged with the application and is EVOULTION
generally self maintaining. The embedded databases
can be relational, hierarchical, network model, XML
based, object oriented etc. The embedded DBMS are
typically used in the mobile phones, PDA’s, set-top OBJECT
ORIENTED NETWORK
boxes, automotives etc. (1990-Present) DATABASE
(1970-1990)

RELATIONAL
Keywords- Embedded Database, DBMS, Software, DATABASE
Oracle, mobile phones (1972-Present)

1. INTRODUCTION
In other words we can say that embedded database
As we know that the database is defined as
is embedded in some another software applications.
collection of interrelated data. Initially small databases
The operations of the embedded database are invoked
were first developed or funded by the U.S. government
by the application. The embedded database is
for agency or professional use. In the 1960s, some
embedded within an application either as in-line code
databases became commercially available, but their use
or linked libraries unlike the traditional general purpose
was funneled through a few so-called research centers
enterprise relational databases such as Oracle, DB2,
that collected information inquiries and handled them
and SQL Server etc which normally run as the separate
in batches [1]. Recent advances in device technology
International Journal of Computer Science & Emerging Technologies (E-ISSN: 2044-6004) 125
Volume 1, Issue 4, December 2010

applications that are independent of the system commercial DBMSs; they require simple query and
application. execute in constrained environments.
The key operational advantage of the
embedded database is that using the embedded 3. Run on mobile devices – The DBMS that run on
database the users and administrators are not burdened mobile devices tend to be specialized versions of
with time-consuming installations or maintenance as mobile and embedded DBMS. In addition to handling
the database is packaged with the application and is the memory, disk and processor limitations of these
generally self maintaining. The embedded databases devices, the DBMS must also run on specialized
can be relational, hierarchical, network model, XML operating systems. The DBMS must be able to store
based, object oriented etc. and forward data to the back-end databases as
synchronization with backend systems is critical for
The embedded DBMS are typically used in the
them.
mobile phones, PDA’s, set-top boxes, automotives etc.
Worth of Embedded Database: Modern embedded 4. Componentized DBMS – Often, to support the
devices are now responsible for storing more data than small footprint requirement, it is important to include
ever before. Some devices get an edge on the only the functionality that is required by the
competition by synchronizing data without interrupting applications. For example, many simple applications
normal use. Important data must not be lost to just require ISAM like record-oriented access. For
corruption caused by a power failure. For these these applications, there is no need to include the
devices, performance and reliability are critical. query processor, thereby increasing the footprint.
Similarly, many mobile and mid-tier applications
2. EMBEDDED DBMS CHARACTERISTICS require only a small set of relational operators while
The data access and management requirements of the others require XML access and not relational access.
applications described above are significantly different So, it should be possible to pick and choose the
from that of traditional server DBMS. These new desired components.
applications must be able to run on multiple tiers
ranging from devices to servers to web and would 5. Automatic DBMS – The embedded DBMS is
benefit from various existing database mechanisms. invisible to the application user. There can be no DBA
However, these database mechanisms (like query, to manage the database and operations like backups,
indexing, persistence) must be unlocked from the recovery, indexing, tuning etc. cannot be initiated by a
traditional monolithic DBMS and made available as DBA. If the database crashes, the recovery must start
embeddable components (e.g. DLLs) that can be instantaneously. The database must be self managed or
embedded within applications, thereby, enabling them managed by the application. Also, embedded DBMS
to meet the requirements described above. Such must auto install with the application it should not be
Mobile and Embedded DBMS have the following installed explicitly (user action) or independently.
characteristics: Similarly when the application is shutdown, the
DBMS must transparently shutdown.
1. Embeddable in applications – Mobile and
Embedded DBMS form an integral part of the 6. In-Memory DBMS – These are specialized DBMS
application or the application infrastructure, often serving applications that require high performance on
requiring no administration. Database functionality is data that is small enough to be contained in main
delivered as part of the application (or app memory. In-memory DBMS require specialized query
infrastructure). While the database must be processing and indexing techniques that are optimized
embeddable as a DLL in applications, it must also be for main memory usage. Such DBMS also can support
possible to deploy it as a stand-alone DBMS with data that may never get persisted.
support for multiple transactions and applications.
7. Codeless database – Portable database should be
2. Small footprint – For many applications, especially free from any threat. The executable code can become
those that are downloadable, it is important to the reason for malfunctioning or destruction of data in
minimize DBMS footprint. Since the database system the form virus. By eliminating any code storage in the
is part of the application, the size of the DBMS affects database, we can make our database consistent and
the overall application footprint. In addition to the safe [4].
small footprint, it is also desirable to have short code
paths for efficient application execution. Most of these 8. Portable databases – There are many applications
applications do not require the full functionality of which require very simple deployment – installing the
application should install the database associated with
International Journal of Computer Science & Emerging Technologies (E-ISSN: 2044-6004) 126
Volume 1, Issue 4, December 2010

it. This requires the database to be highly portable. 4. Conclusion


Typically, single file databases (e.g. like Microsoft
Access databases) are ideally suited for this purpose. Embedded databases differ from typical databases
Again, there should be no need to install the DBMS such as DB2, Oracle, and SQL Server in that it is
separately – installing the application installs the entirely embedded into the application or hardware
DBMS and then copying the database file completes device in such a way that the user has very little
the application migration. With the help of portable knowledge, if any, of its existence. Users and
database [5] application we can reduce the anomalies in administrators are now free from the huge tension of
database migration. installing and maintaining the database because the
database is closely bundled with the application and
9. Synchronize with back-end data sources – In the should be self maintaining. Embedded databases are
case of mobile and cached scenarios, it must be potable in nature and meant to run on many different
possible to synchronize the data with the back-end platforms with various programming interfaces. It also
data sources. In typical mid-tier (application server) help in reducing engineering and quality assurance
caches, the data is fetched from the back-end cost, eliminate some support cost in setup and
databases into the cache, operated on, and implementation. The nature of embedding databases’
synchronized with the back-end database. instruction sets being linked specifically within and for
a specific application gives them a small footprint.
10. Remote management – While mobile and Because embedded database reduces the instruction set
embedded DBMS must be self managed, it is hence it allows them to achieve performance that is
important to allow them to be managed remotely also, hard to beat. The above discussion end with that future
especially those on mobile devices. In enterprises (e.g. is of embedded database. Besides, embedded industry
FedEX, UPS), mobile devices must be configured and will flourish in the area of automotive, industrial,
managed in a manner compliant with the company consumer electronics in coming year.
3. Embedded software in India
REFERENCES
Typically software for embedded systems need to have
a very small footprint (i.e. be able to run in a small
amount of memory) and often have to work in real- [1] Microsoft Encarta Library 2005.
time. Companies here in India offer specialized [2] Graves, Steve. "COTS Databases For Embedded
operating systems and languages, which make this Systems", Embedded Computing Design magazine,
possible. These companies ensure the designing, January, 2007. Retrieved on August 13, 2008.
developing, and testing of software for embedded [4] TinyDB: [Link]
systems and components meet specific customer [5] [Link]
requirements. They use diverse, real-time operating us/library/[Link] (online)
systems, devices and platforms and associated [6] Ramachandra Budihal, Emerging trends in
embedded tools and technologies. The various embedded systems and applications (online)
Embedded Software domains[5] in India are: [Link]
erging-trends-in-embedded-systems-and-applications
Aerospace and
EMBEDDED SYSTEM IN INDIA Defense

Automotive

Consumer
Electronics

Industrial
Measurement and
Control
Servers and Storage

Networking

Process Control
Systems

Figure2: Embedded System in India


The various embedded database system in
commercial market are ElevateDB, Interbase, Oracle
Berkley DB, SolidDB etc.

You might also like