Page 131 - ASBIRES-2017_Preceedings
P. 131
INCREASING THE SPEED OF SEARCHING PROCESS IN MYSQL DATABASE FOR DYNAMIC DATA
modeling and query language (SQL). physical storage space as before. This
(Relational Database Model | Wikipedia) requirement does not meet by the available
When the amount of data stored on tables infrastructure currently. It is suggested to
are increasing rapidly, in order to store large use data mining techniques to filter and
amounts of data NoSQL came into cluster relevant data. Here data mining can
existence. be used to filter important statistical data
that are needed in calculations and just
NoSQL is a non-relational database
management system, designed for remove the rest. Then the mined data will be
stored as data cubes where the data can be
distributed data stores that require very large easily retrieved and stored using less space.
data storage on a large scale. Database The data and their fetching patterns are
framework and computerized NoSQL are analyzed and found that multiple data cubes
used mainly because of their speed, can be created. The attributes needed for
scalability and flexibility. These types of that, as well as sample reports that the
data storing may not require fixed schema, business can be given after implementation
avoids join operations and typically scale was studied. Elastic search and data cubing
horizontally. NoSQL databases provide a can be applied without any restrictions from
mechanism to store and retrieve data using a TravelBox’s end at least as a structure
model that is more than the tabular relations without going into the actual
used in relational databases like MySQL. (1 implementation.
what is NOSQL | Yoda Learning) There are
many database engines following the Even though the performance issue of
NoSQL technology and having non- search functions when data fetched from the
relational models. Some of them are MySQL tables could be solved with the
MongoDB, HBase, Cassandra and selected solution still there exist the storage
ElasticSearch. (What is NoSQL? Why issue. Since MySQL didn’t have the
NoSQL? When NoSQL? | Bodhtree Blog) capability of handling the bulk amount of
Elastic search is a real time search engine data the tables were truncated time to time.
which uses a NoSQL database and also a Therefore, the lack of storage space had not
freeware. (Sense Documentation | Elastic) experienced as a critical issue. But with the
(Elastic search: RESTful, Distributed Search use of NoSQL database and Elastic search,
& Analytics | Elastic) the system will be capable of handling the
actual amount of data without frequent
A data cube is a three or higher trancations. Therefore, when the data start to
dimensional array of values which are be loaded into the database a storage issue
commonly used to store a time series of will be emerged where the disk space
data.
becomes not sufficient for the bulk amount
3 METHODOLOGY of data which will be approximately 1431
GB (Giga Bites) per year without
NoSQL database can be used where a considering increases in transactions in peak
bulk amount of data can be stored. NoSQL seasons. This could be twice as the above
allows high speed searching and higher mentioned value when the peak seasons are
capacity of data which answers to the considered. Therefore, either the storage
available problem. Considering the features capacity should be increased enormously or
and capabilities of the selected database should utilize the existing storage to handle
engines, Elastic search was selected. the bulk data efficiently. As a solution it is
Considering the efficiency, the system suggested to use data cubes to store data in
can be successfully migrated into Elastic the NoSQL database. Since data cubes store
search. But even the issues of reliability, values in a multi-dimensional structure that
capacity and speed will be resolved by this would be possible to keep the statistical data
solution; still needed the same amount of in a fewer number of indexes by compacting
121