Explore >> Select a destination
|
You are here 
|
jonathanlewis.wordpress.com | ||
| | | | |
tanelpoder.com
|
|
| | | | | On Exadata (or when setting cell_offload_plan_display = always on non-Exadata) you may see the storage() predicate in addition to the usual access() and filter() predicates in an execution plan: SQL> SELECT * FROM dual WHERE dummy = 'X'; D - X Check the plan: SQL> @x Display execution plan for last statement for this session from library cache... PLAN_TABLE_OUTPUT ------------------------------------------------------------------------------------------------------------------------ SQL_ID dtjs9v7q7zj1g, child number 0 ------------------------------------- SELECT * FROM dual WHERE dummy = 'X' Plan hash value: 272002086 ------------------------------------------------------------------------ | Id | Operation | Name | E-Rows |E-Bytes| Cost (%CPU)| ------------------------------------------------------------------------ | 0 | SELECT STATEMENT | | | | 2 (100)| |* 1 | TABLE ACCESS STORAGE FULL| DUAL | 1 | 2 | 2 (0)| ------------------------------------------------------------------------ Predicate Information (identified by operation id): --------------------------------------------------- 1 - storage("DUMMY"='X') filter("DUMMY"='X') The access() and filter() predicates come from the corresponding ACCESS_PREDICATES and FILTER_PREDICATES columns in V$SQL_PLAN. But there's no STORAGE_PREDICATES column there! - Linux, Oracle, SQL performance tuning and troubleshooting - consulting & training. | |
| | | | |
iusoltsev.wordpress.com
|
|
| | | | | ??????? ?????? ?? ??????? ??????????? 465 ??????! SELECT A.ID, A.LOGIN, A.NAME, A.LASTNAME, A.EMAIL FROM ACCOUNT A WHERE (A.LOGIN LIKE '%%') AND (A.NAME LIKE '%????????%' OR A.LASTNAME LIKE '%????????%') AND A.COMPANY_ID = 1 ORDER BY A.LOGIN ??? ???????, ????????? ???? ?? ??????? A.COMPANY_ID = 1 ???????? ??????? ???????????????? SQL> SELECT 'ALL' as "Condition", count(*) FROM ACCOUNT... | |
| | | | |
tonyhasler.wordpress.com
|
|
| | | | | When a table is accessed by multiple members of a parallel query server set, the execution plan may show the use of block range granules (PX BLOCK ITERATOR) or partition granules (PX PARTITION [RANGE|LIST|HASH] ITERATOR or PX PARTITION [RANGE|LIST|HASH] ALL). The basic ideas surrounding these concepts are discussed in numerous blogs and books, including my... | |
| | | | |
www.spiezz.com
|
|
| | | Helping small businesses make more money by connecting them with the right customers though websites creation SEO & Conversion Strategies, and Video Ads. | ||
