I understand, same thing here.  We just moved from an Access database (where
I had complete control of the data structures) to Oracle.  Since myself and
several other groups use this "warehouse" of information, I rely on other
Oracle programmers to take care of the data side of the house.  I have had
them make several changes to the indexes and other things and performance
has increased but not completely to the level that I would like.  The code
works and I'm not getting complaints from anyone about the speed but I'm
always looking at ways to increase the performance.  Sri Amudhanar from
Maxys Corporation did some excellent training for us a few months back but
only had time to scratch the surface in Tango Class Files and XML.  However,
he scratched it enough to get me thinking about a new things to try.  I
guess I'm just looking for some ideas to get me started exploring down
different paths.

-----Original Message-----
From: Ben Johansen [mailto:benj@;pcforge.com]
Sent: Friday, October 25, 2002 12:41 PM
To: Multiple recipients of list witango-talk
Subject: RE: Witango-Talk: Looking for a New Idea


Ok, 

Please don't take this wrong, but it sounds like indexing need to be
addressed here.

It is hard to take the information you gave and totally see you issue.
If I could see the view definition this would help us see the tables
involved.


Ben Johansen - http://www.pcforge.com
Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm 
Latest downloads & List Archives @ http://www.witango.ws


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:owner-witango-talk@;witango.com] On Behalf Of Storey, Paul
Sent: Friday, October 25, 2002 10:06 AM
To: Multiple recipients of list witango-talk
Subject: Witango-Talk: Looking for a New Idea

I have a large Oracle database with 100,000+ records in several tables.
Currently, I have to use a very complex view in order to pull
information
from all of the tables that I need a one time but the performance is
much
less than desired.  I have created individual queries to each table
which
gives me a good performance increase but adds a lot of additional code
in
some areas.  Now, finally to my question.  I have an equipment table
that
stores all of the information including a user number about each piece.
In
several cases I need to only pull the acctid (i.e. SMITHJD) from the
user
table for several pieces of equipment in a list and I don't want to
perform
additional queries.  The user list is updated overnight and doesn't
change
during the day so I could either create a two column array in the domain
scope or write an XML file with user numbers and acctids.  I would
somehow
like create a lookup into the array or file to show the acctid as I list
each piece of equipment that would give me the best performance.  Very
wordy
I know, just looking for some ideas.

Current

<@ROWS>
<TR>
<TD>
<@COLUMN MAMS_VIEW_WEB_DEVICE_300.ECN>
</TD>
<TD>
<@COLUMN MAMS_VIEW_WEB_DEVICE_300.BLDG>
</TD>
<TD>
<@COLUMN MAMS_VIEW_WEB_DEVICE_300.ROOM>
</TD>
<TD>
<@COLUMN MAMS_VIEW_WEB_DEVICE_300.ACCTID>
</TD>
</TR>
</@ROWS>

What I would like to have is something like this

<@ROWS>
<TR>
<TD>
<@COLUMN EQUIPMENT.ECN>
</TD>
<TD>
<@COLUMN EQUIPMENT.BLDG>
</TD>
<TD>
<@COLUMN EQUIPMENT.ROOM>
</TD>
<TD>
 ------------ I would like to put either a custom tag or maybe a call to
a
class file or something that would pull the acctid from the array or a
lookup in the XML file.----------- 
</TD>
</TR>
</@ROWS>

Any new approaches or thoughts would be appreciated.
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
                with unsubscribe witango-talk in the message body

Reply via email to