Solution : https://service.sap.com/sap/support/notes/551915 (SAP Service marketplace login required)
Summary :
After a system copy or database restore on a new SQL Server, SAP R/3 may fail to start due to user and schema mismatches, evidenced by errors in the dev_w?? files indicating issues with the user 'prd'. This occurs if the source system was non-MCOD with a 'dbo' database user, and the target is MCOD, or if there's a change in the system ID (SID) which affects schema ownership. Recommended solutions include using SAP Tools for MS SQL Server for fixing the configurations automatically, or manual scripts from note 1294762 for schema assignment and repair. Proper profile parameter setups and environmental configurations are essential for resolving these errors.
Key words :
set dbs/mss/verbose = 1 dbs/mss/dbsl_profile = 1in, set dbs/mss/dbname = <sid> dbs/mss/schema = <sid>, mssql_schema=<sid>mssql_dbname=<sid>mssql_server=<sql_server_name>dbms_type=mssusing, terms user schema mcod sp_attach sp_detach system copy reason, start->control panel->system->advanced->environment variablesnow, dbs/mss/server = <dbservername>\<instance_name><instance_name>, hkey_local_machine\software\sap\<sid>\environment\mssql_schema, setuser 'prd' failed -- connect terminated=====================================================================, microsoft sql server management studio, produce additional files named dbsl_w
Related Notes :
| 1294762 | SCHEMA4SAP.VBS |
| 683447 | SAP Tools for MS SQL Server |
| 610640 | sp_check_sap_login |
| 555223 | FAQ: Microsoft SQL Server |
| 193816 | Restore with SQL Server |
| 151603 | Copying an SQL Server database |
| 98678 | SQL Server Connection Issues |