MSSQL and MYSQL migration

I have a migration issue that should be resolved in ten days. I have an average C # web server that has 50,000 lines of code, and I also have an average SQL Server size with triggers, storage procedures, and 20 tables that contain at least 10 columns.

Since our Microsoft licenses will expire at the end of this month, we have to convert the project to a project that uses the mysql database to reduce the cost of the server without purchasing a Microsoft SQL Server license. I can't change the adapter class simply because I haven't written the C # server code. If I want to make any changes to the server program, I have to understand the whole project and I take at least 2 weeks due to the large amount of codes.

What advice did you give me about the migration process? I need a fast and reliable migration tactic. I cannot take a backup because my server data has exceeded 10TB of data (yes, bad programming).

Thanks for the advice.

+3


source to share


1 answer


Transferring stored code (procedures, triggers) will be difficult. Please read this guide: https://www.mysql.com/why-mysql/white-papers/guide-to-migrating-from-sql-server-to-mysql/



I don't think a migration without changing the C # code would be possible.

+1


source







All Articles