Timeline for Port SQL Server data to MySQL without Workbench
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2017 at 20:34 | answer | added | Kevin Bott | timeline score: 1 | |
| Aug 17, 2017 at 20:30 | answer | added | Jon49 | timeline score: 1 | |
| Aug 17, 2017 at 19:01 | comment | added | John Eisbrener | Gah! What's wrong with my eyes! Regardless, check Github to see if you can find some existing solutions that may make your life easier. Apparently I have db dyslexia... | |
| Aug 17, 2017 at 18:52 | comment | added | Jon49 | I'm actually porting to MySQL not PostgreSQL | |
| Aug 17, 2017 at 18:46 | comment | added | Jon49 | I have about 41 tables with the biggest table having about 91k records (most are much smaller). So, a pretty small database. This is all on my local machine. After working on this project for a year my boss decided he wanted MySQL instead of SQL Server :-( | |
| Aug 17, 2017 at 18:35 | comment | added | John Eisbrener | How big is the db you're trying to migrate? If it's sufficiently small enough you may be able to achieve this quicker by pushing the data via SQL Sever over a Linked Server connection. You could also look into SSIS, but that'll probably require more work than necessary regarding a scenario where you're moving away from MSSQL. | |
| Aug 17, 2017 at 18:31 | history | edited | Jon49 | CC BY-SA 3.0 |
added 465 characters in body
|
| Aug 17, 2017 at 17:26 | review | Close votes | |||
| Aug 19, 2017 at 10:04 | |||||
| Aug 17, 2017 at 17:07 | history | asked | Jon49 | CC BY-SA 3.0 |