Up to and including database version 7.5, the precompiler provided an interface between SAP MaxDB database interfaces and C/C++ application programs. As of database version 7.6, the precompiler has been replaced by the SQLDBC interface. The precompiler is one of the interfaces used to connect an application to the database. In SAP systems (release < 7.00) the database library (DBSL) is linked to the precompiler. In SAP release 4.x on Unix the precompiler runtime is linked statically to the DBSL. Whenever a new precompiler runtime version should be installed, a new DBSL (DBADASLIB) has to be installed. Note 325402 describes how a new SAP MaxDB specific DBSL (DBADASLIB) can be installed.
On Micorsoft Windows systems the precompiler runtime is linked dynamically to the DBSL. When the precompiler runtime should be updated, it is sufficient to update the SAP MaxDB client software (which includes the precompiler runtime). Note 649814 describes how the SAP MaxDB client software can be updated.
As of SAP release 6.10 the precompiler runtime is linked dynamically to the DBSL also on Unix systems.
Information about the Precompiler trace can be found here.
As of SAP release 7.00 the DBSL does not use the precompiler anymore but SQLDBC. The DBSL is then called DBSDBSLIB. SQLDBC is linked dynamically to the DBSL. It is part of the SAP MaxDB client software package and can be updated as described in note 649814. A trace for this interface can be activated as described in SQLDBC trace.
The SQLDBC trace can also be switched on/off and listed via SAP program DBA Cockpit (transaction DBACOCKPIT). Here it is easily possible to create an SQLDBC trace for a special workprocess.
Detailed inforamtion about the SQLDBC trace via DBA Cockpit can be found here.
The SAP MaxDB ODBC driver allows applications ( e.g. SAP Content Server) to access SAP MaxDB databases using the ODBC interface. You can use the SAP MaxDB ODBC driver on all operating systems that are supported by the database system.
The SAP MaxDB ODBC driver is a part of the SAP MaxDB software. The SAP MaxDB ODBC driver supports the complete ODBC SQL syntax. For detailed information about the ODBC function calls, see the ODBC Programmer's Reference documentation at msdn.microsoft.com.
You can use the SDBREGVIEW program to determine which ODBC versions are installed on the relevant host. On Unix platforms: At operating system level, start: sdbregview -l | grep -i ODBC The system displays the version of the ODBC driver that is installed on the host. Example: ODBC /program files/sdb/programs 7.6.00.20 valid On Microsoft Windows platforms: At operating system level, start: sdbregview -l | find /I "ODBC" Example: ODBC c:/program files/sdb/programs 7.6.00.20 32 bit valid The ODBC library is linked statically for the SAP content server on Unix, which means that it does not matter which ODBC driver version is installed on the host.
For information about how to install or upgrade the ODBC driver, refer to SAP Note 698915.
You can use the SAP MaxDB JDBC driver and the SAP MaxDB Java classes to incorporate SAP MaxDB databases into Java applications (to execute SQL statements, for example). The SAP MaxDB JDBC driver and the SAP MaxDB Java classes are included in the software component JDBC.
You can use the SDBREGVIEW program to determine which JDBC version is installed on the relevant host.
The JDBC driver is a part of the SAP MaxDB client software package.