Getting Startedwith pureQuery

More documents

Recommendations

Info

164 Getting Started with pureQuery • pureQueryXml package name and statement entry id • Information about the call stack of the statement at the time the metadata was created (when the SQL was captured) This information, when provided to the application developer, can be used to jump-start problem resolution for monitored applications associated with pureQueryXml. 8.5 Summary Extended Insight provides visibility into, and knowledge about, the application stack that was previously unavailable to DBAs and others trying to monitor and troubleshoot multitiered, data access applications. It provides the ability to pinpoint specific java applications as they are running, regardless of whether they are executing statically or dynamically. For each identified, client-monitored workload, result set processing time, driver time, network time, and server time, along with a variety of additional metrics, can be examined for any group of transactions or statements. This allows the application-centric DBA to identify, rule out, and pinpoint problems anywhere in the data access application stack, not only within the database. Importantly, pureQuery monitoring can increase visibility into the data access stack for existing applications, running in existing frameworks, without changing application code. pureQuery applications with pureQueryXml registered with Optim Performance Manager benefit from the deepest problem determination support, and plain JDBC or CLI applications also benefit from increased visibility through Extended Insight. When pureQuery application metadata is registered with Optim Performance Manager, the monitor can identify the issuing pureQuery application for many pureQuery-issued SQL statements, down to the specific application source line or the specific capture snapshot, reducing resolution and fix time. Extended Insight provides a previously missing link across the persistence layer and data access frameworks. It fits seamlessly between existing application monitor coverage zones and traditional application and database monitoring tools, to monitor currently obscured layers of the data access stack, reducing problem determination time and increasing monitoring effectiveness. 8.6 Review Questions 1. What are some common problems faced by DBA’s in a multi-tiered environment? 2. What is a native pureQuery application? 3. True or false: Extended Insight integrates seamlessly with database-centric monitor data? 4. What is the necessary step required before pureQuery application metadata is useful to the DBA performing monitoring activities?
Chapter 8 – Extended Insight 165 5. Which stack layers does Extended Insight provide new monitoring statistics for? 6. Which of the following products is installed on the application server to deliver client monitoring capabilities? A. Data Studio B. Optim Development Studio C. Optim Performance Manager (OPM) Extended Insight 7. Which of the following pieces of monitoring information is available for native pureQuery applications whose metadata is registered with OPM? A. Source class name B. Source timestamp (version) C. Source code line number D. All of the above 8. Which of the following is NOT a benefit of client monitoring: A. Decrease problem determination time B. Correlate monitored SQL statements with originating line of Java source code C. .NET visual development D. Provide insight into previously obscured layers of the data access stack 9. Which types of applications can be monitored using pureQuery client monitoring? A. plain JDBC or CLI applications B. native pureQuery applications C. pureQuery client optimized applications D. All of the above 10. How does OPM correlate an SQL statement with its source application? A. Using registered pureQuery application metadata B. String matching C. Scanning the source code repository D. It doesn’t
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7:
Trademarks IBM, the IBM logo, DB2,
Page 10 and 11:
10 Getting Started with pureQuery 3
Page 12 and 13:
12 Getting Started with pureQuery C
Page 14 and 15:
Page 16 and 17:
16 Getting Started with pureQuery C
Page 18 and 19:
18 Getting Started with pureQuery m
Page 20 and 21:
20 Getting Started with pureQuery T
Page 22 and 23:
22 Getting Started with pureQuery K
Page 24 and 25:
24 Getting Started with pureQuery A
Page 27 and 28:
1 Chapter 1 - Introduction to pureQ
Page 29 and 30:
Chapter 1 - Introduction to pureQue
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
2 Chapter 2 - Installing pureQuery
Page 47 and 48:
Chapter 2 - Installing pureQuery (O
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61:
PART II - TOOLING
Page 66 and 67:
66 Getting Started with pureQuery F
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
72 Getting Started with pureQuery t
Page 74 and 75:
74 Getting Started with pureQuery A
Page 76 and 77:
76 Getting Started with pureQuery T
Page 78 and 79:
78 Getting Started with pureQuery a
Page 80 and 81:
80 Getting Started with pureQuery r
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
86 Getting Started with pureQuery Y
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
92 Getting Started with pureQuery D
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
98 Getting Started with pureQuery
Page 100 and 101:
Page 102 and 103:
Page 105 and 106:
PART III - SECURITY, PERFORMANCE, A
Page 107 and 108:
6 Chapter 6 - The Client Optimizer:
Page 109 and 110:
Chapter 6 - The Client Optimizer: p
Page 111 and 112:
Chapter 6 - The Client Optimizer: p
Page 113 and 114: Chapter 6 - The Client Optimizer: p
Page 137 and 138: 7 Chapter 7 - The StaticBinder Util
Page 139 and 140: Chapter 8 - Extended Insight 139 No
Page 141 and 142: 7.2.2.3 Changes to pureQueryXml fil
Page 143 and 144: Chapter 8 - Extended Insight 143 Fi
Page 145 and 146: Chapter 8 - Extended Insight 145 Fi
Page 147 and 148: Chapter 8 - Extended Insight 147 -u
Page 149 and 150: Chapter 8 - Extended Insight 149 7.
Page 151 and 152: Chapter 8 - Extended Insight 151 ne
Page 153: Chapter 8 - Extended Insight 153 11
Page 156 and 157: 156 Getting Started with pureQuery
Page 169 and 170: 9 Chapter 9 - Persistence Framework
Page 171 and 172: 9.1.1.1 JPA Chapter 9 - Persistence
Page 173 and 174: Chapter 9 - Persistence Frameworks
Page 181: Chapter 9 - Persistence Frameworks
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 243 and 244:
12 Chapter 12 - Stored Procedures T
Page 245 and 246:
Chapter 12 - Stored Procedures 245
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:
13 Chapter 13 - Handlers In this ch
Page 263 and 264:
Chapter 13 - Handlers 263 Figure 13
Page 265 and 266:
Chapter 13 - Handlers 265 SELECT *
Page 267 and 268:
Chapter 13 - Handlers 267 construct
Page 269 and 270:
13.4.1 Writing a ResultHandler impl
Page 271 and 272:
Chapter 13 - Handlers 271 functiona
Page 273 and 274:
Chapter 13 - Handlers 273 Listing 1
Page 275 and 276:
Chapter 13 - Handlers 275 package h
Page 277:
A. In a getData method in the com.i
Page 281 and 282:
14 Chapter 14 - Best Practices In t
Page 283 and 284:
Chapter 14 - Best Practices 283 @Se
Page 285 and 286:
Chapter 14 - Best Practices 285 Fig
Page 287 and 288:
15 Chapter 15 - pureQuery and pureX
Page 289 and 290:
Chapter 15 - pureQuery and pureXML
Page 291 and 292:
Page 293:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 305 and 306:
A Appendix A - Solutions to the rev
Page 307 and 308:
Appendix A - Solutions to the revie
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
B Appendix B - Understanding the Sa
Page 315 and 316:
B.1.3 The “Employee Information
Page 317 and 318:
Appendix C - Up and Running with DB
Page 319 and 320:
B.1.6 The “Company Employees” s
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
C.4.1 IBM Optim Development Studio
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 355 and 356:
E Appendix E - Options Files This a
Page 357 and 358:
Appendix E - Options files 357 comm
Page 359:
Appendix E - Options files 359 In b
Page 363 and 364:
Resources Web sites 1. pureQuery pl
show all

Getting Startedwith pureQuery

Create successful ePaper yourself

Delete template?

Save as template?