SAP Basis Tech Supports

Symptom
This SAP Note describes the use of SAP Tools for MS SQL Server. The SAP Tools for MS SQL Server are based on the SAPinst installation tool and are used to configure database-related parameters of an SAP system that is running with MS SQL Server.
You can download the latest version of the SAP Tools for MS SQL Server from SAP Service Marketplace at:
http://service.sap.com/msplatforms -> SQL Server.
Other terms
MSS, MSSQL, SQL Server 2000, SQL Server 2005, SQL Server 2008, installation, system copy, detach, attach, schema conversion, STM
Reason and Prerequisites
You use the SAP Tools for MS SQL Server to:
Perform a system copy using the detach/attach or backup/restore method.
This only applies to SAP systems based on kernel 6.40 or lower. If you have an SAP system based on kernel 7.0 or higher, you must perform the system copy with SAPinst.Convert the SAP system to a schema-based configuration.Upgrade SQL Server 2000 to SQL Server 2005 or higher.
This applies to all SAP releases starting with 4.6C, including upgrades to SQL Server 2008 for basis releases 7.00 or higher.
Solution
General
This note describes the different tasks that you can perform with the SAP Tools for MS SQL Server.
Database Copy
Use the “Database Copy” option of the SAP Tools for MS SQL Server to set up an ABAP system with a basis lower or equal to 6.40 after you have performed an MS SQL Server database copy with the detach/attach and backup/restore method.
You cannot use the “Database Copy” option to copy Java systems only, or to copy ABAP systems based on release 7.00 or later. If you want to copy such systems you must follow the instructions in the relevant system copy guide, which is available on SAP Service Marketplace at: http://service.sap.com/instguides
You can copy the databases within different platforms that are supported by the Windows operation system (i386, ia64, x64). You can also copy the databases from MS SQL Server 2000 to MS SQL Server 2005 (but not vice versa).
For more information about the steps performed by the “Database Copy” option of the SAP Tools for MS SQL Server, see section “Step 8: Follow-up procedure” of SAP Note 151603.
Before you run the “Database Copy” option of the SAP Tools for MS SQL Server make sure that:
You already installed the central instance of the target system with SAPinst.The database is attached to/restored on the target database server.If you copy a database from MS SQL Server 2000 to MS SQL Server 2005, the source system fulfills the requirements on the basis support package level that is described in SAP Note 905634. Otherwise, the SAP Tools for MS SQL Server stops with an error.
Schema Conversion
Use the “Schema Conversion” option of the SAP Tools for MS SQL Server to convert your system from a dbo-based to a schema-based configuration.
You must convert the system if you want to:
Install a Java Add-In to an ABAP system that was upgraded from a release prior to 6.20 to a release 6.20 or higher.
In this case you must convert the schema before you install the Java Add-In.Use the MCOD functionality (multiple systems share the same database) with the ABAP system that was upgraded from a release prior to 6.20 to a release 6.20 or higher.
In this case you must convert the schema before you install the additional SAP system.
To find out whether you must run this option in these two cases, check the parameter dbs/mss/schema in the default profile of your system (normaly default.pfl under usr\sap\SID\sys\profiles).
If this parameter does not exist or is set to dbo, you must perform the conversion.
If the parameter is set to SAPSID of your system in lower case, a conversion is not necessary (this check implies that your system is operable).
Before you run the “Schema Conversion” option of the SAP Tools for MS SQL Server make sure that:
The system is stopped.You have a current backup of the database.If you are using the BW functionality, check SAP Note 449891, and delete the temporary objects described there. Otherwise, the conversion might take very long time.
Upgrade to MS SQL 2005 or higher
Use the “Upgrade to MS SQL 2005 or higher” option of the SAP Tools for MS SQL Server to perform mandatory tasks on the database after you upgraded SQL Server 2000 to SQL Server 2005 or higher with the SQL Server setup. If you copied and attached an SQL Server 2000 database to an SQL Server 2005 server, use the “Database Copy” option of the SAP Tools for MS SQL Server instead.
For more information about the upgrade to MS SQL Server 2005, see SAP Note 799058. For more information about the upgrade to MS SQL Server 2008, see SAP Note 1152240.
Before you run the “Upgrade to MS SQL 2005 or higher” option of the SAP Tools for MS SQL Server, make sure that:
The system is stopped.You have a current backup of the database.Your source system fulfills the requirements on the basis support package level that is described in SAP Note 905634. Otherwise, the SAP Tools for MS SQL Server stops with an error.
Performing the Tasks with SAP Tools for MS SQL Server
Run the SAP Tools for MS SQL Server on the central instance host.
Change to the directory, where you downloaded and unpacked the archive. Go to the directory STM\<Your Platform> and start sapinst.exe. Choose the required option of the SAP Tools for MS SQL Server, and follow the instructions in the SAPinst dialogs.If SAP Tools for MS SQL Server detects that in the database there are so-called SAP Y% stored procedures (also called temporary stored procedures in older version of the tools), it suggests to delete them. We recommend that you accept the deletion, as these stored procedures should be deleted regularily. When running the SAP Tools for MS SQL Server this is an ideal point of time to do so.If you perform the “Database Copy” or “Upgrade to MS SQL 2005 or higher” options, and SAP Tools for MS SQL Server detect that your system is dbo-based, the tools suggest to convert it to the schema-based configuration. We recommend that you accept the conversion so that you do not have to do this later.
Known Issues
Currently there are no known issues with the SAP Tools for MS SQL Server.