Difference between UDB workgroup, enterprise, standard versions

[Sacha Prins]

Hi,

Is there a place where the functional differences of all UDB products is
explained? I try to find the info on the
http://www.software.ibm.com/db2/ site but the only thing I can extract
from that info is that the enterprise edition has support for
distributing the database on different UDB nodes. Surely there are other
differences?

Anyway, I'm going to upgrade my DB2/2 2.1.2 server in the near future
with UDB 5.2. I run it as a database on a WebServer on an SMP PII PC
running OS/2. Transaction count is high (300.000+ a day) and some
databases are pretty large IMO (0.5 GIG).

Maybe someone can shed some light on this for me.

Thanks,

Sacha

[Blair Kenneth Adamache]

I don't know if we explain it on the web somewhere, so let me explain it
here.
I'll start by reposting my explanation of the differences between
EE (Enterprise Edition) and EEE (Enterprise - Extended Edition), which I
posted to this group on Monday:

EE runs on single machines (including SMP's). It is available on these
operating systems:
NT, OS/2, AIX, HP-UX, Solaris, SCO.

EEE runs on single machines (including SMP's), but can also run on clusters
of
machines (including clusters of SMP's). Each machine in a cluster is called
a node.
Customers in production are running EEE across machines with hundreds of
nodes interconnected.
These machines can be attached through TCP/IP, or channel attached through
more
sophisticated hardware, such as IBM's SP (AIX), Sun Cluster, and Microsoft
Cluster Server (NT). EEE can also exploit Intel's Virtual Interface
Architecture, for even higher speed attachment. EEE is available on AIX, NT
and
Solaris.

Now for some definitions:

EE - see above, also includes DB2 Connect Enterprise Edition (see below)
EEE - see above, also includes DB2 Connect Enterprise Edition (see below)
Workgroup - same as EE, but does not include DB2 Connect Enterprise;
available on NT, OS/2 and SCO
standard - there is no UDB or DB2 product called "standard edition" -
Workgroup is the closest thing we have to a standard edition
DB2 Connect Enterprise Edition - a gateway for DB2 workstation clients
(NT, OS/2, AIX, HP-UX, Solaris, SCO, SGI, Win95, Win98, Win 3.1, Mac, SNI)
to communicate with DRDA hosts like DB2 MVS (DB2 for OS/390), DB2 VM, DB2
VSE, DB2/400.
While supporting all the clients listed above,
the gateway itself (DB2 Connect Enterprise Edition) is offered on: NT, OS/2,
AIX, HP-UX, Solaris, SCO
DB2 Connect Personal Edition - a direct connect client to communicate with
DRDA hosts like DB2 MVS
(DB2 for OS/390), DB2 VM, DB2 VSE, DB2/400. DB2 Connect Personal Edition is
offered on: NT, OS/2, Win95, Win98, Win 3.1
DB2 Personal Edition - a database for one user. Offered on NT, OS/2, Win95,
Win98

There are other products (DB2 Personal Developer's Edition, DB2 Universal
Developer's Edition)
which have been discussed at length in this newsgroup.
There are also two components:
SDK (software developer's kit) - shipped in the Developer's Editions
CAE (Client Application Enabler) - the run time client. All DB2 products
are a superset of the CAE.
CAE's for all supported platforms are shipped with all
server (EE, EEE, Workgroup) and gateway (DB2 Connect Enterprise Edition)
products.

[John Russell]

Sacha Prins <spr...@businessnet.net> wrote:
>Is there a place where the functional differences of all UDB products is
>explained?

Personal Edition is what you would use if the user of the database is
on the same machine as the server. It can also function as a client
of Workgroup/Enterprise Edition/etc. servers, but can't accept inbound
connections.

Workgroup Edition is what you would use in typical client/server
situations with networks of various PC/workstation-class clients and
servers.

Enterprise Edition is what you would use when also gatewaying to
mainframe databases.

Extended Enterprise Edition is what you would use for distributed
databases on clusters and similar parallel networked machines.

The developer editions give you various combinations of these product
CDs, plus extra docs, samples, libraries etc. for developing apps.
The licensing terms prevent you from using the included servers for
production use.

The DB2 UDB Certification Guide, available through retail channels,
summarizes all this pretty well. In the UDB product documentation,
which you can preview at
http://www.software.ibm.com/data/db2/library/, I would look in the
Quick Beginnings book for each of the products.

John
--
John Russell
joh...@interlog.com, http://www.interlog.com/~john13/

[ktuck...@my-dejanews.com]

Thank you Blair for clearing somne of this up, I do have one more question
though,

Can EE do Table partitioning?, Parse queries on seperate CPU's ie. Oracle's
PQO?

In article <36362907...@ca.ibm.com>,

> > Is there a place where the functional differences of all UDB products is

> > explained? I try to find the info on the
> > http://www.software.ibm.com/db2/ site but the only thing I can extract
> > from that info is that the enterprise edition has support for
> > distributing the database on different UDB nodes. Surely there are other
> > differences?
> >
> > Anyway, I'm going to upgrade my DB2/2 2.1.2 server in the near future
> > with UDB 5.2. I run it as a database on a WebServer on an SMP PII PC
> > running OS/2. Transaction count is high (300.000+ a day) and some
> > databases are pretty large IMO (0.5 GIG).
> >
> > Maybe someone can shed some light on this for me.
> >
> > Thanks,
> >
> > Sacha
>
>

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[Blair Kenneth Adamache]

Q: Can EE do Table partitioning?

A: EEE is the only UDB product that can partition tables across machines based on
data in the table (i.e. using a partition key to hash rows to various nodes). All
UDB products
can separate table data across different devices attached to the same machine,
using table spaces to do striping, and place long field data, regular data, and
indexes on different disks.

Q: Can EE Parse queries on separate CPU's?

A: Yes, all UDB products can take advantage of multiple CPU's on one machine to
divide up a query and process it more efficiently. The same is true for utilities
(Load, backup) and index creation.

[ktuck...@my-dejanews.com]

Thank you sir, I see UDB more clearly now.

In article <3637345D...@ca.ibm.com>,

[Sacha Prins]

Blair Kenneth Adamache wrote:

> I don't know if we explain it on the web somewhere, so let me explain it
> here.

[...]

Thanks, now I know I need the Workgroup version.

Sacha

[jamie becker]

In an application environment where I will be using UDB as a backend
for Domino Go WebServer Pro, is UDB 5.2 Personal edition (single
user) enough? I do need SMP but I don't need clustering. I do have
OS/2 DB2 2.11 that I haven't opened yet so I might be eligible for an
upgrade. Will I get all the web and Java tools with personal?

Thanks!!

[Blair Kenneth Adamache]

Sorry, but you cannot use Personal Edition as a backend for a web-based
application. It is licensed for one user only. Here's what our announcement
letter says:

" Web Connections: Customers using DB2 UDB Workgroup Edition and
DB2 Connect Enterprise Edition must treat users of a Web-based application as
if they were users of the DB2 product. For the DB2 Workgroup Edition and DB2
Connect Enterprise Edition, the Web interface is treated as an application
server as described in the CONCURRENT USERS section."