What are the disk requirements for DB2 on OS/2? 
Author Message
 What are the disk requirements for DB2 on OS/2?

Quote:

>I have server version of DB2 2.1.1 install in 60MB, box say 25-64MB.
>There's not much price difference between single user prices of DB2/2
>and SQLAnywhere.

The thing is, in order to use DB2 with REXX (which is what I want to
do) I have to buy DB2 ($327 from Indelible Blue) *and* the DB2 SDK
($205), which makes it significantly more more expensive than SQL
Anywhere ($295).  And then there's the matter of IBM's Visualizer Suite
(more $); is any of that functionality included in SQL Anywhere?

Quote:
>I have trouble between SQLAnywhere and VA ST that is irritating, VA is
>looking for uppercase and (I think) SQL Anywhere is returning lowercase
>value in query build process.

You have used both DB2 and SQL Anywhere?  How do they compare?  For me,
since the resource requirements of DB2 don't seem to be as outlandish
as I had feared, the main question comes down to ease of use,
documentation, and quirks.  I understand DB2 has better documentation,
but Sybase is pushing {*filter*} ease of use for SQL Anywhere, and I
really don't want to have to spend weeks getting up to speed.  (OTOH,
part of my reason for buying a database is to sharpen my DBA skills, so
maybe I should *want* a challenge).

Then there is the matter of quirks.  There was one particular quirk in
the implementation of the REXX/SQL interface under VM/CMS (RXSQL) a few
years back which especially bugged the hell out of me, because it
showed lack of planning on IBM's part.  If you were inserting a value
from a REXX host variable into a character field you had to enclose the
value in quotes to guarantee that the update wouldn't fail.  That is,
if X contained the value I wanted to insert into a field DBFLD, before
executing the SQL insert statement using X as a host variable I would
have to set X = "'"X"'".

The reason is that, because of poor planning on IBM's part (the API was
first designed with the assumption that it would be called by typed
languages), when RXSQL was preparing an insert or update statement
using host variables it had no good way to determine the data type of
DBFLD, so it would look at the value in the host variable X and make a
guess from that.  Thus if X = "Hello", RXSQL would assume that DBFLD
was character field, whereas if X = "12345" it would assume an integer
field.  So if I set X = "12345" and DBFLD was in fact a character field
(a perfectly legitimate update), RXSQL would look at the value, think
"ah, an integer", internally convert the string into a 4 byte integer
value, set up its internal data structures to do an insert into an
integer field, and of course the insert would fail!  The kludge that
IBM used to get around this was to tell me to set X = "'12345'", to
explicitly inform RXSQL that DBFLD was a character field, the
convention being that such quotes would always be stripped off before
the actual insert.

I am wondering whether IBM ever fixed this (I did put in a request
through SHARE), or whether this annoying quirk has been carried over to
the REXX/DB2 interface under OS/2.  And what about SQL Anywhere?  Does
it share this quirk, or have any particularly annoying quirks of its
own?  I guess what I'd like to know is which of these databases has the
cleanest and most logical design, and I'm hoping that someone who has
used both will have an opinion.
--
John Brock



Sun, 22 Nov 1998 03:00:00 GMT
 What are the disk requirements for DB2 on OS/2?

Quote:
>You have used both DB2 and SQL Anywhere?  How do they compare?  

Yes, I have both installed used SQL Anywhere (Watcom) while waiting for DB2
delivery and with Powerbuilder.  DB2 is supposed to be a top-end RDBMS for
large volumes of data.  Watcom is not in that arena, as yet.  Watcom seems to
perform better during the testing I've done to date.  Both have a native SQL
and an ODBC interface with the product.

BTW,  If you buy the single user version of DB2/2, you get the SDK included,
it's a separate product only in the server version.

Quote:
>Then there is the matter of quirks.  There was one particular quirk in
>the implementation of the REXX/SQL interface under VM/CMS (RXSQL) a few
>years back which especially bugged the hell out of me, because it
>showed lack of planning on IBM's part.  If you were inserting a value
>from a REXX host variable into a character field you had to enclose the
>value in quotes to guarantee that the update wouldn't fail.  That is,
>if X contained the value I wanted to insert into a field DBFLD, before
>executing the SQL insert statement using X as a host variable I would
>have to set X = "'"X"'".

   snip

>through SHARE), or whether this annoying quirk has been carried over to
>the REXX/DB2 interface under OS/2.  And what about SQL Anywhere?  Does
>it share this quirk, or have any particularly annoying quirks of its
>own?  I guess what I'd like to know is which of these databases has the
>cleanest and most logical design, and I'm hoping that someone who has
>used both will have an opinion.

I had the REXX code done for DB2 and it appears to still function as you
describe on VM.  I just used the same code with Watcom's REXX interface,
but I think Watcom followed IBM's lead on REXX.  I had to have separate
'connect' code for each DB, otherwise everything else ran unchanged.

FWIW, SQL Anywhere has no run time charges unless you distribute the
developement environment.  SQL Anywhere's bells and whistles tools are
Win 95/NT only, OS/2 - you're stuck with ISQL.



Mon, 23 Nov 1998 03:00:00 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. I am having a problem with a hard disk drive or floppy disk drive

2. Differences between SQL on DB2-MVS and DB2-OS/2 or DB2-NT

3. z/OS OS/390 DB2 DBA Position available in Dallas, Texas

4. Db2 V7 for z/OS and OS/390

5. Disk to Disk move of DB2 DB

6. desire to move data from OS 390 DB2 to AS/400 DB2 using DTS

7. Table Limit with DB2 Connect to DB2 for OS/390

8. DB2 Spatial Extender & DB2 for z/OS

9. Load data from DB2 in NT to DB2 in OS/390

10. Creating DB2 SQL Procedures in DB2 version 6 on OS/390 (June 2000 PUT)

11. DB2 Conenct & DB2 on OS/390

12. Trigger working in DB2 for NT but not in DB2 on an OS/390-machine


 
Powered by phpBB® Forum Software