UBE Data

A UBE uses the BSVW to create a "picture in time", but how does it read in the data? (two questions)
1) What is the normal way JDE UBEs read in data? In large amounts (which seems correct for batch) or in small amounts or better yet in varying amounts depending on the system?
2) Is dependent on a CNC or system setting then where is it and what should it be ...what is the setting?

It definitely depends on the system and the particular business view in question.

On OS/400, there is a query optimizer that determines the best data path to be used for any SQL statement. (Generally this is the information that is saved in the SQL packages) Once the data path is determined, it depends on the sort sequence, the selection criteria, the grouping and other SQL statements to determine whether it tries to read the entire table sequentially and create an index on the fly or whether it can read an existing index to select the particular records in question. On the AS/400 you can use the database monitor to tell you what it is doing and it will suggest a new index if it can use one.

I'm sure each platform has it's own query optimizer of sorts and each will react differently.