2005 16:24
To: Marvin Wright; mysql@lists.mysql.com
Subject: Re: Correct way to use innodb_file_per_table?
On Jul 26, 2005, at 3:56 AM, Marvin Wright wrote:
Regarding the file size issue, we are on a 32-bit system running
redhat AS3, we already have idb files in excess of 21Gb, I'm not sure
: Correct way to use innodb_file_per_table?
On Jul 25, 2005, at 5:33 AM, Marvin Wright wrote:
Hi,
Thanks for your reply.
I've only just moved all tables to there own table space so that I can
put certain databases on different disks.
Right now my shared tablespace does not hold any
On Jul 26, 2005, at 3:56 AM, Marvin Wright wrote:
Regarding the file size issue, we are on a 32-bit system running
redhat AS3,
we already have idb files in excess of 21Gb, I'm not sure what the
limit is
though if any ?
No, typically a 32 bit file system would have limits like 2G or
Hi,
Can anybody help with this ?
Regards,
Marvin
-Original Message-
From: Marvin Wright
Sent: 22 July 2005 10:46
To: Heikki Tuuri; mysql@lists.mysql.com
Subject: RE: Correct way to use innodb_file_per_table?
Hi Heikki,
I've followed your instructions here and its all worked fine
On Jul 25, 2005, at 5:47 AM, Marvin Wright wrote:
You recommend to dump tables before changing then re-import them
back. But
if all databases are in there own tablespace I should need to do
this dump
should I ?
Unfortunately I think that's your only option to create a new table
space.
July 2005 12:53
To: Marvin Wright
Cc: mysql@lists.mysql.com
Subject: Re: Correct way to use innodb_file_per_table?
On Jul 25, 2005, at 5:47 AM, Marvin Wright wrote:
You recommend to dump tables before changing then re-import them back.
But if all databases are in there own tablespace I should
On Jul 25, 2005, at 5:33 AM, Marvin Wright wrote:
Hi,
Thanks for your reply.
I've only just moved all tables to there own table space so that I
can put
certain databases on different disks.
Right now my shared tablespace does not hold any databases.
I'm aware that I still need the shared
innodb_file_per_table?
Mike,
- Alkuperäinen viesti -
Lähettäjä: Mike Debnam [EMAIL PROTECTED]
Vastaanottaja: mysql@lists.mysql.com
Kopio: [EMAIL PROTECTED]
Lähetetty: Friday, March 04, 2005 2:49 PM
Aihe: Re: Correct way to use innodb_file_per_table?
Heikki,
the best way would be to symlink whole
Heikki,
the best way would be to symlink whole database directories under the
datadir. Then also an ALTER TABLE keeps the new .ibd file on
the drive you
intended it to be on. If you symlink a single .ibd file, then
an ALTER will
create the new .ibd file as not symlinked.
As an
Mike,
- Alkuperäinen viesti -
Lähettäjä: Mike Debnam [EMAIL PROTECTED]
Vastaanottaja: mysql@lists.mysql.com
Kopio: [EMAIL PROTECTED]
Lähetetty: Friday, March 04, 2005 2:49 PM
Aihe: Re: Correct way to use innodb_file_per_table?
Heikki,
the best way would be to symlink whole database
I've added a second drive to my database machine and want to split my
database tables between the two drives to balance the load and improve
performance. I know I'll need to drop and restore the db to get MySQL
to create the tables in their own files. What's the correct way to use
Mike,
- Original Message -
From: Mike Debnam [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Friday, March 04, 2005 6:15 AM
Subject: Correct way to use innodb_file_per_table?
I've added a second drive to my database machine and want to split my
database tables between
12 matches
Mail list logo
