Re: Reading sequential files in COBOL vs SQL

And the SQL can also take advantage of parallel read algorithms, built into the DB2 for i5/OS query engine, to obtain the results quicker. Whereas in the non-SQL case, any parallel read actions would have to be coded into/as part of the application itself. So just as it might be generally considered easier to code the SQL request, it is also easier for the SQL to take advantage of an optimizer and underlying query features.
If the files are all small [it is unclear if the 4K records was a statement of each file or the number of files as obtained from 4K rows identifying the files of an unknown number of records], then the command SETOBJACC may prove beneficial for either row level or SQL access.

Regards, Chuck
--
All comments provided "as is" with no warranties of any kind whatsoever and may not represent positions, strategies, nor views of my employer
.

Relevant Pages

  • row vs page locking...
    ... Somewhere on these newsgroups I recall reading that SQL Server 6 and prior ... used page locking and not row level ... RDMSs like Interbase have a versioning engine so it was built from the ...
    (microsoft.public.sqlserver.server)
  • Re: ORDER BY AND GROUP BY CLAUSE
    ... SQL Server you can use the ansi standard if you want - well, ... VFP supports multiple standards including their own sql standards. ... especially when doing anything on a row by row level .... ...
    (comp.databases.ms-sqlserver)
Loading