Query read / cache modes are set in BW

Hi Experts,
What is query read / cache modes are set in BW in order to improve the query performance?
Thanks
Rohan

Hi
The read mode determines how the OLAP processor gets data during navigation. You can set the mode in Customizing for an InfoProvider and in the Query Monitor for a query.
http://help.sap.com/saphelp_nw04/helpdata/en/57/b10022e849774f9961aa179e8763b6/content.htm
Assign points if it helps...
Regards,
ARK

Similar Messages

No display of iview content after cache properties are set

Hello,
In an effort to improve the portal performance we activated the Iview Load Parameters(Cache level, validity, client side caching etc) and after that we are not seeing any content of the iview in the portal.
Cache level - Shared
Cache validity - 24 hrs
client side caching - yes.
All the views are pointing to KM folders.
If we change the Cache level to none then iview content is visible.
I have flushed the cache but it didnt work either.
Do we have to set any other parameters to support caching Portal KM configuration or Visual adminstrator.
Let me know how to display the content after the caching parameters are set for iview so as to improve the performance.
Thanks,
Praveen
Let me know what

Hi Praveen,
Activating Caching on KM (Navigation, for example) "works", but makes no sense. I don't know on what SP level you are, but I just checked it on SP18:
Take a Nav iView which points to - for example - /documents/xmlform. With your settings, if User A opens the iView and navigates to the subfolder "preview", and then UserB opens the iView, UserB immediately sees /documents/xmlform/preview, instead of the upper folder.
So, on one hand it "works", on the other, in many cases you might have unexpected results on KM iViews.
To improve KM performance, the first step always is to follow the performance guide: http://service.sap.com/~sapidb/011000358700004976172005E.PDF
Hope it helps
Detlev

How to set input ready query to display mode and set edit mode in WAD?

when I create A input ready query but not set query propery start query in change mode ,but I want to set this query in input ready mode ,how to set this in WAD?
hope anyone can help me
regard by
wenlong

Hi,
      You can get all the info from this thread , try it out
       WAD - set data entry mode
       Hope it helps.
Regards,
Priya.

Reading UI mode and setting field mode in WebUI

Hi
Just getting into crm and I have some questions.
How do I determine if a UI view is in create or change mode?
How can i change a fields from input fields to display fields?
The reason is I need to close 2 fields for input on the screen in change mode. But they need to be open i Create mode. It is the same view that is used for Create and Edit mode.
Hope you can hint me in the right direction.
Sonny

Hi,
I suppose you are asking for ABAP statements.
How do I determine if a UI view is in create or change mode?
data: lv_displaymode type abap_bool.
lv_displaymode = view_group_context->is_view_in_display_mode( me ).
How can i change a fields from input fields to display fields?
view_group_context->set_view_editable( ).
If the view groupcontext is not used, you can set the state manually on the HTMLB tags on the .htm page.
Finetuning can be done in the GET_I methods of the context node.
cheers Carsten

Tables in which Read mode and Cache settings are stored for Bex

Hi BI Experts,
We have a requirement for which we need to know the tables in which the read and cache modes are stored(locally and globally) when we change them in the query properties(In T code RSRT) of a query
Thanks in advance
Regards,
M
Edited by: madhu marupudi on Feb 5, 2009 5:30 PM

Hi,
Check in the following tables, these are related to Reports tables.
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSRREPDIR Directory of all reports (Query GENUNIID)
RSZCOMPDIR Directory of reporting components
RSZRANGE Selection specification for an element
RSZSELECT Selection properties of an element
RSZELTDIR Directory of the reporting component elements
RSZCOMPIC Assignment reuseable component <-> InfoCube
RSZELTPRIO Priorities with element collisions
RSZELTPROP Element properties (settings)
RSZELTATTR Attribute selection per dimension element
RSZCALC Definition of a formula element
RSZCEL Query Designer: Directory of Cells
RSZGLOBV Global Variables in Reporting
Thanks
Reddy

Cache Mode Settings Transport

Hello,
We are planning to implement the new BLOB/Cluster Enhanced Cache Mode setting. I plan to use the Query Mass Maintenance feature of RSRT to change the setting for all existing queries of an infoprovider. My question is will this action alone generate a transport? If so what objects are in the transport? Will the transport grab all the infoprovider queries?
Thanks,
TMS

Hello,
No. A transport will not be generated, all the necessary information it is as following:
As per note: 1026944 - New cache mode for BI 7.0 without directory.
Go to SE16 -> run report/table RSADMIN and verify if the data is in there.
u201CThat you can benefit from the new cache mode you have to activate it
for all your queries. Go to RSRT -> enter query -> properties ->
cache mode: 5 BLOB/Cluster Enhanced should be selected.
Or via mass maintenance (transaction RSRT -> menu "Environment" -> "Mass
Maintenance")u201D
Regards,
Diego Seben.

Cached mode on individual outlook accounts

Is it possible to have multiple exchange accounts with cached mode individually set off for group mailboxes?

Hi,
From the description, you want to set Exchange account with cached Exchange mode for some users in a user group and the rest of users set to online Exchange mode, correct?
If this is the case, I think you may consider using Security Filtering. Using security filtering, you can specify that only certain security principals within a container where the GPO is linked apply the GPO. Security group filtering determines whether
the GPO as a whole applies to groups, users, or computers; it cannot be used selectively on different settings within a GPO. See:
https://technet.microsoft.com/en-us/library/cc781988%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
If you need further assistance regarding Security Filtering, I'd recommend you post in the Group Policy forum:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverGP
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Cache mode settings

Hi all,
My requirement is i have change the cache mode settings of particula query from cache mode 1( Main Memory Cache Without Swapping ) to cache mode 3 (Persistent Cache per Application Server).
Here my question is can i transport these settings to the production system or should i do this cache mode settings in my production system itself.
Thank you very much for your suggestions.
Regards
Prasad

Hi ,
After u save the settings in the cache mode u can very well
transport it to the production system
Assigning Points is the way of saying Thanks in SDN
Regards ,
Subash Balakrishnan

Query read mode-Cache mode

Hi,
Can u explain me the functionalities of the options:
A-Query to read all data at once
X-Query to read data during navigation
H-Query to read when u navigate or expand hierarchies
I am not clear of the diff. bet. the X,H options....
<b>Cache Mode:</b>
0-Cache is Inactive
1-Main memory cache without swapping
2-Main memory cache without swapping
3-Main memory cache with swapping
4-Persistent cache for each application server
5-Persistent cache across each application server
<b>Optimization Mode:</b>
0-Query will be optimised after generation
1-Query optimization with individual periods in days
9-Query optimization inactive
Can u explain these functionalities in detail...
Max.points will be assigned

HI,
PLease check this..
1.      Query to be read when you navigate or expand hierarchies (H)
The amount of data transferred from the database to the OLAP processor is the smallest in this mode. However, it has the highest number of read processes.
In the following mode Query to read data during navigation, the data for the fully expanded hierarchy is requested for a hierarchy drilldown. In the Query to be read when you navigate or expand hierarchies mode, the data across the hierarchy is aggregated and transferred to the OLAP processor on the hierarchy level that is the lowest in the start list. When expanding a hierarchy node, the children of this node are then read.
You can improve the performance of queries with large presentation hierarchies by creating aggregates on a middle hierarchy level that is greater or the same as the hierarchy start level.
       2.      Query to read data during navigation (X)
The OLAP processor only requests data that is needed for each navigational status of the query in the Business Explorer. The data that is needed is read for each step in the navigation.
In contrast to the Query to be read when you navigate or expand hierarchies mode, presentation hierarchies are always imported completely on a leaf level here.
The OLAP processor can read data from the main memory when the nodes are expanded.
When accessing the database, the best aggregate table is used and, if possible, data is aggregated in the database.
       3.      Query to read all data at once (A)
There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
Compared to the Query to be read when you navigate or expand hierarchies, the setting Query to read data during navigation only effects performance for queries with presentation hierarchies.
Unlike the other two modes, the setting Query to Read All Data At Once also has an effect on performance for queries with free characteristics. The OLAP processor aggregates on the corresponding query view. For this reason, the aggregation concept, that is, working with pre-aggregated data, is least supported in the Query to read all data at once mode.
We recommend you choose the mode Query to be read when you navigate or expand hierarchies.
Only choose a different read mode in exceptional circumstances. The read mode Query to read all data at once may be of use in the following cases:
      The InfoProvider does not support selection. The OLAP processor reads significantly more data than the query needs anyway.
         1.      Cache is Inactive (0)
The cross-transactional cache is deactivated.
The following modes are possible for the active cache: The cross-transactional cache is activated.
       2.      Main Memory Cache Without Swapping (1)
The cache data is stored in the main memory. When the cache memory has been exhausted, excess data is removed according to the LRU algorithm, i.e. deleted from the memory. When a query is subsequently requested, the result is read from the InfoProvider once again.
       3.      Main Memory Cache with Swapping (2)
The cache data is stored in the main memory. When the caching memory is used up, the excess data is written to a background and can be loaded back into the cache memory when making another request.
After query-relevant data has been loaded again, the background store can no longer be used.
       4.      Persistent Cache per Application Server (3)
The cache data is stored persistently as a database table or as a file in a directory attainable from the application server. We recommend that you choose a directory that is proximate to the application server.
When you save the cache data in a database table this puts a strain on the database. However, it is also then quicker to access uncached data in the database. In comparison to storing data in, for example, a star schema (see InfoCube), fewer tables are read and fewer indexes are accessed.
       5.      Cross-Application Server Persistent Cache (4)
The cache data is stored persistently as a cross-application server database table or file in a file system in the network, accessed from the application server. In this mode there is no displacement of data and no restriction on memory size. More space is required but this method also saves time.
¡        Database table: Strain is put on the database instance for the table.
¡        File: Strain is put on the network node operating system for the file.
¡        In addition, the application server that calculates the data and network communication has to be taken into account with both storage types.
If you do not make any other settings the OLAP processor determines the optimal initial size of the table SP, that is the memory structure in which data is held and processed in the OLAP processor (see Cache Structure). This is done after the first execution and again after a period of 31 days since the last optimization. It automatically generates a report afterwards.
In the Query Properties dialog box in the Query Monitor you can implement, modify of deactivate this function. Choose one of the following options:
·        Query is optimized after generation (0)
·        Query optimization with individual periods in days (1) Here you can determine the optimization period yourself.
·        Query optimization inactive (9)
Hope this helps..
Bye,
Shashikanth.

Cache mode for specific query

Hello BI guys,
This is Calvin from Korea. We are implementing BI 7.0 and have some severe performance problem. For some queries they don't use cache mode, even though the global cache are used.
When I checked these kind of queries by performance information in RSRT, I got following message,
===================================================
InfoProvider Definition                |
===================================================
ZCOAG0101                             | At Least One InfoProvider Not InfoCube
ZCOAG0101                             | Not All InfoProviders Can Use Aggregates
===================================================
===================================================
Query Definition                        |
===================================================
Read Mode                               | Do Not Read upon Drilling Navigation/ Hierarchy
Query Cannot                           | Use the Cache Reason
Cache Mode                             | Cache Not Used By Query
Cache Update                           | Query Does Not Use Delta Process
Type of SP Grouping for Delta Cache Process | No Provider Partitioning
===================================================
And after run of technical information,
===================================================
Cache-Relevant Data                 |
===================================================
Query Can Use the Cache         | No
Query Generation Time              | 2007.09.17 15:05:31
InfoProvider - Last Data Change | 2007.09.16 21:43:11
Last Load of Exchange Rates     | 2007.07.13 15:01:48
===================================================
Does anybody have ideas for this problem?
Your help will be highly appreciated and get points!
Thanks in advance
Regards,
Worried Calvin

hi Dong Suk Choi ,
the technical information which u have furnished clearly says that the settings
that u have made does not enable the query to use cache.
u can enhance cache by customizing the inforovider or in the transaction rsrt
even if the concerned query does not have required settings u can make them in rsrt tcode.
goto rsrt set the read mode and cache mode as u wish, however default settings would give optimum performance.
and run the query.
in the rsrt screen a push button execute + debug enter that and unmark the check box do not use cache.
hope this helps.
reward points if helpful.
bye.
under properties tab u can give the query settingMessage was edited by:
        Rakesh Elangovan

Query Read mode

HI Experts,
What is QueryReadMode? In which Scenario we have to use QueryReadMode?
1.In which situation we have to create Aggregates and how do u know weather the cube has Aggregates or not?
2.In which situation we have to create Indexes and how do u see the indexes bitmap r Btree explain me Briep
3.In which situation we have to do Compression?how can i delete requests and how can i delete records from single request & from Multiple requests based on the fixed value.
4.In which situation we have to create Partitions and how do u know weather the cube has partions or not?
5.4.In which situation we have to create LINE-ITEM Dimentions.
please any body explain me these topics with example...................
what is BW STATISTICS explain me brief......
THANKS IN ADVANCE,
PriyaKodali

HI
What is QueryReadMode?
We use the query monitor to test or regenerate queries and query views, and to check or change query properties. With the query monitor you have the option of displaying technical information about queries
Query Properties.
In the Query Properties window of the Query Monitor, we can configure settings for the Read Mode, Cache Mode etc.
The read mode of a query determines how often the OLAP Processor retrieves data from the database during query navigation. The read mode contains three types of read processes:
Read all data (setting A: Query to Read All Data At Once)
Reread the data (setting X: Query to Read Data During Navigation)
Reread the data when expanding a hierarchy (setting H: Query to Read When You Navigate or Expand Hierarchies)
WE USE T-CODE RSRT.
(H) u2013 Query to read, when you read or expand hierarchies: In H mode, the detailed information within the nodes and sub-nodes of a hierarchy are read on demand (i.e., when you expand a hierarchy node). The amount of data transferred to the OLAP processor is the least of all the three categories. The downside is that the number of database reads increases as you keep expanding hierarchy nodes. SAP recommends setting queries to the H read mode. This is based on the empirical evidence of the relative performance of queries set to each of these modes.
(X) u2013 Query to read data during navigation: In this mode, data are requested by the OLAP processor as
dictated by every navigational step. The difference between X mode and H is that in the case of hierarchies, all the data on a leaf level are completely retrieved by the OLAP processor.
(A) u2013 Query to read all data at once: There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
What Is An Aggregate?
An aggregate stores the dataset of an InfoCube redundantly in a summarized form. In this instance, summarization means the condensing of the original fact table of an Infocube to an aggregate table. This table no longer contains certain characteristics of the Infocube and has been summarized across attributes, or to characteristic values, or a hierarchy level.
The summarization enables you to access the data of an InfoCube quickly when reporting. Aggregates are, therefore, tools for enhancing performance.
Aggregates are created from logical data packets (requests). You can distinguish between the processes of filling and rolling up
http://wiki.sdn.sap.com/wiki/display/BI/Aggregates--SAPBWQueryPerformance
3. In which situation we have to create Indexes and how do u see the indexes bitmap r Btree explain me Briep
Bit map and B-tree index - It is related to Cardinality.
Cardinality means no. of predefined options for perticular Info Object.
e.g *** of person - Male or Female - we have only two options - so it will be considered as Low Cardinality.
Document Number : their can be many document numbers depends on the no. of users. so it is considered as high cardinaltiy
If low cardinality is their, Bit map index is used.
If high cardinalty is their, B tree index is used.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b28d18-f383-2c10-a780-a52349715b54?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21eb47446011d189700000e8322d00/frameset.htm
4. In which situation we have to do Compression?how can i delete requests and how can i delete records from single request & from Multiple requests based on the fixed value.*
Compression improves Performance Tuning as it removes the redundant data. This improvement in the performance can be checked by RSRT and running the query with compression & without compression.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09b7019-4885-2e10-e2b8-fe1fef0643db?QuickLink=index&overridelayout=true
deletion of compressed cube data
Delete compressed request from cube.
5.In which situation we have to create LINE-ITEM Dimentions.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/005f3197-d3da-2e10-1a94-a5c62342f2aa?QuickLink=index&overridelayout=true

Precautions to be taken while changing the Query read mode in PED system

Dear Experts,
I got a task to change the Query Read mode for more No. of queries in Production system directly itself.
Request you to let me what are the steps to be followed/precautions to be taken while changing the Query Read mode in PED.
one more doubt regarding this.....If i plan to change the Read mode of Query say Q1, how can i come to know weather the Q1 is executing or not executing by that time.
Thanks in advance for valuable response.
Thanks & Regards,
Ramesh - Kumar

Hello,
You can change the query read mode in transaction 'RSRT', here are the steps:
1) Access transaction RSRT and enter the query name
2) Select the 'Properties' option
3) Un-check the 'Info provider' setting next to the 'Read mode' --> This enables you to change the read mode of the query --> Execute
4) Choose the option 'Generate Report' to re-generate the query program
Hope this info helps.
Thanks
Bala

Outlook 2013 set cached mode "Mail to keep offline" to All for existing Outlook profiles via GPO or registry changes

We recently migrated from Office 2010 to Office 2013. An annoying change is Outlook's "Use Cached Exchange Mode" setting that changes the previous setting of all email to partial email based on how old emails are. This is confusing
for end users because if they have a 1GB mailbox size limit and they look at the properties of their mailbox, it shows the cached amount which is always then less than the full amount. While they have a 1GB limit, the properties of their mailbox
might say 700MB because that's all that is cached, but meanwhile they can't send because they are actually over 1GB on the server side.
I want to set this cache setting to "All" for EXISTING profiles and new profiles. I think I can do it with GPO for new profiles, but I don't see a way to set it for existing profiles. I assume I have to do this with a registry setting.

Hi,
The cached mode Sync Slider setting is maintained in the Outlook profile settings in the Windows registry. If you want to administer this setting via group policy, you can use the group policy templates, which are available from the Microsoft Web site. The
group policy template files are Outlk15.admx and Outlk15.adml. If you use group policy to manage this setting, the following registry data is utilized by Outlook.
Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\Cached Mode
DWORD: SyncWindowSetting
Value: integer value (Decimal) specifying the number of months (use only the following values)
0 = All (entire mailbox)
1 = One month of mailbox items
3 = three months of email items
6 = six months of email items
12 = twelve months of email items
24 = twenty-four months of email items
Refer from
http://support.microsoft.com/kb/2733062
Hope this will be helpful for you.

Design Studio behaviour according to query read mode property

How does Design studio behave according to the Read Mode property set here in SAP : (RSRT transaction, query properties) :
It seems like Business Objects tools (Analysis, Webi, …) don’t behave in the same way according to these properties, even if they all use the BICS protocol. What is Design Studio behavior?
In fact, I’ve tested 2 queries, both with many free characteristics (because I swap dimensions in my charts thanks to scripting), but
one with default values on CALMONTH (12 last months),
one with a customer exit variable that I set with the exact same values (12 last months),
when analysing the behaviour in RSRT I see that choosing the H option will add a where clause to the 1st query, “SQL” seems then identical in
both cases, and statistics are the same (see below). With A option, the 1st query statistics are worse and the 2nd one statistics stay the same.
So knowing if Design Studio takes this option into account is important.
At the beginning, I was expecting that Design Studio would retrieve more data cells with the default values query (all months are retrieved and some kind of local filter is applied to display only the 12 last months) than with the variable query (only the 12 last months areretrieved, no need to apply any additional filter, and if the end user wants some other months then the script has to update the variable, and waiting time would then be worse). I guess it could be true with read mode option set to A.
I know that some answers have been given on this subject, saying that even updating only default values thanks to the filter panel was implying a roundtrip to the back end, but I can only understand this statement if H option is taken into account by Design Studio…
I would like to better understand exactly what is Design Studio behaviour, and if there is any benefit to use variables to set queries filters (filter panel usage is not straightforward then), or if default values and native filter panel usage is ok as it has the exact same consequences on data volumes retrieved, back end roundtrips and query performances.
I guess that the answer depends on the capacity Design Studio has or not to take the Read Mode option into account.
Thanks in advance!

So DS takes this property into account.
If the read mode is set to H, then playing with the filter panel has the same consequences on data read and data transported statistics (safety belt limit statistic too) than the effects BEx variables would have.
So
- If, as I do, you hate the look of the prompts screen
- and/or if you find that using BEx variables is not optimal for filter panel management (because if you use the same datasource for the filter panel as for the chart, values appearing in the filter panel will be filtered according to the BEx variable, then the end user can't select a value out of this restricted context)
- and/or if you can afford a first run of the query with some default values instead (i.e. if your queries are performant)
then I find it more user friendly to offer your end users to bypass this ugly prompts screen and to directly access a beautiful dashboard based on some default values, that may be interesting to them, values that they can change in a second time having access to the whole list of values in the filter panel... Furthermore, it may take the same time, with performant queries, to set the prompts than to run the query with some default values and to change them thanks to the filter panel.

Cache mode query overview.

Hi guys,
In the Early Watch report I have an overview on how many queries use a certain cache mode (chapter 12.1), but it doesn't show which queries they are.
I have 4 queries with cache switched off and I'd like to know which ones they are. Any idea if there's a table/trx somewhere where I can find this information?
Thanks.
Eduard

hi Eduard,
yes, i added the info later just in case you want go by individual query, RSRT won't serve a mass checking.
please close the thread and reward helpful answer if RSRREPDIR serve your purpose.
hope this help.

Query read / cache modes are set in BW

Similar Messages

Maybe you are looking for