-
Originally posted by marist89
...I heard count(1) was faster...
count(9)
-
Originally posted by marist89
...I heard count(1) was faster...
Ya sure...Even I know that not to be the case...
So, we don't have anything more efficient than a SELECT count(*)??
-
Amar
"There is a difference between knowing the path and walking the path."
-
funky...
"I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."
"Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"
-
could you display the execution plan to check if an index is used for the count or if it does a fts
-
Originally posted by marist89
...I heard count(1) was faster...
Count(NULL) shoud go even faster
-
Once you go above 400 million, does an extra million really matter?
Just tell them it is a "big mother f*&%ing table"
MH
I remember when this place was cool.
-
You could always export the table and see how many rows it exported...
Jeff Hunter
-
how about creating a nice function-based, compressed index ...
Code:
create index my_index on my_table ('X') pctfree 0 compress;
That ought to be reasonably small and quick to modify.
-
what about a procedure that runs when the system is quiet and populates a count history table (table_name,sysdate,count(*)) they can then just look at that. Its also pretty useful for spotting growth trends and what not.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|