SAP ABAP Data Element MSSDBUSER (MSSQL Multiconnect : DB user)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DB-MSS (Application Component) Microsoft SQL Server
⤷ SMSS_TOOLS (Package) Utilities for MS SQL Server
⤷ BC-DB-MSS (Application Component) Microsoft SQL Server
⤷ SMSS_TOOLS (Package) Utilities for MS SQL Server
Basic Data
Data Element | MSSDBUSER |
Short Description | MSSQL Multiconnect : DB user |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MSSSYSNAME | |
Data Type | CHAR | Character String |
Length | 128 | |
Decimal Places | 0 | |
Output Length | 128 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | DB user |
Medium | 15 | Database user |
Long | 20 | Database user name |
Heading | 55 | DB user |
Documentation
Definition
When a connection is established to a SQL Server database, the login is mapped to a DB user local to this database. The SAP database monitor tools require administrative privileges; this means, the database user "dbo" must be used. A SQL Server login must be member of the "SysAdmin" fixed server role to be mapped to dbo.
On your local system, no specific action is required. The SAP database monitor tools will automatically create a secondary database connection with the necessary privileges.
If you want to monitor a remote SQL Server database via multi-connect, you need to manually create the SQL Server login in your target database and you need to make sure that the login is member of the "SysAdmin" fixed server role.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 640 |