SQL (Structured Query Language) is defined as a
special purpose programing language that was designed to work with relational
databases (1). Although it’s been around for a long time, SQL is still the
primary program used for the relation between an application and a relational
database. There are many tools associated with SQL that have been designed for
specific functions or jobs. These tools enhance the ability of various features
of SQL to meet different criteria. For example, PHPMyAdmin allows you to easily
add and edit visuals associated with your database. It also allows you to
create new databases or delete old ones. Once you have a database created you
can begin to build it out using the coding language. You can add request boxes
for things like names, ID numbers, and addresses by creating a table for a
specific type of entry. Once a table has been created specific data can be
added for individual customers or projects. Each line of data can be assigned a
specific ID number, this allows you to edit data associated with a specific
object.
The types of functions can all be entered by hand by
the database administrator but the real power and functionality of this comes
with the ability to automate databases. In the RG Edu video, Brian Alderman talks
about the benefits of using data bases and is quick to point out that a lot of
things that we encounter daily are associated with databases (2). Everything
from grocery store inventories to airline company websites. By using a
collection of tables that are able to talk to each other with primary keys you
can create a functional relational database that is able to do a wide range of
things. In terms of design tools, being able to have a database that contains things
like objects and book cases is extremely helpful for large projects since all
you have to do is grab the data rather than redesign each piece. Data bases like
this already exist and are being used in programs like AutoCAD and Revit. As
these design programs become more powerful the databases associated with them
also need to co-evolve. If you think back to the one BIM video we watched in
class, each door had its own product info that would appear when selected, this
was a prime example of how these databases can be used to further enhance design
tools.
1. Traversy Media. “SQL Crash Course – Beginner to
Intermediate.” Youtube, commentary by Brad Traversy, 29 Mar. 2016, https://www.youtube.com/watch?v=nWeW3sCmD2k
2. RG Edu. “Database Fundamentals – Introduction to
Core Database Concepts.”
Youtube, commentary by Brian Alderman and Pete
Harris, 25 May 2014, https://www.youtube.com/watch?v=GdeaqBCR5PQ
Responses:
Jacob,
It is clear that databases can be very useful for
constructions firms because they can quickly and easily track data for multiple
projects at the same time. Being able to track everything from revision dates
to product inventories is a great way to have a complete understanding of where
a project is at. One problem that could develop is that this amount of data
becomes overwhelming. A good database will keep it organized but it seems like
an easy way to overload a system and cause possible crash scenarios. This is
why these databases must coevolve along with the BIM technologies that they are
associated with.
Amisal,
I agree with your leading point about how any successful
business also has an effective database that they use. I work part time for a
company right now who have a functioning database but there are a lot of reoccurring
flaws. These flaws account for multiple hours of wasted time each week. Its
easy to see how a properly designed database can streamline workflow no matter
what that workflow might be.
Isaac,
You bring up a great point about how each part of
the process can be easily documented and tracked using databases. This can be
especially helpful for regulatory agencies since they need the most updated and
accurate data to enforce regulations and policies. Without accurate tracking
and recording these regulations might as well not exist. Incorporating these new database technologies
is a good step towards making government regulators more efficient.
Wicker,
ReplyDeleteYour writing about Structured Query Language (SQL) was enjoyable, and I agree with you by stating that SQL must evolved alongside with some design programs. In fact, as you understand the relationship between SQL and design program or database, it becomes more efficient for the user, and their both intended purposes are more reachable.
Tyler,
ReplyDeleteMy 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.