As there are several tcodes allowing to enter DBACOCKPIT and switching to the SQL Editor, you can find a summary below (without guarantee of being complete). S_TCODE for the entry point to DBACOCKPIT. Access to the SQL EditorĪccess to the SQL Editor is protected by the following authorization objects. Hint: This should be considered especially in scenarios where client 000 is managed by service providers, since this might open a door for accessing data in productive clients. This leads to data of any client can be accessed or modified, even if the SQL Editor is started, for example, in client 000. Please also note that on database level, there is no special handling of the client field (field ‘MANDT’). With this, the SQL Editor can be used, for example, to access all tables of the ABAP schema.
For the ABAP system’s primary database, it is the schema user SAPDAT, SAP, or SAPABAP. Since the SQL statements are executed on DB level as the connecting user, the privileges of this particular user are applied. : Added info about default roles and profiles containing S_DBCON:ACTVT=36. : Adjusted scope to SAP HANA as primary DB. It was designed to cover the exact scope as the SQL Editor of HANA Studio.
#Sqleditor create a comment area full#
The SQL Editor is a full featured SQL command line and supports all SQL statements as listed, for example, in the SAP HANA SQL Reference Guide for SAP HANA Platform. The DBACOCKPIT of SAP NetWeaver AS ABAP and ABAP Platform provides the SQL Editor which can be used to execute SQL statements on connected databases.