Research Proposal on "Comparison of Database Management Systems"

Research Proposal 12 pages (3329 words) Sources: 3

[EXCERPT] . . . .

Management Systems

Appendix a Project Process Integration Diagram

Appendix B Process Flow Chart

Open Source Security Tools

DBMS Features Analysis

Figure 2 Three Pillars of Security

The database market continues to consolidate with Oracle acquiring Sun Microsystems, who had acquired MySQL AB in January, 2008. While there are dozens of vendors in the database management systems (DBMS) market, IBM, Microsoft and Oracle dominate the market with 88% market share according to International Data Corporation (Worthen, Kiviniemi, 2009). As DBMSs are often customized to the specific needs of the companies using them, this consolidation does not spell the end of the heterogeneous nature of this market. Organizations' needs are so diverse and the structure of their data and use of applications so varied, that the many vendors in this market are staying relevant and growing as a result. This fragmentation of the database market has opened up significant opportunities for Computer Associates (CA), Software AG, Sybase and many open source databases the highest performing being Ingres, MySQL and PostgreSQL. The lower Total Cost of Ownership (TCO) and speed of new product development innovation in open source, specifically MySQL, has redefined the direction of the DBMS market globally (Hyatt, 2008). Oracle as a result continues to be in a defensive posture with regard to the economics of open source, hence their acquisition of Sun Microsystems which includes MySQL AB (Worthen, Kiviniemi, 2009). As a result of these market dynamics, MySQL continues to excel from a technological and user adoption perspec
Continue scrolling to

download full paper
tive (Denton, Peace, 2003). The intent of this analysis is to evaluate MySQL's technical functionality vs. To PostgreSQL, Oracle and Microsoft SQL Server. Components of their current offering, market presence and strategy are defined.

Introduction

For the typical enterprise today the need for integrating a variety of databases is critical, as each contributes a unique strength to an enterprise-wide strategy. The majority of enterprise and organizations are integrating several databases together, each specifically designed for a given applications' needs (Giacomo, 2005). Open source DBMS have had the advantage of a lower TCO, faster potential time-to-market given the open source community's level of innovation relative to enterprise software companies (Hyatt, 2008) and the expanded security model which MySQL has been able to fine-tune the shared security model of their kernel as well (Pereira, Muppavarapu, Chung, 2006). In analyzing a performance benchmarks of open source vs. enterprise applications (Denton, Peace, 2003) (Giacomo, 2005) (Hyatt, 2008) (Pereira, Muppavarapu, Chung, 2006) and (Ramsey, 2003) it is clear that the performance of MySQL on platform scalability and user adoption is exceptional compared to other competing DBMS. MySQL also has concentrated on adoption, and has a result significantly driven up the total user count on their systems as a result (Hyatt, 2008). Application data integration, 3rd party application support, performance analysis, scalability, database programming and application development are all critical factors as well. This report concentrates on a compatibility and performance of Microsoft SQL Server, MySQL, Oracle 11g and PostgreSQL. The specific product versions include Microsoft SQL Server 2008, MySQL 5.1, Oracle 11g, and PostgreSQL 8.3. The majority of these databases were introduced in the late 2008 timeframe, with Oracle 11g being released in October, 2007. The three dominant uses of databases are Online Transaction processing (OLTP), data warehouses and specialized databases. Each of these databases began with the explicit design goal of providing relational database performance in the context of OLTP in the context of role-based workflows. The catalyst of growth for databases, both closed source and open source, continues to be the growth of roles-based technologies including Web Services and Service-Oriented Architectures (Denton, Peace, 2003). MySQL and PostgreSQL have historically lagged in terms of enterprise application support yet have had exceptional growth in security modeling and Web Services. For a matrix overview of representative security utilities and tools on open source DMBS including MySQL please see the Appendix C Open Source Security Tools in the Appendix. In conjunction with the security models open source DBMS developers are adopting, analysis indicates open source DMBS can be more security that closed source (Pereira, Muppavarapu, Chung, 2006) (Ramsey, 2003). These configurations of DBMS are highly dependent on the security requirements and security audit procedures of the organizations adopting them (Pereira, Muppavarapu, Chung, 2006). From the analysis completed for this paper the scalability and platform support for open source, as of 2006, continues to surpass closed source. As the TCO is much lower for MySQL and PostgreSQL there has also been a corresponding increase in interest from system integrators and resellers in these open source DBMS. The reason is that the maintenance frees for Oracle 11g and Microsoft SQL Server continue to escalate rapidly which has also created interest in closed database customers' organizations to seek out the cost advantages of open source as well (Spanbauer, 2008).

Discussion

Analyzing attributes or characteristics of the current offerings of closed database vendors Microsoft SQL Server 2008 and Oracle 11g in addition to open source vendors MySQL and PostgreSQL is the intent of this analysis. Within the current offering, the criteria of performance and scalability, security and adoption of security models, application development, database security, platform support and database administration can be used as a common set of criteria for evaluating closed source and open source offerings. Next, the strategy of the vendors including their product strategy direction, and commitment to the specific design objectives are discussed. Finally factors including company financials, adoption rate, training and certification and system integrator and partner support are evaluated. What emerges from this analysis is an assessment of each of the DBMS.

Across the four DBMS being included in this analysis, it is noteworthy that MySQL 5.1 has the greatest level of reliability as shown by the multiple technologies that are used. Even Oracle 11g, the highest capitalized DBMS from a product development standpoint, has only bitmapped, B-tree, IOT and function-based security. It does not however include full-text, which is essential when a database is being as the foundation of an enterprise content management system for example (Pereira, Muppavarapu, Chung, 2006). Table 1, DBMS Features Analysis provides an assessment of these applications across the functional areas of data storage, indexes support, data integrity, replication, interface methods and Advanced Features. Of the open sources databases the one with the best possible scalability is MySQL. This is specifically due to the design of the OLTP engine and structure within the applications' platform (Ramsey, 2003) (Spanbauer, 2008).

Figure 1: DBMS Features Analysis

MySQL 5.1

PostgreSQL 8.3

Oracle 11g

Microsoft SQL Server 2008

Data Storage

Reliability

MyISAM, InnoDB, Berkeley DB, full-text

Postgres

Bitmapped, B-tree, IOT, function-based

Clustered, nonclustered

Scalability

Large/Very Large

Large

Large/Very Large

Large/Very Large

Indexes

Single and Multi-column, primary key, full text

Yes

Yes

Yes

Yes

Data Integrity

ACID compliance, row-level locking, hot backup and partial backup

Yes

Yes

Yes

Yes

Replication

Single master

Yes

Yes

Yes

Yes

Multimaster

Yes

Yes

Yes

Yes

Clustering

Yes

Yes

Yes

Yes

Interface Methods

ODBC/JDBC, C/C++, & J2EE

Yes

Yes

Yes

Yes

Advanced Features

Stored procedures, views, triggers, sequences and cursors

Yes

Yes

Yes

Yes

Sources: (Denton, Peace, 2003)(Giacomo, 2005)(Goans, Leach, Vogel, 2006) (Hyatt, 2008) (Ramsey, 2003) (Pereira, Muppavarapu, Chung, 2006) and websites

Each of the four database are now analyzed according to the nine attributes of platform scalability, user adoption, application data integration, 3rd party application support, performance analysis, database programming and application development. While the closed source vendors have gone aggressively in the direction of creating Service Oriented Architectures (SOA) and composite applications through Web Services (Pereira, Muppavarapu, Chung, 2006) open source DBMS providers have continued to focus on making their core OLTP performance improve significantly over time (Hyatt, 2008).

As a result of the open source DBMS providers concentrating on this aspect first their product roadmaps have taken them in the direction of supporting greater platform breadth which according to studies from AMR Research, Gartner Group and International Data Corporation (Hyatt, 2008) they are achieving greater levels of RDBS and associated application scalability as well. In analyzing the four vendors including in this paper, MySQL is the most scalable from both an DBMS and application platform standpoint (Pereira, Muppavarapu, Chung, 2006). This is due to the kernel for MySQL being scalable and also modular enough for continual improvement and addition of functionality. All of these factors in conjunction with their support for Very Large Database (VLDB) architectures has open source vendors delivering greater levels of scalability and also more agnostic or non-vendor specific as well. Microsoft and Oracle both tend to see integration often from a purely myopic view; they see only the integration of their components toe ach other and to partners' applications. Open source is forced due to its heavy reliance on innovation to concentrate on having a more heterogeneous and therefore varied integration strategy (Hyatt, 2008). This forces DBMS vendors to continually benchmark OLTP, data warehousing, and Web-based application development to ensure they are continually improving inter-database and inter-process scalability and performance (Pereira, Muppavarapu, Chung, 2006). This has become a best practices specifically for open source… READ MORE

Quoted Instructions for "Comparison of Database Management Systems" Assignment:

The report that I*****m required to create is a work term report for a technical report course. Here is an excerpt (below) from my course*****s engineering report guidelines so that you can get the idea of how my report is structured. My topic will be entitled *****Comparison of Database Management Systems*****. MySQL will be the primary one to compare against with the other two or three database systems such as Postgre SQL, Oracle, MSSQL, and/or DB2. Not all mentioned DBs have to be included but two or three will be sufficient as long as the report is expanded up to approximate 3000 words (or 10 to 14 pages). The report will be focus on analysis and comparison of DBs. It will be dealt with their histories, features, and installation, pricing and licensing, applications in the target organizations and advantages and disadvantages of each. Such comparison, it can be included performance, reliability, scalability, security, cost, downtime, query ability, backup and replication, limits, usability testing, and so on. Not all criteria have to be included, depending on what your findings are then you would know what good criteria to include. I would like the report to have some technical diagrams or tables to point out the essential of comparison. I would consider myself as a consultant engaged by a client and doing a case study (invented, not real) on which DB is superior. I would consider MySQL as superior. If after you compile the report and realize that MySQL might not be superior, you can email me and we may switch to the other winning DB.

The report format is as following (in order):

- Table of Contents

- List of Table and Figures

- Summary

- Glossary (optional)

- Introduction

- Discussion

- Conclusions

- Recommendations

- References

- Appendices (optional)

I*****ll take care of the title page and letter of transmittal.

As for number of sources, I would say 3 or 4, but probably mostly from the web such as Wikipedia.com. Citing some sources from journals or articles would be nice.

I would like to have the report be delivered as a Word doc file in the email.

Thanks very much for your service.

Here*****s the excerpt from the guideline:

=====

The reports are expected to have a significant analysis component which addresses engineering issues, and demonstrates 'engineering thought process'. A report which is purely descriptive and qualitative without a quantitative analytical component (e.g. a user manual or an overview) may expect to receive a very low or possibly even a failing grade. Some examples of analysis include:

*****¢ a discussion of why a certain machine component would be made of a certain material - ease of manufacturing, costs/profit, FEA, stress analysis, etc.

*****¢ a discussion of why a circuit would be designed using one type of chip over another - considerations of cost/profit, manufacturing process, reliability, component availability, size, expansion, heat dissipation, etc.

*****¢ a discussion of why a computer network would use a certain component, say a type of router - cost, ease of use, data transmission considerations, reliability, etc.

*****¢ an analysis of some software - why use a certain language, portability, memory usage, speed - e.g. the program uses 8% less memory and runs 25% faster if written in a certain fashion.

Do not simply write a descriptive report about some technology that interests you, such as 'voice over IP'. If you do want to use this for a topic, then your strategy would be to describe the technology in your introduction/background; then in the discussion you could set up a case study (real or invented) which allows you to do some analysis. For example, in this case you could consider yourself a 'consultant' engaged by a 'client' who wishes to consider the implementation of 'voice over IP' in their corporate structure - as the consultant, you can analyze whether or not this is a good prospect, given conditions which you can draw from a real case, or create them. This analysis should form the main part of the report.

=====

How to Reference "Comparison of Database Management Systems" Research Proposal in a Bibliography

Comparison of Database Management Systems.” A1-TermPaper.com, 2009, https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082. Accessed 5 Oct 2024.

Comparison of Database Management Systems (2009). Retrieved from https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082
A1-TermPaper.com. (2009). Comparison of Database Management Systems. [online] Available at: https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082 [Accessed 5 Oct, 2024].
”Comparison of Database Management Systems” 2009. A1-TermPaper.com. https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082.
”Comparison of Database Management Systems” A1-TermPaper.com, Last modified 2024. https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082.
[1] ”Comparison of Database Management Systems”, A1-TermPaper.com, 2009. [Online]. Available: https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082. [Accessed: 5-Oct-2024].
1. Comparison of Database Management Systems [Internet]. A1-TermPaper.com. 2009 [cited 5 October 2024]. Available from: https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082
1. Comparison of Database Management Systems. A1-TermPaper.com. https://www.a1-termpaper.com/topics/essay/management-systems-appendix-project/9082. Published 2009. Accessed October 5, 2024.

Related Research Proposals:

Database Design Term Paper

Paper Icon

Database

What is a database? Is a database the same as a database management system (DBMS)? Why or why not?

A database by definition is a collection of data records… read more

Term Paper 5 pages (1421 words) Sources: 5 Topic: Computers / IT / Internet


Content Management System Term Paper

Paper Icon

Social Aspects of Content Management Systems

Content Management System

Content Management Systems are mostly used for the easy management of website content. CMS's can also be used for the management… read more

Term Paper 7 pages (2413 words) Sources: 12 Topic: Management / Organizations


Distributed Order Management Systems Term Paper

Paper Icon

Management

Distributed Order Management Systems

Theoretical or Conceptual framework

Questions addressed

Data analysis, discussion and results

Including discussion of any limitation(s))

DDSN Characteristics

SPSS Regression Statistics on DOM Investment by… read more

Term Paper 11 pages (4856 words) Sources: 1+ Topic: Management / Organizations


Workings of Forest Fire Management Systems and Urban Fire Departments Term Paper

Paper Icon

Forest Fire Management Systems and Urban Fire Departments

Forest Fire Management Systems

New Technologies

Urban Fire Department

New Technologies

Descriptive Statistics

Suppression Costs for Federal Agencies. Source: National Interagency Fire… read more

Term Paper 63 pages (17324 words) Sources: 1+ Topic: Management / Organizations


Object-Oriented Database Management Systems vs. Relational Term Paper

Paper Icon

Object Oriented vs. Relational Database management systems

Comparing Object-Oriented vs. Relational Database Management Systems

The proliferation of database technologies, systems and data structures continues to be driven by the needs… read more

Term Paper 10 pages (2917 words) Sources: 7 Topic: Computers / IT / Internet


Sat, Oct 5, 2024

If you don't see the paper you need, we will write it for you!

Established in 1995
900,000 Orders Finished
100% Guaranteed Work
300 Words Per Page
Simple Ordering
100% Private & Secure

We can write a new, 100% unique paper!

Search Papers

Navigation

Do NOT follow this link or you will be banned from the site!