Ease of use of software mainly refers to whether the software is easy to configure before import. Because many software design objects are programmers, not ordinary database managers or even ordinary application implementers, these people often have no experience in data source configuration. Because some programs that use ODBC or ADO for configuration often bring troubles to such users (mainly because they don't know what type of database driver to choose). Let's take a look at the design interfaces of four tools:
& gt& gt& gt& gt
1、SQLyog
SQLyog？ The old ODBC connection is used, but for the new generation of programs, this method is unfamiliar and difficult to use, and the machine must install the ODBC driver of the corresponding database (SQL Server usually comes with it).
& gt& gt& gt& gt
2、Navicat？ premium
NavicatPremium is the most inhuman design of the four application tools: you can't imagine the main points from the above picture. Press that little button to add a new connection. This connection setting will not be saved, and it must be reset every time it is imported. NavicatPremium uses the ADO setting method slightly higher than ODBC (the product of 199X era), but it is still useful for the older generation of programmers.
& gt& gt& gt& gt
3、Mss2sql
Mss2sql？ It is the easiest tool to search on Baidu, one of the reasons is that it appeared earlier.
The migration of Mss2sql from SQLServer to MySQL is very targeted, and because the interface is designed with operation wizard, it is very easy to use. At the same time, in the process of setting, there are many options to adjust the details, and you can feel that the software has been gradually improved after a long period of use.
& gt& gt& gt& gt
4、DB2DB
DB2DB？ Because it was developed by China people, both the interface and the prompt information are Chinese characters. In addition, because DB2DB is functionally targeted, the interface design is clear and easy to use. Like mss2sql, DB2DB provides many options for users to choose and set.
Third, processing speed and memory usage evaluation.
Before this evaluation, a senior colleague of mine downloaded a migration software from the Internet and sent a data table with about 25 million records to MySQL in Alibaba Cloud. As a result, it took three days and three nights (fortunately, two of them were Saturday and Sunday) to move here. So this time it is necessary to do a detailed test on the processing speed of these four tools.
Considering that there are two different situations when migrating from SQL Server to MySQL:
Migrate from SQL Server to local MySQL for code testing and modification;
Migrate from SQL Server to MySQL database in the cloud and put it into use;
The following is a screenshot of the test process:
& gt& gt& gt& gt
1、SQLyog
Please click to enter a picture description.
& gt& gt& gt& gt
2、Navicat Premium
Please click to enter a picture description.
Please click to enter a picture description.
Note: We are testing the migration of Navicat Premium to? MySQL found that the Money type of SQL Server is not supported (it is not excluded that there are other data types that are not supported). The default decimal length of Money type field is 255, which makes it impossible to create a data table and the whole test can't be successful. We need to modify the table structure one by one to complete the testing process.
Navicat Premium？ The processing speed of is moderate, neither fast nor slow, but the CPU utilization rate and memory utilization rate are at a high level. However, with the current computer hardware level, it is still acceptable. However, the CPU occupancy rate is too high, which will lead to the server being unable to be used for other purposes during data import.
& gt& gt& gt& gt
3、Mss2sql
Mss2sql？ There is no timer, so we use manual timing, and the whole process takes more than 726 seconds. The CPU utilization of Mss2sql is higher than other tools, but it is still within the acceptable range.
& gt& gt& gt& gt
4、DB2DB
Please click to enter a picture description.
DB2DB？ Similarly, it took only 2 minutes and 44 seconds to migrate 3 million data, which is quite amazing. However, a BUG appeared in the final result, indicating that the conversion was successful, but the progress bar behind it was not completed (in the later data integrity evaluation, we verified that all the data had been processed).