0Q - MS SQL Server Portierung
The following messages are stored in message class 0Q: MS SQL Server Portierung.
It is part of development package SMSS_TOOLS in software component BC-DB-MSS. This development package consists of objects that can be grouped under "Utilities for MS SQL Server".
It is part of development package SMSS_TOOLS in software component BC-DB-MSS. This development package consists of objects that can be grouped under "Utilities for MS SQL Server".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1&2&3&4 |
| 001 | Error occurred when saving |
| 002 | Data saved |
| 003 | Error when determining the database release |
| 004 | &1 SQL scripts deleted |
| 005 | Error during deletion |
| 006 | SQL script &1 already exists |
| 007 | &1 deleted |
| 008 | SQL script &1 changed |
| 009 | SQL script &1 not found |
| 010 | Inconsistent program parameters |
| 011 | Database system &1 not supported |
| 012 | Error in &1 |
| 013 | Invalid database release &1 |
| 014 | Unexpected DB return code &1 |
| 015 | Invalid release/revision combination: &1 &2 |
| 016 | Invalid release ID: &1 |
| 017 | Invalid script revision: &1 |
| 018 | Version entry &1 &2 already exists |
| 019 | Data record already exists in table &1 |
| 020 | Release/revision entered incompletely |
| 021 | Select a table column (click on the header) |
| 022 | User &1 already processing &2 &3 &4 |
| 023 | Error when locking &1 &2 &3 |
| 024 | Error when reading the local data |
| 025 | RFC error: Could not access remote data |
| 026 | Release dependency for &1 was changed |
| 027 | The name &1 is not unique |
| 028 | Operation terminated |
| 029 | SQL error &1: &2&3&4 |
| 030 | ADBC database error (&1) occurred |
| 031 | Error in database interface (&1) |
| 032 | SQL string was too big for &1 &2 &3 |
| 033 | SQL script(s) executed successfully |
| 034 | Specify a name |
| 035 | Deletion canceled |
| 036 | Specify an SQL script |
| 037 | SQL script &1 &2 &3 not found |
| 038 | Error &1 calling TR function |
| 039 | Data missing in MSSSPVERS (&1) |
| 040 | Incorrect transport object: &1 &2 instead of R3TR SDBP |
| 041 | SQL script &1 &2 &3 will be ignored (incorrect release) |
| 042 | Deletion request for SQL script &1 &2 &3 |
| 043 | SQL script &1 &2 &3 being executed |
| 044 | SQL scripts executed / deleted / ignored: &1 / &2 / &3 |
| 045 | Starting processing of SQL scripts (R3TR SDBP)... |
| 046 | Error occurred during file selection |
| 047 | Error occurred during download |
| 048 | &1 bytes passed |
| 049 | Object &1 not found |
| 050 | Connection &1 does not exist in DBCON |
| 051 | Incorrect database system &1 for connection &2 |
| 052 | Connection &1 cannot be opened |
| 053 | Unexpected return code &1 while setting connection |
| 054 | SQL return code &1 occurred during database access |
| 055 | RFC error &1 during call from &2 |
| 056 | MSS_TOOLS_AUTHORITY : You are not authorized for &1 |
| 057 | MSS_TOOLS_AUTHORITY : Error &1 during authorization check |
| 058 | MSS_TOOLS_AUTHORITY : Illegal program name &1 |
| 059 | Script is unchanged - no save required |
| 060 | DB collector is already stopped |
| 061 | DB collector is already running |
| 062 | DB collector status is inconsistent (&1, &2) |
| 063 | RFC system error : &1&2&3&4 |
| 064 | RFC connection error : &1&2&3&4 |
| 065 | Connection successful : &1(RFC) &2(DBCON) &3(Schema) |
| 066 | DB user is &1 but should be dbo |
| 067 | Error in tree control : &1 |
| 068 | DBCON entry &1 already exists |
| 069 | Select a row (single click) |
| 070 | You can only maintain SQL server data here |
| 071 | DBCON entry &1 saved |
| 072 | The entered passwords are different |
| 073 | An empty password is not permitted for security reasons |
| 074 | Error occurred &1 when encrypting the password |
| 075 | DBCON entry &1 deleted |
| 076 | Entry &1 was applied |
| 077 | Unspecified error occurred in &1 |
| 078 | Return value &1 from function &2 |
| 079 | SAP TSQL objects must only be created in non-dbo schema |
| 080 | SAP TSQL objects must not conflict with existing SAP system |
| 081 | Sources are identical |
| 082 | The sources differ only in empty rows |
| 083 | The sources are different |
| 084 | No comparison of a single source |
| 085 | No more differences |
| 086 | WP cannot be locked remotely; local logon required |
| 087 | Trace &1 stopped |
| 088 | RFC host is not unique due to load balancing - command ignored |
| 089 | This function is not useful in the case of RFC - command ignored |
| 090 | Lock the work process first; command ignored |
| 091 | SQL release &1 is not known in MSS_FORMAT_RELEASE |
| 092 | You cannot edit SQL scripts through an RFC connection |
| 093 | MSSPROCS: Termination due to version conflict (&1 <> &2) |
| 094 | Version conflict (&1 <> &2); command ignored |
| 095 | SolMan schema name is incompatible with SAP release (&1 <> &2) |
| 096 | MSSPROCS execution using DBCON connection &1 is forbidden |
| 098 | Result of the system check: &1 |
| 099 | Result of the schema generation: &1 |
| 100 | Result of the SQL script execution: &1 |
| 101 | You are not authorized for DB access (S_DBCON: &1 &2 &3 &4) |
| 102 | Rollback failed |
| 103 | RFC version and local version are incompatible ( &1 <> &2 ) |
| 104 | Schema name >&1< contains an invalid special character |
| 105 | The version of the monitor schema is invalid (should be/is: &1/&2) |
| 106 | Error when copying the DBCON entry &1 |
| 107 | Result of script execution: &1 warnings, &2 errors |
| 109 | Trace directory entry already exists (&1) |
| 110 | Filter condition already exists |
| 111 | Name of trace column is missing |
| 112 | Select a table row |
| 114 | Template &1 was successfully saved |
| 115 | SQL object &1 returns &2 |
| 116 | Template &1 deleted |
| 117 | Trace directory is invalid and will be overwritten by the default |
| 118 | Trace directory list is empty; not possible to save or start |
| 119 | Trace definition was successfully scheduled &1 |
| 120 | Trace was successfully started (ID = &1) |
| 121 | Too similar to trace &1 |
| 122 | Invalid parameter value: &1 |
| 123 | File &1 already exists in directory &2 |
| 125 | No (further) hits found in search area |
| 126 | Illegal parameter value: &1 |
| 128 | Error when automatically refreshing the DB monitoring objects (DBCON &1) |
| 129 | Download was terminated |
| 131 | DBCON entry &1 not found |
| 132 | Unspecified error occurred in DBCON_READ |
| 133 | DBCON entry &1 already exists |
| 134 | Password container already exists for DBCON entry &1 |
| 135 | Unspecified error occurred in DBCON_INSERT |
| 136 | CL_DBA_SYS : &1 |
| 137 | First specify the release of the target database |
| 138 | Database connection &1 and schema &2 are functioning |
| 139 | Database connection &1 or schema &2 are not functioning |
| 140 | &1: The value &2 is invalid; only 0 or 1 are permitted |
| 141 | &1: The value &2 is not numerical |
| 142 | Script &1 updated for database version &2 |
| 143 | Database-independent script &1 updated |
| 145 | No SQL Server login is assigned to the monitor schema &1 |
| 147 | At least one source code line is too long (>78 characters) |
| 150 | Parameter &1 contains a special character that is not permitted |
| 152 | &1 : &2 |
| 153 | Time interval : &1 &2 to &3 &4 |
| 154 | Records returned : &1 |
| 201 | ###################################################### |
| 202 | ====================================================== |
| 204 | Dropping column KEY_IDX from fact tables |
| 205 | of basis InfoCubes |
| 206 | Start date and time: &1 |
| 207 | End date and time: &1 |
| 208 | Fact table: &1 |
| 209 | =========== |
| 210 | &1 |
| 211 | SQL Error &1 in DDL statement in step &2 for |
| 212 | Begin: Activating remote info cubes |
| 213 | End: Activating remote info cubes |
| 214 | Info cube: &1 |
| 215 | ========== |
| 216 | Begin: Completing the work for basis info cubes |
| 217 | End: Completing the work for basis info cubes |
| 218 | End: Dropping column KEY_IDX |
| 219 | (fact table: &1) |
| 220 | (fact view: &1) |
| 310 | Cannot read version information |
| 311 | Error when uploading file |
| 312 | Error while saving file |