On Tue, July 17, 2007 13:31, Baron Schwartz wrote:
> Mogens Melander wrote:
>> On Tue, July 17, 2007 04:29, Baron Schwartz wrote:
>>> B. Keith Murphy wrote:
The problem is that I am realizing that this dump/import is going to
take
hours and in some cases days. I am looking for
Mogens Melander wrote:
On Tue, July 17, 2007 04:29, Baron Schwartz wrote:
B. Keith Murphy wrote:
Hey all. I have a bit of a problem. We are upgrading from ver 4.1.x to
5.0.45. That's not the problem :). The problem is that MySQL recommends
dumping and importing your data when doing this upgrade
In article <[EMAIL PROTECTED]> [EMAIL PROTECTED]
(BaronSchwartz) wrote:
> B. Keith Murphy wrote:
>> The problem is that I am realizing that this dump/import is going
>> to take hours and in some cases days. I am looking for any way to
>> speed this up. Any suggestions?
> The fastest way I've
On Tue, July 17, 2007 04:29, Baron Schwartz wrote:
> B. Keith Murphy wrote:
>> Hey all. I have a bit of a problem. We are upgrading from ver 4.1.x to
>> 5.0.45. That's not the problem :). The problem is that MySQL recommends
>> dumping and importing your data when doing this upgrade to make sure
>
B. Keith Murphy wrote:
Hey all. I have a bit of a problem. We are upgrading from ver 4.1.x to
5.0.45. That's not the problem :). The problem is that MySQL recommends
dumping and importing your data when doing this upgrade to make sure that
things go as smoothly as possible. We have quite a bit of
Hey all. I have a bit of a problem. We are upgrading from ver 4.1.x to 5.0.45.
That's not the problem :). The problem is that MySQL recommends dumping and
importing your data when doing this upgrade to make sure that things go as
smoothly as possible. We have quite a bit of data spread over mult
