Comments on: SQL performance vs. Internal pgogram database access http://itknowledgeexchange.techtarget.com/itanswers/sql-performance-vs-internal-pgogram-database-access/ Mon, 27 May 2013 00:55:15 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/sql-performance-vs-internal-pgogram-database-access/#comment-69825 tomliotta Mon, 02 Nov 2009 03:01:57 +0000 #comment-69825 Maybe one will be faster; maybe the other. Without any clue about what the program is doing, there’s no way to know. If it’s doing work that’s suited for SQL, then the SQL will probably be faster and more efficient. If it’s interactive random updates, native is probably faster.

Tom

]]> By: thequigs http://itknowledgeexchange.techtarget.com/itanswers/sql-performance-vs-internal-pgogram-database-access/#comment-39567 thequigs Wed, 14 Sep 2005 16:11:11 +0000 #comment-39567 I think the real answer is, “That depends.” You cannot really control the index SQL will use. That can be an advantage or a disadvantage. If you know for certain the most efficient index to use in every case, you can code the program with internal file access and probably be faster. However, IBM spends a lot of effort developing the query optimizer which will review all the indexes it finds “of interest” to the query being processed.

For more information on query optimization you can take a look at the following article (1st in a series) from the eServer iSeries Extra magazine:

http://www.eservercomputing.com/ME2/Audiences/dirmod.asp?sid=BCF4DE820EA64A858FB46EECB7C00BB4&nm=&type=Publishing&mod=Publications%3A%3AArticle&mid=8F3A7027421841978F18BE895F87F791&AudID=1E8FEE745A284521B6CFB3FD70B49099&tier=4&id=FF99621CEC0743D0963727A7EB546E60

]]>