What are the tradeoffs between relational and object-oriented databases and database management systems - Essay Example

?TRADEOFFS BETWEEN RELATIONAL AND OBJECT-ORIENTED DATABASES AND DATABASE MANAGEMENT SYSTEMS Tradeoffs between relational and object-oriented databases and database management systems Author Author Affiliation Date First Part ODBMS or RDBMS This section of the paper will present a detailed analysis of some of the important aspects of relational, object-oriented databases and database management systems. This section also outlines tradeoffs between relational, object-oriented databases and database management systems. RDBMSs (Relational Database Management Systems) have been offering excellent services and benefits to their users; however this achievement is incomplete as well as limited to only some kinds of applications. In view of the fact that the business clients adopt latest versions of systems, as well as develop to previous ones, their efforts to make use of RDBMS come across the "Relational Wall," where RDBMS technology is no longer capable to offer the functionality and services required by the users. Additionally, users face this barrier when they try to enlarge information models to sustain associations among data, novel data types, extensible data types, and straight support of data objects. In the same way, the barrier can take place when implementing database in distributed environments through complicated processes. On the other hand, attempts to resolve these issues with relational technology cause an explosion of tables, a lot of joins, deprived performance, unfortunate scalability as well as loss of integrity. Thus, ODBMSs present a path further than the wall (Objectivity, Inc., 2005). Additionally, the emergence of new generation of Relational Database Management Systems has offered a lot of advantages to clients. These advantages comprise unplanned query, self-governing data from logical application, and a variety of front-end GUI (graphical user interface) systems. In addition, it has also offered many business applications, as well as the business sector has expended to over $4B yearly, comprising tools. There is a question that why we should look beyond RDBMSs? We should perform so simply when essential to capability and support of new types of systems, new associations, distribution, media data types as well as scalability. In reality, the majority of systems and applications have never made use of RDBMSs, and a lot of applications that have utilized RDMBS are now searching for other options, like that ODBMSs (Objectivity, Inc., 2005). In addition, the relational databases have offered a high-quality service in a lot of customary database systems. Despite the fact that, in many scenarios for instance when it is complicated to deal with information, or when superior efficiency is needed (i.e. objects having anonymous identifiers, or objects going from one type to another, etc.), or when we need to manage non-conventional data (such as images, long texts, etc.), additional techniques need to be implemented. Normally, these techniques include object-oriented or semantic databases. Additionally, the semantic database models are object oriented database models. Moreover, they present, a variety of levels, a lot of characteristics of semantic models, in the form of conceptual information, as well as, purify a number of behavioral characteristics of the data (Rishe, 2010). However, if a RDBMS can resolve our problems without numerous efforts as well as offers the required results, efficiency and scalability then there is no need to utilize an ODBMS. If some of the below given situations are convened then we should think about using ODBMS. Below are some of the important reasons that require us to make use of RDBMS: (Objectivity, Inc., 2011) Complicated Relationships: If we are having numerous many-to-many relationships in our database, tree arrangements or network (graph) formations (Objectivity, Inc., 2011). Complicated Data Arrangement: If the data has numerous changeable length parts, such as arrays of structures, multi-dimensional arrays or binary streams (Objectivity, Inc., 2011). Distributed Databases: If we need to implement a physically distributed database, which is implemented and utilized as a separate part or is accessed via a computer network (Objectivity, Inc., 2011). Multiple Platforms or Languages: If the system will be developed by utilizing multiple languages and/or business working and operational platforms (Objectivity, Inc., 2011). Working Sets of Objects: If our business system carries out a lot of consecutive transactions on the similar "working arrangement" of objects (Objectivity, Inc., 2011). Huge Scalability: If we are having an extremely huge quantity (Petabytes) of data, databases located at various different places or an extremely large numbers of database users (Objectivity, Inc., 2011). Costly Mapping Layer: There is no need to customize objects in order to well match with database’s rows and columns; or to stop making unplanned database queries by storing recording data like Binary Large Objects; otherwise to apply artificial JOIN database tables for presenting tree and network or many-to-many application relationships (Objectivity, Inc., 2011). Moreover, Relational Database Management Systems work very efficiently and effectively for various kinds of systems, mainly in the customary Information Technology field. On the other hand, the objective of ODBMSs is to deal with a narrow variety of systems; consequently the possible market share is small. Generally, ODBMSs are able to serve all the systems that an RDBMS could be utilized for; however it is not true in case of RDBMS, in any case not with something like the same efficiency or easiness (Objectivity, Inc., 2011). Furthermore, the RDBMS businesses have a 15 year lead; thus they have a well-known position and a moderately loyal customer base, frequently with database installation licenses that hide the actual prices of possession. On the other hand, ODBMSs are easy to learn as well as less costly to implement as compared to RDBMS, consequently an ODBMS could be a best alternative for a new product or business (Objectivity, Inc., 2011). Second Part Access or Excel This section will analyze different technologies for storing data. The purpose of this analysis is to suggest a database technology that is suitable for the business or personal use. In this scenario I will evaluate spreadsheet and Microsoft Access database. When the analysis of data becomes very difficult then it is necessary to make use of databases. Before choosing Microsoft Access we need to know what we want to do that is beyond Excel, consequently we are searching for alternatives. Additionally, it is as well possible that our IT department would not facilitate us regarding this being even additionally possible as the depression decreases reporting budgets right, left and center. In addition, while deciding for implementing database we need to keep in mind the following points: (Standen, 2009) Flexibility to Join Tables: MS Access offers a simple method to create joins among tables, which is also one of the influential characteristics of relational databases. Data Volume: It is very complicated to manage more than a million rows in MS Excel; even previous to the performance suffers (Standen, 2009). Additionally, MS Excel is recognized as spreadsheet software and for beginner users it is utilized to record fundamental information; like that staff schedules, phone numbers, names and basic calculation inputs. However, for trained users, Excel is an outstanding application for carrying out simple and complicated computations as well as analyzing data on a large scale. In addition, by learning how to produce flexible formulas, making use of Pivot Tables, and a lot of other characteristics like that data validation and macros, Excel is able to complete almost any task (Curmudgeon, 2011). Moreover, MS Excel can be used to track staff’s working plans, calculating the weekly wages of staff members, as well as for personal usage such as determining a retirement plan. All of this could be arranged in as a flexible worksheet, in place of making a new for each task. On the other hand, Microsoft Access is also a great tool for developing business databases and information management. This application is recognized as a relational database, which outlines that data functions both separately and interdependently (using tables) to permit the database client to put together data from different locations and analyze and/or report data in approximately countless ways (Curmudgeon, 2011). Additionally, MS Access is able to store huge amount of information and data in diverse forms which can be turned for simple referencing as well as evaluating. In addition, other kinds of relational databases are the locations that refer to the keywords as well as show articles, etc. However, the question is that which one is best and most suitable for use. It depends on the condition or amount of data we are going to use. MS Excel is a most excellent choice in case of calculations. Thus, it can be used for CPA or financial expert, since spreadsheets were developed to shorten and systematize financial data. On the other hand, making use of MS Access for calculations is similar to making use of a butcher's knife to butter our bread (Curmudgeon, 2011). However, MS Access could be a most excellent choice for storing huge amounts of data and information that have relational fields. Since this tool allows us to simply reference the data as well as keep it preserved. For example, for keeping employees’ address, name and phone number it would be very simple to list it on Excel. On the other hand, if we require storing extra data and information like that personal data, job information, hobbies, networking details, gift buying history, etc., that can be used for more than one entity, we will certainly need to make use of MS Access (Curmudgeon, 2011). Furthermore, if we have additional difficult requirements for our database, Access is a best option. Despite the fact that MS Access is not as simple for a lot of people to be trained on their own, it was developed to be both influential and user friendly. However, through some research and/or training, we could be able to develop a functional database. Additionally, one of the major benefits of Access over Excel is that it is a relational database. In other words, it has the potential to store data in more than one table as well as transmit or link the tables on widespread fields. In this way, it gets rid of the redundancy of a "flat" file database and makes the data entering process very simple. However, if someone is expert in Excel and it convenes their requirements, then the complete data they enter could be brought into MS Access afterward. On the other hand, MS Access has an extremely simple characteristic to export its data to Excel. Lastly, there is no standard rule stopping us from making use of both applications, if we can easily do it (Gee, 2009). References Curmudgeon. (2011). Software Decisions: Access vs. Excel. Retrieved July 14, 2011, from http://hubpages.com/hub/Access_vs_Excel Gee, B. (2009, May 01). Access vs. Excel - Which should I use for my database? Retrieved July 12, 2011, from ArticlesBase.com: http://www.articlesbase.com/computers-articles/access-vs-excel-which-should-i-use-for-my-database-895831.html Objectivity, Inc. (2005). Hitting The Relational Wall. Retrieved July 09, 2011, from http://www.objectivity.com/pages/downloads/whitepaper/pdf/RelationalWall.pdf Objectivity, Inc. (2011). ODBMS versus RDBMS . Retrieved July 12, 2011, from http://www.objectivity.com/pages/objectivity/faq.asp#ODBMS versus RDBMS Rishe, N. (2010). Semantic, Relational and Object-Oriented Databases. Retrieved July 15, 2011, from http://hpdrc.cs.fiu.edu/library/papers/SDBMS.RDBMS.OODBMS.html Standen, J. (2009, May 03). MS Access vs Excel vs Datamartist. Retrieved July 15, 2011, from http://www.datamartist.com/ms-access-vs-excel-vs-datamartist-a-do-it-yourself-guide Read More