MySql Import speed(Was mysql version OSX)
Mike Matthews
omnis at lineal.co.uk
Mon Dec 20 14:39:32 EST 2010
It is a .sql file so next I will google.
Ta
Mike
On 20 Dec 2010, at 19:21, Andy Hilton wrote:
> Mike
>
> Usually when the workbench 'goes mad' it means it hit an error and simply bypassed a whole chunk of the data so beware....
>
> The command line allows you to set all manner of things like indexing etc in your restrore statement - a quick google will tell you all you need to know about it - but you can do all sorts with it - very very powerful....
>
> Trust it far more than workbench restore.....
>
> Provided the import file was/is a .sql file it will more than likely be a MySQL dump.....
>
> Andy
>
> On Dec 20, 2010, at 2:15 PM, Mike Matthews wrote:
>
>> Hello Andy, Bruno & David,
>>
>> After about 40 minutes, the throughput went mad, I have now completed 27gb of import in just under 2 hours, so getting on with it. When this is done, I'll try Andy's test to see if that is faster.
>>
>> The Workbench seems ok then, but a bit odd perhaps, but I used it. Don't know how to turn off the building of indexes on import but understand the consequences however.
>>
>> I don't have a clue what type of file have here David in truth, but I am creating a new file called ibdata1 in the mysql folder. There are also 3 other folders that have been created with schemas in them by the looks. So I guess MySQL is storing the data in this huge file and the definition stuff elsewhere.
>>
>> So, when all done, do I also need to install the mySQL connection stuff for Studio 4 or 5 to connect to this big old file?
>>
>> Thanks guys.
>>
>> Mike
>>
>>
>>
More information about the omnisdev-en
mailing list