Re: Risks involved in MyISAM to Innodb

Am 21.09.2012 18:18, schrieb Rick James: > (Apologies to the rare bottom-poster.) bullshit on mostly egvery mailing-list there are guidlines that you NOT should top-post, try it out on the postfix-list as example and wait what Wietse wille xplain you about both * your top-posting * and your st

RE: Risks involved in MyISAM to Innodb

(Apologies to the rare bottom-poster.) This contains lots of tips on converting from MyISAM to InnoDB: http://mysql.rjweb.org/doc.php/myisam2innodb Generally, the conversion should go smoothly. > -Original Message- > From: Reindl Harald [mailto:h.rei...@thelounge.net] > Sen

Re: Risks involved in MyISAM to Innodb

do NOT top-post which makes threads unreadable Am 21.09.2012 15:55, schrieb Girish Talluru: > On Fri, Sep 21, 2012 at 6:44 AM, Reindl Harald > wrote: > Am 21.09.2012 15:26, schrieb Girish Talluru: > > I have requirement to change my production database table

Re: Risks involved in MyISAM to Innodb

Hi Reindl, I'm sorry if I ask wrong question here? I'm new to this and people before me did the terrible mistake of using myISAM even though they decided to move to Innodb many times. Data grows like hell and now requirements came in where we have to use transactions. At this stage we have to mig

Re: Risks involved in MyISAM to Innodb

On 21/09/2012 9:26 AM, Girish Talluru wrote: Hi Guys, I have requirement to change my production database tables which are using myISAM and now bcoz of some changes we have to move to Innodb. Can anyone suggest how the plan should be and risks involve? Thanks, Girish Talluru Whatafford?

Re: Risks involved in MyISAM to Innodb

Am 21.09.2012 15:26, schrieb Girish Talluru: > I have requirement to change my production database tables which are using > myISAM and now bcoz of some changes we have to move to Innodb. > > Can anyone suggest how the plan should be and risks involve? no because this depends hardly on your data

Risks involved in MyISAM to Innodb

Hi Guys, I have requirement to change my production database tables which are using myISAM and now bcoz of some changes we have to move to Innodb. Can anyone suggest how the plan should be and risks involve? Thanks, Girish Talluru

Re: Migrating my mindset from MyISAM to InnoDB

well. Wow, that sure would be nice... even with some extended information like myisamchk output. That would be an awesome feature to add to 5.5. >Expect to see anywhere from a 1.5x to a 3x increase in size when converting >from myisam to innodb, depending on your field types and indexes.

Re: Migrating my mindset from MyISAM to InnoDB

b" to convert my tables from 4.1.14 to >> 5.5.6, and I'm seeing a 130% increase (more than double) in the raw disk >> space required for the new InnoDB tables compared to their old MyISAM >> counterparts. (I am using single-file-per-table). Is this normal? If >&g

RE: Migrating my mindset from MyISAM to InnoDB

Also note, 5.5 isn't production ready. 5.1 is the current GA release. -Original Message- From: Hank [mailto:hes...@gmail.com] Sent: Tuesday, September 28, 2010 3:29 PM To: mysql@lists.mysql.com Subject: Migrating my mindset from MyISAM to InnoDB Primarily due to many positive

RE: Migrating my mindset from MyISAM to InnoDB

Hank [mailto:hes...@gmail.com] Sent: Tuesday, September 28, 2010 3:29 PM To: mysql@lists.mysql.com Subject: Migrating my mindset from MyISAM to InnoDB Primarily due to many positive posts I've seen about MySQL 5.5 and advances in InnoDB, I'm seriously considering converting all my MyISAM data

Migrating my mindset from MyISAM to InnoDB

Primarily due to many positive posts I've seen about MySQL 5.5 and advances in InnoDB, I'm seriously considering converting all my MyISAM databases to InnoDB.   I don't need many of the InnoDB features, but if I'm going to upgrade from 4.1.14 to 5.5, I might as well bit the bullet since that seems

Re: MyISAM to InnoDB

What is the basic functionality of the MyISAM, InnoDB etc ? http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusD

MyISAM to InnoDB

Hi, What is the basic functionality of the MyISAM, InnoDB etc ? Vikram A The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/

RE: Converting MyISAM to InnoDB

ssage. Regards, Gavin Towey -Original Message- From: Steve Staples [mailto:sstap...@mnsi.net] Sent: Monday, February 08, 2010 9:39 AM To: mysql@lists.mysql.com Subject: Converting MyISAM to InnoDB Hello again! I am trying to convert my tables to InnoDB, and i am getting an error... Error:

Converting MyISAM to InnoDB

Hello again! I am trying to convert my tables to InnoDB, and i am getting an error... Error: 1075 Incorrect table definition; there can be only one auto column and it must be defined as a key Now, I converted a table in my sandbox earlier this morning to do some testing, and it worked fine... mi

RE: MyISAM to InnoDB conversion help

Great, Thank you for your help Rolando, Mikhail Berman -Original Message- From: Rolando Edwards [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 11:41 AM Cc: mysql@lists.mysql.com; Mikhail Berman Subject: Re: MyISAM to InnoDB conversion help I just noticed your

Re: MyISAM to InnoDB conversion help

m: Rolando Edwards <[EMAIL PROTECTED]> To: Mikhail Berman <[EMAIL PROTECTED]> Cc: mysql@lists.mysql.com Sent: Wednesday, November 1, 2006 11:24:00 AM GMT-0500 US/Eastern Subject: Re: MyISAM to InnoDB conversion help Check these variable bulk_insert_buffer_size (Default usually 8M) innodb_buf

Re: MyISAM to InnoDB conversion help

11:13:44 AM GMT-0500 US/Eastern Subject: RE: MyISAM to InnoDB conversion help Hi Rolando, Thank you for your help. I am on MySQL 5, and I have tried to do the conversion using ALTER TABLE command. With the same very slow result. Do you by any chance have specific suggestions how to tweak varia

RE: MyISAM to InnoDB conversion help

[mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 11:05 AM To: Mikhail Berman Cc: mysql@lists.mysql.com Subject: Re: MyISAM to InnoDB conversion help If you are do this in MySQL 5, try this: ALTER TABLE ENGINE = InnoDB; That's all. Let MySQL worry about conversion. You may also

Re: MyISAM to InnoDB conversion help

- From: Mikhail Berman <[EMAIL PROTECTED]> To: mysql@lists.mysql.com Sent: Wednesday, November 1, 2006 10:31:13 AM GMT-0500 US/Eastern Subject: MyISAM to InnoDB conversion help Hi everyone, I am hoping to get help with extremely slow performance of MyISAM to InnoDB conversion. Or find out

MyISAM to InnoDB conversion help

Hi everyone, I am hoping to get help with extremely slow performance of MyISAM to InnoDB conversion. Or find out if this type of performance is usual I have MyISAM table that contains - 3,299,509 rows and I am trying to convert it to InnoDB for the use with row-level locking, and I am getting

Re: Changing engines, MyISAM to InnoDB Heelp

Brian, you can also set a default storage engine in your mysql config file (my.cnf) to ensure future tables get created with the desired storage engine (unless otherwise specified in your create statement). From http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html If you omit the ENGINE

Re: Changing engines, MyISAM to InnoDB Heelp

most of my Storage enines is MyISAM i wanna change them all to|InnoDB how do i do this >? ALTER TABLE tblname ENGINE="innodb"; -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Changing engines, MyISAM to InnoDB Heelp

most of my Storage enines is MyISAM i wanna change them all to|InnoDB how do i do this >?thanks | -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Row count discrepancy when converting from MyISAM to InnoDB

D]> To: Sent: Tuesday, July 25, 2006 11:51 PM Subject: Re: Row count discrepancy when converting from MyISAM to InnoDB On Jul 25, 2006, at 11:55 AM, Frank wrote: Why is the record count so low after conversion to InnoDB? Who should I believe: InnoDB or MyISAM? Any ideas as to what can be d

Re: Row count discrepancy when converting from MyISAM to InnoDB

nt: Tuesday, July 25, 2006 11:51 PM Subject: Re: Row count discrepancy when converting from MyISAM to InnoDB On Jul 25, 2006, at 11:55 AM, Frank wrote: Why is the record count so low after conversion to InnoDB? Who should I believe: InnoDB or MyISAM? Any ideas as to what can be done to avoid loss of

Re: Row count discrepancy when converting from MyISAM to InnoDB

Thank you to everyone who replied. It turned out I had index corruption and after running an OPTIMIZE TABLE I was able to convert all the records to InnoDB. Thanks, Frank

Re: Row count discrepancy when converting from MyISAM to InnoDB

On Jul 25, 2006, at 11:55 AM, Frank wrote: Why is the record count so low after conversion to InnoDB? Who should I believe: InnoDB or MyISAM? Any ideas as to what can be done to avoid loss of this many rows? InnoDB doesn't keep a count on number of rows, like MyISAM does. InnoDB only main

Row count discrepancy when converting from MyISAM to InnoDB

I have a table of type MyISAM that is reporting 47 million rows when I do a SELECT COUNT(*). When I convert this table to InnoDB, running a SELECT COUNT(*) returns only 19 million rows. The conversion confirms 19 million rows were inserted and reports no warnings or duplicates. I have done the co

Re: ERROR 1114 (HY000): The table is full converting a big table from MyISAM to InnoDB on 5.0.18

/www.innodb.com/order.php - Original Message - From: ""Patrick Herber"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Sunday, January 15, 2006 4:16 PM Subject: RE: ERROR 1114 (HY000): The table is full converting a big table from MyISAM to InnoDB o

RE: ERROR 1114 (HY000): The table is full converting a big table from MyISAM to InnoDB on 5.0.18

ull converting > a big table from MyISAM to InnoDB on 5.0.18 > > Hi, > > I think you should change the tmpdir variable value to a > directory which > have enough room to create your temp big table (by default, > it points to /tmp dir). > > Regards, >Jocel

Re: ERROR 1114 (HY000): The table is full converting a big table from MyISAM to InnoDB on 5.0.18

Hi, I think you should change the tmpdir variable value to a directory which have enough room to create your temp big table (by default, it points to /tmp dir). Regards, Jocelyn Patrick Herber a écrit : Hello! I have a database with a big table (Data File 45 GB, Index File 30 GB). Since

ERROR 1114 (HY000): The table is full converting a big table from MyISAM to InnoDB on 5.0.18

Hello! I have a database with a big table (Data File 45 GB, Index File 30 GB). Since I have some performance troubles with "table-locking" in a multi-user environment (when one of them performs a complex query all the other have to wait up to 1 minute, which is not very nice...), I would like to c

RE: MyISAM to InnoDB

> -Original Message- > From: Devananda [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 29, 2005 14:56 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: Re: MyISAM to InnoDB > > > Jeff wrote: > > > > Well the applications with persis

Re: MyISAM to InnoDB

Jeff wrote: Well the applications with persistant connections is a touchy subject. Our apps send and rec data over satelite links which are very expensive. The shorter the duration of the link the less it costs us. So the pervailing theory is that with persistant connections the apps will spend

Re: MyISAM to InnoDB

Hi, 2005/9/23, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > "Jeff" <[EMAIL PROTECTED]> wrote on 09/23/2005 09:57:06 AM: > > > Yes, I meant exactly that. Within each MySQL server is a "special" > database called `mysql`. That is the database that contains the tables of > all of the user login and permi

RE: MyISAM to InnoDB

> "Jeff" <[EMAIL PROTECTED]> wrote on 09/29/2005 08:47:52 AM: > > > > > > Jeff wrote: > > > > > > > > Ugh... > > > > mysqladmin -uroot -ptelaurus processlist | grep -c > "Sleep" And it > > > > returned 200 sleeping connections, all persistant > > > connections > > > > from our app servers and

RE: MyISAM to InnoDB

"Jeff" <[EMAIL PROTECTED]> wrote on 09/29/2005 08:47:52 AM: > > > Jeff wrote: > > > > > > Ugh... > > > mysqladmin -uroot -ptelaurus processlist | grep -c "Sleep" > > > And it returned 200 sleeping connections, all persistant > > connections > > > from our app servers and 4 threads_running > >

RE: MyISAM to InnoDB

> Jeff wrote: > > > > Ugh... > > > > mysqladmin -uroot -ptelaurus processlist | grep -c "Sleep" > > > > And it returned 200 sleeping connections, all persistant > connections > > from our app servers and 4 threads_running > > > > Also a show status gave me a max_used_connections of 236. > >

Re: MyISAM to InnoDB

On Sep 28, 2005, at 5:21 PM, Devananda wrote: Jeff wrote: Lots of stuff goes in here... So without going into specifics here... your sort_buffer and read_buffer become pretty much unimportant if you move everything to InnoDB... keeping in mind the earlier advice to leave the mysql databa

Re: MyISAM to InnoDB

Jeff wrote: Ugh... mysqladmin -uroot -ptelaurus processlist | grep -c "Sleep" And it returned 200 sleeping connections, all persistant connections from our app servers and 4 threads_running Also a show status gave me a max_used_connections of 236. If that's the case then I can probably

RE: MyISAM to InnoDB

"Jeff" <[EMAIL PROTECTED]> wrote on 09/28/2005 02:24:48 PM: > > -Original Message- > > From: Devananda [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, September 28, 2005 13:06 > > To: Jeff > > Cc: mysql@lists.mysql.com > > Subject: Re: M

RE: MyISAM to InnoDB

> -Original Message- > From: Devananda [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 28, 2005 13:06 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: Re: MyISAM to InnoDB > > > Jeff wrote: > >> Cut orignal thread because it was too long >

RE: MyISAM to InnoDB

> -Original Message- > From: Devananda [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 28, 2005 13:06 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: Re: MyISAM to InnoDB > > > Jeff wrote: > >> Cut orignal thread because it was too long >

Re: MyISAM to InnoDB

Jeff wrote: Cut orignal thread because it was too long The system is only used as a database server, it's a dual processor system with 2gig of ram. As you can see, Table1's MyISAM data file is quite large at 2.1 gig. Taking this into account what size InnoDB data files should I configure in m

RE: MyISAM to InnoDB

[mailto:[EMAIL PROTECTED] Sent: Wednesday, September 28, 2005 9:04 PM To: 'Sujay Koduri'; mysql@lists.mysql.com Subject: RE: MyISAM to InnoDB > -Original Message- > From: Sujay Koduri [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 28, 2005 11:04 > To: Jeff; mysq

RE: MyISAM to InnoDB

> -Original Message- > From: Sujay Koduri [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 28, 2005 11:04 > To: Jeff; mysql@lists.mysql.com > Cc: [EMAIL PROTECTED] > Subject: RE: MyISAM to InnoDB > > > > If you think your storage requiremnets will

RE: MyISAM to InnoDB

uning that by running some load tests. Apart from that everything is looking fine for me sujay -Original Message- From: Jeff [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 28, 2005 8:22 PM To: mysql@lists.mysql.com Cc: [EMAIL PROTECTED] Subject: RE: MyISAM to InnoDB > Cut

RE: MyISAM to InnoDB

> Cut orignal thread because it was too long Ok so I'm about to convert two tables in my database from MyISAM to InnoDB. They are currently: 14K Sep 15 13:15 Table1.frm 2.1G Sep 28 14:15 Table1.MYD 198M Sep 28 14:15 Table1.MYI 11K Sep 20 08:45 Table2.frm 424K Sep 28 14:15 Table2.MYD

Re: MyISAM to InnoDB

I see that the thread is getting too long, so I'm cutting out parts that I'm not responding to. Hope no one minds. As far as I'm concerned, simplicity and ease would be to leave it as is but we're looking to eek out as much speed in our transactions >>> >>>as possible >>> so sim

RE: MyISAM to InnoDB

"Jeff" <[EMAIL PROTECTED]> wrote on 09/23/2005 11:36:01 AM: <> > > Is that the only diff (other than the "select count(*)" thing) between > InnoDB and MyISAM? Aren't select statements faster from MyISAM tables > than from InnoDB's? > > There's also been a statement from our lead developer that

RE: MyISAM to InnoDB

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, September 23, 2005 10:25 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: RE: MyISAM to InnoDB > > > "Jeff" <[EMAIL PROTECTED]> wrote on 09/23/2005

RE: MyISAM to InnoDB

"Jeff" <[EMAIL PROTECTED]> wrote on 09/23/2005 09:57:06 AM: > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 23, 2005 09:40 > > To: Jeff > > Cc: mysql@lists.mysql.com > > Subject:

RE: MyISAM to InnoDB

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, September 23, 2005 09:40 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: RE: MyISAM to InnoDB > > > Sorry to butt in but I wanted to make sure you didn't do >

RE: MyISAM to InnoDB

IL PROTECTED] > > Sent: Thursday, September 22, 2005 19:03 > > To: Jeff > > Cc: mysql@lists.mysql.com > > Subject: Re: MyISAM to InnoDB > > > > > > Jeff wrote: > > >>-Original Message- > > >>From: Devananda [mailto:[EMAIL PROTE

RE: MyISAM to InnoDB

> -Original Message- > From: Devananda [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 22, 2005 19:03 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: Re: MyISAM to InnoDB > > > Jeff wrote: > >>-Original Message- > >>From:

Re: MyISAM to InnoDB

Jeff wrote: -Original Message- From: Devananda [mailto:[EMAIL PROTECTED] Sent: Thursday, September 22, 2005 16:14 To: Jeff Cc: mysql@lists.mysql.com Subject: Re: MyISAM to InnoDB Jeff wrote: True, is there a way to tell a slave to not replicate certain queries like alter table

RE: MyISAM to InnoDB

> -Original Message- > From: Devananda [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 22, 2005 16:14 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: Re: MyISAM to InnoDB > > > Jeff wrote: > > True, is there a way to tell a slave to not repli

Re: MyISAM to InnoDB

Jeff wrote: True, is there a way to tell a slave to not replicate certain queries like alter table or would I need to get creative and stop replication and all writes to the main database, then issue the alter table statement, then restart replication with a set global slave_sql_skip_counter=1 s

Re: MyISAM to InnoDB

On Sep 22, 2005, at 11:46 AM, Jeff wrote: True, is there a way to tell a slave to not replicate certain queries like alter table or would I need to get creative and stop replication and all writes to the main database, then issue the alter table statement, then restart replication with a set g

RE: MyISAM to InnoDB

> -Original Message- > From: Bruce Dembecki [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 22, 2005 11:41 > To: Jeff > Cc: mysql@lists.mysql.com > Subject: Re: MyISAM to InnoDB > > > You will need to make sure you have innodb configured in the my.cnf

Re: MyISAM to InnoDB

yisam replication, with a couple of small caveats... an "ALTER TABLE" would replicate and thus... may change the table type from myisam to innodb or vice versa depending on which server the ALTER TABLE came from. To go with that the original conversion from myisam to InnoDB would also nee

MyISAM to InnoDB

Hey all, I've got a production database that made up of all MyISAM tables. I'd like to change some of the more heavily written to tables to InnoDB to take advantage of the record level locking and thus improve write performance of our applications. I currently have a second db server that is r

Re: Considering migration from MyISAM to InnoDB

If it works fine currently, the rule usually is: don't mess with it. :) I would stick with MyISAM if I were you, it should be plenty good enough for such a small table and usage as you described. If you are experiencing performance issues, I would recommend looking at indexes if you haven't alread

RE: Considering migration from MyISAM to InnoDB

PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 14, 2005 7:00 PM To: Stembridge, Michael Cc: mysql@lists.mysql.com Subject: Re: Considering migration from MyISAM to InnoDB see the my.cnf examples in the install dir, and look at innodb* variables. you can migrate each table just using : alte

RE: Considering migration from MyISAM to InnoDB

[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 14, 2005 7:00 PM > To: Stembridge, Michael > Cc: mysql@lists.mysql.com > Subject: Re: Considering migration from MyISAM to InnoDB > > see the my.cnf examples in the install dir, and look at innodb* variables. >

Re: Considering migration from MyISAM to InnoDB

see the my.cnf examples in the install dir, and look at innodb* variables. you can migrate each table just using : alter table toto engine=innodb; Mathias Selon "Stembridge, Michael" <[EMAIL PROTECTED]>: > I currently use MyISAM on an internal web application server; our data takes > up 10mb a

Considering migration from MyISAM to InnoDB

I currently use MyISAM on an internal web application server; our data takes up 10mb at this time, though this is likely to grow substantially in the coming year. The database sees moderate heavy read and moderate write usage from 50 users. We're upgrading our sever from Red Hat 7.3 to SuSE

Alter table from myisam to innodb in one go?

Hello, if you do an alter table, altering some indexes _and_ converting it to innodb, will mysql do the altering and converting in one pass, or will it first change the indexes and than start the innodb conversion? For example, with an myisam table: alter table my_table, drop index an_index, add

Re: Major problem converting MyISAM to InnoDB

]> To: "Cliff" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, March 05, 2004 10:16 AM Subject: Re: Major problem converting MyISAM to InnoDB > Cliff wrote: > > I think I may have gotten closer to the root of the problem. It seems that > > the field nam

Re: Major problem converting MyISAM to InnoDB

Cliff wrote: I think I may have gotten closer to the root of the problem. It seems that the field named 'comments' is the one that crashes the server when it is selected. Here is the output of the logs when I do 'select comments from allusa': 040304 23:14:52 mysqld restarted 040304 23:14:53 InnoD

Re: Major problem converting MyISAM to InnoDB

Discussion« Previous MessageNext Message » From: Cliff Date: March 5 2004 8:12am Subject: Re: Major problem converting MyISAM to InnoDB I think I may have gotten closer to the root of the problem. It seems that the field named 'comments' is the one that crashes the server when it is selected. H

Re: Major problem converting MyISAM to InnoDB

: Thursday, March 04, 2004 1:24 PM Subject: Re: Major problem converting MyISAM to InnoDB > Cliff, > > - Original Message - > From: ""Cliff"" <[EMAIL PROTECTED]> > Newsgroups: mailing.database.myodbc > Sent: Thursday, March 04, 2004 7:07 PM &g

Re: Major problem converting MyISAM to InnoDB

- Original Message - From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 04, 2004 1:24 PM Subject: Re: Major problem converting MyISAM to InnoDB > Cliff, > > - Original Message - > From: "&q

Re: Major problem converting MyISAM to InnoDB

Cliff, - Original Message - From: ""Cliff"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Thursday, March 04, 2004 7:07 PM Subject: Re: Major problem converting MyISAM to InnoDB > Hi, I ran CHECK TABLE with the EXTENDED option on the table a

Re: Major problem converting MyISAM to InnoDB

> Hi, I ran CHECK TABLE with the EXTENDED option on the table and it reports > everything ok: > > mysql> check table allusa extended; > +---+---+--+--+ > | Table | Op| Msg_type | Msg_text | > +---+---+--+--+ > | bb.allusa | check | s

Re: Major problem converting MyISAM to InnoDB

nal Message - From: "Heikki Tuuri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 04, 2004 12:36 AM Subject: Re: Major problem converting MyISAM to InnoDB > Cliff, > > please run > > CHECK TABLE ... > > on your table and look if mysql

Re: Major problem converting MyISAM to InnoDB

, March 04, 2004 7:18 AM Subject: Re: Major problem converting MyISAM to InnoDB > Cliff wrote: > > Recently I tried to convert our largest table from MyISAM to InnoDB. During > > the process I believe there was a problem where something was corrupt along > > the way. It was s

Re: Major problem converting MyISAM to InnoDB

Cliff wrote: Recently I tried to convert our largest table from MyISAM to InnoDB. During the process I believe there was a problem where something was corrupt along the way. It was stupid, but I did not verify that our backup system was working correctly, since I assumed it had been running as

Major problem converting MyISAM to InnoDB

Recently I tried to convert our largest table from MyISAM to InnoDB. During the process I believe there was a problem where something was corrupt along the way. It was stupid, but I did not verify that our backup system was working correctly, since I assumed it had been running as usual. It was

Step on migrating MyISAM to InnoDB

I have MySQL Server 3.23.xx running on RedHat Linux 9 with 40GB harddrive and 256 RAM. I'm using MyISAM table type with around 157 tables. I think i decided to change MyISAM table to InnoDB table. But, I don't know how to do that for the first step. I have read a section on MySQL documentation abo

Re: Step on migrating MyISAM to InnoDB

Asep Andria I.W. wrote: I have MySQL Server 3.23.xx running on RedHat Linux 9 with 40GB harddrive and 256 RAM. I'm using MyISAM table type with around 157 tables. I think i decided to change MyISAM table to InnoDB table. But, I don't know how to do that for the first step. I have read a section o

Re: myISAM to innodb

vinay <[EMAIL PROTECTED]> wrote: > hi, > i have been using mysql-3.23.49a and now i want innodb support for the same > version of the database, can any one tell how should i proceed. > regards If you want to use InnoDB, you should install MySQL-Max binary: http://www.mysql.com/doc/en/mysql

myISAM to innodb

hi, i have been using mysql-3.23.49a and now i want innodb support for the same version of the database, can any one tell how should i proceed. regards -- Vinay Kumar Software Engineer Prologix Software Solutions Pvt. Ltd. Lucknow-226016.India Ph: +91(522)2721387. Res: 2702453. Fax: +91(522)27

Re: Converting MyISAM to InnoDB type.

Hi Matt. Thanks a lot again ! It worked pretty good. There is no problem about the app, because the use of the indexes is in charge of the DBMS (MySQL). The app "doesn't know" about the tables and indexes details. Best Regards, Fred. > Hi Fred, > > Also, you may be able to swap the or

Re: Converting MyISAM to InnoDB type.

3, 2004 6:11 PM Subject: Re: Converting MyISAM to InnoDB type. > Hi Matt and thank you very much > > Now I get the point I'll have to decide if I maintain these > two tables in MyISAM or if I drop the AUTO_INCREMENT and > change the source-code in Delphi. > > It&#x

Re: Converting MyISAM to InnoDB type.

Hi Matt and thank you very much Now I get the point I'll have to decide if I maintain these two tables in MyISAM or if I drop the AUTO_INCREMENT and change the source-code in Delphi. It's clear now that the problem is the lack of support of InnoDB. Thanks for your help and regards, Fre

Re: Converting MyISAM to InnoDB type.

"Fred" Sent: Saturday, January 03, 2004 5:38 PM Subject: Re: Converting MyISAM to InnoDB type. > > > > > > If you change the Type=MyISAM to Type=InnoDB and execute the > > create query, what message do you get? > > > > Hi you all .. again &g

Re: converting tables MyISAM to InnoDB

"Unknown Sender" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > > I recently upgraded from MySQL v3.23 to MySQL 4, and converted > my tables from MyISAM to InnoDB by using the ALTER TABLE > command. I did this for 16 tables. I know that MyISA

converting tables MyISAM to InnoDB

Hi, I recently upgraded from MySQL v3.23 to MySQL 4, and converted my tables from MyISAM to InnoDB by using the ALTER TABLE command. I did this for 16 tables. I know that MyISAM creates seperate data/index files for each table and InnoDB uses a single file for data and log. My question is

RE: migrate data from myisam to innoDB

, September 18, 2003 10:05 PM To: Hsiu-Hui Tseng; [EMAIL PROTECTED] Subject: Re: migrate data from myisam to innoDB Hsiu-Hui Tseng wrote: >Hello, > >I migrated all my tables to innoDB from MyIsam. After migrated, I ran "Show >TAble Status". Why the row count is chan

Re: migrate data from myisam to innoDB

Hsiu-Hui Tseng wrote: Hello, I migrated all my tables to innoDB from MyIsam. After migrated, I ran "Show TAble Status". Why the row count is change. In MyIsam table status.rows = 316202 the new InnoDB table status.rows = 287341 When doing select count(*) from TABLE. I go 316202 rows. Why this hap

migrate data from myisam to innoDB

Hello, I migrated all my tables to innoDB from MyIsam. After migrated, I ran "Show TAble Status". Why the row count is change. In MyIsam table status.rows = 316202 the new InnoDB table status.rows = 287341 When doing select count(*) from TABLE. I go 316202 rows. Why this happening? Is there any

Re: MyISAM to InnoDB

Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm (http://www.ezmlm.org) Cc: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Tue, 24 Sep 2002 11:04:35 +0100 I thought the InnoDB doesn't support a few MyISAM features. FULLTEXT for one.Those features it does support will not

Re: MyISAM to InnoDB

At 12:23 +0200 9/24/02, Harald Fuchs wrote: >In article <[EMAIL PROTECTED]>, >Daniel Kiss <[EMAIL PROTECTED]> writes: > >>> Question is, will this >>> require any SQL code changes to our application? We make heavy use of >>> features like temporary tables, autoincrement columns etc. Would if be

[Fwd: Re: MyISAM to InnoDB]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 grr: sql,query,mysql ;-) Hi Guys, Thanks to everyone that gave a response there, i feel much better now ;-) I'm not using any of the features listed in the recent posts just pain simple boring INSERTS, UPDATES, SELECTS and temporary

Re: MyISAM to InnoDB

> At 10:12 2002.09.24._ +0100, you wrote: > >Question is, will this > >require any SQL code changes to our application? We make heavy use of > >features like temporary tables, autoincrement columns etc. Would if be > >as simple as dumping the database and restoring it to InnoDB tables? > > The si

Re: MyISAM to InnoDB

Hi! At 10:12 2002.09.24._ +0100, you wrote: >Question is, will this >require any SQL code changes to our application? We make heavy use of >features like temporary tables, autoincrement columns etc. Would if be >as simple as dumping the database and restoring it to InnoDB tables? The simple answ

MyISAM to InnoDB

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, Just needing a little advice really, we have a (now) very large mysql database thats keeping track of gas/electrical safety inpection data. Since it was meant to just report on this data to produce very complex safety certificates and

  1   2   >