Multiple choice technology databases

A tablespace has a table with 30 extents in it. Is this bad?

  1. True

  2. False
Reveal answer Fill a bubble to check yourself
B Correct answer
Explanation

Having 30 extents for a table is not inherently problematic. In locally managed tablespaces with uniform extent sizes, Oracle automatically manages extents efficiently. The number of extents becomes a concern primarily in dictionary-managed tablespaces or when it causes performance issues due to excessive extent allocation.

Keep practicing — related questions