Query/400 vs. SQL/400

[EuroN8]

Hi,

Could someone explain to me the differences between Query/400 and SQL/400?
Are there distinct advantages to using one vs the other? Which is more
accepted by the IT industry?

Any help would be appreciated!

Thanks
N8

[milan432]

Hi there,

I have come to know Query/400 as well as SQL/400 quite well over the
last two years, here is my personal point of view :

Result first, I am almost exclusively using SQL/400 these days.
Normally I would use Query/400 only to print out the results I have
created with SQL/400 .

Query/400 is fine for quickly reporting on some data, especially if
you want to print out the results, or you want to create an outfile .
But you can only use plain SQL, that is, only those statements that
query the data. No Inserts, no Updates, no Views, no Triggers, no
DISTINCT key word, ...
What I hate most is more complex data operations, which lead to people
writing one Query to retrieve data and create an outfile, a second
Query to retrieve data from this outfile, do something and create
another outfile which is finally processed by yet another Query, and
so on ...

Using SQL/400, you could write and run a script that does all
operations in one hit. However, you need a pretty good command of the
language to put the full syntax to use . But once you manage that ,
you have unlimited access to the full power of SQL .
Depending on the extense of SQL use, you can create as wonderful
things as triggers, procedures, functions, views, ...
SQL/400 gives you the power to create, manage, maintain data bases and
whatever objects are required.

Then again, you can embed SQL into host languages like RPG or C or
COBOL, I am learning about this myself at the moment .

In a nutshell I would say that Query/400 is a tool for looking at data
and creating output of it.
SQL/400 is the full set of statements and has unlimited power over
anything to do with data bases and the data in it .

Which is more accepted in the IT world, I don't know , sorry . We are
not selling software to customers .

Hope this (very personal) points of view are of any use to you

Regards
milan432

"EuroN8" <glip...@yahoo.com> wrote in message news:<Yd3S8.10404$t%5.42...@newssvr28.news.prodigy.com>...

[Mike Faust]

Query 400 is simply a report writing tool. SQL 400 is a set of
database tools based on the Structured Query Language standards. This
being the case I would say, in answer to your question, that SQL 400
would be more "accepted" although each of these products has it's own
place.

Mike Faust
mikef...@yahoo.com
Check out my book from MC Press "The iSeries and AS/400 Programmer's
Guide to Cool Things" http://mc-store.com/isasprogguid.html

"EuroN8" <glip...@yahoo.com> wrote in message news:<Yd3S8.10404$t%5.42...@newssvr28.news.prodigy.com>...

[Kent Milligan]

They are really quite different. SQL is really is a language that can be used
for programming while Query/400 is just a menu based report writer. SQL is the
industry standard for database access and processing.

There is now a graphical version of Query/400 that is SQL-based, it's from IBM
and called QMF for Windows for iSeries. There are actually conversion utilities
you can buy that automatically convert exisitng Query/400 definition into QMF
for Windows definitions.

--
Kent Milligan, DB2 & BI team
PartnerWorld for Developers, iSeries
km...@us.removethis.ibm.com GO HAWKEYES!!
>>> www.iseries.ibm.com/db2
(opinions stated are not necessarily those of my employer)