Named Searches - Performance Questions

[former_member188973]

Dear MDM Pros,

I have question regarding the performance of Named Searches.

I have a repository with 600.000 datasets (and various lookup tables) now I need to setup named searches for restricting the access to the data.

I have one field with classifications (Number 8 digits / 15.000 different classes) on that I want to restrict access. The restriction should work on the first 2 digits of a class.

Example Classification:

21010509

21010503

21010504

21010507

19050711

19050912

31020530

Rule:

LEFT(CLASSIFICATION,2) >= 19 AND LEFT(CLASSIFICATION,2) <= 21

So my idea is to use this

LEFT(CLASSIFICATION,2) >= 19 AND LEFT(CLASSIFICATION,2) <= 21

Expression in the search and save this as Named Search.

As wrote before I think this is really slow.

Can anybody give me a hint how to find a performance optimized solution for this problem.

Best regards

Roman

[Former Member · Accepted solution]

Hi Roman,

from my experience, if you use the free form search in favor of expessions, it would be faster. So you can try to create three separate named searches and use the "starts with" operator in the free form search directly in the field:

Search1: Classification starts with 19

Search2: Classification starts with 20

Search3: Classification starts with 21

Now you assign all three named searches to a role. When you log on, you should see all classification fields starting with 19, 20 and 21.

Maybe this method is faster.

Christian

[former_member188973]

There is a note (sorry I forgot the number) explaining Free-Form-Search is not supported by Named Searches.

[Former Member]

Hi Roman,

I'm a bit astonished about that, since I did that just yesterday. I have the same problem as you only that my numbers are stored as a hierarchy. I use the "Starts with" operator in order to restrict users according to the parent node. That works. Did you try it out?

Do you have another version? I'm on MDM 5.5.62.53. I will try to find the note you mentioned.

Best regards

Christian

[former_member188973]

Hi Christian,

here is what SAP said:

07.10.2008 - 16:22:51 CET - Antwort von SAP

Dear Mr Becker,

I have looked at this issue that you described.

I have attached 2 notes: 1077701 and 1138862.

Note 1077701 describes under " 6) Named Search" that the use of

expressions is not supported for named search.

The reason for this is that an expression can result in extensive searchoperation as you experience it. The response time in MDM Data Manager

was in a range of 2-3 minutes when I executed a free form search

with the expression you used in my environment. My observation in

our SAPconnect session yesterday was that you have a similar response

time with MDM Data Manager in your environment.

Note 1138862 describes under "Situation 2:" that the

SRM-MDM Catalog Search UI will show a 5-7 times slower response

time then the MDM Data Manager for the same search.

This is why you experience response times of 10-15 minutes in

SRM-MDM Catalog Search UI when calling it with a named search that

uses an expression.

Kind regards,

Alexander Ohlgart

I am running MDM with 5.5 SP3 actual fix.

HTH

Roman

[Former Member]

Hi Roman,

now it is clearer: please do not mix up free-form search and expression. Generally, the free-form search works well with named searches. However, using expressions within a free-form search may not work properly with named searches. That is correct. Please refer to my first post from Sep 9 to solve you problem, i.e. create several named searches with free-form searches (not expressions) and then assign these named searches to the roles. I even did exactly that in an SRM-MDM (Version 2.0 SP01 and SP04) project already. By the way, performance has been greatly enhanced in MDM-SRM 2.0 SP04.

Feel free to get back if you need more information.

Best regards

Christian