with Tags:
limit
X
X
The Preset Limit 5000 Was Exceeded
Any customer with a large database has run into the famous preset limit of 5000 was exceeded error message. There are a few ways around this message, increasing the size of the fetch stop limit. This workaround will not always work as it is a global setting and who wants large result sets across all applications for all users. Another option is to decrease the size of the result set itself by adding further information to filter information as needed. Good option but it we don't always have the option to filter out information into... [More]
Tags: exceeded. prefetch limit |
BiLog: Limits...QBR Record Limits
I need to set limits when faced with these. Knows as Fluffernutters, smooth, decadent peanut butter and sticky marshmallow topping on plain white bread form the ultimate comfort sandwich. With a cold glass of milk, the number I can toss down is crazy high. You may also need to stop your users from over-indulging by setting records limits when they create Ad Hoc or QBR (Query Based Reports.) The creation process of ad hoc reporting is where users select the fields, application query, sorting and grouping that they... [More]
Tags: performance ad_hoc maximo limit ibmeam report bilog qbr |
