Getting Startedwith pureQuery

More documents

Recommendations

Info

108 Getting Started with pureQuery Captured-only SQL: You can use the Client Optimizer’s “captured-only” feature to restrict the SQL statements that an application can execute to those in a whitelist that you approve, even if the SQL statements execute dynamically. This can help you to improve the security of any application. This is particularly useful in environments that do not offer static SQL. SQL Replacement: Using the Client Optimizer for an existing JDBC application makes it easy to substitute executed SQL with optimized equivalent SQL. This can help you to leverage the DBA skills in your organization to optimize SQL statements that are performing poorly, without modifying the application. SQL Literal Substitution: The SQL Literal Substitution feature allows you to convert nonparameterized SQL statements that your application executes into parameterized SQL statements. This feature is particularly useful for applications that generate SQL statements during runtime. SQL Literal substitution can enable you to use static SQL, captured-only SQL, or both for applications that generate non-parameterized SQL statements. Additionally, for SQL statements that execute dynamically, it can reduce the total number of SQL statements in the cache, thereby increasing the cache-hit rate for statements. Locating SQL Statements: The Client Optimizer helps you to identify quickly which parts of your application execute particular SQL statements. When your application executes SQL statements, the Client Optimizer can record stack traces that indicate which part of your application executed the statements. In addition to the enhancements that you can make to your application using the Client Optimizer, you can leverage the integration between the Client Optimizer and the pureQuery tooling in IBM Optim Development Studio to easily analyze and improve the SQL statements in your existing applications. Using the Client Optimizer for existing JDBC applications also increases the amount of information that is available about the SQL statements that your application executes, if you use the Extended Insight feature (See Chapter 11 for more details). 6.2 Overview of how to use the Client Optimizer You must follow four basic steps to using the Client Optimizer to optimize a JDBC application. All of the steps deal with a particular type of file, called a pureQueryXml file, which describes the SQL statements in the application. The extension of a pureQueryXml file must be either .pdqxml or .xml. In the first and fourth step, properties known as pureQuery properties determine the behavior. 1. Capture: Direct pureQuery to capture the SQL statements from your application into a pureQueryXml file. Figure 6.2 shows pureQuery creating a pureQueryXml file containing the SQL statements that your applications executes. A
Chapter 6 – The Client Optimizer: pureQuery for Existing Applications 109 pureQueryXml file that pureQuery’s capture functionality creates is called a capture file. Capture pureQuery Properties: pdq.captureMode=ON Database JDBC Application Run SQL Statement pureQuery Capture Execute Dynamic Statement Cache pureQueryXml File Figure 6.2 - During capture, the Client Optimizer captures SQL statements that your application executes into a pureQueryXml file. 2. Configure: Process the pureQueryXml file with the Configure utility. This simple procedure prepares the file so that the SQL statements in it can be bound in the database, and so that pureQuery can reference the statements in the file during the execution of the application. If you are using IBM Optim Development Studio, the tooling runs the Configure utility automatically. Figure 6.3 shows the Configure utility configuring a pureQueryXml file. Configure pureQueryXml File pureQuery Configure Utility Configure Configured pureQueryXml File Figure 6.3 - The Configure utility prepares a pureQueryXml file for use in binding and execution. 3. Bind: If you intend to use static SQL, use the StaticBinder utility to bind the SQL statements that are in the pureQueryXml file into packages in the database. If you do not intend to use static SQL, you can skip this step. Figure 6.4 shows the StaticBinder utility binding packages of SQL statements in the database.
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:
14 Getting Started with pureQuery 1
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: Chapter 2 - Installing pureQuery (O
Page 59 and 60: Chapter 2 - Installing pureQuery (O
Page 61: PART II - TOOLING
Page 66 and 67: 66 Getting Started with pureQuery F
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 84 and 85: 84 Getting Started with pureQuery 4
Page 86 and 87: 86 Getting Started with pureQuery Y
Page 92 and 93: 92 Getting Started with pureQuery D
Page 98 and 99: 98 Getting Started with pureQuery
Page 105 and 106: PART III - SECURITY, PERFORMANCE, A
Page 107: 6 Chapter 6 - The Client Optimizer:
Page 111 and 112: 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 158 and 159:
158 Getting Started with pureQuery
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
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 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
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?