|
IMO, the SQL tools are for: 1) power users (who you trust to NOT use 'DELETE * from FILEXXX') 2) IT dept. users 3) required if using embedded SQL in your programs Query is better for ad-hoc reporting, since the user interface allows relatively unsophisticated users the ability to quickly create and format reports. If I were told that I could only have 1 tool, I'd probably choose Query. If you have AS/400 query, you can create code a SQL statement in a source member and use CRTQMQRY to compile it, then use STRQMQRY to run it, giving the same results as you would get using interactive SQL, without the syntax checker. Also, the CRTQMQRY & STRQMQRY commands can be secured to only authorized users, so as to prevent a novice from hosing up the system. HTH ----- Original Message ----- From: "Bob Carl" <bcarl@knapheide.com> To: "Midrange Computing Technical NewsGroup for ISeries" <midrange-l@midrange.com> Sent: Thursday, October 10, 2002 10:08 AM Subject: SQL VS QUERY This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] My account is getting ready to purchase some sort of IBM ISeries Query tool, SQL tools, or both. I have been asked to provide justification for investment in the SQL tool over or in addition to Query. Can you use SQL in a CL in the same fashion as query, such as to create a file(Like OPNQRYF). I would think you can. I am wondering if we can scrap query all together in favor of SQL (RUNSQL). Right now we do not use SQL for anything but transferring data, such as in Excel or Client Access, but considering its industry presence, it seems like a no-brainer. Please submit to me your best arguments for using SQL, and if it can replace Query completely and easily. Thanks in advance. Bob Carl, Senior Systems Analyst Knapheide Manufacturing Company 217-223-1848 Ext. 2397 Fax: 217-223-1947 -- _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.