Process
Several operating system processes belong to the SAP MaxDB database software.
Microsoft Windows |
Unix and Linux |
Function |
||
|---|---|---|---|---|
Process Name |
Process Owner (Operating System User) |
Process Name |
Process Owner (Operating System User) |
|
|
When started on the command line: logged-on operating system user When called from another database tool: |
|
When started on the command line: logged-on operating system user When called from another database tool: |
Database Analyzer |
|
logged-on operating system user |
|
logged-on operating system user |
Database Manager CLI |
|
logged-on operating system user |
|
|
Database Manager GUI |
|
|
|
|
DBM Server |
|
logged-on operating system user |
|
logged-on operating system user |
Database Studio |
|
|
|
|
Database system kernel Every database has its own kernel process. On Microsoft Windows, the kernel of the database runs as an individual operating system process. On Unix and Linux, the kernel uses two operating system processes: upon starting, the database system generates a watchdog process which then directly starts the actual kernel process. |
|
logged-on operating system user |
|
logged-on operating system user |
Loader |
On Microsoft Windows, NI support is an integral part of the global listener. |
- |
|
|
NI server (for connections with SAPRouter, in SAP systems only) |
On Microsoft Windows, NISSL support is an integral part of the global listener. |
- |
|
|
NISSL server (for SSL connections with SAPRouter, in SAP systems only) |
|
|
|
|
Global listener On Unix and Linux, a new child process is started for each database connection. |
|
|
|
|
SAP MaxDB X server (communication server) On Unix and Linux, a new child process is started for each database connection. |
|
logged-on operating system user |
|
logged-on operating system user |
SQLCLI |
|
logged-on operating system user |
|
|
SQL Studio |