The database and db connection have already been properly configured. SAP Sourcing will connect to a remote Oracle 11.2 database server. We've installed an SAP NetWeaver 7.3 AS Java running on top of a local MS SQL Server 2008 R2 instance. Query IAPIs – a good alternative for DbHandle.Performance Tuning in SAP Sourcing database.Database User Password Maintenance on Oracle.Pick a DBMS such as SQL Server or MAX DB for Netweaver but ONLY DB2 and Oracle are supported for Sourcing / CLM.įor further references on the installations procedures, please read the installations guides on the Service Marketplace ( Our team has also contributed some more knowledge on best practices related to the database usage:.

Higher flexibility in backup and restore strategy.Easier version control since NetWeaver and SAP Sourcing do not have to use the same DBMS version.Less constraints in planning and execution of upgrade strategy.There are several reasons why this is a good idea: When purchasing a license to deploy SAP Sourcing/CLM on-Premise, the recommendation from a technical perspective is to use one database for the application server (NetWeaver Java) and one database for the application itself. The short answer would to this question would be: “It is technically feasible to install on the same database instance, but it is strongly recommended to install on a separate database” The main questions which have been posted via customer support as well as SCN is: “Is SAP Sourcing/CLM required to be on the same or a separate database from the Application Server NW Java?”. In the past weeks our team has often received requests about best practices with regards to database installations for SAP Sourcing/CLM.

Sap sourcing