List:General Discussion« Previous MessageNext Message »
From:Ow Mun Heng Date:October 9 2006 6:16am
Subject:Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAM
View as plain text  
On Mon, 2006-10-09 at 13:02 +0700, Ady Wicaksono wrote:
> On 10/9/06, Ow Mun Heng <Ow.Mun.Heng@stripped> 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 to SQL, and make sure you know how foreign key SQL syntax
> See:
>   http://www.windowsitlibrary.com/Content/77/12/1.html

Thanks. I'll take look.

> > > Others... for overall, i prefer innodb :)
> >
> > I know it's transaction safe and all, but not too sure if I need the
> > extra overhead.
> 
> If your concern is fast insert, how fast do you need? is 3000 rows
> insert/seconds enough?

I think That's _way_ enough. Looking through the select (group by
date/time etc) I see the max is ~2000 or so inserts (per Minute :-))


> if your concern is fast read, tune your innodb buffer, bigger memory
> bigger performance :)

My concern is fast reads. Based on
http://www.mysqlperformanceblog.com/2006/09/29/what-to-tune-in-mysql-server-after-installation/

the innodb_buffer_pool_size should be ~70-80% of main memory.



Thread
MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAMOw Mun Heng8 Oct
  • Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAMAdy Wicaksono9 Oct
    • Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAMOw Mun Heng9 Oct
      • Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAMAdy Wicaksono9 Oct
        • Re: MSSQL(B-end) to MYSQL(Front-End) -> InnoDB or MyISAMOw Mun Heng9 Oct