Oracle Application Express Schema Design Guidelines Presenter: Flavio Casetta, Yocoya.com

Transcription

1 Oracle Application Express Schema Design Guidelines Presenter: Flavio Casetta, Yocoya.com

2 about me Flavio Casetta Founder of Yocoya.com Editor of blog OracleQuirks.blogspot.com 25+ years in the IT 10+ years developing applications on Oracle 15+ years developing database applications apex developer since htmldb 1.5

3 goals summary db objects mapping to apex components tables, views, indexes performance packages vs standalone procedures snapshots or cached reports? synonyms and db links Q&A June 24, 2009 Flavio Casetta - 3

4 goals June 24, 2009 Flavio Casetta - 4

5 the goals of every apex developer should be to build fast, scalable applications that are easy to use, deploy and maintain to avoid reinventing the wheel goals to avoid writing the same code over and over again the aim of this presentation is to stress the importance of proper database design as a strong foundation for your apex applications June 24, 2009 Flavio Casetta - 5

6 db objects mapping to apex components June 24, 2009 Flavio Casetta - 6

7 June 24, 2009 Flavio Casetta mapping

8 tables, views, indexes June 24, 2009 Flavio Casetta - 8

9 tables, views, indexes oracle provides different types of tables tailored for different situations standard heap tables index organized tables aka IOTs cluster tables temporary tables external tables oracle EE allows table partitioning June 24, 2009 Flavio Casetta - 9

10 tables, views, indexes apex's table builder wizard creates only heap tables June 24, 2009 Flavio Casetta

11 tables, views, indexes SQL Developer's table builder instead comes with advanced options June 24, 2009 Flavio Casetta

12 tables, views, indexes heap tables are best for data that grows over time. The developer must properly design indexes for improving data access. when evaluating the indexes to be created, consider that any column(s) declared as foreign key(s) should be indexed in order to avoid contention if using oracle EE, consider using bitmap indexes for columns containing few distinct values on large tables with low transactional activity (like fact tables in a DW) June 24, 2009 Flavio Casetta

13 tables, views, indexes IOTs are best for tables accessed by primary key and with low transactional activity. often reports and page items need to display a description starting from a foreign key value (which is the primary key of the IOT) unlike ordinary indexes, the primary key of an IOT cannot be rebuilt online June 24, 2009 Flavio Casetta

14 tables, views, indexes cluster tables come in two forms: index clusters hash clusters clusters improve I/O by storing data together cluster tables pre-join tables index clusters require two logical reads hash clusters require one logical read hash clusters are best for very static data hash clusters need precise sizing information June 24, 2009 Flavio Casetta

15 tables, views, indexes external tables are useful when importing data from texts file stored in a directory on the same database server if deploying an application on a multi-tenant hosting server, you might have no access to local folders finding the right format for an external table can be challenging. Certain combinations of parameters may introduce erratic behavior June 24, 2009 Flavio Casetta

16 tables, views, indexes temporary tables are good for volatile data. There are two types of GTTs and they differ in scope: transaction (on commit delete rows) oracle session (on commit preserve rows) given the nature of apex architecture, usage of temporary tables is limited to operations that begin and end within the same transaction practical uses: reporting on data returned by a procedure June 24, 2009 Flavio Casetta

17 tables, views, indexes views are meant to simplify the work of a developer by: hiding complex expressions or joins that would make a query difficult to deal with enforcing data access rules, i.e. to limit the results to data relevant to a certain user decoding values to human understandable language June 24, 2009 Flavio Casetta

18 tables, views, indexes in apex, views are great for: reporting (user defined views) checking apex metadata (APEX_XXX) checking db dictionary (USER_XXX, ALL_XXX and a few V$ dynamic views) checking certain features like oracle text metadata and values (CTX_XXX views) June 24, 2009 Flavio Casetta

19 performance June 24, 2009 Flavio Casetta

20 performance tools for analyzing the performance of an apex page: monitor activity reports apex page debug mode explain plan trace files & TKPROF June 24, 2009 Flavio Casetta

21 performance Monitor activity report Page Views by Weighted Page Performance Page Views by Application and Page June 24, 2009 Flavio Casetta

22 performance page views by weighted page performance June 24, 2009 Flavio Casetta

23 performance apex page debug mode: turn on debug by clicking on the debug link in the developer's toolbar of apex (restrictions apply) enter debug mode by adding YES as fifth parameter in the apex URL in all cases debug mode must be enabled June 24, 2009 Flavio Casetta

24 performance inspect debug output and spot elapsed time anomalies June 24, 2009 Flavio Casetta

25 performance the most likely candidates for big delays in page rendering are non-optimized queries June 24, 2009 Flavio Casetta

26 performance the next step is to check what's wrong with the query by using explain plan statistics must be up-to-date June 24, 2009 Flavio Casetta

27 performance the full table scan indicates that we are missing an index as the query references three columns, the most effective index will contain those three columns the order of the columns in the index is important the analysys is carried out entirely using apex features June 24, 2009 Flavio Casetta

28 performance After creating the index, the cost has decreased dramatically June 24, 2009 Flavio Casetta

29 performance this is confirmed by the time elapsed recorded in the debug output June 24, 2009 Flavio Casetta

30 performance additional considerations about the index: i created a compressed index, consuming fewer blocks the table is 100% static, so i set PCTFREE=0, saving even more blocks The difference in the number of blocks between the index created with default parameters and its extreme version is down 44% June 24, 2009 Flavio Casetta

31 performance index options comparison June 24, 2009 Flavio Casetta

32 performance example of query involving a single table hash cluster containing half million rows June 24, 2009 Flavio Casetta

33 performance explain plan of the query on single table hash cluster June 24, 2009 Flavio Casetta

34 performance what was the difference the day after? June 24, 2009 Flavio Casetta

35 performance when the previously mentioned techniques are not enough, tracing can be enabled instrumenting the code in the right way can be a life safer if properly designed, code instrumentation can be enabled selectively, with minimal impact when it is not in use and without collecting unnecessary information June 24, 2009 Flavio Casetta

36 performance enabling oracle tracing is easy: tracing makes sense only if you have access to folders on the database server (on a multi-tenant hosting service this type of action might have been restricted by the DBA) June 24, 2009 Flavio Casetta

37 performance depending on apex's configuration (either using embedded PL/SQL gateway as Oracle XE or Apache HTTP server, trace files will be found in either in the background_dump_dest folder or in user_dump_dest for shared servers trace file name pattern is sid_snnn_pid.trc for dedicated sessions the trace file name pattern is sid_proc_pid_[tracefile_identifier].trc user_dump_dest and tracefile_identifier parameters don't apply for shared servers June 24, 2009 Flavio Casetta

38 performance in order to spot the relevant SQL statements quickly, you can embed comments containing custom identifiers: select /* my_app LOV_EMP */ emp_name d, emp_id r from employees update order_items /* my_app my_page_num process xyz */ set qty = :P45_QTY where order_id = :P45_ORDER_ID June 24, 2009 Flavio Casetta

39 PL/SQL and apex June 24, 2009 Flavio Casetta

40 pl/sql apex make's possible to write an application without entering a single line of PL/SQL Functionalities that don't come off-the-shelf may require a little or a lot of custom PL/SQL The developer must be aware of pros and cons when adopting a method for executing PL/SQL June 24, 2009 Flavio Casetta

41 pl/sql PL/SQL can be used in many places Processes & Computations Validations & conditions Post calculation, item source & initialization Report queries & report headings Dynamic LOVs PL/SQL regions Authentication functions & authorization schemes Shortcuts Supporting Objects June 24, 2009 Flavio Casetta

42 pl/sql Given the potential ubiquity of PL/SQL inside apex components, the developer must choose how to handle this source code: as anonymous blocks as standalone procedures or functions as packaged procedures or functions June 24, 2009 Flavio Casetta

43 pl/sql anonymous blocks are the most straightforward method to execute pl/sql more difficult to maintain or keep track of in case of an exception the source is exposed source code cannot be obfuscated editable only inside apex June 24, 2009 Flavio Casetta

44 pl/sql standalone procedures or functions can be reasonable if their number is low source code can be obfuscated editable inside apex or with other sql clients potentially they are reusable potentially they can interfere with existing objects if installed in a preexisting schema version management is harder than with packages June 24, 2009 Flavio Casetta

45 pl/sql packages are the way to go for large efforts source code can be obfuscated editable inside apex or with other sql clients packages are potentially reusable less prone to conflicts with existing objects if installed in a preexisting schema version management is easier than with standalone procedure and functions June 24, 2009 Flavio Casetta

46 pl/sql reusable procedures and functions are the best candidates for inclusion in packages: logging procedures black list filtering general purpose utilities (the swiss-knife of each developer) page formatting utilities like HTF/HTP for different web languages June 24, 2009 Flavio Casetta

47 snapshots or cached reports? June 24, 2009 Flavio Casetta

48 snapshots or cache snapshots aka materialized views can save considerable resources they can be combined with cached report regions to achieve top performance snapshots come in handy when: you need to query a column resulting from a combination of multiple columns you need to quickly return aggregated results (sums, averages, etc.) June 24, 2009 Flavio Casetta

49 snapshots or cache weighted page performance (4 wks) June 24, 2009 Flavio Casetta

50 snapshots or cache weighted page performance (2 wks) June 24, 2009 Flavio Casetta

51 snapshots or cache the significant difference was achieved by removing a cached region from page zero caching is not supported in page zero (a fact not mentioned in the manual or help, but mentioned in the output log in page debug mode ) without snapshots, upon expiration of the region cache, page rendering will incur in a significant increase of response time this occurrence can be eliminated by creating a snapshot updated in background June 24, 2009 Flavio Casetta

52 synonyms and db links June 24, 2009 Flavio Casetta

53 synonyms and db links the main reason for using synonyms is to make transparent to the application where the data come from a synonym can point to an object: in the same schema in another schema in a remote database (through a db-link) the type of target object can be decided during the installation for instance June 24, 2009 Flavio Casetta

54 synonyms and db links developing an application basing on synonyms can be tricky apex does not list public synonyms in wizards it can be more productive to develop using local objects that are later replaced by corresponding synonyms typical situations are forms on tables, tabular forms and the query builder June 24, 2009 Flavio Casetta

55 synonyms and db links another typical usage for public synonyms in apex is to make procedures callable by anonymous users from the URL creating a public synonym for RPC calls simplifies the URL syntax: for security reasons the synonym must also be registered in procedure wwv_flow_epg_include_mod_local June 24, 2009 Flavio Casetta

56 Q&A session June 24, 2009 Flavio Casetta