XTrabackup can handle both InnoDB and MyISAM in
a consistent way while minimizing lock time on
MyISAM tables ...
http://www.percona.com/doc/percona-xtrabackup/2.1/
--
Hartmut Holzgraefe, Principal Support Engineer (EMEA)
SkySQL - The MariaDB Company | http://www.skysql.com/
--
MySQL General Ma
ase has a mixture of MyISAM- and
> InnoDB-tables. A backup of this mix does not seem to be easy. Until now it
> was dumped using "mysqldump --opt -u root --databases mausdb ...". What I
> understand until now is that --opt is not necessary because it is default. It
> incl
Hi,
i've been already reading the documentation the whole day, but still confused
and unsure what to do.
We have two databases which are important for our work. So both are stored
hourly. Now I recognized that each database has a mixture of MyISAM- and
InnoDB-tables. A backup of this mix
Check out this thread:
http://www.sitepoint.com/forums/showpost.php?p=3357628&postcount=2
2007/7/17, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
Hello,
we have a MySQL DBMS with a lot of databases. Most of them are using
MyISAM tables but three databases use InnoDB and MyISAM tables.
What is the b
Hello,
we have a MySQL DBMS with a lot of databases. Most of them are using MyISAM
tables but three databases use InnoDB and MyISAM tables.
What is the best method to get a consitent ONLINE backup of both table types?
Thanks,
Spiker
--
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kan
t; To: mysql
> Subject: Re: [OT} How to pronounce GIF (was: Re: How to
> pronounce MyISAM and InnoDB)
>
> On Jan 7, 2007, at 4:23 PM, TK wrote:
>
> > In short, the original inventors of the GIF format (CompuServe,
> > 1987) have always defined the pronunciation to be like &
On Jan 7, 2007, at 4:23 PM, TK wrote:
In short, the original inventors of the GIF format (CompuServe,
1987) have always defined the pronunciation to be like "JIF." So,
that has always been the "correct" pronunciation.
Sure, so I'll start pronouncing "graphics" as "jraphics".
--
MySQL Gen
I'll bite..
Sorry for this silly question but I've been always had trouble
pronouncing "MyISAM" and InnoDB.
How do you pronunce them?
I pronounce MyISAM as "give-me-foreign-keys" and InnoDB as
"curse-you-cryptic-foreign-key-errors"
(currently running
Jan,
In English I pronounce them as...
My-eye-sam
In-oh-dee-bee
...respectively.
Regards,
Phil
2007/1/7, js <[EMAIL PROTECTED]>:
Hi list,
Sorry for this silly question but I've been always had trouble
pronouncing "MyISAM" and InnoDB.
How do you pronunce the
quot; and "inno, d, b"
>>
>>From: "js " <[EMAIL PROTECTED]>
>>
>>Sorry for this silly question but I've been always had trouble
>>pronouncing "MyISAM" and InnoDB.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
2007/1/7, js <[EMAIL PROTECTED]>:
Hi list,
Sorry for this silly question but I've been always had trouble
pronouncing "MyISAM" and InnoDB.
How do you pronunce them?
Thanks in advance.
When I'm speaking Dutch (which is most of the time) I say
My-ee-sahm
Inno-day
essage-
From: "js " <[EMAIL PROTECTED]>
Date: Mon, 8 Jan 2007 00:09:15
To:mysql@lists.mysql.com
Subject: How to pronounce MyISAM and InnoDB
Hi list,
Sorry for this silly question but I've been always had trouble
pronouncing "MyISAM" and InnoDB.
How do yo
I just say
"My, I, Sam" and "inno, d, b"
Michael
-Original Message-
From: "js " <[EMAIL PROTECTED]>
Date: Mon, 8 Jan 2007 00:09:15
To:mysql@lists.mysql.com
Subject: How to pronounce MyISAM and InnoDB
Hi list,
Sorry for this silly quest
Hi list,
Sorry for this silly question but I've been always had trouble
pronouncing "MyISAM" and InnoDB.
How do you pronunce them?
Thanks in advance.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
PRASHANT N wrote:
thnaks for the speedy reply. I already have both the DBs in my
server. is there any way/method that the DB2 which needs transaction
support can be converted from myisam to innodb format without any
hitch
http://dev.mysql.com/doc/mysql/en/alter-table.html
I would strongly reco
hi,
thnaks for the speedy reply. I already have both the DBs in my server. is there
any way/method that the DB2 which needs transaction support can be converted
from myisam to innodb format without any hitch
regards
shann
___
Which f
co-existance of both the MyISAM and InnoDB
engines on the same server?
You don't need to do anything special. As long as you enable InnoDB
support (MyISAM is in by default) then just use the TYPE=InnoDB option
on CREATE TABLE or select InnoDB when creating the table in your chosen
GUI
both the MyISAM and InnoDB engines on
the same server?
regards
shann
___
What is the largest island in the Mediterranean Sea?
http://
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe
Hello.
Among other suggestions think about such way.
If you MyISAM and InnoDB tables are used by different applications or
consistent state between them doesn't play big value, and the size
of MyISAM tables is low enough, you could perform the dump in two steps
listing the tables o
ucture.
Our table defintitions are relatively stable so we don't do it every
night. You could put it in the cron job to do it with the backup.
-Original Message-
From: Scott Plumlee [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 12:36 PM
To: mysql@lists.mysql.com
Subject: Re: Ba
>
> -Original Message-
> From: Scott Plumlee [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 17, 2005 10:21 AM
> To: mysql@lists.mysql.com
> Subject: Backup database with MyISAM and InnoDB tables together
>
> I'm not clear on best practice to use on a database
cuted
-Original Message-
From: Scott Plumlee [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 10:21 AM
To: mysql@lists.mysql.com
Subject: Backup database with MyISAM and InnoDB tables together
I'm not clear on best practice to use on a database containing both
MyISAM and InnoDB ta
I'm not clear on best practice to use on a database containing both
MyISAM and InnoDB tables. For the MyISAM tables, it seems better to use
mysqldump --opt, thus getting the --lock-tables option, but for the
InnoDB the --single-transaction is preferred. Since they are mutually
exclusiv
Mitul,
- Original Message -
From: "Mitul Bhammar" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, November 30, 2004 7:38 AM
Subject: MIXING MYISAM AND INNODB
I'm using multiple dbs for my very high traffic
multiple sites.
One of my db (say par
I'm using multiple dbs for my very high traffic
multiple sites.
One of my db (say parentDb) just maintains users who
can login to all the sites. Others are sites specific
dbs(say childDbs).
I'm using INNODb tables for my parentDb while my
childDbs tables are of MyISAM type.
Some code does have dir
Hi,
I read it somewhere that InnoDB is faster for table with high read/write
concurrency. I have a table look like this:
CREATE TABLE diary (
id INT UNSIGNED NOT NULL AUTO_INCREMENT,
member_id INT UNSIGNED NOT NULL,
title VARCHAR(255) NOT NULL,
body TEXT NOT NULL,
date DATE NOT NULL,
Janusz Krzysztofik wrote:
> ...
> I am trying to optimize MySQL (3.23.49 from Debian stable) setup for
> ASPseek application. I decided to try InnoDB in order to be able
> to update tables while performing time consuming selects.
> After converting all tables to InnoDB I noticed a big difference
>
Hi,
> > > You are not using any indicies, because there aren't any that could be
> > > used in this query.
> > > Try adding an index on (status,deleted)
> >
> > I wonder: how many possible different values would such an index
> > return?
>
> mysql> select distinct status, deleted from urlword;
> +
Martijn Tonies wrote:
>
> Hi,
>
> > You are not using any indicies, because there aren't any that could be
> > used in this query.
> > Try adding an index on (status,deleted)
>
> I wonder: how many possible different values would such an index
> return?
mysql> select distinct status, deleted fr
Hi,
> You are not using any indicies, because there aren't any that could be
> used in this query.
> Try adding an index on (status,deleted)
I wonder: how many possible different values would such an index
return? If this is a (very) low value, won't the index make things
slower (if it's being u
ndex (was: Big difference in MyISAM and InnoDB SELECT
speed)
Marc,
Thank you for your prompt answer.
I run EXPLAIN in both cases and got:
MyISAM (fast):
mysql> explain select url_id from urlword where deleted=0 and status
De : Janusz Krzysztofik [mailto:[EMAIL PROTECTED]
Envoyé : lundi 24 novembre 2003 13:58
A : [EMAIL PROTECTED]
Objet : Big difference in MyISAM and InnoDB SELECT speed
Hello,
I am trying to optimize MySQL (3.23.49 from Debian stable) setup for
ASPseek application. I decided to try InnoDB in order to
evant one).
>
> Have you done an EXPLAIN on your query ?
>
> May be an index on (origin,status,deleted) could help.
>
> Marc.
>
> -Message d'origine-
> De : Janusz Krzysztofik [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 24 novembre 2003 13:58
> A : [E
nvoyé : lundi 24 novembre 2003 13:58
A : [EMAIL PROTECTED]
Objet : Big difference in MyISAM and InnoDB SELECT speed
Hello,
I am trying to optimize MySQL (3.23.49 from Debian stable) setup for
ASPseek application. I decided to try InnoDB in order to be able
to update tables while performing time cons
Hello,
I am trying to optimize MySQL (3.23.49 from Debian stable) setup for
ASPseek application. I decided to try InnoDB in order to be able
to update tables while performing time consuming selects.
After converting all tables to InnoDB I noticed a big difference
in processing speed of one of the
On Thu, May 16, 2002 at 11:45:26AM -0400, adam nelson wrote:
>
> I'm finally getting around to working with InnoDB for real :-)
Great.
> Anyway, is there any reason to still use MyISAM on any tables.
Of course there is.
> Concurrency is my biggest problem (Locked tables, etc.).
Then for you
I'm finally getting around to working with InnoDB for real :-)
Anyway, is there any reason to still use MyISAM on any tables.
Concurrency is my biggest problem (Locked tables, etc.). My theory is
that the tables that wouldn't benefit from converting to InnoDB are so
small (5-50 rows?) that I m
37 matches
Mail list logo
