1

DATABASE MANAGEMENT SYSTEM

Abstract- A database management system (DBMS) is a software [1] package with computer
programs that control the creation, maintenance, and use of a database. It allows
organizations to conveniently develop databases for various applications by database
administrators (DBAs) and other specialists. Information retrieval emerged as independent
research area from traditional database management system more than a decade ago. This
was driven by the increasing functional requirements that modern full text search engines
have to meet. Current database management systems (DBMS) are not capable of supporting
such flexibility. However, with the increase of data to be indexed and retrieved and the
increasing heavy workloads, modern search engines suffer from Scalability, reliability,
distribution and performance problems. We present a new and simple way for integration
and compare the performance of our system to the current implementations based on storing
the full text index directly on the file system.

INTRODUCTION:
New applications like office information systems need interfaces to data bases which integrate
classical data manipulation with management and retrieval of textual (“unformatted”) data. The
relational data model is widely accepted as a high level interface to classical (“formatted”) data
management. It turns out, however, to be inconvenient for handling even simple data structures as
commonly used in information retrieval systems. To attack this shortcoming, we propose an
extension of the relational model by allowing Non First Normal Form (NF2) relations. We
summarize extensions of the relational algebra, with main emphasis on the new “nest” and
“unnest” operations which transform [2] between first normal form relations and the NF2 ones. In
the past, database management systems (DBMS) and information retrieval systems (IRS) were
separated in research and development and different products have been developed for either
purpose. At present there is a trend towards a single integrated system for data base management
and information retrieval called DBMIRS -because of the following reasons: Many applications
need a DBMIRS. Examples are patients’ data within hospital information Systems, laboratory
document administration Pharmaceutical data bases, and library Information systems, and with
growing awareness office information systems. A characteristically feature of these applications
is the fact that it is necessary to combine text management and retrieval with usual formatted data
manipulation. Therefore, a single user interface is necessary. Most commercial database
management systems offer basic phonetic full text search functionality. For example, Oracle has a
module called Oracle Text. Yet, seeking to add more functionality and intelligence to their search
capabilities, many commercial applications use third party specialized full text search engines
instead. There are several commercial products on the market. But certainly Lucene is the most
popular open-source product at the moment. It provides searching capabilities for the Eclipse IDE
, the Encyclopedia Britannica CD-ROM/DVD, FedEx, New Scientist magazine, Epiphany, MIT’s
 2

Open-Courseware and so on. All search engines build an index of the data to be retrieved in user
queries. The index is always stored in the file system on disk and can be loaded at startup in the
memory for faster querying. However, this is not feasible for large indices due to memory size
limitations. So, the standard storage usually remains the file system of the disk.. Reliability
becomes also a problem. The possibility of corrupting the whole index during a system crash is
much higher than losing the data in a database after a similar crash. Restoring a defected index
might also take several hours thus complicating the situation even further. The search engine must
manage its read and write locks by itself as well. Distributing the index among several sites and
providing efficient mirroring techniques is becoming an important issue to large scale search
engine projects such as Nutch .We propose using current DBMS as backend to existing full text
search engines as opposed to either implementing full text search engine functionality into DBMS
or re-implementing core DBMS features into search engines. As a case study, we use the open-
source Lucene and MySQL without loss of generality. We use real world data extracted from an
electronic marketplace and simulate real world workload traces in order to demonstrate that the
overall system throughput and query response time do not suffer with the introduction of DBMS
as a backend with their inherent overhead. spectrum of basic infrastructural facilities offered by
DBMS The rest of the paper is organized as follows.

Background:
By the mid-1960s, as computers developed speed and flexibility, and started becoming popular,
many kinds of general use database systems became available. [3] As a result, customers
demanded a standard be developed, in turn leading to Bachman forming the Database Task Group.
This group took responsibility for the design and standardization of a language called Common
Business Oriented Language (COBOL). The Database Task Group presented this standard in 1971,
which also came to be known as the “CODASYL approach.”
Edgar Frank "Ted" Codd (19 August 1923 – 18 April 2003) was an English computer
scientist who, while working for IBM, invented the relational model for database management,
the theoretical basis for relational databases and relational database management systems. He
made other valuable contributions to computer science, but the relational model, a very influential
general theory of data management, remains his most mentioned, analyzed and celebrated
achievement

Recent trend:
1. Databases that bridge SQL/NoSQL
The latest trends in database products are those that don’t simply embrace a single database
structure. Instead, the databases bridge SQL and NoSQL, giving users the best capabilities offered
 3

by both. This includes products that allow users to access a NoSQL database in the same way as a
relational database.
2. Databases in the cloud/Platform as a Service
As developers continue pushing their enterprises to the cloud, organizations are carefully weighing
the trade-offs associated with public versus private. [4] Developers are also determining how to
combine cloud services with existing applications and infrastructure. Providers of cloud service
offer many options to database administrators. Making the move towards the cloud doesn’t mean
changing organizational priorities, but finding products and services that help your group meet its
goals.
3. Automated management
Automating database management is another emerging trend. The set of such techniques and tools
intend to simplify maintenance, patching, provisioning, updates and upgrades — even project
workflow. However, the trend may have limited usefulness since database management frequently
needs human intervention.
4. An increased focus on security

While not exactly a trend given the constant focus on data security, recent ongoing retail database
breaches among US-based organizations show with ample clarity the importance for database
administrators to work hand-in-hand with their IT security colleagues to ensure all enterprise data
remains safe. Any organization that stores data is vulnerable. Database administrators must also
work with the security team to eliminate potential internal weaknesses that could make data
vulnerable. These could include issues related to network privileges, even hardware or software
misconfigurations that could be misused, resulting in data leaks.
5. In-memory databases

Within the data warehousing community there are similar questions about columnar versus row-
based relational tables; the rise of in-memory databases, the use of flash or solid-state disks (which
also applies within transaction processing), clustered versus no-clustered solutions and so on.
6. Big Data
To be clear, big data does not necessarily mean lots of data. What it really refers to is the ability
to process any type of data: what is typically referred to as semi-structured and unstructured data
as well as structured data. Current thinking is that these will typically live alongside conventional
solutions as separate technologies, at least in large organizations, but this will not always be the
case.
Now days database research is facing major new challenges due to explosion of data, novel usage
scenarios, and a major shift in computing [5] architectures. A recent meeting of leading database
experts characterized the present situation as a “turning point in database research” and identified
a number of trends that necessitate re-evaluation of research directions, and at the same time
present new research opportunities. “The Claremont Report on Database Research”
 4

Future of database management: NOSQL NEWSQL

The database management system(DBMS) is a software which helps the user interact with the
database. Simply put, a database is the collection of data in form of tables, queries, reports and
similar objects. Most of the databases that are in the market today are relational databases. Oracle’s
MySQL, IBM’s DB2, Microsoft’s Access are all relational databases. A relational database is a
digital database in which data is organized in tables with each row of the table having a specific
key. It is far better than the earlier hierarchal databases of the past which were slow and less
organized. But, times are changing fast. [6] Today you can be satisfied in using a relational
database which are exclusively based on the structured query language (SQL). But the future is
already upon us with NoSQL and NewSQL gaining ground. With the need to store, study and
manage large amounts of data these flexible and powerful standards are ready to win over
traditional database languages.

While today’s databases provide well-defined structure and accessibility, they have less
capabilities to handle Big Data. This set the situation up perfectly for the rise of these modern
databases which don’t even require a highly ordered database plan.

NoSQL and NewSQL – Details

NoSQL, also called Not Only SQL is a modified version of the existing SQL databases. [7] There
are several improvements in multiple aspects which cumulate and bring in the capacity to deal
with larger data contexts effectively. One of such improvements is the horizontal scaling and data
fetching. But this doesn’t mean the entire SQL databased are to be converted to NoSQL, and the
choice is completely application oriented. In few projects SQL (the relational database model)
works great with better speed and accuracy while in others NoSQL is the best. So here the problem
at hand is to be keenly observed and one of these implementations is to be selected.

NewSQL, in-turn is a hybrid database management system which adds the capabilities of
NoSQL to the ACID capabilities of a relational database. These systems find vast applications in
the OLTP (Online Transaction Processing) section.

This truly has developed an interesting situation with established database providers feeling the
heat. In addition, the data owners have an even field to choose among several distinct options. This
situation led to the rise of several solutions with broader differences among each of them. These
include Cassandra, HBase (column databases) Mongodb, CouchDB (document databases) Redis
(key-value), VoltDB, Hypertable, Accumulate etc.

The point is that all these mentioned databases are filled with several features. So at the end of the
day it all comes down to the problem in your hand. There are tools with which you can migrate
 5

between each of these and without doubt there’s going to be a lot of development in all these
database management services.

Conclusion:
In conclusion. Database implementation plan is essential for any organization that once to boost is
sales or increase their customers experience, a good database implementation plan I supposed to
have, all the factors and the significance value towards the organization, not forgetting the
requirements that are needed. [8] In my opinion, I could have recommended using computerized,
database management system. This is because it is faster to implement and also it requires less
amount of time and finance to set up, the future of database lies on the power of the organization
.and the funds that they can be able to set aside to implement new database management system.

Reference:
[1] Tahat, Amani, and Wa El Sala. “Comprehensive Online Automatic Database Management
System (DBMS) with Highly Qualified Computing Capabilities.” International journal of
database management system, vol. 3, no. 2,2011, pp. 1-20., doi: 105121/ijdms.2011.3201.
[2] Iwata, S.(n.d). Expert Systems Interfaces for Materials Database. Computerizations and
Networking of Materials Databases.doi:10.1520/stp18624s
[3] Schnoes, markus, and Eberhard Nicke. “A Database of Optional Airfoils for Axial
Compressor Throughflow Design.” Valume 2C: Turbomachinery, 2016, dio:10.1115/gt2016-
56241
[4] Bernstein, David. “Is Amazon Becoming the New Cool Software Company for Developers?”
IEEE Claude Computing, vol. 2, no. 1, 2015,pp. 69-71., doi:10.1109/mcc.2015.10
[5] Sindia, Suraj. “Innovative Practices Session 2C:New Technologies, New Challenge -2. ”
2015 IEEE 33rd VLSI Test Symposium (VTS), 2015, doi: 10.1109/vts.2015.7116258.
[6] Grewwal, J. (2018). Facing new Challenges. Oxford Scholarship Online. doi:
10.1093/oso/9780199467099.003.0009
[7] Balusamy, B, S, N, N, S., & Velu, M. (2017). Cloud Database Systems. Advances on Data
mining and Database Management Advancing Cloud Database Systems and capacity Planning
With Dynamic Applications, 225-245. doi:10.4018/978-1-5225-2013-9.ch010
[8] “Implementation and Conclusion.” Requistite Organization, 2017, pp. 287-293., doi:
10.4324/9781315088846-15.