MySQL for SQL Server 2005

You can use SSIS to copy the table data to a new structure, but this is the easy part. Then you need to check all your sql code to make sure it will work anyway. This link can help you see the differences between how each of the databases implements SQL http://troels.arvin.dk/db/rdbms/

While you're converting, you might be wondering if this might not be the best time to refactor.

The key to making a conversion is to ensure that everything is automated and reproducible. You will want to do this multiple times in dev before moving on to prod data. And when you go to prod you will need to fetch the database for maintanance, otherwise you will get the data added to the old database after you move the data from that table to the new one. You might want to create a process to copy most of the rcords in front of the maintenance window, and then during the maintenace window, only move new records or records that have changed since the main move. This will depend on how large your database is and how long you will be working to move the records. If it can be done in one step without going down for longer than your system can tolerate, it is best to do it.Another choice for a large database might be a customer based on customer data traffic, so instead of being alone every day, you stay for a couple of hours per customer. Again, it depends on your database design and how much you can get it set up and done.

Whatever you do, make sure users are fully aware of what you are doing and ahead of time so they can plan. Also avoid the time of month for a change that coincides with the need to create and run the database. I think in terms of not shutting down the payroll database on the day the payroll is running or the financial database is over, when the fiscal year tasks need to be completed or monthly reports run etc. I don’t know if you have any of these problems, but it’s good to consider whether you are working and working these periods. If users say, "No, we can't do that on Friday," then find out why - they might have a really good reason why the day you decide to implement isbad for their own work schedules.