RE: DB2 table vs Physical files

["Pete Helgren" <pete@xxxxxxxxxx>]

Not exactly sure what you mean here.  Are you planning to build new tables
on the iSeries and want to know if you should use DDS vs the Create Table
commands?  Or, are you migrating data from the iSeries to your windows apps.

Whether the file resides in a library, or the table resides in a collection,
ODBC really doesn't care, they will both look the same to the Windows app.
On the iSeries, the table/collection looks VERY different.  And, Create
Collection will generate many more objects in the "library" on the iSeries.

But ODBC is the great "emancipator" on the Windows side.  It will be
oblivious to the differences between files/libraries tables/collections on
the iSeries.

Pete Helgren
Timpanogos Technologies, Inc
801.892.9106 x 202




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Lokesh Gupta
Sent: Wednesday, May 12, 2004 7:20 AM
To: Midrange Systems Technical Discussion
Subject: DB2 table vs Physical files


Hi,
I used to work with Physical Files (PF)  and this is first time when I may
have to work
with DB2 tables. I need to pull data from As400 to windows environment (this
could be
.net or Java) over ODBC and I have an option to use physical files or DB2
tables.
My question is (1) which option would be better for performance pov PF or
DB2 tables.
I do not need to join lot of tables, it is just couple of tables and a
simple query.
I do not see any difference from windows side to access the data.

Secondly, Is there any data conversion involved (db2 or PF) as I am pulling
data
from AS400 to Windows, if yes, how will that affect the performance.


regards,
Lokesh



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.