SAP BW (BeX and SQL) runs in DIALOGUE mode = memory hungry

[andy]

Hi,

Having memory issues in SAP BW with Qlik requests. 

When we run job in Qlik Sense on Windows it triggers corresponding SELECT statement in SAP , but this statement runs in DIALOGUE mode .

DIALOGUE mode is memory hungry and not recommended I've learned. 

SAP guys have increased dialogue memory from 2 to 6 GB.

Is there a way to tweak the SAP connector to run in background mode?

Any hints are appreciated!

[SankarReddyK]

Hi @andy 

Qlik SAP connector requires a background user, not a dialog user.

The QTQVCACCESS role is used by a connector back-end user who performs extraction jobs from Qlik.

Please refer to the help page.

https://help.qlik.com/en-US/connectors/Subsystems/SAP_Connectors_Help/Content/Connectors_SAP/Configu...

Best Regards,

Sankar Reddy K.

[Hakan_Ronningberg · Accepted solution]

Hi,

The extraction of data for the SQL connector is performed in a background process. The data is then fetched from a shared memory buffer in the SAP system by calling a function module repeatedly. The function module uses dialog processes, but the time consuming part is done in the background. You can read more in the attached document (page 25) about how the SQL connector works.

It is true that the BEx connector works in a dialog process. Unfortunately it is not possible to do that extraction in the background.

Regards,
Håkan