SAP NW Newbie

Unless you are good with remembering numbers, you can't just look at the version number information of MS Windows or MS SQL Server and tell what the release, SP levels etc are. To quickly establish a correlation, you can use these two resources: Operating System Version (Windows) Microsoft SQL Server Version List For a quick reference, I have copied the latest information here: Operating system Version number Windows 10 10.0* Windows Server 2016 Technical Preview 10.0* Windows 8.1 6.3* Windows Server 2012 R2 6.3* Windows 8 6.2 Windows Server 2012 6.2 Windows 7 6.1 Windows Server 2008 R2 6.1 Windows Server 2008 6 Windows Vista 6 Windows Server 2003 R2 5.2 Windows Server 2003 5.2 Windows XP 64-Bit Edition 5.2 Windows XP 5.1 Windows 2000 5 * For applications that have been manifested for Windows 8.1 or Windows 10. Applications not manifested for Windows 8.1 or Windows 10 will return the Windows 8 OS version value (6.2). RTM  (no  SP ) SP1 SP2 SP...

Disaster Recovery is the process, policies and procedures of restoring operations critical to the resumption of business, including regaining access to data (records, hardware, software, etc.), communications (incoming, outgoing) workspace, and other business processes after a natural or human-induced disaster. Here are some common aspects of designing a Disaster Recovery environment for a business application: 1. DR Server The server-that you intend to use in case of disaster-should contain the same version/patch of the Operating System as the primary server. You have to ensure that the disk allocation is similar to that of primary. You need not allocate identical server resources on the DR site, but you may need them when you intend to run the DR site as primary in the event of a disaster. 2. Standby Database Most of the database vendors provide you with an option to install and maintain a standby database, which keeps itself cloned with the primary database. Ex: ...

If the receiver JDBC channel executes a lot of UPDATE statements, then the performance can be improved by using SQL bind mode . SQL bind mode makes use of bind variables instead of actual values so that when a similar statement is executed, the parsed SQL statement can be reused from the shared pool. This has a performance improvement as parsing of the statement is avoided each time a similar statement is executed. Here is an example of SQL statement in bind mode: In this example A0 is the bind variable and not the actual value executed by the SQL. To activate SQL bind mode, add the parameter sqlBindMode with value true in the additional parameters section of the Communication Channel. Note that the variable is case sensitive. You should use this option only on UPDATE, INSERT, DELETE and SELECT statements. Do not activate for any other type of statement (ex: UPDATE_INSERT). Apart from adding the parameter, ensure that Database Auto-Commit-Enabled(No Transaction Handling) is...

Tweaking the SAP installation tool SAPinst, SAP has provided as set of tools that can be used to perform the following tasks on MS SQL Server: Perform a system copy (for SAP kernel <= 640) Convert to a schema-based configuration from dbo-based one Upgrade SQL Server 2000 to SQL Server 2005 or higher You can download the SAP Tools for MS SQL Server (STM) from http://service.sap.com/msplatforms --> SQL Server . Apply security patch from SAP note 1375494 before using the tool and change any DB specific profile parameters. Example: Change dbs/mss/server=$(SAPDBHOST) to dbs/mss/server=<db hostname> Usage of the tool for above mentioned tasks is pretty straightforward. Once you have downloaded and extracted the tool, go to <Path to STM tool folder>STM\<Your Platform> and call sapinst.exe. The dialogue screens will guide you from there.

1. Database connection hangs during logon When connecting to SQL Server DB with a JDBC sernder/receiver Communication Channel, if the channel errors out during logon due to poor performance of MS SQL server (for example), you can adjust the timeout for logon by adding the following parameter in the advanced mode section of the channel configuration driver:loginTimeout   30 This parameters changes the default logon timeout from 15 seconds (version 3 sqljdbc.jar or sqljdbc4.jar) or unlimited (sql driver version 1.2) to the custom value of this parameter (in seconds). 2. SQL Statement Execution hangs If the SQL statement execution hangs, the Communication Channel hangs. Again the timeout for the Channel to wait for execution can be controlled from advanced mode section of the channel configuration. Add the following parameter: driver:lockTimeout    300000 The default lockTimeout is unlimited, you can set this parameter (in ms) in order to avoid hang situation. ...