In general, you
should favor using SIMILAR over FORCE, because SIMILAR will allow for a new execution plan
to be generated reflecting any histogram data known about the literal value.
Setting CURSOR_SHARING to EXACT (the default setting) reuses previously parsed commands
only when the literal values are identical.
To use stored outlines with CURSOR_SHARING set to FORCE or SIMILAR, the outlines must
have been generated with that CURSOR_SHARING setting in effect.
NOTE
Dynamic SQL commands are always parsed, essentially bypassing the
value of the shared SQL area.
Managing Package Development
Imagine a development environment with the following characteristics:
None of your standards are enforced.
Objects are created under the SYS or SYSTEM account.
Proper distribution and sizing of tables and indexes is only lightly considered.
Every application is designed as if it were the only application you intend to run in your
database.
As undesirable as these conditions are, they are occasionally encountered during the
implementation of purchased packaged applications. Properly managing the implementation
of packages involves many of the same issues that were described for the application development
processes in the previous sections. This section will provide an overview of how packages should
be treated so they will best fit with your development environment.
Generating Diagrams
Most CASE tools have the ability to reverse-engineer packages into a physical database diagram.
Pages:
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295