On Mon, 2006-10-09 at 11:42 +0700, Ady Wicaksono wrote: > Is your MSSQL data structure contain such foreign key? > > If yes, my isam is not suitable for you
Actually, you know what? I don't really know. How does one go about checking? > > Others... for overall, i prefer innodb :) I know it's transaction safe and all, but not too sure if I need the extra overhead. > > On 10/8/06, Ow Mun Heng <[EMAIL PROTECTED]> wrote: > > I'm just curious as to which would have better performance for my needs. > > > > backend is a MSSQL server and I want to replicate it into a MySQL > > Frontend for user accesses. > > > > replication would be done via "mysqlimport/load data infile". I'm > > thinking of doing the inserts something like ever 5 seconds or so. > > > > MyISAM tables are faster than InnoDB, but they are more optimised for > > READS than WRITEs, however due to the replication, (being done every 5 > > secs on ~5 tables), I'm wondering if this will cause performance losses > > due to table-locks etc. > > > > Thanks > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
