On 1/4/07, Michael Parker <[EMAIL PROTECTED]> wrote:
Big Wave Dave wrote:
> On 1/3/07, Gary V <[EMAIL PROTECTED]> wrote:
>> >It finally finished the restore.
>> >
>> >For the sake of information to help future users
>> >
>> >The "backup" file being used to restore into the new SQL database wa
Big Wave Dave wrote:
> On 1/3/07, Gary V <[EMAIL PROTECTED]> wrote:
>> >It finally finished the restore.
>> >
>> >For the sake of information to help future users
>> >
>> >The "backup" file being used to restore into the new SQL database was
>> >99MB and took 17hrs to import on my AMD 1.2Ghz ma
On 3 Jan 2007 at 21:45, Gary V wrote:
> >It finally finished the restore.
> >
> >For the sake of information to help future users
> >
> >The "backup" file being used to restore into the new SQL database was
> >99MB and took 17hrs to import on my AMD 1.2Ghz machine with 1GB of
> >RAM.
> >
> >Da
On 1/3/07, Gary V <[EMAIL PROTECTED]> wrote:
>It finally finished the restore.
>
>For the sake of information to help future users
>
>The "backup" file being used to restore into the new SQL database was
>99MB and took 17hrs to import on my AMD 1.2Ghz machine with 1GB of
>RAM.
>
>Dave
Could
It finally finished the restore.
For the sake of information to help future users
The "backup" file being used to restore into the new SQL database was
99MB and took 17hrs to import on my AMD 1.2Ghz machine with 1GB of
RAM.
Dave
Could be your database was not expiring. Probably a good ide
On 1/3/07, Michael Parker <[EMAIL PROTECTED]> wrote:
Big Wave Dave wrote:
>
>
> What am I missing?
>
> I'd be thankful for any input.
You're not missing anything. The import takes a long time to run. Its
doing a lot of updates which are expensive in SQL. The good news is
that you can pretty m
On 1/3/07, Michael Parker <[EMAIL PROTECTED]> wrote:
Big Wave Dave wrote:
>
>
> What am I missing?
>
> I'd be thankful for any input.
You're not missing anything. The import takes a long time to run. Its
doing a lot of updates which are expensive in SQL. The good news is
that you can pretty m
Big Wave Dave wrote:
>
>
> What am I missing?
>
> I'd be thankful for any input.
You're not missing anything. The import takes a long time to run. Its
doing a lot of updates which are expensive in SQL. The good news is
that you can pretty much use the system while its doing the import
becaus
As mentioned in a previous thread, I'm migrating to SQL based bayes.
I performed the backup from the original bayes DB, which took about a
minute to export.
I then setup the SQL, and now am trying to import into it... but it
has been running for m more than 6 hours!?
When I check MySQL I see:
my
