MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: SQL created table slows reporting tool



fixed

Actually I'm not saying that you have to make either a stored proc or LFs or views.

You do need to be sure that you tell Crystal to run the query on the server, not at the PC. Crystal at least used to, by default, run all queries on the PC, which means that the entire table had to be downloaded from the server, then the query is run against that "full" copy.

I like the idea of using a view - to limit the columns downloaded - and maybe the rows, due to selection. You will still benefit from making the query be run on the server, then downloading only the results. I think this is especially the case, because you will likely not want to make a view for each WHERE possibility - so if your Crystal report has parameters for selection, again, you need to run the query on the server - it's a setting somewhere in Crystal, last I saw, which is years ago!

HTH
Vern

On 12/23/2013 7:55 AM, Hoteltravelfundotcom wrote:
in this case i was just taking a peek at the raw table. So it seems that
what you are saying is we have to make either stored proc or logical/views
on the Ibm i. this is fine, This is what we currently do on the dds based
PF's.


On Sun, Dec 22, 2013 at 11:42 PM, Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx>wrote:

Is the out-of-memory condition on the PC or on the IBM i?

In any case, be sure to set CR to have the SELECT done on the server,
that is, on the IBM i - NOT on the PC - in the latter case, the entire
file has to be downloaded, THEN the query is run against it. Bad Bad Bad!!

There are other confusing things about this question, but I'll leave my
questions to what I asked already.

HTH
Vern

On 12/22/2013 4:58 PM, Hoteltravelfundotcom wrote:
We have for first time a consultant is making a data warehouse for us.
This
particular
file is in DDS as TXT. It has about 3.5 million records with more coulmns
than below.
I selected this table in the Crystal Reports and only about 8 fields but
it
creates an
out of memory shutdown. Prior I am using always Views or logical index
based files and never had this issue. Is this something where we need to
creates such logicals on ths
raw data ware house file?

CREATE TABLE PROJ_1/WHS1 (
CUSTOMER# CHAR ( 8),
NAME CHAR (40 ),
CITY CHAR (30 ),
STATE CHAR (3 ),
COUNTRY CHAR (3 ),
ZIP_CODE char (10 ),
ITEM# CHAR (15 ),
ITEM_TEXT CHAR (40 ),
ORDER# CHAR (8 ),
ORD_STATUS CHAR (2 ),
INVOICE# CHAR (8 ),
ORD_DATE NUMERIC (8 , 0),
INV_DATE numeric (8 , 0),
ORD_TYPE CHAR (3 ),
CUST_TYPE CHAR (3 ),
PROD_LINE CHAR (3 ),
SALES_REP CHAR (3 ),
WAREHOUSE CHAR (3 ),
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact