SQL administration (storage management): which command is used to change or tune a table's storage characteristics (for example, tablespace, extent, or physical attributes) in a relational database?

Introduction / Context:
Administrators often need to adjust how an existing table is stored on disk—such as moving it to another tablespace, allocating an extent, or altering physical properties. The question asks which SQL command is used for changing a table's storage characteristics after it has already been created.

Given Data / Assumptions:

• The table already exists in the database.
• The task is to modify storage-related attributes, not to create a new table.
• We consider broadly recognized SQL/DDL terminology used by mainstream RDBMSs.

Concept / Approach:
The canonical DDL verb to change the definition or storage properties of an existing table is ALTER TABLE. Vendor dialects allow storage options in ALTER TABLE (for example, moving tables between tablespaces, allocating extents, or setting fill factors). Nonstandard phrases like MODIFY TABLE or CHANGE TABLE are not general SQL commands for this purpose, even though the keyword MODIFY may appear as a column-level clause within ALTER TABLE in some products.

Step-by-Step Solution:

Verification / Alternative check:
In Oracle, PostgreSQL, SQL Server, and MySQL, storage-related adjustments (when exposed) are implemented via ALTER TABLE syntax. Documentation consistently places such changes under ALTER TABLE, not under MODIFY TABLE or CHANGE TABLE as independent commands.

Why Other Options Are Wrong:

Common Pitfalls:
Confusing column-level “MODIFY” with a top-level command; or assuming every engine exposes identical storage controls—capabilities vary, but the top-level verb remains ALTER TABLE.

Final Answer:
ALTER TABLE