Faster alternative in Oracle to SELECT COUNT FROM sometable

Question

I ve notice that in Oracle  the query  SELECT COUNT    FROM sometable    is very slow for large tables   It seems like the database it actually going through every row and incrementing a counter one at a time   I would think that there would be a counter somewhere in the table how many rows that table has   So if I want to check the number of rows in a table in Oracle  what is the fastest way to do that

User · Answer

The fastest way to get a count of a table is exactly what you did. There are no tricks you can do that Oracle doesn't already know about.

There are somethings you have not told us. Namely why do you think think this should be faster?

For example:

Have you at least done an explain plan to see what Oracle is doing?
How many rows are there in this table?
What version of Oracle are you using? 8,9,10,11 ... 7?
Have you ever run database statistics on this table?
Is this a frequently updated table or batch loaded or just static data?
Is this the only slow COUNT(*) you have?
How long does SELECT COUNT(*) FROM Dual take?

I'll admit I wouldn't be happy with 41 seconds but really WHY do you think it should be faster? If you tell us the table has 18 billion rows and is running on the laptop you bought from a garage sale in 2001, 41 seconds is probably not that far outside "good as it will get" unless you get better hardware. However if you say you are on Oracle 9 and you ran statistics last summer well you'll probably get a different suggestions.

User · Answer

Option 1  Have an index on a non-null column present that can be used for the scan  Or create a function-based index as   create index idx on t 0     this can then be scanned to give the count   Option 2  If you have monitoring turned on then check the monitoring view USER TAB MODIFICATIONS and add subtract the relevant values to the table statistics   Option 3  For a quick estimate on large tables invoke the SAMPLE clause     for example      SELECT 1000 COUNT    FROM sometable SAMPLE 0 1      Option 4  Use a materialized view to maintain the count     Powerful medicine though   um

User · Answer

This worked well for me  select owner  table name  nvl num rows -1   from all tables  --where table name in   cats    dogs   order by nvl num rows -1  desc   from https   livesql oracle com apex livesql file content EPJLBHYMPOPAGL9PQAV7XH14Q html

User · Answer

You can have better performance by using the following method   SELECT COUNT 1  FROM  SELECT    FIRST ROWS   column name  FROM table name  WHERE column name    xxxxx  AND ROWNUM   1

User · Answer

If the table has an index on a NOT NULL column the COUNT    will use that   Otherwise it is executes a full table scan   Note that the index doesn t have to be UNIQUE it just has to be NOT NULL   Here is a table     SQL gt  desc big23  Name                                      Null     Type  ----------------------------------------- -------- ---------------------------  PK COL                                    NOT NULL NUMBER  COL 1                                              VARCHAR2 30   COL 2                                              VARCHAR2 30   COL 3                                              NUMBER  COL 4                                              DATE  COL 5                                              NUMBER  NAME                                               VARCHAR2 10   SQL gt    First we ll do a count with no indexes       SQL gt  explain plan for   2      select count    from big23   3     Explained   SQL gt  select   from table dbms xplan display    2    select   from table dbms xplan display   PLAN TABLE OUTPUT -------------------------------------------------------------------- Plan hash value  983596667  --------------------------------------------------------------------   Id    Operation            Name    Rows    Cost   CPU   Time       --------------------------------------------------------------------     0   SELECT STATEMENT                 1    1618    1   00 00 20       1    SORT AGGREGATE                  1                               2     TABLE ACCESS FULL  BIG23     472K   1618    1   00 00 20   --------------------------------------------------------------------  Note  PLAN TABLE OUTPUT --------------------------------------------------------------------    - dynamic sampling used for this statement  13 rows selected   SQL gt    No we create an index on a column which can contain NULL entries      SQL gt  create index i23 on big23 col 5    2     Index created   SQL gt  delete from plan table   2     3 rows deleted   SQL gt  explain plan for   2      select count    from big23   3     Explained   SQL gt  select   from table dbms xplan display    2     PLAN TABLE OUTPUT -------------------------------------------------------------------- Plan hash value  983596667  --------------------------------------------------------------------   Id    Operation            Name    Rows    Cost   CPU   Time       --------------------------------------------------------------------     0   SELECT STATEMENT                 1    1618    1   00 00 20       1    SORT AGGREGATE                  1                               2     TABLE ACCESS FULL  BIG23     472K   1618    1   00 00 20   --------------------------------------------------------------------  Note  PLAN TABLE OUTPUT --------------------------------------------------------------------    - dynamic sampling used for this statement  13 rows selected   SQL gt    Finally let s build the index on the NOT NULL column       SQL gt  drop index i23   2     Index dropped   SQL gt  create index i23 on big23 pk col    2     Index created   SQL gt  delete from plan table   2     3 rows deleted   SQL gt  explain plan for   2      select count    from big23   3     Explained   SQL gt  select   from table dbms xplan display    2     PLAN TABLE OUTPUT --------------------------------------------------------------------- Plan hash value  1352920814  ----------------------------------------------------------------------   Id    Operation               Name   Rows    Cost   CPU   Time       ----------------------------------------------------------------------     0   SELECT STATEMENT                   1     326    1   00 00 04       1    SORT AGGREGATE                    1                               2     INDEX FAST FULL SCAN  I23      472K    326    1   00 00 04   ----------------------------------------------------------------------  Note  PLAN TABLE OUTPUT ----------------------------------------------------------------------    - dynamic sampling used for this statement  13 rows selected   SQL gt

User · Answer

You could use COUNT 1  instead

User · Answer

This works great for large tables   SELECT NUM ROWS FROM ALL TABLES WHERE TABLE NAME    TABLE NAME IN UPPERCASE     For small to medium size tables  following will be ok   SELECT COUNT Primary Key  FROM table name    Cheers

User · Answer

There was a relevant answer from Ask Tom published in April 2016   If you have sufficient server power  you can do select     parallel    count    from sometable  If you are just after an approximation  you can do   select 5   count    from sometable sample block  10    Also  if there is  a column that contains no nulls  but is not defined as NOT NULL  and there is an index on that column  you could try  select     index ffs t     count    from sometable  t where indexed col is not null

User · Answer

If you want just a rough estimate  you can extrapolate from a sample   SELECT COUNT      100 FROM sometable SAMPLE  1    For greater speed  but lower accuracy  you can reduce the sample size   SELECT COUNT      1000 FROM sometable SAMPLE  0 1    For even greater speed  but even worse accuracy  you can use block-wise sampling   SELECT COUNT      100 FROM sometable SAMPLE BLOCK  1

User · Answer

Think about it  the database really has to go to every row to do that  In a multi-user environment my COUNT    could be different from your COUNT     It would be impractical to have a different counter for each and every session so you have literally to count the rows  Most of the time anyway you would have a WHERE clause or a JOIN in your query so your hypothetical counter would be of litte practical value   There are ways to speed up things however  if you have an INDEX on a NOT NULL column Oracle will count the rows of the index instead of the table  In a proper relational model all tables have a primary key so the COUNT    will use the index of the primary key   Bitmap index have entries for NULL rows so a COUNT    will use a bitmap index if there is one available

User · Answer

You can create a fast refresh materialized view to store the count   Example   create table sometable   id number 10  not null primary key   name varchar2 100  not null    create materialized view log on sometable with rowid including new values   create materialized view sometable count refresh on commit as select count    count from   sometable   insert into sometable values  1  Raymond    insert into sometable values  2  Hans     commit   select count from sometable count     It will slow mutations on table sometable a bit but the counting will become a lot faster

[oracle] Faster alternative in Oracle to SELECT COUNT(*) FROM sometable

Examples related to oracle

Examples related to count