RE: PF or table?

David,

It's a good idea to keep your DDL (DDL=SQL, DDS=native) CREATE
statements, as well as any subsequent ALTER statements in source files
to run at any time. Typically I have a source member for CREATE
statements for a project's tables, views, indexes, etc., and another
source member for ALTER statements for those things that happen over the
life of the project. Also, I would have a third source member for
populating master/static/lookup data for the project; these things would
be internal lookup codes or other project-specific master data that
rarely change or provide initial defaults.

If you use a source control product, you almost certainly would have
this anyway so it can be tracked and versioned.

It sounds like you are on the right path. Good luck!


Loyd Goodbar
Business Systems
BorgWarner Shared Services
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Tuesday, August 05, 2008 5:17 AM
To: midrange-l@xxxxxxxxxxxx
Subject: PF or table?

Hi,

I'd created a table for testing an SQL statement by a file transfer from
EXCEL. As I was going to make this table permanent, I started writing
some DDS.
As the table will be used only by SQL, would there be a performance loss
if I used DDS? We don't have any standard yet for storing DDL but I am
putting the DDL at least temporarily into a QSQLSRC file to be used by
RUNSQLSTM.

Thanks