Re: GHOST ROWS ON TABLE PARTITIONED


SELECT TABLE_NAME,PARTITION_NAME,NUM_ROWS FROM USER_TAB_PARTITIONS;

TABLE_NAME PARTITION_NAME NUM_ROWS
--------------------- --------------- ----------
-------------------
HA_EVENT_P ENTRO_MARZO02
HA_EVENT_P DOPO_MARZO02

or:
SELECT TABLE_NAME,NUM_ROWS FROM USER_TABLES WHERE TABLE_NAME =
'HA_EVENT_P';

TABLE_NAME NUM_ROWS
-------------------- -----------------
HA_EVENT_P

the numbers of rows on USER_TAB_PARTITIONS and USER_TABLES are null !!
although, the select count(*) give the numbers of rows on table
partitioned..

what could be happened? why i don't see the num. rows with query on
these views??

thanks very much
andrea

Have you calculate stats ?


.

Relevant Pages

  • Re: ADO.NET query execution much slower than SQL Management Studio
    ... When you first start using a new database it creates stats. ... the first few queries run slowly, as will any unique type of query, as it ... Something that would affect the .NET SqlClient but not SQL Mgmt Studio? ... compare this to the profiler command (meaning what is actually run in the ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: How to link tables via the field names themselves, not their c
    ... you can query the database to do what you want easily. ... There are approximately 30 different aspects (or statistics) which are ... Beacuse there are so many stats per contract, ...
    (microsoft.public.access.queries)
  • Re: [Info-Ingres] To order by, or NOT to order by
    ... Ah, sampled stats. ... [Info-Ingres] To order by, ... QEPs with a sample query ... Query and QEP, ...
    (comp.databases.ingres)
  • Re: Weird Optimizer Error
    ... Are the stats 'coherent' with the keys and indexes? ... I've gone so far as to convert the installation from an SQL- ... I've now managed to use trace point sc924 to identify the query causing ... The table has an isam secondary index that reverses this key, ...
    (comp.databases.ingres)
  • Re: Strange Cost Based Optimizer Decision Making
    ... The statistics on this table are 100% completely up to ... > I run an identical SELECT clause to the last query against this table. ... > the stats are fully up to date for LARGE_TABLE. ... compare that number with clustering factor and number ...
    (comp.databases.oracle.server)