RE: upgrade from 4.1 to 5.0 (novice user)

lucretias <[email protected]>
Newsgroups gmane.comp.db.mysql.windows
Message-ID <002101c66fcd$9a71b5c0$0201a8c0@alucxp1>
Comments inline...

> -----Original Message-----
> From: Leigh Sharpe [mailto:[email protected]]
> Sent: Monday, May 01, 2006 5:41 PM
> To: ray; win32
> Subject: RE: upgrade from 4.1 to 5.0 (novice user)
>
>
> >I guess before I go any farther, the first question I should ask is
> >should I do this update. Is this new version  important, or
> is it a case of, "If it ain't broke, don't fix it"?

In some cases it's better to say 'if it ain't broke, break it.'


> It's very much the case. We are still running v 3.23 on our

This has vulnerabilities to you and your clients.

> production servers, simply because there is no real need to upgrade.

Actually yes there are real reasons to upgrade to at least 4.1.x

> There's a couple of gotchas when upgrading, too. The exact

Always.


> version numbers escape me at the moment (I think it was from
> 3.x to 4.x), but a lot of people got caught by the new
> authentication scheme when upgrading. All of a sudden their

Yes, many folks didn't realize that this new scheme would have a serious
impact.  You can either keep the old auth.scheme in place or update your
users to the new scheme.  I recommend the latter.
If you review the upgrading from 3.x to 4.x document in the manual it will
explain your options in a clearer fashion than my brain can recall.

> remote clients couldn't connect, because the old client
> wouldn't talk to the new server. These and other non-obvious
> things are usually a good reason not to upgrade unless you
> specifically want features available in the new version.

Well there are many other reasons one may wish to upgrade also, but you need
to decide for yourselves whether it's worth it or not for you.  But moving
away from unsupported versions like 3.x or 4.0 is very wise.

> As far as your backup goes, I would recommend scripting it.
> Table locks are a tricky beast sometimes, and it would be for
> more difficult and time-consuming to do it manually. Also,
> have a look at the mysqlhotcopy facility. It may or may not
> do what you want, but much faster.
> Standard disclaimer applies here: This is just my opinion,
> others may beg to differ.

I have done it differently myself, but I can attest that this tool works
well also.

>
> Regards,
>              Leigh
>
> Leigh Sharpe
> Network Systems Engineer
> Pacific Wireless
> Ph 9584 8966
> Mob 0408 009 502
> email [email protected]
> web www.pacificwireless.com.au
>
> -----Original Message-----
> From: Ray [mailto:[email protected]]
> Sent: Monday, May 01, 2006 8:36 AM
> To: [email protected]
> Subject: upgrade from 4.1 to 5.0 (novice user)
>
> hello,
> I hope this is the right place to ask this question. (I
> couldn't find a novice list) I am more of a programer than
> system admin, but we do what we have to. I have just updated
> all the software on a win 2003 server, except I couldn't
> figure out how to update MySQL, or more accuratly, I couldn't
> figure out how to restore the data after a program update.
> I found the following page (wasn't hard, it's on the download
> page :) )but I'm having a problem following it.
> http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html
>
> these pages also seem relevant:
> http://dev.mysql.com/doc/refman/5.0/en/windows-upgrading.html
> http://dev.mysql.com/doc/refman/5.0/en/backup.html
>
> I guess before I go any farther, the first question I should
> ask is should I do this update. Is this new version
> important, or is it a case of, "If it ain't broke, don't fix it"?
>
> this server has about a dozen databases with around the same
> number of database users.
> I tried to follow the instructions on the pages indicated
> above, with very limited success.
> I find that much of the user documentation gives commands to
> be issued from  shell>  (unix right?) and I'm not sure how
> this applys to windows.
> Also instructions are given like "...do a LOCK TABLES on the
> relevant tables...". Lock tables is a SQL command (right?)
> but from where? do I need to write a script to do the backup,
> or do I issue the commands from PhpMyAdmin or ...? any
> pointers on how to do this would be very much appreciated.
> please forgive errors on my part, I fought this thing till
> very late last night  :) Ray
>
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/[email protected]
>
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/[email protected]
>



-- 
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.