A presentation that discusses staff, server, and storage needs for IBM DB2. Comparisons with Oracle Database and Microsoft SQL Server are included where possible.
2. Legal Notices
The information on features in development is intended to outline our general product direction
and it should not be relied on in making a purchase decision. The information on the features in
development is for informational purposes only and may not be incorporated into any contract.
The information on the features in development is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. The development, release, and timing
of any features or functionality described in our products remains at our sole discretion.
The information contained in this presentation is provided for informational purposes only.
Although efforts were made to verify the completeness and accuracy of the information
contained in this presentation, it is provided "as is", without warranty of any kind, express or
implied. In addition, this information is based on IBM’S current product plans and strategy and
represent IBM'S goals and objectives only, and are subject to change or withdrawal by IBM
without notice.
IBM shall not be responsible for any damages arising out of the use of, or otherwise related to,
this presentation or any other documentation. Nothing contained in this presentation is intended
to, or shall have the effect of creating any warranty or representation from IBM (or its affiliates
or their suppliers and/or licensors); or altering the terms and conditions of the applicable license
agreement governing the use of IBM software.
7. DB2 Needs 43% Less Staff on System p
16.0
DB2
Oracle
27.9
Database
Microsoft
Not
0.0 Available on System p
SQL Server
Source: Solitaire Interglobal Ltd Whitepaper: DB2 Performance on IBM System p® and System x®
12. DB2 Self-Tuning gives Best Performance
Self-Tuning 63,796
Manually
Tuned for 63,302
Benchmark
16,713
No Tuning
Source: Internal Testing with Benchmark Systems
13. “DB2’s automated administration features are going to save
me 30% to 35% of my support costs.”
—Bob Maddocks, Maddocks Systems
16. More Performance with Less CPU Cores
TPC-C Benchmark
DB2 9.5
64 CPU Cores
tpmC: 6,085,166; Price/tpmC: 2.81 USD; System Available: 12/10/08
Processors: 32; Cores: 64; Threads: 128
Oracle 10g
128 CPU Cores
tpmC: 4,092,799; Price/tpmC: 2.93 USD; System Available: 8/6/07
Processors: 64; Cores: 128; Threads: 256
SQL Server
64 CPU Cores
tpmC: 1,231,433; Price/tpmC: 4.82 USD; System Available: 6/5/06
Processors: 64; Cores: 64; Threads: 64
Source: Published TPC-C Benchmark Results
17. More Performance with Less CPU Cores
TPC-H 10TB Benchmark
DB2 9.5
64 CPU Cores
QphH: 343,551; Price/QphH: 32.89 USD; System Availability: 04/15/08
Processors: 64; Cores: 128; Threads: 128
Oracle 10g
64 CPU Cores
QphH: 208,457; Price/QphH: 27.97 USD; System Availability: 09/10/08
Processors: 64; Cores: 128; Threads: 128
SQL Server
32 CPU Cores
QphH: 63,650; Price/QphH: 38.54 USD; System Availability: 02/27/08
Processors: 32; Cores: 64; Threads: 64
Source: Published TPC-H 10TB Benchmark Results
18. More Performance with Less CPU Cores
SAP SD 3-Tier Benchmark
DB2 8.2
32 CPU Cores
168300
Oracle 10g
64 CPU Cores 100000
Source: Published SAP SD 3-Tier Benchmark Results
20. Consistently Better Performance
Number of Days Leading TPC-C Benchmark
IBM DB2 1,433
Oracle
Database 721
Microsoft
SQL Server 119
Source: Between 01 Jan 2003 and 23 Mar 2009
21. Consistently Better Performance
Number of Days Leading TPC-H 10TB Benchmark
IBM DB2 1,623
Teradata 425
Oracle
Database 225
Source: Between 01 Jan 2003 and 23 Mar 2009
22. Consistently Better Performance
Number of Days Leading SAP 3-Tier SD Benchmark
IBM DB2 2,066
Oracle 207
Database
Microsoft
SQL Server 0
Source: Between 01 Jan 2003 and 23 Mar 2009
23. Only DB2 has led performance in
these key benchmarks at the same time
24. “…we have observed a 40% cut in
response times with DB2…”
—Peter Boegler, SAP IT
36. “To move our application to DB2 9.5 would have
taken an estimated two-year effort…
it took only one week to move it to DB2 9.7”
—Paolo Juvara, Openbravo
37. “This feature is a paradigm shift in the very
concept of database migration!”
—Godson Retna, Cognizant Technology Solutions