[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

RE: [sqr-users] Move Command



thats slow.  Talk to your DBA about making a join work.  You can set up an
index on PSAUDIT if you need, but it's got to be faster than grabbing info
from one table, doing a lot of array processing, then grabbing info from the
other table to do more processing.  It's too much unnecessary overhead
processing.

That array processing is slowing you way down.  If you cant figure a good
way to join them, talk to your DBA.   They should be able to help you.

-----Original Message-----
From: sqr-users-bounces+bstone=fastenal.com@sqrug.org
[mailto:sqr-users-bounces+bstone=fastenal.com@sqrug.org]On Behalf Of
Murty Mirthipati Venkata Suryanarayan
Sent: Thursday, November 18, 2004 1:40 PM
To: This list is for discussion about the SQR database reportinglanguage
from Hyperion Solutions.
Subject: RE: [sqr-users] Move Command


I am afraid if Join makes things more worse.
I have PSAUDIT table, which is vast in size and I feel joining it with the
root table will be a problem. So I used arrays to read data from PSAUDIT
table and then used the array info with the root table.
   I didn't cross check the timing difference between using Arrays and
without arrays.
   Hope this gives a picture of my program. Please let me know your
suggestions on the same.
 
PS: PSAUDIT has no keys and seach keys in it

        -----Original Message----- 
        From: harriaj@NU.COM [mailto:harriaj@NU.COM] 
        Sent: Thu 18-Nov-2004 13:34 
        To: This list is for discussion about the SQR database reporting
languagefrom Hyperion Solutions. 
        Cc: 
        Subject: RE: [sqr-users] Move Command
        
        

        > the time
        > spent on database operations (inserts, updates, deletes, and
selects) is
        > usually several orders of magnitude greater than anything you
might do
        with
        > variables in memory.  That's where you should focus your efforts.
        
        I agree.  If you get your SQL execution moving quickly, there is
little you
        can do in the remainder of
        your SQR to slow it down much; except maybe too much array
processing.
        Where you can (and
        you almost always can), combine multiple begin-select paragraphs --
that
        are related via bind
        variables -- into single paragraphs using joins instead.  Let the
database
        do as much of the work
        as possible.  Using this strategy I've revised programs that were
running
        in 30 - 40 minutes to reduce
        processing to 20 seconds and less.
        
        Andrew :)
        Reporting Hero
        X 3523
        
        
        
        
**********************************************************************
        This e-mail, including any files or attachments transmitted with it,
is confidential and intended for a specific purpose and for use only by the
individual or entity to whom it is addressed.  Any disclosure, copying or
distribution of this e-mail or the taking of any action based on its
contents, other than for its intended purpose, is strictly prohibited.  If
you have received this e-mail in error, please notify the sender immediately
and delete it from your system.  Any views or opinions expressed in this
e-mail are not necessarily those of Northeast Utilities, its subsidiaries
and affiliates (NU).  E-mail transmission cannot be guaranteed to be
error-free or secure or free from viruses, and NU disclaims all liability
for any resulting damage, errors, or omissions.
        
**********************************************************************
        
        
        _______________________________________________
        sqr-users mailing list
        sqr-users@sqrug.org
        http://www.sqrug.org/mailman/listinfo/sqr-users
        
        


DISCLAIMER:
Information contained and transmitted by this E-MAIL is proprietary to
Hexaware Technologies and is intended for use only by the individual or
entity to which it is addressed and may contain information that is
privileged, confidential or exempt from disclosure under applicable law.
If this is a forwarded message, the content of this E-MAIL may not have
been sent with the authority of the Company. If you are not the intended
recipient, an agent of the intended recipient or a person responsible
for delivering the information to the named recipient, you are notified
that any use, distribution, transmission, printing, copying or
dissemination of this information in any way or in any manner is
strictly prohibited. If you have received this communication in error,
please delete this mail & notify us immediately at
adminchn@hexaware.com.

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users