SQL VOLATILE / NOT VOLATILE

All,

In reading about VOLATILE vs NOT VOLATILE, I have a couple of questions for
you more seasoned SQLers:

1) As I understand it, VOLATILE refers to cardinality of rows or some such.
I interpret VOLATILE to mean there will be a large number of rows
added/removed on a regular basis, as opposed to updating of existing rows.
Do I understand this correctly?

2) Assuming I do understand this correctly, is a large number of rows an
_absolute_ number or a _relative_ number? For example, I have a file that I
will soon convert to DDL (from DDS) that will rarely contain over 200 rows.
But in a typical day, however, 100 rows could be added while another 100
rows could be deleted. I reorg it every night. Should this be considered
VOLATILE? Or because the table is so little, who cares?

3) How about things like history files? Thousands of records will be added
daily, but none will be deleted. Deletions only take place once a
month/quarter/year or something like that. VOLATILE?

I see a lot of examples that say NOT VOLATILE, but not many that say
VOLATILE. I was actually wondering whether VOLATILE was one of those
features that is available, but no one ever uses. :)

Thanks.