Hi,
Data migration made last night.
Use of a new MySQL instance has been quite useful to operate, the outage
was about 7 minutes.
ibdata1 is now using 58 MiB of disk space ! each table having a proper
.ibd file and full data directory from 13GiB to 3.2GiB ...
Server load divided by 3 ~ 4 ;).
I
Hi Shawn, and thanks for this concise anwser ;) .
Le 22/03/2014 05:35, shawn l.green a écrit :
>
> The system is operating exactly as designed. The ibdata* file(s) contain
> more than just your data and indexes. This is the common tablespace and
> it contains all the metadata necessary to identify
Hello Christophe,
On 3/21/2014 4:47 PM, Christophe wrote:
Hi list,
I'd like your advice, (one more time ;) ) about this case :
The context is :
A huge database using InnoDB engine from filling about several years
(without possible shrinking, as I've seen, except dropping all databases
to recr
Hi list,
I'd like your advice, (one more time ;) ) about this case :
The context is :
A huge database using InnoDB engine from filling about several years
(without possible shrinking, as I've seen, except dropping all databases
to recreate them ... ) the ibdata file , which is taking over 9GiB o
prunning missing/exceeding bits?
>
> My current plan is more or less like below. I removed task descriptions
> removed, guess the task name is descriptive enough. Indenting marks
> sub-tasks, as expected.
>
> Many thanks in advance.
> Cheers!
>
> - BEGIN TASK LIST -
Hi Luis,
On Jan 2, 2008 11:12 AM, Luis Motta Campos <[EMAIL PROTECTED]> wrote:
> Baron Schwartz wrote:
> > On Jan 2, 2008 10:04 AM, Luis Motta Campos wrote:
> >> Baron Schwartz wrote:
> >>> What are the biggest changes you anticipate? I'd say they will be
> >>> the version upgrade, converting to
Baron Schwartz wrote:
> On Jan 2, 2008 10:04 AM, Luis Motta Campos wrote:
>> Baron Schwartz wrote:
>>> What are the biggest changes you anticipate? I'd say they will be
>>> the version upgrade, converting to InnoDB, and using
>>> replication. It looks like you have planned well for all but
>>> u
Hi,
On Jan 2, 2008 10:04 AM, Luis Motta Campos <[EMAIL PROTECTED]> wrote:
> Baron Schwartz wrote:
> > What are the biggest changes you anticipate? I'd say they will be the
> > version upgrade, converting to InnoDB, and using replication. It
> > looks like you have planned well for all but using
Baron Schwartz wrote:
> What are the biggest changes you anticipate? I'd say they will be the
> version upgrade, converting to InnoDB, and using replication. It
> looks like you have planned well for all but using replication.
That's interesting. What kind of activities (besides configuration,
t;
> My current plan is more or less like below. I removed task descriptions
> removed, guess the task name is descriptive enough. Indenting marks
> sub-tasks, as expected.
>
> Many thanks in advance.
> Cheers!
>
> - BEGIN TASK LIST -
> Database Migration P
s
sub-tasks, as expected.
Many thanks in advance.
Cheers!
- BEGIN TASK LIST -
Database Migration Project
Current Database Procedures Mapping
Plan Database Test Procedure
Determine Current Database Backup Procedures
Determine Current Database Restore Proce
avril 2005 01:03
To: mysql@lists.mysql.com
Subject: database migration puzzle.
Hi all,
I have removed mysql 4_0_20d and installed 4.1.
My puzzle is this:
1. I have prior databases in 4.0 (intact data directory with InnoDB
files *.idb, etc.) data directory with sub directories.
2. I
Hi all,
I have removed mysql 4_0_20d and installed 4.1.
My puzzle is this:
1. I have prior databases in 4.0 (intact data directory with InnoDB files
*.idb, etc.) data directory with sub directories.
2. I want to bring in some of the databases to the new 4.1 version.
The 4.0 databases
HI,
I would like to know if there is a program/script that can migrate data
from sybase ASE server to MySQL ???
Just tables - lots and lots of tables (about 12GB of data !!!)
Many Thanks
Tonino
-
Before posting, please check:
14 matches
Mail list logo
