HELP! Importing sql file into 1&1 mysql db

Hi,

I'm trying to import an sql file (~22mb) into my 1&1 (business package, uk)
mysql db.

I don't have ssh access.

I have tried bigdump, but it throws the error:

"Stopped at the line 1019.
At this place the current query includes more than 300 dump lines. That can
happen if your dump file was created by some tool which doesn't place a
semicolon followed by a linebreak at the end of each query, or if your dump
contains extended inserts. Please read the BigDump FAQs for more infos."

Any ideas anyone please?

I'm a complete newbie to sql and know no php either so I am struggling here.

TIA

--

Neil

Re: HELP! Importing sql file into 1&1 mysql db

Neil Monk wrote:
> Hi,
>
> I'm trying to import an sql file (~22mb) into my 1&1 (business package, uk)
> mysql db.
>
> I don't have ssh access.
>
> I have tried bigdump, but it throws the error:
>
> "Stopped at the line 1019.
> At this place the current query includes more than 300 dump lines. That can
> happen if your dump file was created by some tool which doesn't place a
> semicolon followed by a linebreak at the end of each query, or if your dump
> contains extended inserts. Please read the BigDump FAQs for more infos."
>
> Any ideas anyone please?
>
> I'm a complete newbie to sql and know no php either so I am struggling here.
>
> TIA
>

Just what it says - your SQL dump contains queries that are too long for the
importing tool. If you can make another SQL dump file, try disabling the
"extended inserts" option.

Otherwise, how do you interact with the database anyway? If you don't have shell
access, perhaps there is some tool in your admin panel, like phpMyAdmin? As far
as I know, phpMyAdmin can handle extended inserts. However, if the file is
really 22MB long, you may be hitting the upload limit already.

--
Christoph Burschka

Re: HELP! Importing sql file into 1&1 mysql db

"Christoph Burschka" wrote in message
news:55io4nF25e9p6U1@mid.dfncis.de...
> Neil Monk wrote:
>> Hi,
>>
>> I'm trying to import an sql file (~22mb) into my 1&1 (business package,
>> uk)
>> mysql db.
>>
>> I don't have ssh access.
>>
>> I have tried bigdump, but it throws the error:
>>
>> "Stopped at the line 1019.
>> At this place the current query includes more than 300 dump lines. That
>> can
>> happen if your dump file was created by some tool which doesn't place a
>> semicolon followed by a linebreak at the end of each query, or if your
>> dump
>> contains extended inserts. Please read the BigDump FAQs for more infos."
>>
>> Any ideas anyone please?
>>
>> I'm a complete newbie to sql and know no php either so I am struggling
>> here.
>>
>> TIA
>>
>
> Just what it says - your SQL dump contains queries that are too long for
> the
> importing tool. If you can make another SQL dump file, try disabling the
> "extended inserts" option.
>
> Otherwise, how do you interact with the database anyway? If you don't have
> shell
> access, perhaps there is some tool in your admin panel, like phpMyAdmin?
> As far
> as I know, phpMyAdmin can handle extended inserts. However, if the file is
> really 22MB long, you may be hitting the upload limit already.
>
> --
> Christoph Burschka

Thanks for the reply.

With a lot of arm-twisting needed, 1&1 eventually agreed to import it from
their side using ssh (which my package doesn't allow me to use).

Problem solved, although it's still shit that there was no other way around
this (phpmyadmin didn't like it either!).
--
Neil