Enable Remote Database Access and Parallel Transaction Processing Using Secondary Database Connections in Your ABAP Programs

  • by Juergen G. Kissner, SAP NetWeaver Development, SAP AG
  • November 15, 2007
SAP NetWeaver Application Server 2004 and higher provides a default connection between your applications and your SAP system database. What you may not know is that you can supplement these default connections in certain scenarios — if you want to access a remote database or trigger a separate, parallel database transaction — by creating secondary connections in your ABAP programs. This article shows you how to use secondary connections, which are an extension of Open SQL, ADBC, and EXEC SQL, and provides some tips and tricks for working with them and monitoring them.

Juergen G. Kissner

Jürgen G. Kissner received his doctorate in theoretical physics at the University of Manchester (UK). In 1996, he joined the SAP Server Technology development team as a member of the Database Interface group, where he worked on high availability, in particular database reconnect and switchover, and the integration of parallel database systems with R/3. Jürgen is currently responsible for the connection and transaction handling aspects of SAP Web Application Server, including multiple database connections in a heterogeneous database landscape. His second development focus is the ABAP and Java table buffer, especially the buffer manager and the SQL statement processor, and the Native SQL layer of the Open SQL engine.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.