Re: ** statistics for zero row table - Yes or No?


One other thing to consider if your table is over 1MB and zero rows: if this table is being used as an intermediate table for other processing, it looks as if the application, or user, is doing a "delete" instead of a "truncate" to clear the table. This in general is bad practice because a "delete" will not reset the high water mark, while a truncate will. Oracle will have to scan 1MB worth of blocks even if the table has zero rows, i.e. another performance hit on top of incorrect statistics.




    Going further what if the table size is over 1 MB and zero rows ?


Other related posts: