Results 1 to 1 of 1
  1. #1
    Join Date
    Jun 2011
    Posts
    3

    Unanswered: SAP MaxDB query precalculation

    Hi all.

    Could someone please tell me is there a way how to prevent and/or circumvent SAP MaxDB's (sub)query precalculation.

    Obvious examples are:

    a) SELECT COUNT(*) FROM DOMAIN.DOMAINS AS T1, DOMAIN.COLUMNS AS T2, DOMAIN.TABLES AS T3 WHERE 12=32
    b) SELECT * FROM (SELECT COUNT(*) FROM DOMAIN.DOMAINS AS T1, DOMAIN.COLUMNS AS T2, DOMAIN.TABLES AS T3 WHERE 12=32) WHERE 52=23

    These will actually delay while it's obvious that it shouldn't. Thing is that with this kind of behavior I am getting pretty heavy benchmark hit (in some normal case it would be happening e.g. 50% of times while with this kind of behavior CPU load goes crazy for every similar case - whenever WHERE is true or false).

    Please help.

    KR
    Last edited by mirekjozic; 06-26-11 at 20:30.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •