Comparison of MySQL and SQLServer

  • 2020-05-06 11:47:37
  • OfStack

From: http: / / www qqread. com/mysql/z442108305 html

The two most popular backend databases for application developers are MySQL and SQLServer. The fundamental similarity between the two is the data store and the query system. You can use sql to access data from both databases because they both support ansi-sql. Also, both database systems support binary keywords and key indexes, which greatly speeds up queries. Both also offer various formats that support xml. Besides the obvious difference in software price, is there any obvious difference between the two products? How do you choose between the two? Let's look at the major differences between the two products, including release costs, performance, and their security.

The fundamental difference between is the basic principle that they follow:

The basic principle they follow is their main difference: open vs is conservative. The narrow, conservative storage engine of the SQLServer server is quite different from the extensible, open storage engine of the MySQL server. While you can use the sybase engine on the SQLServer server, MySQL offers many more options, such as myisam, heap, innodb, and berkeley db. MySQL does not fully support unfamiliar keywords, so it has fewer relevant databases than the SQLServer server. At the same time, MySQL also lacks some of the features of a stored program, such as the ability for the myisam engine to support switching.

distribution fee: MySQL is not all free, but it is very cheap

When it comes to the cost of distribution, the two products make two very different decisions. For SQLServer servers, the most common way to get a free development fee is to buy Microsoft office or visual studio. However, if you want to use it for commercial product development, you must also purchase sql server standard edition. Schools or nonprofit businesses may not consider this additional fee.

performance: advanced MySQL

Purely for performance, MySQL is excellent because it includes a default desktop format, myisam. The myisam database is very compatible with disk without taking up too much cpu and memory. MySQL can run on windows systems without collisions, and unix or similar unix systems are better. You can also get some extra performance by using 64-bit processors. Because MySQL USES 64-bit integers a lot of the time inside. Yahoo! Business websites use MySQL as the backend database.

When it comes to software performance, SQLServer servers are far more stable than their competitors. However, these features come at a price. For example, additional complex operations must be added, disk storage, memory loss, and so on. If your hardware and software do not fully support SQLServer servers, I recommend that you choose a different database such as dbms, because you will get better results.

security features

MySQL has a binary log for changing data. Because it is binary, this log can quickly copy data from the host to the client. Even if the server crashes, the binary log remains intact and the copied parts are not damaged.

You can also record SQLServer queries on SQLServer servers, but this can be costly.

security

Both products have their own complete security mechanisms. As long as you follow these security mechanisms, normal procedures are fine. Both use the default ip port, but unfortunately these ips can sometimes be broken into by hackers. Of course, you can also set up these ip ports yourself.

recovery: advanced sql server

Recovery is also a feature of MySQL, which is mainly manifested in the myisam configuration. This approach has its inherent drawbacks, and if you accidentally damage the database, the result may be that all the data is lost. However, for the SQLServer server, it is very stable. The SQLServer server is able to monitor switching points and save database corruption.

determines your choice as needed
If I had to tell you which of these two databases is better, I might disappoint you. In my opinion, any database that helps you in your work is a good database, and no database is absolutely brilliant, and no database is absolutely terrible. What I'm trying to tell you is that you should start more with your own needs, which is what kind of tasks are you going to accomplish? Don't just start with the functionality of the software.

If you want to build a.net server system, which can access data from many different platforms and participate in database management, then you can choose SQLServer server. If you want to build a third-party site that can read data from several clients, MySQL is the best choice.

Both databases work well under.net or j2ee, and again, both can take advantage of raid.

===========================
ORACLE, SQLSERVER, MYSQL and DB2 comparison
http://book.chinaz.com/CSDN/phppost5/php39602.htm

The following is cited :ORACLE large, perfect, safe
SQLSERVER simple, friendly interface, WINDOWS platform under the good choice
MYSQL is free, it works fine
DB2 is very large, similar to ORACLE and
The following is cited :ORACLE large, perfect, safe
SQLSERVER simple, friendly interface,
WINDOWS platform is a good choice
MYSQL is free.
is good DB2 is very large, similar to ORACLE and
oracle: where data integrity and security requirements are high;
sqlserver(sybase and ms) : ms sqlserver is simple and easy to use for enterprise-class data applications.
mysql: basically free, suitable for personal website and some small business website application;
db2: large database, the specialty is in the information access.
The following is cited :Oracle is suitable for larger systems, but it is difficult to get started, and even after you get started, it is difficult to improve. It takes a lot of practice and trial and error, but it does work well for large systems. Backup and restore are good, but you have to be very experienced to do them well. The amount of data does not exceed 1T, it can be used to
SqlServer: the best database for MS platform. Interface simple and friendly, easy to operate, backup and recovery are relatively easy to learn. And after learning SqlServer and SYBASE are also relatively close.
MYSQL used to learn PHP, it felt relatively simple, whether it is to get started or its own function.
I have used DB2 on AS/400 and MS platform, and I feel that it is very rigorous and must have very standard operation. If the amount of data exceeds 100 G, it is recommended.
oracle has nothing to boast about, just look at his performance this year. Now that his technology is available even to Microsoft, is there really no technical reason to adopt
The DB2 data warehouse is still quite good, and the data mining is quite good, especially the clustering technology can make DB2 scalable to the maximum. A look at this year's performance shows the advantages of DB2, which is of course slightly more expensive than the others, but still acceptable, at least far lower than oracle's price,
Sybase is on its way out. Few new systems use it now, but my current company has abandoned
MySQL is a good thing, highly recommended, but it is really an alternative to use, such as no stored procedures, if you do not consider the cluster, in fact, its efficiency is much higher than oracle
SQL Server Microsoft stuff, it feels good to use, but because it can't be used on UNIX, businesses, telecommunications, and governments are reluctant to use it. Don't use it if you don't make ERP, or you might not be able to buy it

Related articles: