Getting Started with IBM Data Studio for DB2

More documents

Recommendations

Info

320 Getting Started with IBM Data Studio for DB2 Developers can spend considerable time isolating performance issues: first to a specific SQL statement, then to the source application, then to the originating code. Three-tier architectures and popular frameworks make this isolation more difficult as the developer may never see the SQL generated by the framework. Data Studio makes it easier to isolate problems by providing an outline that traces SQL statements back to the originating line in the source application, even when using Java frameworks like Hibernate, OpenJPA, Spring, and others. Be sure to read the Getting Started with pureQuery book of this series to read about the capabilities of Data Studio and pureQuery Runtime. 11.2.3 Develop and Optimize: InfoSphere Optim Query Workload Tuner InfoSphere Optim Query Workload Tuner is focused on enabling developers to tune queries and query workloads by providing them with advice on how to achieve better query performance [2]. See Figure 11.5 for a screenshot. Figure 11.5 – InfoSphere Optim Query Workload Tuner provides help for tuning queries and workloads InfoSphere Optim Query Workload Tuner provides advice for statistics, queries, access paths, and indexes. As you learned in Chapter 7, the tabs along the left side help step you through tuning steps, and the tool can format the queries for easy reading and include associated cost information, an access plan graph, access plan explorer, and access plan comparison.
Chapter 10 – Developing data web services 321 InfoSphere Optim Query Workload Tuner can provide either single query analysis and advice , but can take as input an entire SQL workload (such as all SQL used in an order processing application) as input, which enables database administrators to determine for example what indexes or what statistics might provide the most benefit for the overall performance of the workload. 11.2.4 Deploy and Operate: Data Studio, InfoSphere Optim Configuration Manager, and DB2 Advanced Recovery Solution Managing availability is often job number one for database administrators. When your database goes down and the data is unavailable to the end users, it can look bad for you and your organization. If you’re supporting a business, that can have a direct impact on the bottom line. Data Studio, as you have learned in this book, provides all the basic database administration capabilities required for managing a DB2 deployment. However, when managing many deployments, more capability is desirable to manage, synchronize, and govern configuration across hundreds of databases. InfoSphere Optim Configuration Manager discovers databases, clients, and their relationships and tracks configuration changes across them. It assists with application upgrades to determine that all clients have been changed correctly, and lets organizations quickly visualize and report on inventory and configuration changes. Such changes can also be correlated to performance degradation via contextual links in InfoSphere Optim Performance Manager, see section 11.2.5 for more information. DB2 Advanced Recovery Solution is focused on reducing time to recover by aligning backup strategies with outage related Service Level Agreements providing faster methods to recovery and is comprised of the following: • InfoSphere Optim High Performance Unload provides a high-speed unload utility as an alternative to the DB2 export feature. This product significantly reduces the time required to migrate databases, manage within batch windows, capture data for test environments, and move data without impacting production systems. Because unloads are so fast, you can use this as a means for migration, moving large amounts of data from one system to another or for backup. The product is fast because it can o go directly to the data files, bypassing the database manager altogether. The tool does not interfere with or slow down production databases or impact CPU resources as it is completely outside of the database. It can also perform unloads from multiple database partitions, and it provides repartitioning capability in a single step for rapid data redistribution on the same or different system. This is particularly useful in warehouse environments where repartitioning can be very much a manual process. • DB2 Merge Backup lets you avoid full database backups by merging incremental and delta backups into a full backup. Thus, it reduces resource requirements to maintain a full backup for large databases and it shortens recovery times on production servers ensuring full backups are always available when needed.
Page 1 and 2:
]
Page 3 and 4:
3 Notices This information was deve
Page 5 and 6:
Table of contents 5 Table of conten
Page 7 and 8:
3.3.1 Exporting data...............
Page 9 and 10:
Chapter 7 - Tuning queries ........
Page 11 and 12:
11.4 Community and resources ......
Page 13 and 14:
Preface 13 Keeping your skills curr
Page 15 and 16:
around the world have participated
Page 17 and 18:
17 About the authors Dimple Bhatia
Page 19 and 20:
Contributors 19 The following peopl
Page 21:
21 Acknowledgements The authors owe
Page 24 and 25:
24 Getting Started with IBM Data St
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Getting Started with IBM Data S
Page 103 and 104:
103 Chapter 3 - Maintaining the dat
Page 105 and 106:
Chapter 3 - Maintaining the databas
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Figure 3.35 - Selecting additional
Page 135 and 136:
Page 137:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 159 and 160:
159 Chapter 5 - Creating SQL and XQ
Page 161 and 162:
Chapter 5 - Creating SQL and XQuery
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
On Success On Error Result Chapter
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
193 Chapter 6 - Managing jobs Job m
Page 195 and 196:
Chapter 6 - Managing jobs 195 6.3 J
Page 197 and 198:
Chapter 6 - Managing jobs 197 6.4 C
Page 199 and 200:
Chapter 6 - Managing jobs 199 Figur
Page 201 and 202:
Chapter 6 - Managing jobs 201 Comp
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Chapter 6 - Managing jobs 207 6.5 R
Page 209 and 210:
Chapter 6 - Managing jobs 209 6.6.2
Page 211 and 212:
Page 213 and 214:
213 Chapter 7 - Tuning queries In t
Page 215 and 216:
Chapter 7 - Tuning queries 215 Figu
Page 217 and 218:
Chapter 7 - Tuning queries 217 You
Page 219 and 220:
Chapter 7 - Tuning queries 219 •
Page 221 and 222:
Page 223 and 224:
7.4.2 Run the Statistics Advisor an
Page 225 and 226:
Chapter 7 - Tuning queries 225 7.4.
Page 227 and 228:
Chapter 7 - Tuning queries 227 For
Page 229 and 230:
Page 231 and 232:
Chapter 7 - Tuning queries 231 To s
Page 233 and 234:
Chapter 7 - Tuning queries 233 3. O
Page 235 and 236:
Chapter 7 - Tuning queries 235 7.6
Page 237 and 238:
237 Chapter 8 - Developing SQL stor
Page 239 and 240:
Chapter 8 - Developing SQL stored p
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271: 270 Getting Started with IBM Data S
Page 355 and 356: 355 Appendix D - The Sample Outdoor
Page 357 and 358: Appendix D - The Sample Outdoor Com
Page 363 and 364: Appendix E - Advanced topics for de
Page 371 and 372:
Appendix E - Advanced topics for de
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
E.5.4 Data web services artifacts A
Page 391 and 392:
References 391 References [1] HAYES
Page 393 and 394:
References 393 Books and articles 1
Page 396:
396 Getting started with IBM Data S
show all

Getting Started with IBM Data Studio for DB2

Create successful ePaper yourself

Delete template?

Save as template?