\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Data Migration from Relational Database to MongoDB},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2019-01-15 (revised: 15 January 2019)}
\def\TheID{\makeatother }
\def\TheDate{2019-01-15}
\title{Data Migration from Relational Database to MongoDB}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Ajit  Singh}

             \affil[1]{  Patna Womens College}

\renewcommand\Authands{ and }

\date{\small \em Received: 9 December 2018 Accepted: 31 December 2018 Published: 15 January 2019}

\maketitle


\begin{abstract}
        


MongoDB is a document-oriented database which helps us group data more logically. This paper demonstrates the conversion of data from a native tabular form to unstructured documents. The document and collections within it needs not to be well defined prior to the creation of unstructured data in MongoDB. The MongoDB has lots of extensive built-in-features and is highly compatible with other software systems, with extensive and flexible ways of accessing data beyond JSON query, its highly compatible Business Intelligence Connector is highly compatible which makes it compatible with existing databases. High scalability is making it remarkable and popular in the World and hence made me think about writing a paper demonstrating the data conversion. This conversion has helped me in making the most of modern data to be compatible with MongoDB. Data is stored on the cloud as cloud-based storage is an excellent and most cost-effective solution. My solution is highly scalable as the built-in shading solution for data handling makes it one of the best big data handling tool. The data that i have used, is location based in MongoDB that can directly yeild document ACID transactions to maintain data integrity.

\end{abstract}


\keywords{data migration, relational database, MongoDB, XAMPP, NoSQL, ACID transactions.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
Database is usually defined as collection of data and the system that handles data, transactions, problems and issues of the database is known as Database Management System (DBMS). A Database was incepted in 1960 in order to satisfy the need of storing and finding data. It began with navigational databases which were based on linked-lists, moved on to relational databases with joins, and then afterwards object-oriented and then without joins in the with NoSQL (MongoDB, Cassendra, HBase/Hadoop, CouchDB, Hypertable etc.), emerged and has become a popular trend \hyperref[b0]{[1]} in the late 2000s. On one hand, there is relational database management system (RDBMS) that offers more consistency as well as powerful query capabilities and a lot of knowledge and expertise over the years \hyperref[b1]{[2]}. On the other hand, NoSQL approach, which offers higher scalability i.e. it can run faster and support bigger loads.\par
The NoSQL in general doesn't support complicated queries and doesn't have a structured schema. It recommends de-normalization and is designed to be distributed (cloud-scale). Because of the distributed model, any server can answer any query. Servers communicate amongst themselves at their own pace. The server that answers our query might not have the latest data. This research paper is based on data conversion using Mongo DB. I have demonstrated data conversion from traditional database to MongoDB document-based database. Section II covers the related work done in this field. In section III, the performance of the proposed concept has been verified with the aid of XAMPP and MongoDB management system. Results are followed up in Section IV presents the conclusion. 
\section[{NoSQL characteristics}]{NoSQL characteristics} 
\section[{II.}]{II.} 
\section[{Related Work}]{Related Work}\par
This research work is based on MongoDB in which the relations within the applications are well defined by two main tools which are references and embedded documents. The references store the relationships between data by including links or references from one document to another. The applications can resolve these references to access the related data. Having the URL link within the field definitely adds to its range of accessing data. The embedded documents capture the relationships between data by storing related data in a single document structure. The MongoDB documents make it possible to embed document structures in a field or array within a document along with a new feature.\par
The MongoDB is derived from the word humongous as the database has a characteristic of exceptional scale-up capability. So, big data are huge massive exponentially changing and growing data sets \hyperref[b2]{[3]}. The traditional framework was not able to handle and analyze large amount of data. Also the internet of things (IoT) is creating exponential growth in data. The Big data and linked data are two faces of the same coin both representing the integral and concentric part of web based world. Each data element is connected via a URLs and are identifiable, locatable and accessible. Stronger the bond between the two, higher will be the unsustainability and big data utility. Semantically well structured, interconnected and linkied data will add intelligence to the data. The main goal is to make data more interactive, participatory and innovative. Making sense and extracting information from the data for organizational benefits. So, semantic technologies can help us extracting the main value from the data. Test analytics aids in the conversion of unstructured text to structured meaningful text by deriving and extracting patterns.\par
Database scaling is a highly difficult task. The modern applications require high scalability and data curating capacity. I have used XAMPP which is apache distribution web server solution for creating a local web server, after setting the environment for the database was tested. The JSON enables the transferring data between the master server and the web application in human readable form. This improved the overall efficiency. 
\section[{III.}]{III.} 
\section[{Proposed Work}]{Proposed Work}\par
The key benefits of NoSQL are speed, scalability, price, flexibility and simplicity. The main characteristics is its Non-adherence to relational database concept. As an example, Grolinger et al \hyperref[b3]{[4]} identified the difficulties in handling information which can be the huge Map Reduce. Naheman and Wei \hyperref[b4]{[5]} studied and compaired various BigData tools like HBase and other NoSQL databases eg Bigtable, Cassandra, CouchDB, and MongoDB etc. Laurence \hyperref[b5]{[6]} worked on a virtualization system which does allow us to enquire and join information making use of a sql query and the result in API that is underlying to MongoDB.\par
Hadoop -the main frame technology being used is a Java based framework that supports the processing and storage of tremendously large data sets in a distributed computing environment. Even though, as we all we know that Hadoop is written in Java programming language, programs for Hadoop can be written in other languages like Python. Mostly, Python code is translated to Java jar files using Jython. The Hadoop has two major areas of concern. The first one is Hadoop which is built using Java and hence the application developers should know Java to develop the framework and to develop the map reduce technologies. The Hadoop provides a framework by which Map Reduce applications can be built using python. The second is the co-sister technologies which work on top of this framework is one of the example being Cassandra, Cassandra being a NoSQL database technology which is ideal for high-speed online transactional data, while as Hadoop being a big data analytic system.\par
Apache Spark once a component of the Hadoop ecosystem is now fetching big data platform of choice for enterprises. Surveys reveal that many data analyst and data scientist preferred spark over map reduce, which is batch-oriented and it does not offer itself for interactive applications and real time stream processing. As we advance towards the Internet of things, we towards the era of sensor based things too, the sensors that are intended to send the data back to the mother ship repository. The data that we deal with is mostly very complex and is deployed across various relational and non-relational systems. However, the demand for analytical tools is increasing. Such tools helps us in extracting and utilizing data stored anywhere. Even for the sensor input data, the input data is tremendous. To cater the efficiency, the Metadata catalogues help us to relate and understand data. The Machine learning is definitely automating the task of finding data in Hadoop. Some of the emerging tracks in Big Data are in the fields of sensing and Internet of things Services, Smart City Data, Big Data Networking. 
\section[{a) NoSQL comparisons}]{a) NoSQL comparisons}\par
The NoSQL system of designing the database is a relation less and hence schema less, they are now constructed on a single model but and layer out to adopt different ones. There are almost a handful of different operational models for NoSQL. Key/value, e.g. in MemchacheDB, Redis, etc.\par
Column, e.g. HBase Document, e.g. MongoDB, Couchbase, etc. Graphs, e.g. Neo4j, OrientDB. I have used MongoDB which is document based. This technology uses deeper nesting and handles much more complex structures. 
\section[{b) Defining data model}]{b) Defining data model}\par
I have created three collections in my paper. They are movies, ratings and users. The data model used in Movies is as \{ "\textunderscore id" : ObjectId("58ab3f58ce38be146435cc76"), "id" :"35", "title" : "20", "release\textunderscore date": "F", "IMDBURL" : "homemaker", "genre ":42459" \} The data model used in ratings is as \{ "\textunderscore id" :ObjectId("58ab3f58ce38be146435cc76"), "user" : "35", "movie" : "20", "rating" : "F", "timestamp" : "homemaker 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology}\par
Volume XIX Issue II Version I18 Year 2 019 ( ) C \}\par
The data model for users is \{ "\textunderscore id" :ObjectId("58ab3f58ce38be146435cc76"), "id" : "35", "age" : "20", "gender" : "F", "occupation" : "homemaker", "zip\textunderscore code" : "42459" \}\par
Process to be followed for data conversion INPUT: The input for this proposed paper is a movie.normalised\textunderscore 2015-11-30.sql file, which i have compressed to zip file by using WinRAR file compressor and later imported the same into XAMPP phpMyAdmin. 
\section[{Conversion Methodology}]{Conversion Methodology}\par
The first tool we used was XAMPP. XAMPP Stands for Cross platform (X), Apache (A), MariaDB (M), PHP (P), and Perl (P).\par
Using XAMPP, i have taken the compressed input file movie and then normalized and converted it to JSON file. But before it, i have created a view of genres and movies. The view is named as moviefile. The attached snapshot covers the view creation with only the required attributes needed. The original database is with five tables where i merged two tables into one view and named it as moviefile. In Moviefile view, i have taken id, title, release date, IMDBURL. I dropped video attribute since the column was empty.\par
The code we used to create a view is as follows: CREATE VIEW Moviefile AS SELECT id, title AS Name\textunderscore OftheMovie, release\textunderscore date AS DateofRelease, IMDBURL ,Genres FROM movies, genres WHERE movies.id = genres.id ;\par
But before i exported the file, i supposed to convert the view created above with the SQL files users and ratings to JSON file which is later imported into NoSQL manager for MongoDB. The NoSQL Manager GUI which has an embedded smart shell to work on, act as a platform to work upon to maintain, update, embed, delete, interact and querying the database repository in a protocol set environment. The performance rate of NoSQL manager for MongoDB is a grade efficiency, especially the enterprise version. its easy to use document view and easier management utility features make it excellent to use and implement. It's SSH tunneling capacity for the connection, enables us to work on a highly secure system. The Map-Reduce operations inbuilt editor feature is remarkable in itself. It saves all map reduce parameters on the current session in an XML format. Another point to add is its GridFS which will divide the file onto chunks of size 255KB, with an exception of the fast chunk with as large as needed. Therefore the technological feature uses two collections; one for the file chunks and the other for file metadata.\par
Though for analyzing the data, MongoDB can work very well, but still the complexity of the database may increase while leading to have a platform to hold it. This is where Hadoop can provide a powerful framework for complex analytics and measurements. During the encounter of such a scenario, data can be pulled from MongoDB and processed and cared by Hadoop via the tool of map reduce. Nevertheless, Hadoop is stronger enough so that it can act as data warehouse and can hold the central control.\par
Data business analytics now has an option of holding Map Reduce \hyperref[b3]{[4]} and Pig Map Reduce procedure is used to extract, transform and load data repository from one location to another. It pulls data from a place, transforms the data by using new methods and after transforming it to the desired shape it will load the data to another repository. Using this approach, i can handle huge data very easily. MongoDB is implemented in C++ \hyperref[b6]{[7]}\hyperref[b7]{[8]} {\ref [9]}  Select the JSON file type and enter the file name along with path, is the first foremost step. Figure \hyperref[fig_0]{1} represents it.  IV. 
\section[{Results and Discussions}]{Results and Discussions}\par
The MongoDB guarantees data integrity with multi-documents transaction which makes MongoDB remarkable. This makes it well versed for developers to address the complete set of queries on the database. Interacting with the database constructed in MongoDB, supports multi-documents due to which a global consistent view of data is maintained. This new outlook of MongoDB made it possible to transact through multiple databases with the power of multi-documents ACID transaction.\par
I was successfully able to convert the JSON files to MongoDB format and consequently. Now my database is ready for interactions. Once the database is ready, i can extract information from the MongoDB multisite database by verifying multi-document ACID transaction.\par
MongoDB Queries 1. db.movies.find (\{title:\{\$regex:/\textasciicircum A/I\}\}): This extract titles starting with letter A.\par
2. The Second query is db.ratings.count (\{ rating:\par
1 \})\par
I have movies as the collection name and ratings as one of the attribute and count is as the member function which will count the number of instances of ratings.\par
V. 
\section[{Conclusion}]{Conclusion}\par
The efforts to ensure the smooth and flexible functioning of a business, depends on the software capabilities of the Big Data Management Framework, The Data curation, scalability and data security are the key features. Through this paper it is clear that interactions have become easier on Big Data and even huge real time data management is possible with high er level of understanding and accuracy. The sensor data and many more can be translated to a MongoDB format which is composed of fields and value pairs. The document in MongoDB is being similar to JSON. In this paper, JSON enabled the transferring of data between the master server and the web application, in human readable form. It is concluded from the observed results that MongoDB provides high performance on data persistence, support for embedded data models, reduces I/O activity on database and high speed interactions can include keys from embedded documents and arrays. The resultant data repository has been in document format. The JSON document that i have, can be very easily parsed with the help of JavaScript.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{}
\end{longtable} \par
 
\caption{\label{tab_1}}\end{figure}
 			\footnote{© 2019 Global JournalsData Migration from Relational Database to MongoDB} 			\footnote{( ) C © 2019 Global Journals Data Migration from Relational Database to MongoDB} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Carme et al.]{b3}\label{b3} 	 		\textit{},  		 			Julien Carme 		,  		 			Atos R\&d Engineer 		,  		 			Francisco Worldline 		,  		 			José 		.  		 	 
\bibitem[Jimenez]{b4}\label{b4} 	 		\textit{},  		 			Ruiz Jimenez 		.  	 	 		\textit{Atos Spain, Open Source}  		 	 	 (Technical Architect Manager) 
\bibitem[Hall (2014)]{b7}\label{b7} 	 		\textit{},  		 			S Hall 		.  		 \url{http://www.scriptrock.com/articles/mysql-vs-mongodb,acceseednov}  		2014. Jul) MySQL vs MongoDB, jul, 2014. 2018.  	 
\bibitem[Berg et al. ()]{b0}\label{b0} 	 		‘History of Databases’.  		 			K Berg 		,  		 			T Seymour 		,  		 			R Coel 		.  	 	 		\textit{International Journal of Management and Information Services}  		2013. 17.  	 
\bibitem[Lawrence (2014)]{b2}\label{b2} 	 		‘Integration and Virtualization of Relational SQL and NoSQL Systems Including MySQL and MongoDB’.  		 			R Lawrence 		.  	 	 		\textit{Proceedings of International Conference on Computational Science and Computational Intelligence (CSCI)},  				 (International Conference on Computational Science and Computational Intelligence (CSCI))  		Mar.2014. p. .  	 
\bibitem[Solutions for Big Data Management]{b5}\label{b5} 	 		\textit{Solutions for Big Data Management},  		Atos.  	 
\bibitem[Stonebraker (2013)]{b1}\label{b1} 	 		 			Michael Stonebraker 		.  	 	 		\textit{SQL databases v. NoSQL databases},  				Dec.2013. MEC. p. .  	 
\bibitem[Khan (2013)]{b6}\label{b6} 	 		‘Vanita Mane SQL Support over MongoDB using Metadata’.  		 			Sanobar Khan 		,  		 			Prof 		.  	 	 		\textit{IJSRP}  		October 2013. 3  (10) .  	 
\end{bibitemlist}
 			 		 	 
\end{document}
