The information stored in databases can most easily be organized like a spreadsheet, with rows and columns that have the ability to hold various types and quantities of data, while still being updatable. Each database is useful to and for different people and things, and within a construction company, there can be many applications. For instance, construction companies can have internal databases, where past project information (such as plans, coordination, notes), company information (such as policies, agendas, employee info), and presentation information (such as templates, letterheads, procedures) can be stored. Construction companies will also deal with external databases, where current and future project information, vendor lists, and product specifications can be stored.
Storing data like these in databases is helpful from an organizational standpoint. The user knows what they need and what database to search in. Often, database results can be queried or filtered to make finding the information required even easier. Databases are even more valuable because of the ability to put the database online. External databases can be accessed by anyone at any time, even have multiple users at once, because it is open to the public. Internal company databases may not be open to the public, but are most often than not put on the cloud, that is, internet based data storage. This means that a database does not need to be downloaded onto one’s personal computer or onto a flash drive to be saved or stored. This makes sharing and access either between companies or within a company extremely simple.
Responses
Madeline,
With today's technology and the pace at which we are moving, I think it would be really difficult to get anywhere as a design firm without integrating the use of databases. I like how you tied collaboration and databases together, what would the point be if all this stored information could not be shared? Also, your Augmented Reality example is something that makes complete sense, but I would have never thought that the components that go into AR are themselves databases. Goes to show how applicable and essential databases truly are.
Amanda,
From someone who has never heard of Object-oriented databases, you really broke this concept down well. It seems much more complicated than general databases, which at their simplest form are just spreadsheets, but more worthwhile, especially from a saving and sharing standpoint. It makes sense that OODBs aid on the interoperability front.
Mika,
I have never heard of SQL or NoSQL before, so I appreciate the concise way that you broke the two down. From my understanding, the only benefit to using NoSQL is that it is better at handling large data sizes. Is there ever a time where you would use NoSQL for a basic database, or is it simply more beneficial to stick with SQL because it is easier to learn and apply? It seems like not only is SQL really valuable in data management, but also as a general skill that can be applied to various fields.
1 comment:
Hey,
I read through this article too so it was interesting to hear your take on it. The planning, coordinating, and organizational aspects that databases present firms like this is by far the most beneficial aspect in my opinion. I think you also bring up some interesting points of the different type of databases and how the different ways they are accessed can be helpful lin different ways.
Post a Comment