RE: Create View

Marco

Each LF adds some overhead - first of all is the space it takes. And then there 
is the time to maintain an index, if the LF has one. 

Now I'm going to toss in another unknown - are the SST keywords processed as 
each record is added, or are they run when the record is retrieved? If the 
former, are the values stored in memory, possibly increasing the size of the LF?

HTH
Vern

-------------- Original message -------------- 

> In my SQL ignorance I made LF = VIEW... 
> 
> And I WAS thinking VIEWs as a more efficient way to access data instead of 
> DDS. 
> 
> I can now choose between: 
> 
> UDTF, LF or Trigger. 
> 
> Creating 200 LF over a single phisical is something I never done and I don't 
> know if there is a 
> performance issue. 
> 
> UDTF, nice approach since I have a single object for multiple data libraries. 
> 
> Trigger, 200 phisical files to write/update/delete 
> 
> I think trigger is the light one. 
> 
> Thanks 
> Marco 
> 
> --- Vernon Hamberg wrote: 
> 
> > A further consideration - you mentioned the performance issue in reply to 
> > the post about UDTFs - but views are also run at the time you use them - 
> > the SQL SELECT that is used to define the view is run dynamically, so 
> > performance is an issue there, as well. Whereas the LF access path is 
> > maintained and can even include an index. 
> > 
> > Maybe? 
> > 
> > Vern 
> > 
> 
> 
> 
> 
> ____________________________________________________ 
> Start your day with Yahoo! - make it your home page 
> http://www.yahoo.com/r/hs 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>