 | |
MySQL 5.1 -- how to move InnoDB tables to another location?
comp.databases.mysql comp.databases.mysql
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
MySQL 5.1 -- how to move InnoDB tables to another location? -
01-22-2011
, 01:03 PM
#2
| |||
| |||
|
|
I used to move my databases that were based on MyISAM, by simply moving the directory to where I wanted it to be, and then creating a symlink from /var/lib/mysql to the new location. I am working in creating a appx. 40 GB database and decided to use InnoDB, to avoid the horrors of repairing tables. When I looked into /var/lib/mysql/mynewproject, to my surprise I found that the files are empty and, seemingly, innodb files were right under /var/lib/mysql. -rw-rw---- 1 mysql mysql 5242880 Jan 22 02:22 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 Jan 22 02:20 ib_logfile1 -rw-rw---- 1 mysql mysql 329252864 Jan 22 02:22 ibdata1 My root partition is not big enough to hold all that stuff. So, how would I create or move them elsewhere? It would seem that some options are available under my.cnf, but I would really like to be able to specify that per-database, is that possible? Thanks i |
googling for: "location of innodb"
second link:
http://dev.mysql.com/doc/refman/5.0/...iguration.html
--
Luuk
#3
| |||
| |||
|
|
I used to move my databases that were based on MyISAM, by simply moving the directory to where I wanted it to be, and then creating a symlink from /var/lib/mysql to the new location. I am working in creating a appx. 40 GB database and decided to use InnoDB, to avoid the horrors of repairing tables. |
Quote:
|
When I looked into /var/lib/mysql/mynewproject, to my surprise I found that the files are empty and, seemingly, innodb files were right under /var/lib/mysql. -rw-rw---- 1 mysql mysql 5242880 Jan 22 02:22 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 Jan 22 02:20 ib_logfile1 -rw-rw---- 1 mysql mysql 329252864 Jan 22 02:22 ibdata1 |
Quote:
|
My root partition is not big enough to hold all that stuff. So, how would I create or move them elsewhere? |
--innodb-file-per-table
XL
#4
| |||
| |||
|
|
Ignoramus3188 <ignoramus3188 (AT) NOSPAM (DOT) 3188.invalid> wrote: I used to move my databases that were based on MyISAM, by simply moving the directory to where I wanted it to be, and then creating a symlink from /var/lib/mysql to the new location. I am working in creating a appx. 40 GB database and decided to use InnoDB, to avoid the horrors of repairing tables. Unfortunately you didn't decide to RTFM too ... When I looked into /var/lib/mysql/mynewproject, to my surprise I found that the files are empty and, seemingly, innodb files were right under /var/lib/mysql. -rw-rw---- 1 mysql mysql 5242880 Jan 22 02:22 ib_logfile0 -rw-rw---- 1 mysql mysql 5242880 Jan 22 02:20 ib_logfile1 -rw-rw---- 1 mysql mysql 329252864 Jan 22 02:22 ibdata1 Yeah. Just as configured (by defaults). My root partition is not big enough to hold all that stuff. So, how would I create or move them elsewhere? RTFM --innodb-file-per-table XL |
reading the FM. Sorry about that.
Also, I have decided to move this database to a server that has a huge
root partition, so this is not an issue. That server is colocated at a
real ISP, and will be better suited to hold a large database. I have
another large database project planned too, and they will live just
fine there.
How is InnoDB working on 5.1? Any major bugs?
i
#5
| |||
| |||
|
|
How is InnoDB working on 5.1? Any major bugs? |
InnoDB is used. But there is also the InnoDB plugin with additional
features (page compression, online add-index, better diagnostics)
and slightly better performance.
I suggest to go for 5.5 immediately. There the builtin InnoDB has
been replaced with the plugin implementation already.
XL
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.