Académique Documents
Professionnel Documents
Culture Documents
IBM, the IBM logo, ibm.com and DB2 are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms
are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this information was published.
Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM
trademarks is available on the Web at Copyright and trademark information at
www.ibm.com/legal/copytrade.shtml
Warehousing Workloads :
Most Consumable, Most Scalable
In-Memory Warehousing Platform
Massive Scale Warehousing at
In-Memory Performance
MPP BLU Scalability
PB scale in-memory warehousing
Enhanced Compatibility
Multi-Lingual SQL Advances
PostgresSQL
Support for European Languages
Codepage 819
2016 IBM Corporation
Exclusions
Metric
New Price
Workgroup
Express
PVU
100
158
68
AUSI
354
554
291
Virtual Server
14,100
Sockets
7520
Data Partitioning
Prices are in US dollars and are subject to change.
SQL Warehouse (SQW)
BLU Acceleration, Compression, Materialized Query Tables
No MQ or CDC Replication
Simple Limits
Authorized User (AUSI) , PVU, and Virtual Server
16 Cores (8 for Virtual Server)
128 GB of memory with no database size limit
9
Exclusions
Data Partitioning
SQL Warehouse (SQW)
BLU Acceleration, Compression
No MQ or CDC Replication
Restrictions
DB2 Connect included for using SQW tooling to access DB2 for z and
DB2 for i
InfoSphere Data Architect limited to 10 authorized users
Cognos Analytics limited to 5 authorized users
Optional Packages
Advanced Recovery Feature
11
12
Benefits to Customers
Simplifies Processor and Sub-capacity Licensing
Aligns to Cloud Hosted Solution Licensing standards across MSPs
Makes it easier for customers On-prem and in Cloud to stay in compliance
Metric
Standard
Advanced
VPC Monthly
135
354
13
Application
14
15
Migration
Customers on these platforms will continue to be supported until the end-ofservice date for DB2 V10.5 (last release that supports these platforms)
17
IBM Power
IBM PowerVM and PowerKVM and IBM Workload Partitions on
IBM Power Systems
VMWare ESXi
Docker container support Linux only
Microsoft
Hyper-V
Microsoft Windows Azure on x86-64 Windows Platforms only
HADR environments can now be upgraded without the need to reinitialize the standby database after performing an upgrade on the
primary database
Applies to all editions except DB2 pureScale
DB2 Version 10.5 Fix Pack 7, or later
19
20
21
TERM
The TERM option can be used to terminate a table move in progress
Terminates a running or table move
TERM will force off the application running the table move, roll back all open
transactions and set the table move to a well defined operational status
From here, the table move can be cancelled or continued
22
Supported Storage
IBM SoftLayer Object Storage
Amazon Simple Storage Service (S3)
23
db2relocatedb Options
The db2relocatedb includes a new option: -g
For generating scripts that can be used as input for database
relocation operations
For cloning a database with different database name and paths
To extract path information from snapshot image without requiring a
DB2 instance
24
DB_NAME=oldName,oldName
DB_PATH=oldPath,oldPath
INSTANCE=oldInst,oldInst
NODENUM=nodeNumber
LOG_DIR=oldDirPath,oldDirPath
CONT_PATH=oldContPath1,oldContPath1
CONT_PATH=oldContPath2,oldContPath2
...
STORAGE_PATH=oldStoragePath1,oldStoragePath1
STORAGE_PATH=oldStoragePath2,oldStoragePath2
...
FAILARCHIVE_PATH=oldDirPath
LOGARCHMETH1=oldDirPath
LOGARCHMETH2=oldDirPath
MIRRORLOG_PATH=oldDirPath
OVERFLOWLOG_PATH=oldDirPath
2016 IBM Corporation
26
06:00
90%
Not
Compressed
05:00
80%
70%
04:00
50%
03:00
Minutes
60%
Backup to /dev/null
Software Compressed
H/W
Compressed
40%
02:00
30%
20%
01:00
10%
0%
00:00
Uncompressed
Compressed
NX842 Compressed
27
ENTERPRISE SECURITY
28
DB2 Native
Encryption
KMIP 1.1
Local Keystore
File
Centralized Key
Manager
DB2 V11.1
Hardware
Security Module
Technology
Preview
PURESCALE ENHANCEMENTS
30
30-step native GPFS setup reduced to simple 4-step DB2 install process
Also easier conversion to GPFS replication post-deployment using db2cluster
32
VMWare
Partitions
RoCE
Network
33
CF
CF
Primary Cluster
CF
34
CF
Standby DR Cluster
M1
M3
CFP
CFS
Site A
M2
M4
Site B
en2
Primary
CF
ro0 ro1
Member 3
en2
ro0 ro1
en2
Site 1
Storage
Switch 1
Switch 2
Peer 1
Peer 1
GPFS
Site 3
replication
Storage
Switch 3
Switch 4
Peer 2
Peer 2
Site 2
ro0 ro1
35
en2
Member 2
ro0 ro1
en2
Secondary
CF
ro0 ro1
en2
Member 4
1.58x
10000
2.1x
8000
6000
4000
2000
DB2 V10.5 fp5
5040
DB2 V11.1
7950
tps
DB2 V11.1
12448
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
36
Sockets
RDMA
133
120
100
105
82.7
80
70
60
40
50.8
26.8
72.8
38
20
0
1 member
2 members
3 members
4 members
37
Example
Workload with INGEST (blue) and TRUNCATE (green) of an unrelated table
DB2 v11.1 has much smaller impact on OLTP workload than DB2 10.5 fp5
Application throughput - DB2 v10.5 fp5
38
Validations performed include, but are not limited to, the following:
40
41
Value Proposition
Improve Response Time
Query #1
Query #1
processing
Query #1
processing
Query #1
processing
1/3 data
1/3 data
1/3 data
Hash partition
(BLU
Acceleration)
Hash partition
(BLU
Acceleration)
Hash partition
(BLU
Acceleration)
42
10s of TB
1000s of TB
100s of Cores
1000s of Cores
1.92x
200
100
Queries Per Hour
250
150
100
50
0
QpH
3 Node (10TB) - 6
MLNS
6 Node (10TB) - 12
MLNS
111
213
QpH
Held up!
80
60
40
20
0
QpH
6 Node (20TB) - 12
MLNS
113
109
43
1.9x
Faster!!
250
200
150
100
50
0
QpH
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
44
Performance Improvements
BLU Acceleration includes a number of performance improvements
in the columnar engine
Faster SQL MERGE processing
Nested Loop Join Support
Industry Leading Parallel Sort
Push-down of a number of OLAP functions into the BLU engine
45
2000
BLU Sort
1500
1000
4.6 X faster
500
13.9 X faster
5.4 X faster
0
Sort+OLAP query 1
Sort+OLAP query 2
Sort+OLAP query 3
Configuration Details
On 4-socket Intel Xeon platform with 72 Cores and 742G RAM
1 TB TPC-DS database
Query scenarios involving multiple sort and OLAP operations
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
46
Row Sort
45
40
35
30
25
20
15
10
5
0
BLU Sort
1.86 X faster
1.48 X faster
1.51 X faster
Sort query 1
Sort query 2
Sort query 3
Configuration Details
BLU MPP with 1 physical node/4-MLNs and 8 cores per MLN
4-socket, 40 Cores Intel Xeon platform and 1 TB RAM
Used Sort Target Workload 1 TB (an internal workload based on the TPC-DS
schema), with 10-Million rows to sort for each scenarios
Query scenarios involving single ORDER BY concentrating on sort operation
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
47
Query Throughput BD
Insights (800GB)
1.36x
1200
Native BLU
Evaluation
Native Sort
Native OLAP (usually combined with sort)
Enables query plans to remain as much as
possible within the columnar engine
Query Rewrite
Improvements
1000
800
600
400
200
0
QpH
DB2 V11.1
955.82
Improved
SORTHEAP
Utilization
Configuration Details
2 socket, 36 core Intel Xeon E5-2699 v3 @ 2.3GHz
192GB RAM
BD Insights Internal Multiuser Workload 800GB
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
48
Wide rows
Logical character support (CODEUNITS32)
Numeric Functions
POWER, EXP, LOG10, LN
TO_NUMBER
MOD
SIN, COS, TAN, COT, ASIN, ACOS, ATAN
TRUNCATE
Miscellaneous
COLLATION_KEY
50
52
with v1 as(
select i_category, i_brand, cc_name, d_year, d_moy, sm_type,
sum(cs_sales_price) sum_sales,
avg(sum(cs_sales_price)) over
(partition by i_category, i_brand, cc_name, d_year)
avg_monthly_sales,
rank() over
(partition by i_category, i_brand, cc_name
order by d_year, d_moy) rn
from BDINSIGHTS.item
, BDINSIGHTS.catalog_sales BDINSIGHTS.date_dim, BDINSIGHTS.call_center
, BDINSIGHTS.ship_mode
where cs_item_sk = i_item_sk and cs_sold_date_sk = d_date_sk
and cc_call_center_sk= cs_call_center_sk
and cs_ship_mode_sk = sm_ship_mode_sk
and d_year = 2000
group by i_category
, i_brand , cc_name , d_year , d_moy, sm_type),
v2 as(
select v1.i_category, v1.i_brand, v1.cc_name, v1.d_year, v1.d_moy
, v1.avg_monthly_sales, v1.sum_sales, v1.sm_type, v1_lag.sum_sales psum
, v1_lead.sum_sales nsum
from v1
, v1 v1_lag , v1 v1_lead
where v1.i_category = v1_lag.i_category
and v1.i_category = v1_lead.i_category and v1.i_brand = v1_lag.i_brand
and v1.i_brand = v1_lead.i_brand and v1. cc_name = v1_lag.cc_name
and v1. cc_name = v1_lead.cc_name and v1.rn = v1_lag.rn + 1
and v1.rn = v1_lead.rn - 1)
select *
from v2
where d_year = 2000
and avg_monthly_sales > 0
and case when avg_monthly_sales > 0
then abs(sum_sales - avg_monthly_sales) / avg_monthly_sales
else null end > 0.1
order by sum_sales - avg_monthly_sales
, cc_name
fetch first 100 rows only
25
20
4.3x Faster!!
15
10
5
0
OLAP Query
V10.5
V11.1
22.814
5.326
53
16x Faster !
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
54
SQL ENHANCEMENTS
55
56
57
INITIATE
ACCUMULATE
MERGE
FINALIZE
58
COLLATION_KEY Function
COLLATION_KEY
The COLLATION_KEY function returns a VARBINARY string that represents
the collation key of the expression argument, in the specified collation
This function is used in SQL for ordering and comparison operations
Format
COLLATION_KEY( expression, collation_name, [length] )
Arguments
Expression - An expression for which the collation key is determined
Collation_Name - An expression that specifies the collation to use when the
collation key is determined
Length - An expression that specifies the length attribute of the result in bytes
Example:
The following query orders employees by their surnames by using the
language-aware collation for German in code page 923
SELECT FIRSTNME, LASTNAME FROM EMPLOYEE
ORDER BY COLLATION_KEY (LASTNAME, 'SYSTEM_923_DE')
59
CUME_DIST
The CUME_DIST function is a distribution function that returns a cumulative
distribution of a row within an OLAP window
PERCENT_RANK
The PERCENT_RANK function is a distribution function that returns a relative
percentile rank of a row within an OLAP window
Compatibility Features
Double-dot notation
You can use double-dot notation to specify a database object
Date/Time
Statistics
Bit Manipulation
Data Types
Strings
DATE_PART
ADD_YEAR
COVARIANCE_SAMP
HASH
INT2
STRPOS
RANK
FIRST_VALUE
DATE_TRUNC
ADD_MONTHS
STDDEV_SAMP
HASH4
INT4
STRLEFT
DENSE_RANK
RATIO_TO_REPORT
AGE
ADD_DAYS
VARIANCE_SAMP
HASH8
INT8
STRRIGHT
ROW_NUMBER
EXP
LOCALTIMESTAMP
ADD_HOURS
CUME_DIST
TO_HEX
FLOAT4
REGEXP_COUNT
LPAD
LOG10
NOW Function
ADD_MINUTES
PERCENT_RANK
RAWTOHEX
FLOAT8
REGEXP_EXTRACT
RPAD
COLLATION_KEY
THIS_QUARTER
ADD_SECONDS
PERCENTILE_DISC
INT2AND
BPCHAR
REGEXP_INSTR
TO_CHAR
LN
THIS_WEEK
DAYOFMONTH
PERCENTILE_CONT
INT2OR
BINARY
REGEXP_LIKE
INITCAP
TO_NUMBER
THIS_YEAR
FIRST_DAY
MEDIAN
INT2XOR
VARBINARY
REGEXP_MATCH_COUNT
TO_DATE
MOD
THIS_MONTH
DAYS_TO_END_OF_MONTH
WIDTH_BUCKET
INT2NOT
LOG
REGEXP_REPLACE
MONTHNAME
SIN
NEXT_QUARTER
HOURS_BETWEEN
COVAR_POP
INT4AND
RANDOM
REGEXP_SUBSTR
DAYNAME
COS
NEXT_WEEK
MINUTES_BETWEEN
STDDEV_POP
INT4OR
BTRIM
POWER
TAN
NEXT_YEAR
SECONDS_BETWEEN
VAR_POP
INT4XOR
AVG
COT
NEXT_MONTH
DAYS_BETWEEN
VAR_SAMP
INT4NOT
COUNT
ASIN
NEXT_DAY
WEEKS_BETWEEN
INT8AND
COUNT_BIG
ACOS
INT8OR
MIN
ATAN
INT8XOR
MAX
TRUNCATE
INT8NOT
SUM
EXTRACT
62
OLAP Pushdown
OLAP Pushdown
Reference Information
DB2 Version 11.1 Information Center (Preview)
www.ibm.biz/db2v11docs
63