As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
I've currently been put in charge of researching, and learning about Resource Analyzer here at our office.
One of the big questions is, what specifies the term 'request'. We have a user that has a incredibly larger amount of requests among all of the others.
I can assume what a request is, but to understand what is going on I need to know what it is physically. Is it once whenever a report is ran? Or is it whenever a table is used? Resulting in numerous user 'requests' every time a report is ran.
I passed this one around and here is what I heard from the internal: A request also referred to as procedure, could be a simple TABLE FILE or SQL Passthru to a data source, or multiple TABLE FILE, MATCH FILE, and SQL Passthru in a procedure against data sources. The data sources have to have monitoring enabled or Global monitoring can be enabled which will monitor requests against all data sources including temporary HOLD and SAVE files. Resource Analyzer also monitors the procedure that was submitted and all requests with in it.
Hope this helps.
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004