Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAM

2006-10-08 Thread Ow Mun Heng
On Mon, 2006-10-09 at 13:02 +0700, Ady Wicaksono wrote: > On 10/9/06, Ow Mun Heng <[EMAIL PROTECTED]> wrote: > > 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,

Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAM

2006-10-08 Thread Ady Wicaksono
On 10/9/06, Ow Mun Heng <[EMAIL PROTECTED]> wrote: 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? Dump it

Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAM

2006-10-08 Thread Ow Mun Heng
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 t

Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAM

2006-10-08 Thread Ady Wicaksono
Is your MSSQL data structure contain such foreign key? If yes, my isam is not suitable for you Others... for overall, i prefer innodb :) 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