Mssql vs Mysql

Only available on StudyMode
  • Download(s) : 221
  • Published : July 25, 2012
Open Document
Text Preview
l Introduction
An important aspect of database development is how to access your data using standard protocols. Both MySql and MSSql Server do a good job of supporting all major protocols for accessing their respective databases. MYsql and MSsql are the two Sql Servers that are commonly used today by the programmers and other IT people. These two are the most popular choices when considering a utility for data management. Both are efficient at keeping the data organized and readily available through a user interface but they differ in many drastic areas. Both are freely accessible for running small or big databases. Even they do have the same functionality; the existence of differences of the two known Sql Servers will still be a question to the users and to the future users. The major differences of this two will include the licensing costs, performance, and security. This research paper will answer some key questions in determining which data management tool is best suited for the needs of the user like the flexibility of the data you are creating; the security of the data; the need of support in utilizing the data management tools; and the standard language support. In this way the users of these management tools will determine which of the two will efficiently works on the programs they will be creating. It will also include here some of the important factors to consider a perfect database to be used in terms of their functional attributes that they could give for the users. Basically, the significance of this study is to come up with a comparison of each database servers and will enable to answer the questions that are popping in the minds of the future users and the importance of a right and appropriate tools to be used. It will also identify the complexity of between the when it comes to some features and functionality. By going through the pages of this research you will be able to identify the answer/s on the questions that arisen in choosing between the two said databases. A deeper understanding on these databases will help a lot the users in determining the suitable database to be used for the program they will be created.

METHOD;
As with the problems encountered and was raised between the two databases we came up with a comparison and the differences of the said databases. This will elaborate well how does each work in terms of data protection, recovery, performance, security and replication, pricing and licensing, and data storage. The differences begin with principles: open vs. proprietary. MSSQL Server with its closed, proprietary storage engine is fundamentally different from MySQL’s extensible, open storage engine. You’re stuck with the MSSQL Server’s Sybase-derived engine for better or worse, while MySQL provides multiple choices such as MyISAM, Heap, InnoDB, and Berkeley DB (Sanders “kaufman, Jr.”). This open vs. closed difference is, by itself, enough reason for some people to choose one over the other. But, there are some technical differences as well. To begin with, MySQL doesn't fully support foreign keys, making it less of a relational database than MSSQL Server, which has full relational features. Also, MySQL has previously lacked support for stored procedures, and the default MyISAM engine doesn't support transactions. Licensing costs.

When it comes to licensing costs, both products use a two-tiered scheme. With MSSQL Server, the most popular way to get a free developer license is to purchase a license for Microsoft Office Developer or Microsoft Visual Studio, both of which give you a free "development use only” SQL Server license. If, however, you want to use it in a commercial production environment, you'll have to pay for at least the SQL Server Standard Edition, which will set you back around $1,400 for five client connections. (Sanders “Kaufman, Jr.”). However, the many outstanding features that are far above MySql offset the price paid for the MSSql Server significantly. On the...
tracking img