Monitoring Remote SQL Server
Databases 
Use
As of SAP Web Application Server 6.40, you can administer not only your local SAP database, but also remote SQL Servers and their databases from a central console. You can use the SQL Server database monitor transactions to point at remote SAP systems of a different release than the local SAP system. There are no restrictions with respect to the remote database. It can belong to an ABAP-based SAP system, a JAVA-based SAP system or a non-SAP application.
Remote Connect Mechanisms
The following connect mechanisms are used:
Database multi-connect allows an ABAP program to open a database connection to a database other than its default database and run SQL commands on this secondary database. For more information on multi-connect, see SAP Notes 323151 and 178949.
The generic SAP database multi-connect function, which is implemented for all Database Management Systems (DBMS), has been extended for SQL Server. To adapt to the specifics of the SQL Server login, schema and user concept, we introduced the idea of an object source schema. All SAP database objects, which implement the low-level database monitor functions, such as stored procedures, user defined functions and tables, are placed into this database schema to keep them separate from other objects inside the target database. At the same time, the connection used to monitor the target database connects as dbo rather than the database user associated with the object source schema.
The object source schema can be specified when you maintain a database multi-connect destination with the tools described in Creating a DBCON Entry.
· Combination of RFC and Database Multi-Connect
Do not use the standard table maintenance SM31 to create destinations for remote SQL Server database monitoring.
Transactions to be used with Remote Database Monitoring
You can use transactions ST04, DB02 and DB12 for remote database monitoring. They fully implement the new remote monitoring functions. If you want to use these transactions on a non-SQL Server system and connect to a remote SQL Server database, you have to use transactions ST04_MSS, DB02_MSS and DB12_MSS instead.
In previous releases you could use transaction DB13C to schedule backups and other maintenance tasks for remote databases. So far, only RFC connections could be used to administer SQL Server databases. As of Web AS 6.40, the full DB13C functionality is available and you can also use DB multi-connect. In contrast to transactions ST04, DB02 and DB12, you cannot use a combination of RFC and database multi-connect in transaction DB13C.