RE: Indexing an SQL view

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

Rob,

Yes and no.  On our development system I used debug to determine what indexes 
were being used or suggested.  Unfortunately I don't have authority to the 
debug command on our production box.  This is significant as the number of 
records can differ significantly (sometimes as much as 200,000,000 or so) 
between the two systems.

I used to information from the development system to create the indexes on the 
production system and run some tests.  The exact issue I had was that the 
records requested would be returned quickly but the program seemed to hang; 
presumable SQL not knowing it was done.  This will be embedded into an 
interactive program and called repeatedly so I didn't want the wait time.  
After adding the LF as Vern suggested, the wait after the records were returned 
disappeared.

My theory is that SQL was doing a table scan and kept reading the view after my 
records had been returned.  Adding the LF allowed SQL to stop after returning 
the requested records.

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
Sent: Monday, April 19, 2004 4:20 PM
To: Midrange Systems Technical Discussion
Subject: RE: Indexing an SQL view


I wonder if he ran the query over the SQL view, with the debug, etc going, 
what indexes it would have recommended?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com