Data Base Management Systems - Literature review Example

DATA BASE MANAGEMENT SYSTEMS (DBMSs) By Name Course Instructor Institution City/State Date Table of Contents Table of Contents 2 Data Base Management Systems (DBMSs) 3 1.0 Introduction 3 2.0 Popular DBMS Products that are based on the Relational Data Model 4 2.1 DB2 4 2.2 Oracle 5 2.3 MySQL 6 2.4 MS Access 2010 6 3.0 DBMS products are based on a logical model 7 3.1.0 Object-Based Logical Models 7 3.1.1 Object-Oriented Model 8 3.1.2 The Entity-Relationship (E-R) Model 8 3.2 Record-Based Logical Models 8 3.3 Objects-Relational Data Models 9 4.0 Relative Strengths and Weaknesses of the Different Types of DBMSs 10 The relational databases have a number of strengths; for instance, its supports tables, which are a simple form of data structure and they also limit data duplication and redundancy. In addition, inconsistencies associated with data are avoided and they offer a largely physical data independence. Besides that, relational databases provide independence in the logical database to the extent that different users can view the data in different ways. The data in the RDBMS can be communicated easily with others and there is no need for the users to utilise the predefined keys while inputting the information. In RDBMS, searching can automatically be optimised and makes the learning and implementation of SQL easier. Furthermore, RDBMS supports very large databases and are considered to be more productive since learning the SQL is very easy. As a result, the users can use more of their time to input information rather than learning. The RDBMS has some weaknesses; for instance, it does not have effective as well as efficient integrated support and lacks adequate storage area to manage data like audio/video, digital and, images. Given that the relational tables it is difficult for RDBMS to offer sufficient support for structures that are nested, like arrays as well as sets. Moreover, representing some types of relationships in RDBMS, like the sub-typing between objects of the database is more challenging. 10 5.0 Conclusion 11 6.0 References 12 Data Base Management Systems (DBMSs) 1.0 Introduction The database management system (DBMS) can be described as a software package that has computer programs utilised for managing the database creation, use, and maintenance. Basically, DBMS enables business organisations to develop databases conveniently for different applications by specialists such as database administrators (DBAs). Therefore, DBMS can be defined as software developed purposely to help in maintenance and utilisation of large data collections. Actually, DBMS is a tool utilised to perform all types of operation on the database data and also offers security as well as protection to the database. More importantly, it ensures that there is data consistency when the number of users is high. Common DBMS includes IBM DB2, Sybase, Oracle, MySQL, Microsoft Access, and so forth. The DBMS has the ability to provide both physical as well as logical data independence. Specifically, applications and users are protected from the need to know the place where the storage of data happens or becoming worried about changes of the physical data structure. Provided that the application programming interface (API) program is utilised for the database offered by the database management system, there will be no need for developer to modify programs due to changes made to the database. The objective of this report is to examine the popular DBMS products that are based on the relational data model and other logical data models as well as their relative strengths and weaknesses. 2.0 Popular DBMS Products that are based on the Relational Data Model According to Singh (2015, p.76), the data files relationship in relational databases is not hierarchical but relational. The needed data in network and hierarchical databases can only be accessed when the user pass down through hierarchy. Basically, data in relational databases are connecting in various files through a key field or common data elements. Different tables are used as storage of relational databases’ data; all have key fields which distinctively identify all the rows. Besides that, relational databases are considered to be more flexible as compared to network and hierarchical database structures. Files or tables in relational databases are filled with data recognised as relations, columns are known as fields or attributes, and a record or row is designated by tuples. The principle of relational databases is that all tables have key fields which identify all rows uniquely, and such key fields could be utilised in the connection of data tables. Therefore, one table could have a row that has the account number of a customer as the key field together with telephone as well as address number. In this table, the account number of the customer could be connected to a different table of data which entails a key field (the account number of the customer), but contains information regarding the returns of the product, which includes another key field such as an item number. 2.1 DB2 One Popular DBMS products associated with relational data model is the DB2, which is a Relational Database Management System from IBM. Basically, DB2 was developed purposely for the efficient storage, analysis, and retrieval of the data. DB2 normally runs on Linux, Windows or UNIX server machines and could be administered from a GUI interface or a command-line. Bassil (2012, p.22) describe the GUI as a Java client multi-platform that has different wizards appropriate for novice users. On the other hand, the knowledge needed in the command-line interface needs with regard to the product is high but could be automated and scripted more easily. Bassil (2012) asserts that the DB2 supports XQuery as well as both SQL and has espoused the XML data storage, whereby XQuery is used to facilitate the storage of XML data as XML to improve accessibility. Furthermore, DB2 facilitates the Visual Studio and Eclipse integration. The error processing is considered to be the most crucial feature of DB2 whereby area structure of SQL communications is utilised in the DB2 program to ensure that after every API call, error information is returned to the application program for a Structured Query Language (SQL) statement. Clearly, DB2 is a suitable choice for business solutions since it provides reliability, scalability and flexibility to all types of businesses regardless of their sizes. 2.2 Oracle Oracle Database is also another type of RDBMS product from the Oracle Corporation that has no less than one application instance and data storage. Basically, an instance includes a set of memory structures as well as operating system processes which are interacting with the storage. Other than storage, Oracle database has an online-based redo logs that normally archive the transactional history. In consequence, the archive logs can be used by the processes to archive the online-based redo logs and offers a source for data replication and data recovery. In the Oracle as mentioned by Bassil (2012), data is physically and logically, as data files and table-spaces, respectively. Data files at the physical level involve more than one data blocks, in which the size of the block could differ between data files. Oracle database normally includes data clusters, indexes, and dictionary. 2.3 MySQL MySQL as pointed out by Saikia et al. (2015, p.160) is an open-source, free, multi-user, and multithreaded SQL DBMS. In this product, the server is the basic program offering multi-user access to numerous databases. The MySQL normally comprises of a broad subset of the American National Standards Institute (ANSI) SQL 99, and updatable views, cross-platform support, extensions, triggers, stored procedures, cursors, as well as a distributed transaction processing (X/Open XA) support. In addition, MySQL supports embedded database library, Secure Sockets Layer (SSL) support, independent storage engines, commit engine (two phase), replication, query caching, as well as Atomicity Consistency Isolation Durability (ACID) compliance. MySQL offers scores of features such as platform, supports many types of data, works in multiple platforms, and its execution is very fast. 2.4 MS Access 2010 Microsoft Office Access is another type of RDBMS product from Microsoft that integrates a graphical user interface with a Microsoft Jet Database Engine as well as tools for software development. MS Access is considered to be beneficial because it is compatible with the SQL queries. The Jet Engine is different from the complete RDBMS because it does not have stored procedures and database triggers. But still, it offers a unique syntax which facilitates the use of parameters to create queries, in a manger that is similar to the creation of stored procedures; however, there is limitation to these procedures since one statement can be generated per procedure. MS Access enables the forms to have code capable of triggering changes to the underlying table. Besides that, MS Access is commonly utilised by large corporations’ departments, small business enterprises, and also by hobby programmers in creating improvised customised desktop systems that handles data creation as well as manipulation. A number of professional developers utilise the MS Access to develop application rapidly, particularly when creating standalone and prototypes applications which serve as on-the-road salesmen tools. 3.0 DBMS products are based on a logical model According to Birgi et al. (2016, p.611), logical data models (LDMs) are commonly utilised to understand and organise the structure of information. They are utilised in exploring the concepts as well as associated relationships of the problem domain. Furthermore, LDMs demonstrates the entity types, the relationships that exist between these entities, and the data attributes defining such entities. As pointed out by Birgi et al. (2016) LDMs are hardly utilised in the agile projects as compared to the traditional projects. They include all the needed key groups, attributes, entities, as well as the relationships representing the business information. Therefore, the LDM can be described as a data model that is fully-attributed which is independent of data storage, technology, DBMS or organisational limitations. The LDM common characteristics include its ability to describe the requirements of data from a major subject area or a single project and can be integrated with other LDMs through a shared entities repository. Normally, a logical data model is associated back with or comes from objects within the conceptual data model. 3.1.0 Object-Based Logical Models Object-based models as indicated by Silberschatz et al. (1996, p.105) utilise the concepts of objects or entities as well as the relationships between them instead of concepts based on implementation, like records, utilised in the record-based models. This type of LDM offers numerous capabilities such as flexible structuring and facilitates the explicit specification of data constraints. Object-based models can be grouped into entity the object-oriented model as well as -relationship model. 3.1.1 Object-Oriented Model Silberschatz et al. (1996) posit that this model is a version of the database systems’ object-oriented programming language model. Basically, Object-Oriented Model is rooted in the encapsulating data concept, as well as the code operating on the data, within the object. The data and code encapsulation has been cited by Silberschatz et al. (1996) as valuable in the development of modular systems. This type of model lengthens the object-oriented paradigm’s features of data modelling. In this case, the extensions comprises of data persistence (that facilitates the differentiation of transient data from the persistent data), data integrity constraints, as well as collections’ support. 3.1.2 The Entity-Relationship (E-R) Model This model is considered to be amongst the semantic data models that try to signify the data meaning. Normally, this model utilises three basic concepts: attributes, relationship sets, as well as entity sets. In this case, the entity as the basic concept can be described as an object within the real world which could be differentiated from the other objects. Therefore, an entity set includes a same type of entities set sharing a similar attributes (or properties). On the other hand, the attributes are considered to be properties that are descriptive and which every entity set member possesses. All entities have their own values for all attributes. The relationship can be defined as the connection amongst numerous entities. Some of the E-R model includes generalisation, specialisation, lower-level and higher-level sets of entity, aggregation, as well as attribute inheritance. 3.2 Record-Based Logical Models The structuring of this type of LDM is in fixed-format records, whereby all types of records define the attributes and the number of fields that have been fixed. Normally, every field has a fixed length and the utilisation of the fixed-length records makes the physical- level database implementation simpler. Aside from relational model, other types of record-based logical models established include the hierarchical model and the network model which are closely associated with the database underlying implementation, but their significance has declined. The network data model is commonly utilised in the databases implementation. For that reason, the model is not associated closely with the relational model as compared with the physical-level design. In addition, the representations of data items in the network model are achieved through records collections as well as data relationships are represented through links. On the other hand, the hierarchical model is almost the same as the network model save for the fact that its links in have to form a tree structure, while the network model permits for arbitrary graphs. 3.3 Objects-Relational Data Models This type of model according to Silberschatz et al. (1996, p.107) is the hybrid of the relational data models and the object-oriented. In essence, the relational data model is extend through offering of an object-oriented concepts as well as extended type system. As a result, the complex types such as nonatomic values are allowed by the extended type at the relations and attribute domains levels. Basically, these extensions try to protect the relational foundations and at the same time extend the power of modelling. 4.0 Relative Strengths and Weaknesses of the Different Types of DBMSs The relational databases have a number of strengths; for instance, its supports tables, which are a simple form of data structure and they also limit data duplication and redundancy. In addition, inconsistencies associated with data are avoided and they offer a largely physical data independence. Besides that, relational databases provide independence in the logical database to the extent that different users can view the data in different ways. The data in the RDBMS can be communicated easily with others and there is no need for the users to utilise the predefined keys while inputting the information. In RDBMS, searching can automatically be optimised and makes the learning and implementation of SQL easier. Furthermore, RDBMS supports very large databases and are considered to be more productive since learning the SQL is very easy. As a result, the users can use more of their time to input information rather than learning. The RDBMS has some weaknesses; for instance, it does not have effective as well as efficient integrated support and lacks adequate storage area to manage data like audio/video, digital and, images. Given that the relational tables it is difficult for RDBMS to offer sufficient support for structures that are nested, like arrays as well as sets. Moreover, representing some types of relationships in RDBMS, like the sub-typing between objects of the database is more challenging. On the other hand, the Object-Oriented Model DBMS (OODMS) has some strength such as ability to represent information that is more semantic, data types’ extensibility, ability to support complex objects, attributes such as reusability and versioning, and the ability to integrate DBMSs to create a single environment. Some of the OODMS weaknesses include; low presence in the market, stiff competition from established RDBMSs, non-existing standard ad hoc query language, and incompatibility between various types of OODBMSs. Objects-Relational DBMS (ORDBMS) also has strengths; for instance, the database engine can manage all the issues associated with backup and transaction integrity. It can handle complex and large applications and allows the use of parallel server technology. The major weakness of ORDBMS is the fact that the database must be integrated with the long-running design transactions as well as adequate client-side data management so as to offer adequate technical applications support. Besides that, its performance in web applications is very poor. 5.0 Conclusion In conclusion, this report has examined the popular DBMS products that are based on the relational data model and other logical data models as well as their relative strengths and weaknesses. As evidenced in the report, the RDBMSs are widely utilised in the modern-day business organisations to offer adequate data retrieval and storage. For the OODBMS to be included in the RDBMS environment the existing databases should be modified so that data access and communication can be allowed among them. All in all, the DBMS help business to generate an environment where customers can easily access data that is storage. As a result, customers are able to quickly respond to changes within their environment. As pointed out in the report, the DBMS offers a framework that improves data security and privacy. The DBMS products do not only improve data access in business organisations, but also enhances the processes of decision making. Clearly, an improved access to data facilitates the generation of better-quality information that can be used to make better decisions. The RDBMSs improves the end-user productivity since the users are empowered to make informed and quick decisions which could make the difference between failure as well as success in the market. 6.0 References Bassil, Y., 2012. Comparative Study on the Performance of the Top DBMS Systems. Journal of Computer Science & Research, vol. 1, no. 1, pp.20-31. Birgi, J.S., Khaire, M. & Hira, S., 2016. Data Model: A Blueprint for Data Warehouse. International Journal of Scientific and Research Publications, vol. 6, no. 1, pp.610-13. Saikia, A., Joy, S., Dolma, D. & Mary, R., 2015. Comparative Performance Analysis of MySQL and SQL Server Relational Database Management Systems in Windows Environment. International Journal of Advanced Research in Computer and Communication Engineering, vol. 4, no. 3, pp.160-64. Silberschatz, A., Korth, H.F. & Sudarshan, S., 1996. Data models. ACM Computing Surveys, vol. 28, no. 1, pp.105-08. Singh, S., 2015. Database Management System. Journal of Management Research and Analysis, vol. 2, no. 1, pp.72-80. Read More