Query Design Tips for Performance

• Use filters - use as many as possible to reduce amount of data need to read from source
• Use the 0infoprov in query restriction if data model is designed in a multiprovider that contain data segregated by same definition for each Infocube
• Avoid using condition and exception
• Use free characteristics - use as few as possible
• Use restricted key figure with care - generate more complex sql
• Use more than one structure with care
• Characteristics/Navigational attribute are more efficient than hierarchies
• Avoid complex queries - consider RRI to offer analysis path rather than define queries showing everything in the infoprovider
• Check the Use Selection of Structure Elements option

*While filters are evaluated by the database, conditions and exceptions are usually 
evaluated by the application server resulting in a much larger volume of data being transferred between both servers.