Convert MSSQL data to MySQL (mssql2mysql)

I have been trying to solve this problem for a long time, but it may not be able to solve it yet, but at least list the feasible methods I have struggled to and the methods I have tried, let everyone take a closer look

Dbconvert for MSSQL and MySQL tools should be used at the earliest, but I don't know why I cannot connect to my MSSQL. It may be 2005. The link 2000 seems to be very OK, because I tested that the connection to the virtual host mssql2000 was completely normal, and the connection to the local mssql2005 failed, there was no way to give up.

Then I continued to find a method and found that I did not find any Chinese materials (that is, the Chinese webpage found by Google), which gave me good results, it is best to use the English keyword to find: Convert MSSQL to MySQL, the first is the official MySQL web page. After going in and browsing, I found it very good and basically solved my problem, five methods are proposed. The Chinese Web pages I search for are basically solved by using the ODBC tool, even ifCodeAnd so on. It's really a gap. Easy to read,ArticleFive methods are proposed as follows (in fact, the title of this web page is not mssql2mysql, so there are five methods to understand, the original link: migrating from Microsoft SQL Server and access to MySQL):

Mssql2mysql
Microsoft DTS
Sqlyog
Access Export
Text Import/Export

I think we should use ODBC for MySQL tools for the above conversions. Therefore, please download and install them on your own and restart your computer before using the above methods.

Microsoft DTS should be the built-in import and export tool of MSSQL. MSSQL is good in terms of import and export access and text, but ODBC is not found in the import and export tool of mssql2005, dizzy enough, isn't it? It seems that you still need to check the documentation.

Access export is the access export tool. When exporting data, select ODBC. Of course, you must configure the ODBC parameters of MySQL first.

Sqlyog is a MySQL management tool. It is not tested because it is too lazy to download it.

Text import/export: I can import text files in phpMyAdmin, which may be suitable for a small amount of data. It is not very convenient for a large number of tools.

Mssql2mysql is a VB Code. For all the code, see http://www.kofler.cc/mysql/mssql2mysql.txt. Copy the code to the VBA or vB class module and set the parameters according to the instructions. The data conversion process starts when running. It is worth noting that different database engines use different field types, So field type conversion is involved, but this code has solved this problem, therefore, you don't need to consider data conversion, but I will never change the basic data type to the image type, and so on. So I don't think it has much to do with me. I opened VB6 and set the parameters to run it again. You can use it to prepare for writing a tool. It turns out that someone else has provided a third-party GUI tool. Alas, I knew I would just go through the GUI tool and try again without having to be so tired. OK, the author's mssql2mysql page: http://www.kofler.cc/mysql/mssql2mysql.html. there is a GUI versions section under it. Here we provide two mssql2mysql GUI tools, both of which are relatively simple. Let me briefly talk about the parameters, the link parameters of MSSQL and MySQL are all I want to know. The DROP DATABASE parameter indicates that the database in MySQL is deleted before conversion, so that the conversion is clean, therefore, if you want to convert to an existing database, you need to note that verbosity is actually the output option, whether to convert to the database or to the SQL file, and 1 is the output file, 0 for direct import to MySQL, the rest of the nothing to say, character encoding in general I want to also use UTF-8. Think about the rest.

 

The efficiency of mssql2mysql is really disappointing. Although such a method is found, the real conversion is not just a pain point. In the above mssql2mysql code conversion method, the efficiency is about 5000 records per hour, and the use of access export does not seem to be much faster. Do you want to know that I have 6 million records? Crazy. It seems that you have to find another method. However, it takes more than half an hour to import 6 million records to SQL server using the BCP ing method, the SQL Server export function is used to export the database as access, and the time is not short. The last wait is not patient, so I have to go to bed on the computer.

This is probably the mssql2mysql method I have tried at this stage. If you have a friend who has a better and faster method, please let me know. Thank you.

================================
Update: You may be prompted that you cannot connect to MySQL. This part may be related to the MySQL ODBC you installed, because the default setting text seems to be faulty, I set the ODBC version to "MySQL ODBC 5.1 Driver" so that the connection can be established. Maybe the new version of MySQL ODBC has been updated, but the code is still in the old version, so it is not supported.