Raj,
I needed a 12 pack adter this one, it's from PeopleSlop:
SELECT 0001560265,OPL.BUSINESS_UNIT,OPL.PRODUCTION_ID,OPL.OP_SEQUENCE,
PID.INV_ITEM_ID,TMP.COST_ELEMENT,'04',0,0,0,0,0,0,PID.ORIG_UOM,PID.PRDN_AREA_COD
E,
PID.PRODUCTION_TYPE,OPL.QTY_SCRAPPED,OPL.PERCENT_COMP,' ',1,0,' ','
',0000000000
FROM PS_BU_ITEMS_INV INV,PS_SF_PRDNID_HEADR PID,PS_CE_OP_LIST_COPY OPL,
PS_CE_OP_LIST_VW OPLIST,PS_SF_COMP_LIST CMP,PS_CE_ITEMVAR_TMP TMP
WHERE INV.BUSINESS_UNIT='VICOR'
AND PID.BUSINESS_UNIT='VICOR'
AND OPL.BUSINESS_UNIT='VICOR'
AND OPLIST.BUSINESS_UNIT='VICOR'
AND CMP.BUSINESS_UNIT='VICOR'
AND TMP.BUSINESS_UNIT='VICOR'
AND TMP.PROCESS_INSTANCE=0001560265
AND OPL.PROCESS_INSTANCE=0001560265
AND OPLIST.PROCESS_INSTANCE=0001560265
AND OPL.PRODUCTION_ID= PID.PRODUCTION_ID
AND OPL.PRODUCTION_ID= CMP.PRODUCTION_ID
AND OPL.PRODUCTION_ID= OPLIST.PRODUCTION_ID
AND INV.INV_ITEM_ID= PID.INV_ITEM_ID
AND ( OPL.OP_SEQUENCE= CMP.OP_SEQUENCE OR (CMP.OP_SEQUENCE = 0 AND
OPL.OP_SEQUENCE = OPLIST.OP_SEQUENCE))
AND PID.PROD_STATUS BETWEEN '30' AND '60'
AND TMP.INV_ITEM_ID= CMP.COMPONENT_ID
AND TMP.CONFIG_CODE= CMP.CONFIG_CODE
AND CMP.SOURCE_CODE <> '5'
AND CMP.NON_OWN_FLAG = 'N'
AND NOT EXISTS (SELECT 'X' FROM PS_CE_SCRAPCST_TMP TMP2
WHERE TMP2.PROCESS_INSTANCE=0001560265
AND TMP2.BUSINESS_UNIT = OPL.BUSINESS_UNIT
AND TMP2.PRODUCTION_ID = OPL.PRODUCTION_ID
AND TMP2.OP_SEQUENCE = OPL.OP_SEQUENCE
AND TMP2.COST_ELEMENT= TMP.COST_ELEMENT)
GROUP BY OPL.BUSINESS_UNIT,OPL.PRODUCTION_ID,OPL.OP_SEQUENCE,PID.INV_ITEM_ID,
TMP.COST_ELEMENT,PID.ORIG_UOM,PID.PRDN_AREA_CODE,PID.PRODUCTION_TYPE,
OPL.PERCENT_COMP,OPL.QTY_SCRAPPED
____________________Reply Separator____________________
Author: "Jamadagni; Rajendra" <[EMAIL PROTECTED]>
Date: 11/15/2002 5:33 AM
Funny ... that Cary mentioned it ....
Some developers here think that by setting some magic instance parameters we
can make all RBO tuned code run well under CBO ... (I just bought a 6 pack
of Mylanta yesterday ...)
Raj
______________________________________________________
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!
____________________Reply Separator____________________
Author: "Cary Millsap" <[EMAIL PROTECTED]>
Date: 11/14/2002 10:34 AM
Hamid,
I'm sorry: Unless your SQL returns fewer than about 800,000 rows to the
calling application (or an aggregation of 800,000 rows), then the
statement "we have done all the necessary tuning on all the SQL queries"
is not yet true.
If your SQL does actually return about 800,000 rows, then it is time to
begin thinking about the mismatch between business processing
requirements and the logical structure of your data.
The answer to your problem is not in your instance parameters.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>RE: RE: CONSISTANT GETS</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Funny ... that Cary mentioned it ....</FONT>
</P>
<P><FONT SIZE=2>Some developers here think that by setting some magic instance
parameters we can make all RBO tuned code run well under CBO ... (I just bought
a 6 pack of Mylanta yesterday ...)</FONT></P>
<P><FONT SIZE=2>Raj</FONT>
<BR><FONT SIZE=2>______________________________________________________</FONT>
<BR><FONT SIZE=2>Rajendra Jamadagni
MIS, ESPN Inc.</FONT>
<BR><FONT SIZE=2>Rajendra dot Jamadagni at ESPN dot com</FONT>
<BR><FONT SIZE=2>Any opinion expressed here is personal and doesn't reflect that
of ESPN Inc. </FONT>
<BR><FONT SIZE=2>QOTD: Any clod can have facts, but having an opinion is an
art!</FONT>
</P>
<P><FONT SIZE=2>____________________Reply Separator____________________</FONT>
<BR><FONT SIZE=2>Author: "Cary Millsap"
<[EMAIL PROTECTED]></FONT>
<BR><FONT SIZE=2>Date: 11/14/2002 10:34
AM</FONT>
</P>
<P><FONT SIZE=2>Hamid,</FONT>
</P>
<P><FONT SIZE=2>I'm sorry: Unless your SQL returns fewer than about 800,000 rows
to the</FONT>
<BR><FONT SIZE=2>calling application (or an aggregation of 800,000 rows), then
the</FONT>
<BR><FONT SIZE=2>statement "we have done all the necessary tuning on all
the SQL queries"</FONT>
<BR><FONT SIZE=2>is not yet true.</FONT>
</P>
<P><FONT SIZE=2>If your SQL does actually return about 800,000 rows, then it is
time to</FONT>
<BR><FONT SIZE=2>begin thinking about the mismatch between business
processing</FONT>
<BR><FONT SIZE=2>requirements and the logical structure of your data.</FONT>
</P>
<P><FONT SIZE=2>The answer to your problem is not in your instance
parameters.</FONT>
</P>
<BR>
<P><FONT SIZE=2>Cary Millsap</FONT>
<BR><FONT SIZE=2>Hotsos Enterprises, Ltd.</FONT>
<BR><FONT SIZE=2><A HREF="http://www.hotsos.com";
TARGET="_blank">http://www.hotsos.com</A></FONT>
</P>
</BODY>
</HTML>
*********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************1
