32个字节限制Oracle直方图优化
Oracle直方图的限制往往让不少初学者头痛mdash;mdash;超过32字节不显示,以及前32字节相同产生错误。由于OBJECT_TYPE列上的DIS
Oracle直方图的限制往往让不少初学者头痛——超过32字节不显示,以及前32字节相同产生错误。
由于OBJECT_TYPE列上的DISTINCT值的个数小于254,ORACLE将会在此列上建立频率直方图,优化器将会准确的估算出CONTENTS='TABLE'的查询返回37条记录。
下面看看如下的情况:
SQL> TRUNCATE TABLE T;
Table truncated.
SQL> SET AUTOT OFF
SQL> INSERT INTO T
2 SELECT ROWNUM,OBJECT_NAME,RPAD('*',32,'*')||OBJECT_TYPE
3 FROM ALL_OBJECTS WHERE ROWNUM
10000 rows created.
SQL> COMMIT;
Commit complete.
SQL> SELECT COUNT(1) FROM T;
COUNT(1)
----------
10000
SQL> SELECT CONTENTS ,COUNT(1) FROM T GROUP BY CONTENTS ;
CONTENTS COUNT(1)
-------------------------------------------------- ----------
********************************SEQUENCE 1
********************************LIBRARY 3
********************************WINDOW GROUP 1
********************************INDEX PARTITION 347
********************************PACKAGE 164
********************************SCHEDULE 1
********************************TABLE PARTITION 25
********************************VIEW 1150
********************************TABLE 37
********************************PROCEDURE 11
********************************CONSUMER GROUP 2
********************************INDEX SUBPARTITION 3328
********************************OPERATOR 15
********************************WINDOW 2
********************************INDEX 34
********************************FUNCTION 60
********************************SYNONYM 2552
********************************TABLE SUBPARTITION 1714
********************************TYPE 538
********************************JOB CLASS 1
********************************PACKAGE BODY 13
********************************EVALUATION CONTEXT 1
22 rows selected.
SQL> EXEC DBMS_STATS.GATHER_TABLE_STATS(USER,'T',method_opt=>'FOR COLUMNS CONTENTS SIZE 254');
PL/SQL procedure successfully completed.
SQL> SELECT * FROM T WHERE CONTENTS='********************************TABLE';
Execution Plan
----------------------------------------------------------
Plan hash value: 2153619298
--------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
--------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 10000 | 654K| 24 (0)| 00:00:01 |
|* 1 | TABLE ACCESS FULL| T | 10000 | 654K| 24 (0)| 00:00:01 |
--------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
1 - filter("CONTENTS"='********************************TABLE')
由于CONTENTS列的前32位都一样,ORACLE在收集统计信息直方图的时候只考虑前32位,这会导致ORACLE认为
所有的记录的列CONTENTS都是相同的,因此优化器估算返回的行数为10000。
SQL> UPDATE T SET CONTENTS=SUBSTR(CONTENTS,2);
10000 rows updated.
SQL> COMMIT;
Commit complete.
SQL> EXEC DBMS_STATS.GATHER_TABLE_STATS(USER,'T',method_opt=>'FOR COLUMNS CONTENTS SIZE 254');
PL/SQL procedure successfully completed.
SQL> SELECT CONTENTS ,COUNT(1) FROM T GROUP BY CONTENTS ORDER BY 1;
CONTENTS COUNT(1)
-------------------------------------------------- ----------
*******************************CONSUMER GROUP 2
*******************************EVALUATION CONTEXT 1
*******************************FUNCTION 60
*******************************INDEX 34
*******************************INDEX PARTITION 347
*******************************INDEX SUBPARTITION 3328
*******************************JOB CLASS 1
*******************************LIBRARY 3
*******************************OPERATOR 15
*******************************PACKAGE 164
*******************************PACKAGE BODY 13
*******************************PROCEDURE 11
*******************************SCHEDULE 1
*******************************SEQUENCE 1
*******************************SYNONYM 2552
*******************************TABLE 37
*******************************TABLE PARTITION 25
*******************************TABLE SUBPARTITION 1714
*******************************TYPE 538
*******************************VIEW 1150
*******************************WINDOW 2
*******************************WINDOW GROUP 1
SQL> SELECT SUBSTR(CONTENTS,1,32),COUNT(1) FROM T GROUP BY SUBSTR(CONTENTS,1,32);
SUBSTR(CONTENTS,1,32) COUNT(1)
---------------------------------------- ----------
*******************************E 1
*******************************J 1
*******************************P 188
*******************************C 2
*******************************S 2554
*******************************T 2314
*******************************F 60
*******************************O 15
*******************************L 3
*******************************W 3
*******************************I 3709
*******************************V 1150
12 rows selected.
SQL> SET AUTOT TRACEONLY EXP
SQL> SELECT * FROM T WHERE CONTENTS='*******************************TABLE';
Execution Plan
----------------------------------------------------------
Plan hash value: 2153619298
--------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
--------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 2314 | 149K| 24 (0)| 00:00:01 |
|* 1 | TABLE ACCESS FULL| T | 2314 | 149K| 24 (0)| 00:00:01 |
--------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
1 - filter("CONTENTS"='*******************************TABLE')
SQL> SELECT * FROM T WHERE CONTENTS='*******************************TYPE';
Execution Plan
----------------------------------------------------------
Plan hash value: 2153619298
--------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
--------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 2314 | 149K| 24 (0)| 00:00:01 |
|* 1 | TABLE ACCESS FULL| T | 2314 | 149K| 24 (0)| 00:00:01 |
--------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
1 - filter("CONTENTS"='*******************************TYPE')
从上面可以看出,ORACLE只考虑前32个字节,下面每一个值查询的估算行数都是等于3者实际记录数之和。
*******************************TABLE 37
*******************************TABLE PARTITION 25
*******************************TABLE SUBPARTITION 1714
*******************************TYPE 538
更多Oracle相关信息见Oracle 专题页面 ?tid=12

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
