Showing posts with label relational database. Show all posts
Showing posts with label relational database. Show all posts

Tuesday, February 13, 2018

Week 6: Blog Post 5 - Relational Database Theory

Relational Database Theory


Definition

A relational database (RDB) is defined as a collection of multiple data sets stored and organized as items in a set of formally described tables (rows & columns). This data can be accessed or reassembled in any customizable way at a later point in time. This neat piece of creation was invented by Edgar F. Codd at IBM 1970 [1]. RDB runs on Structured Query Language (SQL), an application that provides a user-friendly programming interface for database interaction. [2] 


Types of RDBs
In an RDB, data is stored in a tabular format with rows and columns. A row represents a data instance and a column represents a column. One or more data that is stored relates to one or more data records to form functional dependencies. There are four types of dependencies:


  • One to One: One table record relates to another record in another table.
  • One to Many: One table record relates to many records in another table.
  • Many to One: More than one table record relates to another table record.

  • Many to Many: More than one table record relates to more than one record in another table. [2]
Function

The main capabilities of an RDB is its ability to communicate and relate one data instance stored in any row, any column, any table and any data set to another data instance in a likewise manner. The basic database operations are select, project and join. "Select" retrieves data, "project" identifies data characteristics and "join" combines relations of data instances.[2]

Other advantages include scalability and data security. It is basically a useful tool similar to Microsoft Excel, except instead of having computational power, it only stores data but can be store an enormous amount of data/information. Data security capabilities provide certain users access to all datasets while giving the option of preventing some users to access only certain databases. 

[1] http://searchsqlserver.techtarget.com/definition/relational-database

[2] https://www.techopedia.com/definition/1234/relational-database-rdb


Comments:

Mark:

I read your article as a way to compare the content we found since we have the same topic. Essentially, we cover the same content such as keywords in the definition of a database, the importance of relations. Great job on including the figures as it highlights and exemplifies the difference between tables with relations and one without.

Tyler:

My blog post covered the topic of Relational Database Theory which is basically the body of data storing. But while reading I saw that SQL is the main "language" used when talking to these databases we created. And your article reinforced my initially understanding of what SQL does. The highlight of your article to me is that SQL is still used as the main language used to talk to databases which I would assume technology nowadays would have probably have replaced it. But I like your idea (more so a statement) that SQL is and should co-evolve with databases and its various types. Not just simple inventory tables but complex large scale data such as AutoCAD and Revit related data per family created.


Chris:

I agree that time is money and money is time in the world of construction. this DSM sounds like a pretty neat piece of technology that could potentially revolutionize future construction work. Hours vs Months is quite a feat to achieve but what I would be worried is the socio and economical problems that will arise when "machines start stealing human's jobs".



B5- Database

Database

I think data is the real asset of an organization. We will most likely interact heavily with databases during our professional career. Core database concepts and practices are extremely durable, and are likely to serve us for years to come. So, a collection of related data organized for easy storage and retrieval in electronic form will dramatically increase the efficiency of processing and understanding them. Almost any construction firm or other company in this field of appreciable complexity has information management requirements that are hard to satisfy without using a database. Since construction process always involve multiple companies working together from different aspects, the arrangement of database allows a number of different kinds of applications to work with the same set of data. Database can also ensure that the data must always meet certain conditions, such as ‘the span can’t be entered twice,’ regardless of the measurement manipulating it. We can also get the benefits of its security and concurrency. We can control who is authorized to manipulate what and govern what types of activities can take place at the same time. A database can also prevent data loss since it has the character of backup and disaster recovery. The most important thing is it can present different users with customized views of the same data. For example, each of your subcontractors will only have access to the data you want them to read. This can avoid wrangling and protect your trade secret in some degree.

I want to share an experience as the support of my above opinions. I was working for a small energy company for my first co-op cycle. Their duty is to re-design old structure's HVAC (heating, cooling and ventilating) system. I was involved in both field work and engineering design process. Their data managing techniques are relatively primary. They are collecting data from site investigation manually and I have to spend two hours per day for inputting them into computer. They do not process raw data before modeling or designing even though it is easy to be done on excel. I always need to convert units of the data for different design purpose. There are thousands of folders on their server and it always consumes a lot of time to find the proper one. These make their working efficiency lower than it should be. If they have a database that can perform all of the advantages as discussed in the first paragraph, their business will grow a lot faster and their work quality will increase a lot.
Comments:


Uses of databases in design offices
Shaden
We were doing the same topic. I am more focusing on database’s advantages while you made good efforts on illustrating the functions of database. You made a comparison between excel and database. This is really helpful to me since these two are having similar format and I sometimes confused about them.

SQL – What is it and why is it important?
Thomas
This is an informative and interesting post. I have only heard of database but I never know that there is a thing playing key roles interacting with elements in a database. I am taking a construction management course and I am taught to use Procore. It is an online software that the architect, engineer, GCs, owners can share and modify data. I think this platform is a good example of SQL. You can take a look of it if you are interested.

Object Oriented Database
Sherry
I like the graphs you used to help us to have a better understanding of object oriented databases. I have also read the original articles you listed in references. They are informative and helpful.

Monday, February 12, 2018

Relational Database Theory - Deutsch - B5

Before diving directly into what "Relational Database Theory" is I think it is first important to fully comprehend how a database is defined, along with how Big Data is defined. 

In general, a database can be defined as any collection or storage of information that is valuable, organized, searchable and applicable. In other words, it allows for management of files and their records which can be searched, grouped, rearranged and cross-referenced to facilitate easy retrieval for its users. Databases can be organized in any number of ways that are most applicable for what is being structured. A new technique that is being used more commonly as of late, is combining separate databases into larger entities which are now defined as "data warehouses". This is done mostly to help assist in pattern recognition which just reinforces how important databases and data sources are. 

Next, there is Big Data. According to Cringely, "Big Data" can be defined as "the accumulation and analysis of information to extract meaning." Even though this definition is quite broad, I like how far it allows us to delve into how much data we use and rely on without even knowing or realizing that we do so. I feel as though Big Data is similar to the "data warehouses" I mentioned earlier. In the past, storage of data and the capability to analyze that data was expensive and not done as often. Ever since individual computers became a normalized thing, data collection and storage has become much easier and cheaper to keep records of. Big Data is important because it aids in predicting events, the safety of groups or individuals, problem solving and connecting seemingly unrelated events that would have never otherwise been noticed. 

BIM is similar to Big Data and data warehouses in the way that it is also its own "environment". What I mean is that we treat it like data warehouses when we combine separate Autodesk programs in order to complete a project and use them as cross references, as our guest speaker last week, Derek, had mentioned he does often. It is also used as Big Data in the way that it keeps and stores all information in an organized and applicable way that allows its files to be easily accessed and managed by all those who require it to do so. 

This takes me to Relational Database theory. As stated by Darwin "Relational database theory is built around the concept of a relation" which is meant to be taken from a mathematical standpoint so that any number of things can be more easily related. What is important to remember when thinking of this definition is that relationships between multiple characteristics or objects are relational and not exactly "equal to" and this can be shown most easily by using a table, or most specifically the tables given by Darwin himself:
This table does not depict a relation
This table does depict a relation

What is of utmost importance to note however, is that although the second picture does demonstrate relational data, it does not matter what order the columns and rows are shown in. This data in these tables shown can then be searched. When a this relational data is searched, it is called a "query". To output specific information, constraints dictated by the inputted "query statement" will be applied and this will produce the desired data. Microsoft makes a program named Access Database which allows you to set up your own relational tables and query it at the end. It can be done using any desired informational fields, whether large or small.
 Although I had never thought too much about databases until this term, this is now the second time I have come across it since we just used Microsoft Access in my AE T580 class to teach ourselves how to relate specific data we came up with ourselves in a simple way. As explained by Darwin the order in which we defined our relationships did not matter when we ran a query. Seeing this fact in action helped me understand relational database theory much better. 

Sources:

https://dvikan.no/ntnu-studentserver/kompendier/an-introduction-to-relational-database-theory.pdf

https://www.evernote.com/pub/aengineer/ae-510#st=p&n=b751f481-0f42-4f45-a51b-a77127a94351&t=ec0a31ef-f3b4-42b8-b58d-6ed4124da841

https://www.britannica.com/technology/database


Comments:

Dung Tran - 
I really like how you approach the main topic of relational databases by first defining databases in general. I did something similar in my post. I also think you did an exceptional job in explaining how the the math side of relational data, or the relational algebra, connects to the overall concept. I did not get the chance to check out Codd's research paper but it seems to be very helpful in understanding this broad and complicated theory.

Chris Thatch - 
I agree that databases are of utmost importance within the construction field, especially within the management aspect of things. I know that a lot more companies are making a bigger effort in going paperless in more recent years which would be very helpful when it comes to contributing to the databases already in existence. While this is more efficient, offices have found themselves actually using more paper. I wonder why this is, do you have any input? Also, could you define what RS Means is in a bit more detail? I have never heard of it but it seems to be quite important.

Jianfeng Xiao - 
Reading your post is very interesting. I like the examples you give that connect ways in which we use data readily available to us now through new technologies that make prior methods of achieving the same tasks obsolete. Data is such a useful tool when it comes to design because it allows for us to take what we know and apply it in smarter ways, hence smarter buildings and environments also! I will have to check out the articles you cited.