Now the test script with a very simple SQL statement, where the test script is actually divided into two halves, the first of which will be thrown away so that physical reads from recursive SQL statements may be factored out. The output of the above query was identical for both databases. LEVEL USER,TABNAME=>'T1',ESTIMATE_PERCENT=>NULL,METHOD_OPT=>'FOR ALL COLUMNS SIZE 1')
Next, a simple table is created with an index in an ASSM autoallocate tablespace, the table and index statistics are collected at a 100% sample size without histograms, and then the table and index extent sizes are displayed: CREATE TABLE T1 NOLOGGING AS First, I specified the following CPU (system) statistics for both databases to help eliminate potential differences in the workload statistics: EXEC DBMS_STATS.SET_SYSTEM_STATS('MBRC',16)ĮXEC DBMS_STATS.SET_SYSTEM_STATS('CPUSPEED',2664)ĮXEC DBMS_STATS.SET_SYSTEM_STATS('SREADTIM',8)ĮXEC DBMS_STATS.SET_SYSTEM_STATS('MREADTIM',10)ĮXEC DBMS_STATS.SET_SYSTEM_STATS('MAXTHR',19181568)
Oracle 11g enterprise edition license#
Diagnostic Pack, Tuning Pack, and the other extra cost license optionsĪre there other differences, possibly related to optimizer or execution behavior? I created a 10.2.0.5 database on the Standard Edition and Enterprise Edition, and then performed a couple of tests.Partitioning (this is an extra cost option).
Conversion of B*tree indexes to bitmap indexes in execution plans to permit bitmap index join operations.( Forward to the Next Post in the Series)Īs I am sure that quite a few people are aware, the Standard Edition of Oracle Database is likely to be suitable for many of the smaller databases that you might find in your organization, as long as the following are not needed:
0 kommentar(er)
