SQL performance: creating tables using SQL DDL

To get the SQL performance benefits of larger page size, etc., I'm
wondering if creating a simple table in SQL, yada yada, and then using
CHGPF SRCFILE{} to add the rest of the columns, text, column headings,
and edit codes/words would preserve the SQL-ness of the object.

I know OpsNav has facilities to reverse-engineer DDS files into SQL
but I'm looking at the step above as part of a bigger-picture build
process.

Thanks,
Reeve