Skip to Content
author's profile photo Former Member
Former Member

BW Performance - opening query definition on BEx Analyzer


We are seeing some very bad performance problems when opening existing query definitions in the Bex Analyzer. When you click on "Change query(Global Definition)" or just simply click on the "change query" button, it takes approx 27 seconds before you the query definition is fully displayed. (which is long)

The steps it seems to be going through are:

1. Lock the query against external changes

2. Reading query definition

3. Reading infoobjects

4. Authorisation check.

Steps 1 and 2 are where it is hanging and taking the most time.

Does anyone know whether these steps correspond to any tables and if so, which tables these are?



Add comment
10|10000 characters needed characters exceeded

1 Answer

  • Posted on Jun 17, 2004 at 05:32 PM

    Hello Allan,

    since database selections are involved, you should first check that the database statistics are up-to-date (on Oracle the BRCONNECT tool should run daily). Nevertheless, query definitions can be complex especially if you use a lot of restricted or calculated key figures, two structures, or even cell calculations.

    Did you always have this performance problem with queries or has it come up recently? Is it for specific queries and not for others? What's different between the queries?

    If you can reproduce it on a regular basis, open an OSS message so our support can take a look.



    SAP NetWeaver RIG, US BI

    PS: There are too many tables involved to list them. A SQL trace will show you which exactly.

    Add comment
    10|10000 characters needed characters exceeded