RE: Changing database to SQL from DDS

Rick wrote:
>> ...
>> To summarize, their recommendations pretty much
>> all pointed us to switching from DDS to SQL.  
>> ...
--------------------
OK, now I am somewhat confused, which happens more often than I would
care to admit ;->

As I understand the iSeries, DB2 is the underlying database
architecture.  SQL is one way of addressing commands to the database. 
DDS is another way of addressing commands to the SAME database.  DDS and
SQL have a different command set and capabilities, some of those
differences have been expounded on in this thread.  But the database is
the database, and once a table/file is created the language issues end,
with the exception of some features that SQL cannot access.

Now, I can see how changing the PROGRAMS from using DDS-based access to
using SQL-based access might have an impact on performance.  I can also
see how a techie would find changing the file creation language and
rebuilding the database to be a very cool project.  What I do NOT see is
how changing the file creation language from DDS to SQL and rebuilding
the database can have an impact on performance.

I stand ready to be enlightened, and eagerly await a continuation of
the holy war!

Thanks.
THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.