Though I use MySQL, many in the open source community are a little peeved about changes being made to the MySQL license. Instead, take a look at Postgre SQL, which may already have most of the features you would be waiting for, and which is open source.
Regarding migration, MySQL has a couple of quirks:
Timestamp columns: the first timestamp column in a table gets auto updated, no matter what.
If you have one varchar in a table, all character types become varchar.
On Wednesday, August 11, 2004, at 03:09 PM, Wilcox, Jamileh (HSC) wrote:
We run all of our databases on MS-SQL2000 or MS Access.� (I've been slowly working towards moving all the Access databases to SQL.)
We're considering changing database servers.� Under discussion so far are Oracle and MySQL.� The campus has a site license for Oracle, so purchase cost isn't much of a factor.� I've been researching MySQL and it looks a bit limited (no stored procs yet, no scheduler/jobs/etc.), but the new version due out next year has a several of those features added (although I'm not sure *when* in 2005 it'll be available).
How difficult is it to switch to MySQL or Oracle from MS-SQL?� I realize there will be some conversion issues in any db migration (i.e., SQL language variations, datatype variations, etc.), but there appear to be tools available to assist with that.� I'm mostly concerned about the learning curve and how long it would take to come up to speed on a new db.
Does anyone have experience with such a migration, or experience with using more than one of these dbs?� Any info or advice would be most appreciated!
Thanks.
jamileh
