Mailing List Archive


Back to the month index Back to the list index
Jethro Wright (jetman@li.net)
Wed, 12 Nov 1997 16:37:57 -0500 

Message-Id: <199711122145.QAA17445@linet06.li.net>
From: "Jethro Wright" <jetman@li.net>
Subject: Re: mSQL evaluation report
Date: Wed, 12 Nov 1997 16:37:57 -0500


--
[snip]
> A company considering licensing mSQL, requested me an evaluation
> report about it.  I am in trouble because although the whole thing may
> end up in a Unix mSQL server they also want information about Windows
> mSQL ports and Windows client API's. I use mSQL only under Linux and
> Solaris systems with the Java, C and Perl languages. The only mSQL
> related code I've run on Windows was a Java applet. I'll put the
> information I obtained about Windows on the end of the email.
> 
> I need some help in doing the Windows part of this report, is there
> anyone with a working Windows-mSQL-SomeProgLanguage system? Please
> provide me some evaluation on your system (please send system
> configuration detais as well: operating system versions, api versions
> and sites were to download system components, performance, bugs). 
> 

	Andre:  I'm using the Win32 version of mSQL 1.16c w/ Visual Basic
4.0.  Works well, both DB server and client DLL.  I just started
development
work (exclusively for past two weeks) using mSQL, so I can't give you a
detailed review, but my initial efforts have been encouraging.

	Server:  P60, 32MB of RAM, 700MB of hdisk space, Windows 95, connected
	via Ethernet.

	Client: 486DX-33, 12 MB of RAM, 340MB of hdisk space, Windows 95, and
	Ethernet (of course.)

	I picked up all of the sware from the Bond site (ftp://bond.edu.au.),
as indicated in the FAQ.  Can't say much about performance, bec the server
machine seems to run unusually slow (due to reasons that have nothing to
mSQL or Windows, for that matter.)  My only criticism is that the
documentation
for the port didn't talk about all of the differences bet the Unix, OS/2,
and
Windows versions and so I had to stumble along until I discovered the SETUP
util
didn't create a mSQLDB sub-dir, so efforts to create a database during my
1st
few hours w/ mSQL failed.  I also had a problem using the ORDER BY clause
in a simple SELECT (select * from name_addr order by fname asc).  The mSQL
monitor comes back w/ 'ERROR: Couldn't create temporary table.'  Never got
back to it, to debug what caused the problem.  Again, I suspect it's a
documentation oversight.  Probably it needs an environment variable that I
haven't defined.  

	Hope this helps....Jet