Then I am thinking of something else.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Monday, April 8, 2019 12:01 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Maximum OBDC Query Size
Rob,
It depends on what client you are using on the PC side ... e.g. in Microsoft Office products like Access, Excel, etc., you must check a "check-box" on the connection to tell it you want to use a "Pass through" query, IIRC.
Mark
On Monday, April 8, 2019, 11:41:39 AM EDT, Rob Berendt <rob@xxxxxxxxx> wrote:
I know that it took zero amount of additional configuration. It was all in the way of how you used your statement.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Monday, April 8, 2019 11:18 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Maximum OBDC Query Size
Rob,
I believe the term you are thinking of is called an "SQL pass through query" -- a very important and useful concept when running remote queries via ODBC/JDBC.
HTH,
Mark S. Waterbury
On Monday, April 8, 2019, 11:14:05 AM EDT, Rob Berendt <rob@xxxxxxxxx> wrote:
I cannot remember the terminology but there is a way in ODBC to tell it to run the select on the host instead of pulling all of the data down to the client and mulling it over.
Basically instead of doing a
Select...
You do something else and the guts of the sorting and selection are done on the host. I remember covering this many years ago but I couldn't remember and couldn't find it in the archives.
It was not converting to a view, calling a stored procedure, extracting the data earlier or any other such solutions. It was just a different way of doing the statements in odbc.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Spencer Elliott
Sent: Monday, April 8, 2019 10:57 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx>
Subject: Re: Maximum OBDC Query Size
Hi Richard,
The actual issue boils down to speed. Which is faster? A single select with a large result set that is processed by the program or a bunch of selects with a small result set. I chose the single select approach. It just seems to me that it would be faster than 500 selects and 500 open cursor, close cursor ect.
Spencer C Elliott
949-366-5234 X152 (O) l (949) 544-1237 (Skype)
Spencer@xxxxxxxxxxxxxx
www.s4isystems.com
Follow us:
[image: Follow_us][image: Follow_us][image: Follow_us][image: Follow_us][image:
Follow_us]
NOTE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by replying to this email, and destroy all copies of the original message.
On Mon, Apr 8, 2019 at 7:42 AM Richard Schoen via MIDRANGE-L < midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Yeah I realized that once I re-read the question 😊
Looks like what you've discovered should give you enough runway unless
you've had an issue with running your large statement.
One option to consider might be to call an RPG program that contains
the SQL and return a resultset for processing from the RPG app perhaps.
Seems like this might be a good use case for some pre-processing on
the IBMi to a temp table, but I don't know enough about the actual
business case.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 3
date: Mon, 8 Apr 2019 07:01:31 -0700
from: Spencer Elliott <spencer@xxxxxxxxxxxxxx>
subject: Re: Maximum OBDC Query Size
Hi Richard,
The question was about how big can a SQL statement be when submitted
through ODBC NOT how big can the result set be. I am working on a
project where I need to submit an extremely large SQL statement (in my
opinion,
10k+) to the IBM i with a very large WHERE (500+ predicates) clause.
Spencer C Elliott
949-366-5234 X152 (O) l (949) 544-1237 (Skype)
Spencer@xxxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
