February 18, 2025 at 9:17 pm
I am needing to migrate a MSSQL db to MySQL, on a different server in the same network.
The MSSQL is on Windows Server 2012 (not R2). I was looking at ODBC for connection.
I have looked at several different routes, including generating table and data scripts, then trying to get AI to convert to MYSQL syntax. Howevcr, there is a line limit with the AI I was using, and it proved too error prone, working with the large number of rows.
I tried installing the MySQL Workbench on Windows Server 2012; however, the latest version of Workbench will not run, although it installs successfully. I tried installing an older version of Workbench (version 5 - I tried everything from 8 to 5, and 5 was the first to successfully install and run). However, version 5 does not have migration tools.
Would my most efficient route be: to: 1. Export Table , 2. Export Data, 3. Export other objects (stored procedures, views, etc) ?
I found this article on using Powershell to move data. Would it be possible to use Powershell to build the tables, or would it be easier to export the table scripts and build them in MSSQL, then use Powershell to move the data? Could I connect to the other server within this powershell script, in order to move the data?
https://www.mssqltips.com/sqlservertip/6526/transfer-data-from-sql-server-to-mysql/
Thanks for any leads or ideas
February 18, 2025 at 9:34 pm
I saw this recommended, but likely some $$.
I haven't done what you've done, but I migrated the Lahman mysql db to mssql. I had to take the schema code and tweak it with some search replaces to get it to run. I assume you could do the same with the reverse. Script out the mssql code, then fix it to run in mysql.
For the data, I would think export/import makes the most sense. Export to csv as character files and import. Python or PoSh should do this for you.
February 19, 2025 at 2:16 am
Thanks so much!
I'll check into those options to see what direction to go in.
February 19, 2025 at 12:44 pm
This was removed by the editor as SPAM
February 19, 2025 at 12:45 pm
This was removed by the editor as SPAM
February 28, 2025 at 9:05 pm
I've been doing a bit more research into this in between other projects.
If I used powershell to export (like in this link - below), is there a way to use the basic approach explained in the link, but to not link the MSSQL to the MySQL, but rather to only export from MSSQL to csv file?
https://www.mssqltips.com/sqlservertip/6526/transfer-data-from-sql-server-to-mysql/
Then, I could upload the csv file in a separate step, into MySQL on the other server.
Thanks for any ideas!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy