Solution : https://service.sap.com/sap/support/notes/1299865 (SAP Service marketplace login required)
Summary :
When using SAP BW on Microsoft SQL Server 2005 or higher with database partitioning, issues may arise involving large shadow tables not being_deleted due to full transaction logs or deadlocks, using naming conventions such as /BI0/<*>@k#. These are visible in DB02 as unknown ABAP dictionary objects. The note explains_shadow table management for partitions needing removal, and increasing the namespace to accommodate more shadow tables. To resolve_error messages during deletions like RSDU_TABLE_DROP_PARTITION_MSS, it includes checking SQL Server logs, addressing database blockages, and using SAP program RSDD_MSSQL_CUBEANALYZE. Details are available in SAP Note 1313557.
Key words :
bc-sys-db-mss customer message, /isv/sap/technology/interop/bi, bc-sys-db-mss, < > means multiple alphanumeric characters, customers encountered technical problems, choose settings -> expert mode, sap_basis support package resp, request_delete rsdu_fact_requid_delete sql-error, customer compresses infocube 0be_c01, simple drop partition command
Related Notes :
| 1427804 | RSDU_TABLE_TRUNC_PARTITION_MSS -ALTER TABLE SWITCH failed |
| 991014 | (Vardecimal) Compression for SQL Server 2005 SP 2 |
| 869407 | Partitioning on Microsoft SQL Server |