Flat dimensions and retrieval performance

Hello,How would you improve reporting performance in a database containing a flat dimension with 20.000 members?And is it possible to use 'Navigate without data' in Analyzer 5 for Windows?Thank you very much

You have to remember with an Analyzer view when the retrieval request goes to Essbase it spools the "entire retrieval" and then sends it back to Analyzer. So your issue with long response times is probably on the Essbase side and you might have to optimize your database. Also how large is your Analyzer view you are working with? Your response time is directly to this also.In regards to the "Navigation without Data" and Analyzer I do not think this is possible. I tried to do the same thing and found that even though the database is available to me through the Admin Tool the database is not available as a selection in the Windows client. I will look into this further and get back to you.John RussoSr Staff ConsultantHyperion Solutions-Essbase & Datawarehousing Practice

Similar Messages

Creating Flat Dimensions in AWM

Hi,
We have a proposed cube structure with 8 dimensions (apart from the TIME dimension) as follows:
3 Dimensions have a Level-Based Hierarchy
2 Dimensions have a Value-Based Hierarchy
3 Dimensions are flat with no levels or hierarchy.
We are using Oracle Analytic Workspace Manager v10.2.0.3.0A for formulating the cube structure.
We want to introduce a top level “All” column in all the dimensions so as to facilitate analysis of data by eliminating the dimension itself (by selecting its “all” level). Inclusion of such a top level “All” level seems intuitive for Level based and value based hierarchy as we can just introduce the new level.
However, we are not sure of how we can create a “flat” dimension and also have the top level “all” column in it by using AWM. Any insights on the process of creating a flat dimension in AWM would be much appreciated.
Thanks,
Piyush

I am not sure what the problem is? You simply create a dimension with two levels:
- Top level
- Base level
Assign an 'All Members" description to the top level and all all other members are assigned to the base level.
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Infocube line item dimension and performance optimization

Hi,
I remodelled an infocube and line item dimension contains only one characteristics set as line item dimension.
previously the dimension as one characteristics but it wasn't set as line item dimension.
and when I checked the SAP_INFOCUBE_DESIGNS from SE38 it looks ok.
/SAP/CUBE /SAP/CUBE3 rows: 8663 ratio: 3 %
After setting it as line item the rows is now minus but it is showing red which means that there is problem with the dimension
/SAP/CUBE /SAP/CUBE3 rows: 1- ratio: 0 %
Its this a performance problem since it is showing red.
thanks

hi,
No,its not performance issue.
for a dimension to be line item dimension...the dimension size shouldn't be more than 20% size of the fact table size.
when a dimension is set as line item dimension,the regarding SID will be placed in Fact Table,but not the DIM ID.
may be that is the reason when your dimension is not line item dimension,it shows the number of rows and when it is made line item dimension,its not showing any rows and the ratio also null.
hope this is clear for you.
Regards
Ramsunder

Improve Performance of Dimension and Fact table

Hi All,
Can any one explain me the steps how to improve performance of Dimension and Fact table.
Thanks in advace....
redd

Hi!
There is much to be said about performance in general, but I will try to answer your specific question regarding fact and dimension tables.
First of all try to compress as many requests as possible in the fact table and do that regularily.
Partition your compressed fact table physically based on for example 0CALMONTH. In the infocube maintenance, in the Extras menu, choose partitioning.
Partition your cube logically into several smaller cubes based on for example 0CALYEAR. Combine the cubes with a multiprovider.
Use constants on infocube level (Extras->Structure Specific Infoobject properties) and/or restrictions on specific cubes in your multiprovider queries if needed.
Create aggregates of subsets of your characteristics based on your query design. Use the debug option in RSRT to investigate which objects you need to include.
To investigate the size of the dimension tables, first use the test in transaction RSRV (Database Information about InfoProvider Tables). It will tell you the relative sizes of your dimensions in comparison to your fact table. Then go to transaction DB02 and conduct a detailed analysis on the large dimension tables. You can choose "table columns" in the detailed analysis screen to see the number of distinct values in each column (characteristic). You also need to understand the "business logic" behind these objects. The ones that have low cardinality, that is relate to each other shoule be located together. With this information at hand you can understand which objects contribute the most to the size of the dimension and separate the dimension.
Use line item dimension where applicable, but use the "high cardinality" option with extreme care.
Generate database statistics regularily using process chains or (if you use Oracle) schedule BRCONNECT runs using transaction DB13.
Good luck!
Kind Regards
Andreas

Difference in WS performance between Search and Retrieve operations?

All,
We are currently working on a new repository and planning to use MDM webservices on top of that repository for searching and retrieving the data.
Now I'm curious about the difference in performance between the Search and the Retrieve operations and also within the Retrieve operation, between the different identification methods (internal ID, auto ID, remote key, unique field and display field).
Because in the webservices guide is stated that the identification methods are listed in order of best performance, but what are these performance differences between these methods (e.g. a retrieve on internal ID is x times faster than a retrieve on remote key which on his turn is x times faster than a retrieve on display fields which on his turn is x times faster than a search operation on same display field).
Of course the performance depends on lot of other things as well, but I just want to get a feeling on the performance related to eachother (keeping all other variables that can influence the performance the same!)!
I hope that any of you has experiences with all possibilities and can share performance measurements between the different operations related to eachother. Thanks in advance.
Regards,
Marcel Herber

Hi,
Did you implment Webservices in your site.
We are also having a similar scenarion where we have to serach a Records in MDM from SAP PI based on the certain criteria. I am concerned about the SAP MDM performance , since we are having heavy amount data being loaded every 30 minutes.
Please let me know the performace aspects of using Webservices.
Thanks
Ganesh Kotti

Adjusting Dimensions via Planning Performance Settings and getting error

On 9.3.1 Planning and doing some clean-up of an old application. In Dimensions, under the Performance Settings tab when I try to move a member higher or lower past the 'Years' dimension I get the error:
An error occurred while processing this page. Check the log for details
Ok what error log? I went through all and do not see exactly the problem
JTS

John,
Thanks I adjusted regedit and restarted all services. Here is the error I got when trying to move dimension members down on the performance settings tab. If I am reading this correctly the first error in RuntimeException appears to be security related?
java.lang.RuntimeException: Consolidtaion operator for all plan types on root dimension members must be set to Ignore.
     at com.hyperion.planning.db.HspDEDBImpl.saveDimension(Lcom.hyperion.planning.sql.HspDimension;Lcom.hyperion.planning.sql.actions.HspActionSet;I)V(Unknown Source)
     at com.hyperion.planning.db.HspDEDBImpl.setDimPositionforPlanType(IIII)V(Unknown Source)
     at com.hyperion.planning.HyperionPlanningBean.setDimPositionforPlanType(III)V(Unknown Source)
     at HspPerformanceSettings.handle(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
     at HspPerformanceSettings.doPost(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

Possible to limit dimensions and measures when creating presentations?

We are trying to use OLAP/BI Beans to add BI functionality to our next-generation data warehouse application. This application has its own security framework, with the ability to define permissions/privileges for objects. We need to integrate BI Beans/OLAP with this security framework.
One of the things we need to do is control which OLAP objects (like dimensions and measures) are available to a given user in the Items tab when creating a presentation. For example, user A might see dimensions Alpha, Bravo and measure Charlie, while user B might see dimensions Delta, Echo and measure Foxtrot.
We need to be able to apply these dimension/measure restrictions without using different Oracle users, with each having access only to their own OLAP objects. Our data warehousing application does not use Oracle and Oracle users to control security; it has its own internal frameworks for privileges/permissions. We therefore need to find a way to restrict access to OLAP objects in some programmatic way.
Here's an example of how this might work:
- I am a clinical analyst. I sign on to the data warehouse application. The data warehouse knows that as a clinical analyst, I have access to a certain list of objects and functionality across the application. One of the apps I have privilege to is the BI Bean Presentation Creation Application, so I click the menu to bring this up. I can now create BI presentations, but since I am a clinical analyst my list of available dimensions and measures do not contain any of the G/L, payroll or other financial OLAP objects.
- If I signed onto the data warehousing application as a different user, one that has a financial analyst role, I might see a different set of OLAP objects when I run the presentation application application.
So what we need is some API way to specify which dimensions and measures are available to a given user when they launch the presentation wizard. I've been digging through the BI Beans help and javadoc and have found a few things, but they aren't what I need.
Here's what I found:
- setItemSearchPath: this allows you to specify which folders are to be displayed. We want control at the OLAP object level, not at the folder level, so this doesn't work for us
- setVisibleDimensions: this controls which dimensions are available in the Dimensions tab, not which dimensions can be selected in the Items tab. Doesn't work for us
- setDimensionContext/setMeasureContext: These might work for us but I haven't been able to get them to retrieve anything yet. It also seems to me that these might set which dimensions/members are initially selected in the Items tab, not the list of dims/measures that are available for selection.
Any assistance on this matter would be greatly appreciated.
s.l.

Reply from one of our developers:
The get/setMeasureContext and get/setDimensionContext methods are currently only used by the Thick CalcBuilder (in a few limited scenarios) and cannot be used "to scope the dimensions and measures listed in Query and Calc builder based on user access rights".
The scoping of dimensions and measures based on user access rights should be performed at the MetadataManager/Database level.
This may change going forward as the real issue here is the static nature of the metadata and a general issue with the GRANT option within the database. So from the database perspective it is not possible to grant select priviledges on a single column of a table.
The metadata issue is more complex as the OLAP API reads the metadata only once on startup of a session. The list of available measures is based on the GRANT priviledge, so for relational OLAP this limits the data scoping capabilities. In 10g, the metadata for AW OLAP becomes more dynamic and contained and read directly from the AW. Therefore, with an AW OLAP implementation with 10g it could be possible to scope boht dimensions and measures quickly and easily.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

Any way to use OBDC in SAP to access MySQL DB and retrieve data

I'd like to logon to an external MySQL DB (can de done easily enough with PHP)   but I'd like to do it with ABAP if possible.
Connecting via OBDC I should be able to retreive the data from the DB and then use it in my SAP application.
Some databases will allow connection via
EXEC SQL.
connect to :dbsid
ENDEXEC.
EXEC SQL.
    set connection :dbsid
ENDEXEC.
EXEC SQL.
open xxxxxxx for
select
...... data from external DB
from tablespace in external db
ENDEXEC.
do.
EXEC SQL.
    fetch next XXXXXX into
           :db_table_field, .... etc
             ENDEXEC.
if sy-subrc ne 0.
    exit.
endif.
insert table int_sap_table.
enddo.
EXEC SQL.
close XXXXXX
ENDEXEC.
If you can make this type of stuff work for a MySQL DB i'd appreciate the answer.
Using PHP has a drawback as you need to have it installed on the front end PC and run in Foreground.
The EXEC SQL commands run in batch which is what you need if you are talking about 100,000's of records from an external DB.
Cheers
jimbo

Hi Graham
Currently it doesn't seem to support MySQL.
Now that SAP has taken over again the development of MAXDB I can't see it providing direct MySQL to SAP functionality.
MAXDB is available but that would mean changing the entire architecture and we don't want to do that.
I think probably the best route to go would be to create a BAPI which is capable of performing a logon to the remote MySQL DB server, get the data and either send it back as IDOCS, an external flat file, or as an internal table depending on the volume of data to be retrieved.
The good thing about MySQL is that the command line interface makes logging on and retrieving data quite simple.
This data is actually wanted in a BI / BW system to provide for a number of business proces analyses.
I did think abut using "Web Services" but the data retrieval will essentially be done offline.
There is no requirement currently for transferring data FROM SAP back to the MySQL database ( although if you've ever dealt with top level management you know how quickly developments can change).
PHP for all it's drawbacks is the really easy way - but we'll have a problem doing this in background from the SAP servers. For foreground tasks it's a real doddle if you have php on your front end.
for example
<?php
$username = "pee_wee";
$password = "let_me_in";
$hostname = "localhost";        */* IP address of remote DB server */*
$dbh = mysql_connect($hostname, $username, $password)
or die("Unable to connect to MySQL");
print "Connected to MySQL<br>";
// you're going to do lots more here soon
mysql_close($dbh);
?>
Batch mode also seems OK also from the documentation
http://dev.mysql.com/doc/refman/5.1/en/batch-mode.html
so running an ABAP which can issue system commands (readily available) should work in theory provided the SAP server can connect to the remote MySQL server machine.
Thanks for your suggestions however
Cheers
jimbo

Part 2: Flat files and Business Contents: Any issues with this scenario?

I will appreciate some clarification on the some points made in response to my previous post "Flat files and Business Contents: Any issues with this scenario?"
1.
" ...youd better analyze those cubes for data redundancy and presence of data youll never use. " I will appreciate some clarification on the type of analysis you are referring to. Examples will help.
2.
"If you want to combine several found IOs in your custom dataprovider, then again you must know (or figure out) relationships between these IOs." I will appreciate some clarification on the type of relationship you are referring to. Examples will help.
3.
I am a bit confused with "..include into ODS structure ALL fields required for the cube" but you also noted noted that "...except navigational attributes and chars and KFs that are going to be determined in TRs or URs."
If you exclude ALL these, haven't you excluded all the fields you included in the ODS structure?
4.
"Consider carefully the ODS key fields selection. Their combination should not allow data aggregation that you dont need."
I may be missing the point here, I understand that you need to select the fields which will form the unique ID for the records in the ODS under the Key Field (please correct me if I am wrong with the purpose of the Key Field), but I don't understand the discussion of "aggregation" in the context.
Thanks in advance

Hallo
I try to give some exaplanation based on the previous answer.
1. Data redundancy - make sure you do not store the same information. does not make sense to have data redundanty across you Data Warehouse. this is also a cost. just sotre the same information one time if you get all what you need.
2. whatwhever you build you dp, which consist of IO, you need to know with kind of relation (1:1 or 1:n - n:n and so on) exist between them. that will help you when you model you infoprovider. For example I would never pit togheter IO (n:m) in the same dimension if you expect an high number of cardinality. Sometime an IO can be an attribute of another one (depend on relation. For example
Business Partner and his Address. Usually you have a relation 1:1, in this case address is an attribute of BParten and store it in the Masterdata instead then DP
3. Sometime when you load from ODS to CUBE, you can fill some IO (which are in the infocube and not in the ODS)through ABAP routine in TR-Start Routine of Update Rule. Does not make sense to include these IO in the ODS as they are NULL or Blank (the deault value). This can happen when for example, you first load in the ODS (Price and Quantity) and then you calculate Sell price later (Price * Quantity). of course it could be doen also in the Bex. Depends on other factors (Performance - Loaidng -Sizing)
4. Make sure that the KEY definition of ODS is accordingly to the data otherwise you will aggregate the data and later maybe if you need the detail you miss it.
for example: customer - product - Distr Chan - Sell Price
if each Customer can buy each product for any Distrution Channel, then when you build your ODS(Customer - Product and Distribution must be KEY) otherwise (if you have only Customer - Product KEY for example) you will lose the details for Distribution Channel.
I hope eveyrhting is clear
Regards
Mike

Improving retrieval performance of essbase server in unix environment

HI,
Our production environment is unix system. can any one suggest settings which impact the retrieval performance and how to do these settings in unix environment.

Naveen,
For retrieval perfomance, Increase the retreival buffer size.
Default is 10 KB for 32 bit platforms and 20 KB for 64 bit.
make it 100 KB.
2. if the data block size is large ,and you are retriving cells across several blocks
set VLBREPORT true in the essbase.cfg configuration file
NOTE: this will increase the retrival process but , its applicable to the outlines which does not include dynamic calcs.
3. If the format of your reoport is of not much importance. group dense dimension in colums and groping sparse in rows ,this would be faster.
4. An applicaion/database does has a limt on its memory consumption.
So, RAM is the key for the speed.
Best part is that ,as you have UNIX operating system ,addressabe memory in your case is 3.9GB(which is very good) unlike 2 GB in case of windows.This is per application.
Sandeep Reddy Enti
HCC

Line item dimensions and cardinality?

hi all,
how to identify nor use the cardinality relationship as well as the line item dimension?
can anyone explain me about it. since i am trying to create an multi provider which enables to fetch data from 3 ods.
regds
Hari Chintu

Hi,
Below is some useful information on Line item dimension and high cardinality.
These concepts hold good for Cube design only, coming to ODS, these dont help you. As ODS is nothin but a flat structure, we do not have the facility of Star schema. Reporting on ODS can lead to performance issues, it is better to load data from ODS into Cube and then have a multiprovider on them instead of having it on ODS.
Hope this helps.
Regards,
Kalyan
Use
When compared to a fact table, dimensions ideally have a small cardinality. However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic document is used, in which case almost every entry in the fact table is assigned to a different document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension. In BW 2.0, this was also known as a line item dimension, in which case the characteristic responsible for the high cardinality was seen as a line item. Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
       1.      Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
        When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
        A table- having a very large cardinality- is removed from the star schema. As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
       2.      High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above. Be aware that a line item dimension has a different meaning now than in SAP BW2.0.
However, we recommend that you use ODS objects, where possible, instead of InfoCubes for line items. See Creating ODS Objects.
Activities
When creating dimensions in the InfoCube maintenance, flag the relevant dimension as a Line Item/ having High Cardinality.

ASO Cube, increase aggregation or improve retrieval performance

We've been using the essbase cube to create report using OBIEE.
When we use level-0 member filter, it takes quit a long time to get the results.
Any idea to improve the performance?
Is there anyway that I can improve the number of aggregation occurs at a time? Thank you.

What doesn't make sense to me is you don't need aggregations on level zero members as that is where the data is stored. I'm guessing oyu mean level sero members of one dimension and higher level members of other dimensions. Are those other dimensions dynamic or stored? Do you have a lot of calculations going on that are being retrieved? Have you materalized aggregations on the cube?

What is line item dimension and cardinality in BI 7.0

Can u plz suggest me what is line item dimension and cardinality in BI 7.0..
Thanks in advance.
Venkat

Hi Babu
Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
¡ When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
¡ A table- having a very large cardinality- is removed from the star schema. As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above. Be aware that a line item dimension has a different meaning now than in SAP BW2.0.
SAP recommends that you use ODS objects, where possible, instead of InfoCubes for line items.
Hope this helps.
Plz check these links:
SAP Help:
http://help.sap.com/saphelp_nw04s/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Thanks & Regards
Reward if helped
Edited by: Noor Ahmed khan on Aug 5, 2008 2:36 PM

Bi beans- i can't see my dimensions and measures!!!!

hye! i have cretaed 2 cubes in oem (rolap)...
i inserted some information in the tables (some tables are empty)...
anyways...
now, when i try to connect to olap from jdev it's working!!!!!
but, when i try to make a graph or anything a can't see any of the stuff that i made in oem:::
bi designer---new graph---on the step 2 of 8 the only things available are:
- financial data
- sales performance data
(dimensions and measures from bibdemo i think....)
where are my dimensions and measures???????????
i tryded to copy objects from remote catalog... and make new catalog connection... with bibcat but it's not working!
but i think this was not the thing to do!!!!!
what shoul i do next??????
help asap!!!! plezzzz!!!!

Did you execute the following after defining your OLAP Catalog metadata in OEM?
EXECUTE CWM2_OLAP_METADATA_REFRESH.MR_REFRESH;
The CWM2_OLAP_METADATA_REFRESH package provides procedures that refresh the cached metadata tables used by the OLAP API / BI Beans. This step is required to 'see' your ROLAP cubes. Unfortunately, OEM does not execute this package. It must be done manually.
Please refer to the OLAP Application Developer's Guide 9.2.0.4.1 or OLAP Reference 9.2.0.4.0. You can find them on OTN at the OLAP site:
http://www.oracle.com/technology/products/bi/olap/olap.html

Flat File and IDoc

Hi,
Is it possible to read a flat file and create the sale order through IDoc. Can i do this by DOC_INBOUND_FROM_FILE without XI?? What file format should i pass??
Regards,
Kit

Hi ,
you can create Sales order through IDoc. IDOC_INPUT_ORDERS
At a high level, the IDOC processing executes in the following manner:
1.     Interpret IDOC header segments and captures organizational, customer master and purchase
               order header details. Performs user exits for each segment to process customizations to data
                 processing.
2.     Interprets item level segments and captures item level details like material information. Again,
               it performs user exits for each segment.
3.     Sums up the order data and determines the posting criterion viz. creating order with reference
                  etc.
4.     Builds up batch data communication sequence (BDC) with respect to the required screen
              sequence of posting a sales order.
5.     While building up the BDC data, system performs user exit to process customizations to BDC
                data.
6.     Calls transactions VA01 using the BDC data.
7.     If the processing fails, an appropriate workitem is generated for workflow processing.
if you give me brief i can help you out more.
if helpful REWARD points
Thank you .
Regards
Ramana

Flat dimensions and retrieval performance

Similar Messages

Maybe you are looking for