Jakovits, Pelle, juhendajaGarayev, SoltanTartu Ülikool. Loodus- ja täppisteaduste valdkondTartu Ülikool. Arvutiteaduse instituut2023-09-052023-09-052020https://hdl.handle.net/10062/91985The usual preference of storing data is Relational Databases for enterprise applications. It provides relational model, and helps to keep data in organized structure. For last few decades relational database models have been the first choice of the companies. Things started to change with the term of Big Data which is about storing all kind of data related to end-user behaviour. User behaviour is random which can be understood non-structural as well. In this scenario usual relational database model does not fulfill the requirements. There was a need, and a new concept named NoSQL was the best option to fill this gap. NoSQL means Not Only SQL, and it provides a suitable environemtn to companies to store data in any form without having to define a structure. As time passes non-relational databases became priority in other concepts such as storing not only randomly structured data but structured data as well. If we think about big tech companies like Facebook or Google usual relational database model is unsatisfactory for storing huge amount of data. Companies started to move data from relational database to non-relational databases to store their data. There are articles/papers on data migration from relational to non-relation databases. The main issue here is designing the scheme in non-relational data model based on existing complex relational data model. In this research we aim to suggest ways to solve this issue.engopenAccessAttribution-NonCommercial-NoDerivatives 4.0 InternationalData MigrationRDBMSRelational Database Management SystemRelational Data ModelNon-Relational Data ModelNoSQLPostgresPostgreSQLCassandraScheme DesignmagistritöödinformaatikainfotehnoloogiainformaticsinfotechnologyThesis