Import to MySQL

[Thorsten Hohage]

On 2008-10-13, at 18:54, Ruslan Zasukhin wrote:

> On 10/13/08 7:52 PM, "william humphrey" <shoreagent at gmail.com> wrote:
>
>> What is the largest text file a program like BBEdit can open?
>
> It can open and 2GB, but works unreal slow
>
> I have try once


But of course 5 GB or even 50GB of db file size doesn't really mean  
that file size is necessary for a DB dump AND additionally most  
probably you'll end with a much largen TEXT file size when dumping  
everything.

First of all you need to check, e.g. if in the VALENTINA file (<> DB  
file) the index is included or if this is in a separate file. If this  
is all in one file, data might be use much less disk space.

And of course it might be a little work, but you can dump table by  
table, if necessary divide a table in different parts - depending on  
the structure divided rows or columns.

When NOT using sql, but instead CSV you can save a real hugh amount of  
file size.

...

So it's not really necessary to keep the biggest file size BBEdit can  
edit in mind, when designing a DB task.


Regarding the real topic of this mail, I would talk about "IMPORT to  
mySQL", but instead of a database migration to mySQL. There will be  
much more things, then simply dumping all values to a file and re- 
import them. Perhaps enconding issues, length and precision of  
numbers, ...

What's about Stored Procedures, Triggers, System Table usages,  
calculated columns, ... so IMHO it would be the best solution to write  
a small app, grabbing record by record on one site and writing it out  
to the other.


I know it's work, and work means money, but at least leaving Valentina  
especially to use mySQL must be punished :-))))


regards,

Thorsten Hohage
-- 

Valentina Technology Evangelist
generic objects  GmbH - Leiter Solution Center Nord