Ran into an interesting issue with a client today who was using innodb_file_per_table. This client had a lot of tables ( 300K+), they were using innodb_file_per_table. Today they had a problem that caused their db to crash. After fixing their issue, the database restart seemed to hang. The only thing in the error log was the mysql was started, their was no crash recovery messages. An strace revealed that the mysqld process was stating all the datafiles. It seems that during a recovery the first step is to just check to see if all the individual files are really their. The entire process to simply stat each datafile took over 45 minutes to complete after which the actual crash recovery started. Just a quick note to remind myself in the future if I see this again.
Content suppressed by ://URLFAN, for full article visit source
Migrating from one RDBMS to anotherFrom: haidongji.com
Post Date: 2008-03-03 20:17:34
Here is some of my thoughts on migrating MySQL to Sql Server. It came out of an email discussion. I’d love to hear your thoughts on migrating to a different database platform, not just MySQL to Sql Server.
I actually thought about writing a white paper or even a course on migrating from MySQL to Sql Server, but never got the time to do it. Sometimes a project doing similar things can serve as a launchpad for this endeavour, but that never came along, at least not yet. I am very intere...
more iodbc and mac os x problemsFrom: trainedmonkey.com
Post Date: 2008-03-03 19:23:01
working with the iodbc driver manager on mac os x has been a frustration on two fronts. first, the installer api functions provided by iodbc constantly set the configuration mode to ODBC_BOTH_DSN, which means you have to keep resetting it to the correct value after nearly every installer api call. this problem is platform-agnostic ? the iodbc code is just plain wrong. second, when called from the odbc administrator application on mac os x, any failures that the driver reports or passes throu...
more