Relational Database Research Paper

It is a database which shows the links and relationships between two sets of data/stored information in a document or mainly entities. This means e.g. if a computer system has to store a lot of data/information about people instead of repeating the same row of information which may include personal or unnecessary things, you will then be able to click on the main primary key data which then leads to the actual personal things. This is the relationship between the primary key and foreign key. Ians & Co will benefit with a relational database as it has many links to primary and secondary data. Ians & Co being a large company will have a lot of data which means it will be harder to maintain with a simple and old database.

The purpose of normalization is to create a stable set of relations is representative of the operations of an enterprise. By doing this we are able to reduce redundancy to save space and avoid inconsistencies in data. It also ensures that the design is free of certain updates, insertions, and deletion anomalies (Ricardo, 2012). With normalization as with most anything else there are advantages and disadvantages. The advantages of normalization are: ACID, which stands for atomicity, consistency, isolation, and durability. Atomicity means the transaction is a single unit. Either the entire set of actions is carried out or is not.

My thoughts on normalization is that it requires multi-steps to enter the data into tabular format to ensure they are well-organized in a way that is consistent and lacks redundancy as well as prevent unintended or unambiguous results. As stated by Demba (2013) that normalization in relational database design often involves the process of organizing data and dividing the database into two or more tables with defined relationships in order to minimize

Database model defines the logical structure of the database by determining manner in which the data will be stored. Relational model is one of the most popular database models, which defines tables and relationships between the tables.

General a database has a lot of tables and some tables are related to each other so relationship is use to make the connection between two or more tables. It is a method to avoid excessive data and to ensure the data integrity. There have three types of relationships:

Relational data is when you can put data in a computer one time and it grows

Data normalization is a process by which large tables are divided into smaller tables, and then relationships are defined between them. These relationships could be one-to-one, one-to-many, or many-to-many. The idea behind normalization is to eliminate redundant information and avoid data anomalies that could compromise the integrity of your data. Additionally, you can reduce the amount of space your database consumes and cut the need for

In representing a 1:N relationship in a relational database design, the key of the table representing the entity on the "many" side is placed as a foreign key in the table representing the entity on the "one" side of the relationship.

We chose to use this software because it is suitable for small scale databases, the software is available through an Office 365 Pro Plus subscription which is available for $12 a month, which also includes the full Office suite (Word, Excel, Outlook etc) which is eligible to be installed on up to five computers and receive free upgrades to the newest version of Office when released which prevents the software from being “outdated” and unable to run on newer machines. The advantage of Access is that it is a Microsoft software meaning support is easily available and requires very little user knowledge to use due to it’s easy to navigate user interface. It will easily allow the user to add new books to the database without needing to learn any SQL commands, and simply fill in a pre designed form and click a button which will add the book to the database. It also allows us to create user views so that only certain users can perform specific functions. This allows the database to be user friendly, easily updatable and easily supported on almost any

Relational database affects my daily life because I use at work all the time. I started to work as a caregiver and I have to have many fields for many occasions, for example I need to do a table for her food and have breakfast, lunch, snack, and dinner as her fields to identify what she will be her choices in having that day. Then I will have another table for her medicine that she needs to drink at a certain time. Clearly, I have used relational database daily. I also use relational database for my personal life like my data for contacts, music, and pictures, all these data have their own table set up, for example, my music, I have all the music organized by there genres, I have about 2 I only have rap music and Spanish music and when i downloaded

Example 1 – Consider the following relational database for the Super Baseball League. It keeps track of teams in the league, coaches and players on the teams, work experience of the coaches, bats belonging to each team, and which players have played on which teams. Note the following facts about this environment:

Firstly a relational database contains a set of tables which basically are linked collectively by the relationships between the tables. Also it is also known as reason such as a database is called relational database.

In this report I am going to explain what a database is, features of a relational database, and the benefits of a relational database, purpose of primary keys and how they are used to build relationships, and I am also going to focus on, what are foreign keys and how they are been used, explain referential integrity and finally, how to apply referential integrity. I am also going to backed up my views and opinions with the valid references.

Normalization is a process in the database design process which is done to ensure that the right data is in the right table. It helps to overcome the update problems. There are various forms of normalization namely 1NF, 2NF, 3NF, 4NF and 5NF. Another type of normalization is BCNF.

At the U.S. Census Bureau, hundreds, perhaps more than a thousand heterogeneous databases are currently operating. Some divisions have standardized the database technology on Oracle, while others are using a combination of Sybase, MySQL, SQL Server, etc. These Relational Database Management Systems (RDBMSs), supporting many databases and applications and each hosted on dedicated servers, are often under-utilizing the server resources available to them. Such a database infrastructure, therefore, is not cost-, or resource-effective from a maintenance or administrative standpoint. Consequently, the best solution to mitigate these issues involves the implementation of database consolidation technology. Database consolidation is the process of centralizing database resources, so that they are shareable among several databases and instances. In other words, it is the process of consolidating databases from multiple servers onto one or fewer servers. For example, Multitenant Architecture of Oracle 12c moves the database management principle to a completely new level with database consolidation. Consequently, for the U.S. Census Bureau, consolidation initiatives such as the following are beneficial: