sunfloweremryologistΔιαχείριση Δεδομένων

31 Οκτ 2013 (πριν από 4 χρόνια και 8 μήνες)

114 εμφανίσεις


Prisbild enligt uppgifter från återförsäljare i Sverige

DB2 licensieras antingen per processor eller per server och namngivna

användare. IBM/Lotus har ett centralt avtal för skolan, Passport Advantage

academic option som reglerar rabattnivån för
skolan. Processor modellen är

till för Internet och Intranetanvändare, dvs obegränsat antal användare

per processorlicens.


Årlig avgift /Maintenance

Enterprice Edition, Processor.

182 171 SEK / processor

40 487 SEK / processor

group Edition unlimited

129 796 SEK / processor

28 844 SEK / processor

Workgroup Edition Server

userlicens enligt nedan

8 478 SEK / server

1 882 SEK / server

Workgroup Edition User Licens

2 192 SEK / användare

486 SEK / använ

Samtliga ovanstående priser är giltiga per dagens datum och gäller under

Statskontoret Passport Advantage licensavtal. I priserna ingår ett års

programvaruprenumeration och support. Licenspriserna är en engångsavgift

medans Maintenance är en årlig a

Skillnaden mellan Workgroup Edition och Enterprise Edition ligger i en

begränsning på 8 CPU(nt)/ 4 CPU(unix) för Workgroup Edition. Övrigt

innehåller den samma funktionalitet.

Med andra ord, har ni inte behov idagsläget av att köra databasen på st

maskin kan ni börja med Workgroup Edition.

Nedan följer utdrag av jämförelse med Oracle 9i.



DB2 UDB EE (Enterprise Edition) license fees are half Oracle9

license fees in

all configurations with external Internet
deployment. In addition, DB2 UDB EE

offers substantial price benefit for all configurations with 25 or more named

users, and it lists at one half of Oracle9

for all configurations with more than 50

users per processor. In configurations with 25
50 users

per processor, DB2 UDB

EE offers a significant price advantage, while in configurations with fewer than

25 users per processor, DB2 UDB EE lists higher than Oracle9
. These

conclusions apply equally well to data warehousing configurations.

models for Oracle9

and DB2 UDB 7.2 differ somewhat. DB2 UDB uses

a straightforward per
processor model, providing an unlimited user license for

both DB2 UDB (DB2 UDB EE) and DB2 UDB Enterprise . Extended Edition

(DB2 UDB EEE) licenses. Oracle9

pricing strategy encompasses two models .

an unlimited user model and a named
user model.

As a result of this discrepancy between pricing models, DB2 may be more

economical in some cases whereas Oracle9

might be more economical in other

. For this reason, we analyze the pricing rules and price points to determine

the actual charges to customers across a range of installation sizes and using the

various pricing options. Resulting price schedules appear in the Appendix and are

summarized in

Exhibit 1 (x
axis refers to the number of users).


A comparison of results reveals the following characteristics for each DBMS

within an OLTP or Internet environment:


charges twice as much as DB2 UDB for unlimited
ser licenses.

charges twice as much as DB2 UDB for configurations of 50 named

users per CPU.

DB2 offers a price advantage for all installations that configure more than 25

named users per CPU.

Under its named user policy, Oracle9

can offer

a reasonable price for

configurations with up to 25 users per CPU. DB2 configurations with this

number of users may do well with the Workgroup Edition of the DBMS.

Both Oracle and DB2 offer versions for workgroups.

Although the named
user opti
on may appear to be an economical solution for

certain CPU
intensive applications, where a small number of users require much

CPU power, it appears likely that many customers will opt for the per

pricing model in most cases for the follow
ing reasons:

Under the named user pricing option, Oracle9
does not distinguish between

time users and occasionally connected users; customers must count all

users, even those who log on just once or twice a week. For this reason, it is

likely that
most Oracle customers will prefer the per
processor, unlimited

user pricing.

Under the named user option, customers must notify Oracle as users are

added to the system. It is likely that any given system will grow over time, so

that even systems pu
rchased on a per
user basis will revert to per

pricing over time.

Internet applications must operate under a per
processor license, since users

cannot be named in advance. Intranet applications with a finite number of

known users, ho
wever, can run under Oracle9
s named
user pricing, since

the users can be identified.

For data warehousing environments, results are the same as for OLTP or

Internet environments. That is, under the per
processor license, Oracle9


twice as much as DB2 UDB. Under its named
user policy, Oracle9

can offer a

modest price for configurations with fewer than 25 users per CPU, an attractive

choice for many data warehousing environments. DB2 offers a price advantage,

however, for all instal
lations that configure more than 25 users per CPU.