Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Which download file for just Windows client 4.1.14? 1

Status
Not open for further replies.

SantaMufasa

Technical User
Jul 17, 2003
12,588
US
I know that I have exhausted my budget of MySQL questions for the day, but I have one more and promise that I won't ask anymore today.

I must install MySQL 4.1.14 client only on Windows XP 2002 SP2. When I go out to " the only choices there are for Server downloads.

Does anyone have guidance for me for downloading just the 4.1.14 client for Windows XP 2002 SP2? I would also be obliged if there are also warnings of foxholes on MySQL client-only installs.

Thanks,

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
 
see here for info on windows installs, and here for the current downloads page.

______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.
 
KarveR,

Thanks for the postings. Since 4.1.14 is an "Older Release", I went to the Old Releases / MySQL Database Server 4.1 page, where the only offerings there are for MySQL Database Server 4.1.x., wherein there are two offerings: "4.1.16 (286 files)" and "4.1.14a (2 files)".

So, fundamentally my questions are:

1) Must I download 1, or both, of these SERVER offerings just to get a Windows MySQL-client-install versus my going to another link to download a file for just a client-install 4.1.14,

and,

2) What are the differences between these two files, represented in terms of installed functionality.

And since my user is chomping at the bit, calling me every 20 minutes to see "is it soup yet?", I'm grateful for any early responses like KarveR has already effected. (But I also understand that most of the MySQL world has gone home for the day or is asleep right now.[smile])

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
 
I could understand (mostly) why you'd need an older server, but can't figure out what merits an older client would have - afterall, the server is the bit which performs all the magic.

______________________________________________________________________
There's no present like the time, they say. - Henry's Cat.
 
KarveR is right. For normal Windows usage, MYSQL Query Browser is the way to go. It has a GUI which is much friendlier than the command-line client which is bundled with the server. You would only use the latter if you needed MySQL access within scripts.

If you do decide that the command-line client is what you need, then what you would do is download the "no-installer" version of the MySQL server, strip out everything except the client (mysql.exe) and necessary libraries (cygwin*.dll, libmysql.dll and possibly some other bits). You might also need to keep the appropriate locale files, located in the /share directory.
 
Gentlefolk,

Thanks for your welcomed responses. Here are some background of my need and some responses to your questions that might help you to help me:

First, the platform that we are assembling is a Certification Platform for our software. Contractually, the platform must match exactly the version specifications of a specific customer for whom the certification platform exists. The versioning came to me as a specification document that I must match. This is the reason that we are not using the most current MySQL version offering (4.1.15).

Next, we do have a MySQL database server installation on a Linux server to which the Windows MySQL client installation connects. The client installation exists to run a suite of nightly tests. I believe that there is no human intervention that would even benefit from a GUI interface...the client simply connects to the server and runs the batched MySQL code.

Given the above scenario, is Tony's advice, below, my best strategy?
TonyGroves said:
...download the "no-installer" version of the MySQL server, strip out everything except the client (mysql.exe) and necessary libraries (cygwin*.dll, libmysql.dll and possibly some other bits). You might also need to keep the appropriate locale files, located in the /share directory.

Are there any addenda you recommend that I consider/follow?

Thanks for everyone's help.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
 
Since I'm under extreme pressure to get this problem resolved, I'm forging ahead with a 4.1.14 download/install, even if it includes far more than I actually need for the client install (i.e., a sever install).

The problem that I now face is that when go to the appropriate 4.1.14 download screen, my choices are:
MySQL 4.1.14 download said:
Microsoft Windows 32 (18 Aug 2005, 37.0M)
Signature MD5: d77df5da252e44716cbebb0e97f5ec9b

Microsoft Windows 32 (21 Aug 2005, 16.4M)
Signature MD5: 0f63b0070c2901fd1a2da32992ca41d2

Microsoft Windows 32 (18 Aug 2005, 38.8M)
Signature MD5: 20138f87444cf492dd028ccd915880b7
How does a person differntiate amongst these choices if the names are all the same, the dates are close, and the sizes are rather disparate?


Appreciative of an early response.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
 
The first file is the "full installer" archive.
This contains everything, including unnecessary scripts for benchmarking, debugging, etc, and a GUI installer.

The second is the "essentials installer" file.
This contains just the server and client, with a GUI installer.

The third is the "full no-installer" archive. You just unzip the archive into a chosen directory; nothing gets "installed". You can then strip out the bits you don't need.

If you don't mind using a GUI installer, then the second file, being the smallest, should be sufficient, as long as it allows you to skip setting-up the server (I don't know if it does).
 
As a follow-on update, Tony, to your excellent (Purple-Star-worthy suggestion), when I executed the "essentials installer" .msi that you recommended, I chose the "custom install" button (hoping that it would allow me to install just the client), and, sure enough, one of the options was "Client Only". I installed via that option, and although it also demanded to create a local (client-side) database, it gave me my objective: a MySQL client.

Thanks again for your (and the other's) help.

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top