- Page 1: Best Practices for SAP BI using DB2
- Page 5 and 6: Contents Notices . . . . . . . . .
- Page 7 and 8: 7.4.3 Data Partitioned Secondary In
- Page 9 and 10: Related publications . . . . . . .
- Page 11 and 12: Notices This information was develo
- Page 13 and 14: Preface This IBM® Redbooks® publi
- Page 15 and 16: Georg Mayer is a Senior Development
- Page 17 and 18: Thanks to the following people for
- Page 19 and 20: Chapter 1. Introduction 1 In any en
- Page 21 and 22: Furthermore, the SAP BI application
- Page 23 and 24: 7 x 24 application availability 99.
- Page 25 and 26: - MCOD - System z first - reduces c
- Page 27 and 28: Chapter 2. Overview of SAP BI and r
- Page 29 and 30: A DSO, or data store object, is a d
- Page 31 and 32: 2.2.1 Report SAP_BWTOOLPGM_DB2 If y
- Page 33 and 34: Note that in Figure 2-5 the Adminis
- Page 35 and 36: 2.3.2 Range partitioning of F- fact
- Page 37 and 38: ROTATE SQL statement. This defines
- Page 39 and 40: 2.3.5 Usage of data partitioned sec
- Page 41 and 42: Table structure of facttable Indice
- Page 43 and 44: 2.4 SAP BI snowflake schema Figure
- Page 45 and 46: ► SAP Analyze Tool This new query
- Page 47 and 48: Chapter 3. Top ten SAP BI recommend
- Page 49 and 50: A cost-based optimizer relies on cu
- Page 51 and 52: - Improved bufferpool hit ratio (mo
- Page 53 and 54:
4 Chapter 4. Benefits of DB2 9 for
- Page 55 and 56:
Figure 4-1 shows an SAP BI snowflak
- Page 57 and 58:
DB2 V9 Dynamic Index ANDing � Dyn
- Page 59 and 60:
If you are interested in how SAP BI
- Page 61 and 62:
) SHRLEVEL CHANGE REPORT NO cause f
- Page 63 and 64:
Figure 4-7 explains how to influenc
- Page 65 and 66:
► A single value is never broken
- Page 67 and 68:
Global query optimization addresses
- Page 69 and 70:
WHERE clause). The performance impr
- Page 71 and 72:
4.7 RENAME INDEX DB2 8 for z/OS onl
- Page 73 and 74:
Chapter 5. Best practices for PSA 5
- Page 75 and 76:
Figure 5-1 illustrates the data upd
- Page 77 and 78:
Figure 5-3 shows the available opti
- Page 79 and 80:
In BI 7.x releases the scheduling o
- Page 81 and 82:
During the first test case, we defi
- Page 83 and 84:
The PSA load process was running su
- Page 85 and 86:
The package size depends on the SAP
- Page 87 and 88:
added. If you do not manage PSA pro
- Page 89 and 90:
Using the SE14 transaction with the
- Page 91 and 92:
Chapter 6. Best practices for InfoC
- Page 93 and 94:
Some of the terminology has changed
- Page 95 and 96:
► SAP RemoteCube In an SAP Remote
- Page 97 and 98:
You would repartition an InfoCube w
- Page 99 and 100:
At this stage (Figure 6-6) you will
- Page 101 and 102:
The repartitioning process can be m
- Page 103 and 104:
In our example, our repartitioning
- Page 105 and 106:
You are also able to view the new p
- Page 107 and 108:
► Partitioning enables fast delet
- Page 109 and 110:
6.3.1 Procedure for remodeling an I
- Page 111 and 112:
Next you add an operation to the li
- Page 113 and 114:
Figure 6-22 Remodeling monitor Once
- Page 115 and 116:
6.4.2 Data validation ► SAP compr
- Page 117 and 118:
► Load impact - Loading data into
- Page 119 and 120:
- When not condensing all requests:
- Page 121 and 122:
7 Chapter 7. Best practices for Dat
- Page 123 and 124:
7.2.2 DataStore object for direct u
- Page 125 and 126:
7.3.1 Creating a secondary index on
- Page 127 and 128:
partitioning and table-controlled p
- Page 129 and 130:
BIC/A00) table. Keep in mind that t
- Page 131 and 132:
DPSI indexes provide an alternative
- Page 133 and 134:
SYSREC DD DSN=LYDIA.SMPLUNLD.SYSREC
- Page 135 and 136:
From the window DB2/390 Storage Att
- Page 137 and 138:
Now return to the window ABAP Dicti
- Page 139 and 140:
POSITION( 00033:00042) VARGRAPHIC ,
- Page 141 and 142:
To use the LimitKey function, call
- Page 143 and 144:
Example of an SAP object log for ta
- Page 145 and 146:
| '19990424' ) , PART 5 VALUES ( '2
- Page 147 and 148:
| Table type /BIC/WADSOTEST00 was a
- Page 149 and 150:
| COMMIT WORK | DDL time(___3): ...
- Page 151 and 152:
7.5.1 Materialized query tables Mat
- Page 153 and 154:
Chapter 8. Query and Load performan
- Page 155 and 156:
When users complain about performan
- Page 157 and 158:
Use transaction SM21 to check your
- Page 159 and 160:
ST04, ST05 RSRT Find problem SQL DB
- Page 161 and 162:
cause could be any phase of the loa
- Page 163 and 164:
Additionally, we can get more infor
- Page 165 and 166:
Here you can see whether there is i
- Page 167 and 168:
Figure 8-10 STAD window Furthermore
- Page 169 and 170:
Double-click to go to the Single Re
- Page 171 and 172:
Alternatively, if temporary trace i
- Page 173 and 174:
If transfer time takes the most ela
- Page 175 and 176:
performance. Then rebuild them for
- Page 177 and 178:
Figure 8-16 shows the data provided
- Page 179 and 180:
To drill down to an individual exec
- Page 181 and 182:
oad map to determine the cause of t
- Page 183 and 184:
Analysis of the processing on the p
- Page 185 and 186:
Type in the query name that you wou
- Page 187 and 188:
Figure 8-24 RSRT RSDDSTAT Pressing
- Page 189 and 190:
transferred is greater than 10), th
- Page 191 and 192:
Figure 8-30 ST04 Explain output Sel
- Page 193 and 194:
Figure 8-31, Figure 8-32 on page 17
- Page 195 and 196:
Figure 8-33 Visual Explain - graphi
- Page 197 and 198:
The SAP Query Analysis Tool enables
- Page 199 and 200:
For join performance it is essentia
- Page 201 and 202:
Figure 8-39 Table /BIO/SSALESORG in
- Page 203 and 204:
The Index information tab shown in
- Page 205 and 206:
The SAP query visualizer gives you
- Page 207 and 208:
The graphical view is obtained by c
- Page 209 and 210:
► Table cardinalities and selecti
- Page 211 and 212:
The link between the objects as ind
- Page 213 and 214:
Chapter 9. SAP BI Accelerator 9 Thi
- Page 215 and 216:
9.2 Sizing BIA managed because only
- Page 217 and 218:
This is actually a BI 7.0 installat
- Page 219 and 220:
► SAP BI user ► SAP BI password
- Page 221 and 222:
Chapter 10. Tips for SQL efficiency
- Page 223 and 224:
Step 1 - Join Analysis Figure 10-2
- Page 225 and 226:
The second predicate joins "/BIC/AZ
- Page 227 and 228:
This step involves breaking apart t
- Page 229 and 230:
10.2 SQL efficiency for InfoCube No
- Page 231 and 232:
Within the WHERE clause, we first f
- Page 233 and 234:
With all table join relationships r
- Page 235 and 236:
This step involves breaking apart t
- Page 237 and 238:
is run on an empty table (dimension
- Page 239 and 240:
Table 10-2 Indexing options Column
- Page 241 and 242:
10.3.1 Index design for post-DSO ac
- Page 243 and 244:
For efficient join performance, it
- Page 245 and 246:
Chapter 11. Project Jupiter: large
- Page 247 and 248:
This very powerful combination of t
- Page 249 and 250:
► The BI Accelerator was installe
- Page 251 and 252:
the input files for the InfoCube lo
- Page 253 and 254:
11.3.1 SAP BI database The four mos
- Page 255 and 256:
On the other hand, the bufferpools
- Page 257 and 258:
Table 11-1 lists our Jupiter BI Acc
- Page 259 and 260:
atch work processes are available.
- Page 261 and 262:
(max_size=250,000,000, and max_spli
- Page 263 and 264:
Figure 11-5 shows that the average
- Page 265 and 266:
Objectives The goal for the multi-u
- Page 267 and 268:
Figure 11-9 shows that the average
- Page 269 and 270:
The SAP BI Accelerator with DB2 for
- Page 271 and 272:
After a successful run of the tool,
- Page 273 and 274:
Chapter 12. Concepts, activities, a
- Page 275 and 276:
► SAP compression This refers to
- Page 277 and 278:
where requested data is saved uncha
- Page 279 and 280:
All of these data differences requi
- Page 281 and 282:
12.5 Hierarchies SAP BI allows the
- Page 283 and 284:
SID Table SID Table SID Table An In
- Page 285 and 286:
12.7 Data load into InfoCube When d
- Page 287 and 288:
12.8.1 Aggregate example The conten
- Page 289 and 290:
Activating and filling In order to
- Page 291 and 292:
12.9 Compression of requests Data i
- Page 293 and 294:
The DSO objects can store the data
- Page 295 and 296:
Name Type Description /BIx/E Table
- Page 297 and 298:
Business Explorer SAP BW Server Sou
- Page 299 and 300:
Appendix A. Glossary for SAP BI A I
- Page 301 and 302:
aggregation level Selection of char
- Page 303 and 304:
asic characteristic and the target
- Page 305 and 306:
BI Java Connector One of a set of f
- Page 307 and 308:
oadcasting wizard Assistant that su
- Page 309 and 310:
BI Metadata Repository Manager Tool
- Page 311 and 312:
comparison column A write-protected
- Page 313 and 314:
supported by the data source, a hie
- Page 315 and 316:
member can be unique (it occurs onl
- Page 317 and 318:
Planning profiles are used to only
- Page 319 and 320:
Two query models are provided by th
- Page 321 and 322:
ResultSet API A set of interfaces t
- Page 323 and 324:
which contain a reference to planni
- Page 325 and 326:
tabular reporting Reporting based o
- Page 327 and 328:
Table A set of rows, also known as
- Page 329 and 330:
You want to structure the header se
- Page 331 and 332:
XML metadata interchange XML-based
- Page 333 and 334:
B Appendix B. SAP BI installation a
- Page 335 and 336:
SAP application servers ran on AIX
- Page 337 and 338:
Figure B-2 shows how the GUI SAPCL
- Page 339 and 340:
Appendix C. SAP BW OSS Notes This a
- Page 341 and 342:
General notes for SAP BI 935815 Que
- Page 343 and 344:
D Appendix D. Project Jupiter: eval
- Page 345 and 346:
DEVICE CU0B1080 MPCIPA LINK P17E18
- Page 347 and 348:
129.40.28.0 129.40.28.10 UHSb 0 0 e
- Page 349 and 350:
Table name Average row length Total
- Page 351 and 352:
Tables D-2 through D-5 show the set
- Page 353 and 354:
drwxr-xr-x 108 t11adm sapsys 4096 2
- Page 355 and 356:
Figure D-1 shows TREX Admin setting
- Page 357 and 358:
drwxr-xr-x 4 t11adm sapsys 2048 200
- Page 359 and 360:
BIC/NUMBER14 69 DECIMAL 17 3 N 4 N
- Page 361 and 362:
-rw-r--r-- 1 t11adm sapsys 2181036
- Page 363 and 364:
-rw-r--r-- 1 t11adm sapsys 36098 20
- Page 365 and 366:
Related publications IBM Redbooks T
- Page 367 and 368:
Help from IBM IBM Support and downl
- Page 369 and 370:
Index A ABAP Dictionary 115 access
- Page 371 and 372:
same record 98 Shortens RUNSTATS pr
- Page 373 and 374:
PSA record 267 attribute values 267
- Page 375 and 376:
Best Practices for SAP BI using DB2
- Page 378:
Best Practices for SAP BI using DB2