RE: SQL sort

Hi Booth

I understand and agree with your comment about your biggest problem being that you haven't yet figured out how to ask the right questions.

I have been using SQL for quite a few years now - and I STILL not yet figured out how to ask the right questions.

When I first started using SQL - I was told - ALWAYS use the physical with your selects (or omits) within the SQL script (although I could never find out why)

I followed this directive UNTIL I had to run one particular (relatively simple) SQL script.
It gave me the answers I was looking for - but it took a rather long time to run - 20 minutes or so - a LARGE file
So just for the hell of it, I changed the script to use a logical (for the selects and omits) and it literally took seconds - with the same results

Nowadays - I still tend to use the physical - but I keep the idea of using a logical in the back of my head
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Thursday, September 03, 2015 4:15 PM
To: Midrange Systems Technical Discussion
Subject: SQL sort

I am fairly new with SQL so please excuse what are most likely very simple questions.

I am looking to understand the pros and cons with SQL.
On large files with data that will be used in various applications and in various sort-by schemes, are logical files a help?
If so, does one reference the physical file and then SQL finds the best logical, or does it help to specify a specific logical file?
What is the right way to collect a set of records equal to SFLPAGE?

So far, I believe my biggest problem is that I haven't yet figured out how to ask the right questions.