VIAINDEX usage

Mon, 17 Feb 2003 14:34:16 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2D691.A64050B0
Content-Type: text/plain

To this day I don't understand why ORDERBY was implemented in Qdesign/Quick
but not in Quiz and QDesign. Use of VIAINDEX really shouldn't be necessary
in a relational database environment, but there is no other efficient way of
doing the job, other than creating a ordered view on the database.

Kevin Gordon
Sea Containers Services Ltd

-----Original Message-----
From: Deskin, Bob [mailto:Bob.Deskin@cognos.com] 
Sent: 17 February 2003 14:10
To: 'Peter Bateman'; Roughsedge, Greg N; PowerhouseList
Subject: RE: VIAINDEX usage

Peter is correct and so is your DBA. We take the VIAINDEX and break it down
to the associated columns. We also generate an ORDER BY. It's up to the
database to determine the best retrieval using those columns. So you can use
SORTED.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178 3755
Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: Peter Bateman [mailto:shediac92@hotmail.com]
Sent: Monday, February 17, 2003 7:22 AM
To: Roughsedge, Greg N; PowerhouseList
Subject: Re: VIAINDEX usage

Greg:

When using VIAINDEX PowerHouse I believe
sends an ORDER BY the segments of the index to
the database. So you should be able to use SORTED.

You can check this by using DBAUDIT=FULL
on your run of PowerHouse.

Regards,
Peter Bateman

----- Original Message -----
From: "Roughsedge, Greg N" <Greg.N.Roughsedge@team.telstra.com>
To: "PowerhouseList" <powerh-l@lists.swau.edu>
Sent: Monday, February 17, 2003 2:41 AM
Subject: VIAINDEX usage

> Hi,
>
> I would like some clarification around the use of the VIAINDEX clause.
>
> Background:
> Op Sys:        Open VMS V7.1-2
> Database:      Oracle RDB 7.0-6
> Powerhouse:  7.10.G1
>
> I've used the CHOOSE VIAINDEX <indexname> clause and then assumed that 
> I
can use the SORTED clause as the records have been retrieved via the named
index.
> The DBA's believe there is no way to force the retrieval via a 
> specified
index as the database will determine the most appropriate index and use this
regardless of what's specified.
>
> This equally relates to the LINK VIAINDEX clause as well as part of 
> the
ACCESS statement.
>
> My question is, can I be absolutely guaranteed that the VIAINDEX 
> option
will retrieve records using that index (and consequently know the sequence
of records retrieved). Or, should I not specify the VIAINDEX option and use
SORT instead of SORTED.
>
> Cheers
>
> Greg Roughsedge
> Media Solutions - Telstra
> (Black Diamond Technologies)
> (03) 8696 5968
>

******************************************************************************
The information contained in this e-mail is confidential. 
It may also be protected by legal privilege. 
It is intended only for the stated addressee(s). 
If you are not an addressee you must not disclose, copy, circulate nor use the information contained in it. 
If you have received this e-mail in error please inform the sender immediately and delete it and any copies from your system.
******************************************************************************

------_=_NextPart_001_01C2D691.A64050B0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 5.5.2653.12">
<TITLE>RE: VIAINDEX usage</TITLE>
</HEAD>
<BODY>

To this day I don't understand why ORDERBY was implemente=
d in Qdesign/Quick but not in Quiz and QDesign. Use of VIAINDEX really shou=
ldn't be necessary in a relational database environment, but there is no ot=
her efficient way of doing the job, other than creating a ordered view on t=
he database.

<P><FONT SIZE=3D2>Kevin Gordon</FONT>
<BR><FONT SIZE=3D2>Sea Containers Services Ltd</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Deskin, Bob [<A HREF=3D"mailto:Bob.Deskin@cognos.c=
om">mailto:Bob.Deskin@cognos.com</A>] </FONT>
<BR><FONT SIZE=3D2>Sent: 17 February 2003 14:10</FONT>
<BR><FONT SIZE=3D2>To: 'Peter Bateman'; Roughsedge, Greg N; PowerhouseList<=
/FONT>
<BR><FONT SIZE=3D2>Subject: RE: VIAINDEX usage</FONT>
</P>
<BR>

Peter is correct and so is your DBA. We take the VIAINDEX=
 and break it down to the associated columns. We also generate an ORDER BY.=
 It's up to the database to determine the best retrieval using those column=
s. So you can use SORTED.

Bob Deskin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 PowerHouse Web Product Manager, Application Development =
Tools, Cognos Inc. bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613)=
 727-1178 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANA=
DA

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Peter Bateman [<A HREF=3D"mailto:shediac92@hotmail=
.com">mailto:shediac92@hotmail.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, February 17, 2003 7:22 AM</FONT>
<BR><FONT SIZE=3D2>To: Roughsedge, Greg N; PowerhouseList</FONT>
<BR><FONT SIZE=3D2>Subject: Re: VIAINDEX usage</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Greg:</FONT>
</P>

When using VIAINDEX PowerHouse I believe
 sends an ORDER BY the segments of the index to
 the database. So you should be able to use SORTED.

<P><FONT SIZE=3D2>You can check this by using DBAUDIT=3DFULL</FONT>
<BR><FONT SIZE=3D2>on your run of PowerHouse.</FONT>
</P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Peter Bateman</FONT>
</P>

<P><FONT SIZE=3D2>----- Original Message -----</FONT>
<BR><FONT SIZE=3D2>From: &quot;Roughsedge, Greg N&quot; &lt;Greg.N.Roughsed=
ge@team.telstra.com&gt;</FONT>
<BR><FONT SIZE=3D2>To: &quot;PowerhouseList&quot; &lt;powerh-l@lists.swau.e=
du&gt;</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, February 17, 2003 2:41 AM</FONT>
<BR><FONT SIZE=3D2>Subject: VIAINDEX usage</FONT>
</P>
<BR>

&gt; Hi,
 &gt;
 &gt; I would like some clarification around the use of t=
he VIAINDEX clause.
 &gt;
 &gt; Background:
 &gt; Op Sys:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; O=
pen VMS V7.1-2
 &gt; Database:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Oracle RDB =
7.0-6
 &gt; Powerhouse:&nbsp; 7.10.G1
 &gt;
 &gt; I've used the CHOOSE VIAINDEX &lt;indexname&gt; cla=
use and then assumed that 
 &gt; I
 can use the SORTED clause as the records have been retri=
eved via the named index.
 &gt; The DBA's believe there is no way to force the retr=
ieval via a 
 &gt; specified
 index as the database will determine the most appropriat=
e index and use this regardless of what's specified.
 &gt;
 &gt; This equally relates to the LINK VIAINDEX clause as=
 well as part of 
 &gt; the
 ACCESS statement.
 &gt;
 &gt; My question is, can I be absolutely guaranteed that=
 the VIAINDEX 
 &gt; option
 will retrieve records using that index (and consequently=
 know the sequence of records retrieved). Or, should I not specify the VIAI=
NDEX option and use SORT instead of SORTED.

<P><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Cheers</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Greg Roughsedge</FONT>
<BR><FONT SIZE=3D2>&gt; Media Solutions - Telstra</FONT>
<BR><FONT SIZE=3D2>&gt; (Black Diamond Technologies)</FONT>
<BR><FONT SIZE=3D2>&gt; (03) 8696 5968</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<CODE><FONT SIZE=3D3><BR>
<BR>
***************************************************************************=
***<BR>
The information contained in this e-mail is confidential. <BR>
It may also be protected by legal privilege. <BR>
It is intended only for the stated addressee(s). <BR>
If you are not an addressee you must not disclose, copy, circulate nor use =
the information contained in it. <BR>
If you have received this e-mail in error please inform the sender immediat=
ely and delete it and any copies from your system.<BR>
***************************************************************************=
***<BR>
</FONT></CODE>
</BODY>
</HTML>
------_=_NextPart_001_01C2D691.A64050B0--