Description Of A Relational Database

The term “No SQL” is considered in a much wider vision which means “Not Only SQL”. This can be elaborated in the sense that the concept of No SQL does not consider the complete elimination of SQL language, rather it focuses on supporting other SQL like queries. The No SQL Database basically follows a model-free approach. The leading advantage of implementing the No SQL database is eliminating all the restrictions of the rigorously followed structured model in the relational database system. In No SQL approach, there are many flexibilities of choosing eligible data structure according to the information or data that has to be handled. Some of the widely followed data models of the No SQL database are key value stores, column family stores, document database, graph database, etc. The fundamental concept behind the development of the key-value store data model is to create a data model that

Relational database systems came into existence in the 1970’s, and revolutionized the way data is maintained in computers. Like every technology that is subjected to test of time, relational database systems are under criticism for not being scalable enough to meet growing users and exponentially increasing data management needs. Today, a new technology called NoSQL is being pioneered by leading companies like Google, Amazon, and Facebook etc. to meet the shortcomings of the 40-year-old relational database technology. Modern web applications are making a transition from traditional relational databases to NoSQL databases to meet the demand of steadily growing concurrent users and big data.

Since 1960 and beyond the need for an efficient data management and retrieval of data has always been an issue due to the growing need in business and academia. To resolve these issues a number of databases models have been created. Relational databases allow data storage, retrieval and manipulation using a standard Structured Query Language (SQL). Until now, relational databases were an optimal enterprise storage choice. However, with an increase in growth of stored and analyzed data, relational databases have displayed a variety of limitations. The limitations of scalability, storage and efficiency of queries due to the large volumes of data [1] [2].

One size fits all. The developers go to for all data. You need only a relational database. This is the false assumption that you will see when it comes to database models. The relational database model is great for data that normally can fit into a table, or shows relationships between data, but not all data falls into that category. There are a few options for these situations. You can use an object-oriented database, a hierarchical database, a network database, and a flat-file database.

The relational model, which uses predefined tabular relations to store data, has remained the preeminent model for data storage since it was first implemented in the early 1980s. However, due to the proliferation of the Internet, today data flows in and out of organizations quickly, and most of this data is in a semi-structured state that is designed for communication over http. It is difficult to fit this complex data into a flat two dimensional array. For that reason, it is imperative that companies have the ability to store data in a semi-structured format compatible with modern network communications as well as various platforms and devices. The market has realized this and responded with document stores that support formats,

The idea of relational database was first introduced by E.F.Codd at IBM in 1970. It is a kind of computer database in which data is stored in Relations and is represented in the form of tables with rows and columns. Databases can vary in sizes, ranging from very small and simple to very large and complex ones. Database users can access the data practically in an unlimited number of ways. Relational databases help in finding the information in a quick and efficient manner that one is looking for.Today many popular databases use the model of relational database.

For example, Facebook which is the most popular social networking website recently announced their adoption of a NoSQL based graph data store for efficient storage of user data. In other words, NoSQL has already made its way into the enterprise. However, just like every other widely accepted technology, NoSQL has its own set of advantages and disadvantages. It is important for an enterprise to quantify the pros and cons of a particularly new database technology against the already existing solutions based on their custom requirements. For example, legacy enterprise applications may require extensive community support from their database vendors. Moreover, traditional relational database vendors such as Oracle have already established themselves for providing excellent support. On the other hand, NoSQL has been rapidly growing since the past few years and is consistently evolving in terms of big data handling, data warehousing and lesser complexity. Hence, there is a need to study the current market of data stores based on the most popular NoSQL data stores and how well they fair against the widely accepted traditional database systems. This requires a study of the commonly used NoSQL data stores.

Relational databases play a major role in making many apps and programs work. They provide an easy way to store large amounts of data in a consistent, non duplicating, and maintainable way to be used by developers for analytical or software use ("Advantages of a relational database", n.d.). However, more and more applications and companies with a tremendous amount of data such as search engines, social networks, and e-commerce sites have been requiring a level of speed and scalability that relational databases can not provide ("Why NoSQL?", n.d.). NoSQL is a name given to a quickly growing type of database known as non-relational databases, which are being used to store and manage huge amounts of structured, semi-structured, and non-structured data known as "Big Data" ("Why NoSQL?" n.d.). With the advent of social networks and apps with millions of users, the rate of growth of non-structured and semi-structured data is exponential, and the value in being able to quickly traverse it, analyze it, and use it for development is also growing quickly (McGuire, Manyika, & Chui, 2012).

Provide reasoning to support the use of the NoSQL database as the database of choice to solve the problem faced by TWC. Identify one strength and one weakness for each of the other three kinds of databases to solve the problem for TWC.

Define the structure of a database: data types and restraint that the data have to satisfy.

Utilizing databases within a department allows users to access various types of information all at once as well as link information from different sources. Information data is processed, organized or summarized, records data is a collection of logically related fields or items, and file data is a collection of related sequence of records.

For the purpose of this paper, we are going to focus on these three type of NoSQL database BigTable, Cassandra, DynamoDB.

The modern RDBMS advancements are not capable of supporting unstructured information with ideal space necessity. The plan winds up plainly mind-boggling and is henceforth troublesome for designers. The requirement for unstructured information administration is so annoying with conventional RDBMS arrangements (Big data in financial services industry: Market trends, challenges, and prospects 2013 - 2018). Moreover, RDBMS turns out to be an exorbitant answer for creating light-footed web applications with direct information investigation necessities. NoSQL is developing as a proficient possibility in this situation, which connects the issues related with RDBMS innovation. The market development can credit to creative dispatches of NoSQL arrangements, and collective endeavors by NoSQL sellers and clients. The endeavors of organizations, to enhance their market offerings, are creating the request of NoSQL, as a back-end bolster (Big data in financial services industry: Market trends, challenges, and prospects 2013 - 2018). The emergence of agile software development is creating the demand for NoSQL (Big data in financial services industry: Market trends, challenges, and prospects 2013 - 2018). They offer users much more avenues to accept data in many different forms. NoSQL is adaptable as SQL but offers many more uses that can apply to many organizations.

P1 - Explain the features of a relational database. This is to be shown as a report or presentation and must discuss the following.

For this coursework two kinds of data models can be used. The object oriented data model, Object Oriented Database Management System(OODBMS), or the relational data model, Relational Database Management System(RDBMS). The differences between these two models and the data model to be used are described in this chapter.