I did something similar. The easiest way is to have a direct connection between your MSSQL server and the MySQL server. You install the linked server in MSSQL on the MySQL server, and then use insert, update, etc. To complete transactions on a linked server. This is what his answer says. However, you do not have a direct link to the MySQL server, so the option is not viable.
Another option is to use the MSSQL Service broker. With the help of a service broker, you can queue individual updates, delete and paste them into a web service. This web service can be hosted on IIS. Webservice is called from the queue, and then you can apply individual transactions one at a time to the MySQL database. A service broker is an asynchronous messaging system built into MSSQL 2005+. With it, you can send messages to other servers, databases and even external services.
Just keep in mind that the Service Broker architecture takes time to learn and implement. I created my own replication architecture between mssql and mysql using a service broker that processes 88 million plus transaction per day on a celeron laptop. It just took some serious elbow grease.
UPDATE It seems that SQL2008 allows you to run Service Brokers outside of the SQL server. See Link http://blogs.msdn.com/b/sql_service_broker/archive/2008/11/21/announcing-service-broker-external-activator.aspx I donβt know if this could be on your street.
source share