Purpose

Overview

Related Content

Purpose

The purpose of this document is to provide a list of the top ten most viewed SAP Notes/KBAs for SAP on SQL Server in the month of January 2013.

Overview

Below are the top 10 most viewed SAP Notes/KBAs for SAP on SQL Server.

Please note, in order to view the contents of the SAP Notes, you will need to be logged into Service Marketplace.

Related Content

Top 10 SAP KBAs (Knowledge Base Articles) for SAP on SQL Server for 2013 - ordered by month

Database Performance Warehouse Report Content

The Database Performance Warehouse uses the SAP BW content of the SAP Solution Manager to store database specific performance metrics. The DBA Cockpit within Solution Manager provides flexible analysis reports  for these metrics  based on BW technology. Learn more about how you can use the report content for capacity planning, trending analysis, troubleshooting, etc.. 15 Feb 2013

SQL Server 2012 Column-Store Available For All Major SAP BW Releases

SQL Server 2012 introduced a new storage format for data. Besides the traditional row-oriented store, there is now also a column-oriented store available. The column-oriented store is optimized for aggregating mass data, while the row-oriented store can be optimally used when accessing just a single row. SQL Server 2012 column-store support has been integrated into all major SAP BW releases. You can now benefit from increased query performance and reduced disk space requirements. 05 Nov 2012

SAP now supports SQL Server 2012

SAP now supports SQL Server 2012 with SAP products based on SAP NetWeaver 7.0 (including all Enhancement Packages). For more information, see SAP Notes 1651862, 1684545, and 1676665 (SMP login required).  Microsoft SQL Server is known as an out-of-the-box and easy-to-use database solution with low TCO. SQL Server 2012 offers many new features such as AlwaysOn, a set of functions for high availability and disaster recovery.  For more information, see the FAQs and the following link. 13 Jul 2012

SAP Database Performance Warehouse for SQL Server in Solution Manager 7.1

The SAP Database Performance Warehouse (DPW) contains key database performance indicators of your SAP system landscape for status reporting and long term performance analysis. It is used by the Solution Manager Diagnostics (SMD) back-end and is therefore an integrated part of SAP Solution Manager.

For information about SAP DPW for the previous SAP Solution Manager version 7.0 EHP1, see the following presentation.  26 Jan 2012

Immense Disk Space Savings with SQL Server

Database compression dramatically reduces the disk space needed for an SAP NetWeaver system running on Microsoft SQL Server. As of SQL Server 2008 R2, this uses an improved encoding algorithm for Unicode, also known as Unicode-compression. This results in less storage requirements for SAP Unicode systems. Therefore, SAP databases containing some non-Latin1 data even shrink during an SAP Unicode conversion. For more information, see this blog. In May 2011, SAP also changed the default compression type from ROW to PAGE compression, which led to an additional dramatic reduction in the database size. For more information about the different SQL Server compression types and how to implement compression for an SAP NetWeaver system, see this document. 22 Sep 2011

The DBA Cockpit and Microsoft SQL Server

The DBA Cockpit is a powerful feature for SAP NetWeaver applications. The following presentations provide tips and advice on how system administrators can use the DBA Cockpit for local monitoring and analysis of Microsoft SQL Server systems. Each presentation includes a PowerPoint with audible narration.

• SAP DBA Cockpit and Microsoft SQL Server
• SAP DBA Cockpit and Microsoft SQL Server - Real Time Performance Analysis
• System Administration for SAP and SQL Server with DBA Cockpit
• SAP DBA Cockpit and Microsoft SQL Server - Historic Performance Analysis

31 Aug 2011

See more recently featured content

Whenever SAP* user got locked (mainly in 000 Client), in most cases we are supposed to unlock the SAP* User in database level.

Before logging into SAP system using SAP* user, be aware whether the parameter login/no_automatic_user_sapstar is set to value 0 (Zero).

If the value of parameter login/no_automatic_user_sapstar is set to 1, it will not allow the SAP* user to login to the SAP system.

Steps to Unlock the SAP* user (DB level)

1. Try login SAP system with SAP* user

    SAP* user got locked due to too many attempts with wrong password.

2. Login to Ms SQL Database,

3. Execute the query:

     select*fromer1.USR02

    The status of the user is locked/Not locked is identified in the field UFLAG.

    In the above screenshot, value of UFLAG is 128 for the user SAP*, means the SAP* user got locked.

    Note : If the value of UFLAG results in a Non-Zero value, then it means that the user got locked.

4. Execute the query: 

     select*from er1.USR02 where BNAME='SAP*'and MANDT='000' to find the details of only SAP* user.

    For Unlocking the user, the value of UFLAG should be set to 0 (Zero).

5. Execute the query: 

    update er1.USR02 set UFLAG='0'where BNAME='SAP*'and MANDT='000'

6. Now execute the query : 

    select*from er1.USR02 where BNAME='SAP*'and MANDT='000'

    Now the Value of UFLAG has been altered to 0.

    SAP* user has been unlocked.

==========================================================

You want to use SQL Statement History to gather further information about the SQL statements which have produced high load on the server in the past.

DBACockpit -> Performance folder -> History folder -> SQL Statement History

You can find the SQL Statement History in SAP systems with MS SQL Server database and the following releases:

• SAP enhancement package 2 for SAP Netweaver 7.0 SP 06 or newer
• SAP Netweaver 7.3 SP 02 or newer
• SAP enhancement package 1 for SAP Netweaver 7.3 or newer
• SAP Netweaver 7.4 or newer

The upper half of the screen (Workload history) shows the overall statement load over time (measured every twenty minutes).

The list is sorted by the sample date/time with the latest measurements appearing first, which can be re-ordered.

The lower half of the screen (Period details) shows individual statements which were executed during the selected period. Initially the most recent period is selected.

A fragment of the statement text is displayed with the percentages of the load for each criteria. The cells where a particular statement was in the top 5 for a criteria are marked in red.

Further performance data can be viewed pressing the "Detailed view" button.

Double click on a line for a statement, or press the button "SQL statement" will bring up the statement analysis screen for the saved statement.

This informs the user that the saved plan is from history, and may be different from the current plan.

The data is collected within the database collector job which runs every twenty minutes.

The data is retained for 30 days by default.

This can be changed in transaction DBACOCKPIT -> Configuration folder -> Monitoring Environment -> Monitor configuration tab, under the section STMTHIST.

The tables which store the data are:

• sap_stmt_history : The summary information for each collection data point (the upper half of the screen).
• sap_stmt_workload: The statement information (the lower half of the screen)
• sap_stmt_sqltext: The saved statement SQL handle and the actual SQL text for that handle.
• sap_stmt_plan: The saved plan handle and the actual XML for the saved plan.
• sap_workload_snapshot: A snapshot from sys.dm_exec_query_stats saved in the last execution.

The data is collected by stored procedure sap_collect_stmt_history and stored procedure sap_save_top_n.

All the tables and procedures needed for the job are created by the script named sap_stmt_history.

See also SAP Help Portal documentation:

The purpose of this document is to provide a list of KBAs/Notes that were released on September 2013.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on October2013.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on November 2013.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

  In SQL server 2008 and later version, Microsoft introduces a new light weight trace tool called extended events. I found it is useful to identify expensive SQL statements in time using rpc_completed extended events. Unlike DMVs, this shows individual statement instead of cumulative data. and it is much useful to identify the source of the problem. I create a new T-SQL to generate rpc_completed extended event and an extracted T-SQL to view this data. Hope this can help others who want to identify expensive SQL statements. I give an exmaple below.

  There is one issue there. I still can't get the correct plan_handle and extract the execution plan. Maybe someone can tell me how to do it.

PS: I recommend you to read raw file(.xel) directly. The information there is more complete.

-- This script creates an extended event

IF EXISTS(SELECT * FROM sys.server_event_sessions WHERE name='RPC_Expensive_Queries')
    DROP EVENT SESSION [RPC_Expensive_Queries] ON SERVER;
GO

CREATE EVENT SESSION [RPC_Expensive_Queries] ON SERVER
    ADD EVENT sqlserver.rpc_completed(
         ACTION (sqlserver.database_id,
                 sqlserver.plan_handle,
                 sqlserver.session_id,
                 sqlserver.sql_text)
    WHERE cpu_time > 1000000000 /*total ms of CPU time, night 0, 000000000*/
       OR duration > 1000000000 /* night 0*/
       OR logical_reads > 100000000 /* eight 0 */
       OR physical_reads > 1000000 /* six 0 */
       OR writes > 100000 ) /*five 0 */
    ADD TARGET package0.ring_buffer(SET max_memory=2048),
    ADD TARGET package0.asynchronous_bucketizer(
        SET filtering_event_name='sqlserver.rpc_completed',
            source='sqlserver.sql_text'),
    ADD TARGET package0.asynchronous_file_target
        (SET FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\RPC_Expensive_Queries.xel',
        METADATAFILE = N'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\RPC_Expensive_Queries.xem')
WITH (MAX_MEMORY = 4096KB,
      EVENT_RETENTION_MODE = ALLOW_SINGLE_EVENT_LOSS,
      MAX_DISPATCH_LATENCY = 10 SECONDS,
      MAX_EVENT_SIZE = 0KB,
      MEMORY_PARTITION_MODE = NONE,
      TRACK_CAUSALITY = OFF,
      STARTUP_STATE = OFF)
GO

ALTER EVENT SESSION [RPC_Expensive_Queries] ON SERVER STATE = START
GO

-- This script extracts xml information

SELECT

data.value (

  '(/event[@name=''rpc_completed'']/@timestamp)[1]',

   'DATETIME') AS [Time],

data.value ('(/event/data[@name=''cpu_time'']/value)[1]', 'BIGINT') AS [CPU (ms)],

data.value ('(/event/data[@name=''duration'']/value)[1]', 'BIGINT') AS [duration (ms)],

-- CONVERT (FLOAT, data.value (

--  '(/event/data[@name=''cpu_time'']/value)[1]', 'BIGINT')) / 1000000 AS [CPU (s)],

-- CONVERT (FLOAT, data.value (

--  '(/event/data[@name=''duration'']/value)[1]', 'BIGINT')) / 1000000 AS [Duration (s)],

        data.value('(/event/data[@name=''logical_reads'']/value)[1]','bigint') LogicalReads,

        data.value('(/event/data[@name=''physical_reads'']/value)[1]','bigint') PhysicalReads,

        data.value('(/event/data[@name=''writes'']/value)[1]', 'bigint') as writes,

data.value ('(/event/action[@name=''sql_text'']/value)[1]','VARCHAR(MAX)') AS [SQL Text],

--        data.value ('(/event/data[@name=''statement'']/value)[1]','VARCHAR(MAX)') AS [Statement],

CAST(data.value('(event/action[@name="plan_handle"]/value)[1]', 'varchar(max)') AS XML) as plan_handle

FROM

(SELECT CONVERT (XML, event_data) AS data

FROM sys.fn_xe_file_target_read_file

  ('C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\RPC_Expensive_Queries*.xel',

  'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\RPC_Expensive_Queries*.xem', null, null)

) entries

ORDER BY [Time] DESC;

GO

-- This is an expensive SQL statement I captured. Someone queries a mass data in table MSEG using SE16

-- you can get xml format using

-- SELECT CONVERT (XML, event_data) AS data

-- FROM sys.fn_xe_file_target_read_file

--  ('C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\RPC_Expensive_Queries*.xel',

--  'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\RPC_Expensive_Queries*.xem', null, null)

<event name="rpc_completed" package="sqlserver" timestamp="2013-12-13T03:42:20.284Z">

  <data name="cpu_time">

    <value>614925000</value>

  </data>

  <data name="duration">

    <value>747622927</value>

  </data>

  <data name="physical_reads">

    <value>10545780</value>

  </data>

  <data name="logical_reads">

    <value>53445177</value>

  </data>

  <data name="writes">

    <value>0</value>

  </data>

  <data name="result">

    <value>0</value>

    <text>OK</text>

  </data>

  <data name="row_count">

    <value>4</value>

  </data>

  <data name="connection_reset_option">

    <value>0</value>

    <text>None</text>

  </data>

  <data name="object_name">

    <value>sp_prepexec</value>

  </data>

  <data name="statement">

    <value>declare @p1 int

set @p1=773450

exec sp_prepexec @p1 output,N'@P1 nvarchar(3),@P2 nvarchar(16)',N'SELECT TOP 4000 "MANDT" AS c ,"MBLNR" AS c ,"MJAHR" AS c ,"ZEILE" AS c ,"LINE_ID" AS c ,"PARENT_ID" AS c ,"LINE_DEPTH" AS c ,"MAA_URZEI" AS c ,"BWART" AS c ,"XAUTO" AS c ,"MATNR" AS c ,"WERKS" AS c ,"LGORT" AS c ,"CHARG" AS c ,"INSMK" AS c ,"ZUSCH" AS c ,"ZUSTD" AS c ,"SOBKZ" AS c ,"LIFNR" AS c ,"KUNNR" AS c ,"KDAUF" AS c ,"KDPOS" AS c ,"KDEIN" AS c ,"PLPLA" AS c ,"SHKZG" AS c ,"WAERS" AS c ,"DMBTR" AS c ,"BNBTR" AS c ,"BUALT" AS c ,"SHKUM" AS c ,"DMBUM" AS c ,"BWTAR" AS c ,"MENGE" AS c ,"MEINS" AS c ,"ERFMG" AS c ,"ERFME" AS c ,"BPMNG" AS c ,"BPRME" AS c ,"EBELN" AS c ,"EBELP" AS c ,"LFBJA" AS c ,"LFBNR" AS c ,"LFPOS" AS c ,"SJAHR" AS c ,"SMBLN" AS c ,"SMBLP" AS c ,"ELIKZ" AS c ,"SGTXT" AS c ,"EQUNR" AS c ,"WEMPF" AS c ,"ABLAD" AS c ,"GSBER" AS c ,"KOKRS" AS c ,"PARGB" AS c ,"PARBU" AS c ,"KOSTL" AS c ,"PROJN" AS c ,"AUFNR" AS c ,"ANLN1" AS c ,"ANLN2" AS c ,"XSKST" AS c ,"XSAUF" AS c ,"XSPRO" AS c ,"XSERG" AS c ,"GJAHR" AS c ,"XRUEM" AS c ,"XRUEJ" AS c ,"BUKRS" AS c ,"BELNR" AS c ,"BUZEI" AS c ,"BELUM" AS c ,"BUZUM" AS c ,"RSNUM" AS c ,"RSPOS" AS c ,"KZEAR" AS c ,"PBAMG" AS c ,"KZSTR" AS c ,"UMMAT" AS c ,"UMWRK" AS c ,"UMLGO" AS c ,"UMCHA" AS c ,"UMZST" AS c ,"UMZUS" AS c ,"UMBAR" AS c ,"UMSOK" AS c ,"KZBEW" AS c ,"KZVBR" AS c ,"KZZUG" AS c ,"WEUNB" AS c ,"PALAN" AS c ,"LGNUM" AS c ,"LGTYP" AS c ,"LGPLA" AS c ,"BESTQ" AS c ,"BWLVS" AS c ,"TBNUM" AS c ,"TBPOS" AS c ,"XBLVS" AS c ,"VSCHN" AS c ,"NSCHN" AS c ,"DYPLA" AS c ,"UBNUM" AS c ,"TBPRI" AS c ,"TANUM" AS c ,"WEANZ" AS c ,"GRUND" AS c ,"EVERS" AS c ,"EVERE" AS c ,"IMKEY" AS c ,"KSTRG" AS c ,"PAOBJNR" AS c ,"PRCTR" AS c ,"PS_PSP_PNR" AS c ,"NPLNR" AS c ,"AUFPL" AS c ,"APLZL" AS c ,"AUFPS" AS c ,"VPTNR" AS c ,"FIPOS" AS c ,"SAKTO" AS c ,"BSTMG" AS c ,"BSTME" AS c ,"XWSBR" AS c ,"EMLIF" AS c ,"EXBWR" AS c ,"VKWRT" AS c ,"AKTNR" AS c ,"ZEKKN" AS c ,"VFDAT" AS c ,"CUOBJ_CH" AS c ,"EXVKW" AS c ,"PPRCTR" AS c ,"RSART" AS c ,"GEBER" AS c ,"FISTL" AS c ,"MATBF" AS c ,"UMMAB" AS c ,"BUSTM" AS c ,"BUSTW" AS c ,"MENGU" AS c ,"WERTU" AS c ,"LBKUM" AS c ,"SALK3" AS c ,"VPRSV" AS c ,"FKBER" AS c ,"DABRBZ" AS c ,"VKWRA" AS c ,"DABRZ" AS c ,"XBEAU" AS c ,"LSMNG" AS c ,"LSMEH" AS c ,"KZBWS" AS c ,"QINSPST" AS c ,"URZEI" AS c ,"J_1BEXBASE" AS c ,"MWSKZ" AS c ,"TXJCD" AS c ,"EMATN" AS c ,"J_1AGIRUPD" AS c ,"VKMWS" AS c ,"HSDAT" AS c ,"BERKZ" AS c ,"MAT_KDAUF" AS c ,"MAT_KDPOS" AS c ,"MAT_PSPNR" AS c ,"XWOFF" AS c ,"BEMOT" AS c ,"PRZNR" AS c ,"LLIEF" AS c ,"LSTAR" AS c ,"XOBEW" AS c ,"GRANT_NBR" AS c ,"ZUSTD_T156M" AS c ,"SPE_GTS_STOCK_TY" AS c ,"KBLNR" AS c ,"KBLPOS" AS c ,"XMACC" AS c ,"VGART_MKPF" AS c ,"BUDAT_MKPF" AS c ,"CPUDT_MKPF" AS c ,"CPUTM_MKPF" AS c ,"USNAM_MKPF" AS c ,"XBLNR_MKPF" AS c ,"TCODE2_MKPF" AS c ,"/BEV2/ED_KZ_VER" AS c ,"/BEV2/ED_USER" AS c ,"/BEV2/ED_AEDAT" AS c ,"/BEV2/ED_AETIM" AS c ,"OINAVNW" AS c ,"OICONDCOD" AS c ,"CONDI" AS c FROM "MSEG" WHERE "MANDT" = @P1 AND "XBLNR_MKPF" = @P2

/* R3:/1BCDWB/DBMSEG:1298 T:MSEG */

',N'218',N'5585577476'

select @p1</value>

  </data>

  <data name="data_stream">

    <value />

  </data>

  <data name="output_parameters">

    <value />

  </data>

  <action name="database_id" package="sqlserver">

    <value>5</value>

  </action>

  <action name="plan_handle" package="sqlserver">

    <value>0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</value>

  </action>

  <action name="session_id" package="sqlserver">

    <value>1262</value>

  </action>

  <action name="sql_text" package="sqlserver">

    <value>(@P1 nvarchar(3),@P2 nvarchar(16))SELECT TOP 4000 "MANDT" AS c ,"MBLNR" AS c ,"MJAHR" AS c ,"ZEILE" AS c ,"LINE_ID" AS c ,"PARENT_ID" AS c ,"LINE_DEPTH" AS c ,"MAA_URZEI" AS c ,"BWART" AS c ,"XAUTO" AS c ,"MATNR" AS c ,"WERKS" AS c ,"LGORT" AS c ,"CHARG" AS c ,"INSMK" AS c ,"ZUSCH" AS c ,"ZUSTD" AS c ,"SOBKZ" AS c ,"LIFNR" AS c ,"KUNNR" AS c ,"KDAUF" AS c ,"KDPOS" AS c ,"KDEIN" AS c ,"PLPLA" AS c ,"SHKZG" AS c ,"WAERS" AS c ,"DMBTR" AS c ,"BNBTR" AS c ,"BUALT" AS c ,"SHKUM" AS c ,"DMBUM" AS c ,"BWTAR" AS c ,"MENGE" AS c ,"MEINS" AS c ,"ERFMG" AS c ,"ERFME" AS c ,"BPMNG" AS c ,"BPRME" AS c ,"EBELN" AS c ,"EBELP" AS c ,"LFBJA" AS c ,"LFBNR" AS c ,"LFPOS" AS c ,"SJAHR" AS c ,"SMBLN" AS c ,"SMBLP" AS c ,"ELIKZ" AS c ,"SGTXT" AS c ,"EQUNR" AS c ,"WEMPF" AS c ,"ABLAD" AS c ,"GSBER" AS c ,"KOKRS" AS c ,"PARGB" AS c ,"PARBU" AS c ,"KOSTL" AS c ,"PROJN" AS c ,"AUFNR" AS c ,"ANLN1" AS c ,"ANLN2" AS c ,"XSKST" AS c ,"XSAUF" AS c ,"XSPRO" AS c ,"XSERG" AS c ,"GJAHR" AS c ,"XRUEM" AS c ,"XRUEJ" AS c ,"BUKRS" AS c ,"BELNR" AS c ,"BUZEI" AS c ,"BELUM" AS c ,"BUZUM" AS c ,"RSNUM" AS c ,"RSPOS" AS c ,"KZEAR" AS c ,"PBAMG" AS c ,"KZSTR" AS c ,"UMMAT" AS c ,"UMWRK" AS c ,"UMLGO" AS c ,"UMCHA" AS c ,"UMZST" AS c ,"UMZUS" AS c ,"UMBAR" AS c ,"UMSOK" AS c ,"KZBEW" AS c ,"KZVBR" AS c ,"KZZUG" AS c ,"WEUNB" AS c ,"PALAN" AS c ,"LGNUM" AS c ,"LGTYP" AS c ,"LGPLA" AS c ,"BESTQ" AS c ,"BWLVS" AS c ,"TBNUM" AS c ,"TBPOS" AS c ,"XBLVS" AS c ,"VSCHN" AS c ,"NSCHN" AS c ,"DYPLA" AS c ,"UBNUM" AS c ,"TBPRI" AS c ,"TANUM" AS c ,"WEANZ" AS c ,"GRUND" AS c ,"EVERS" AS c ,"EVERE" AS c ,"IMKEY" AS c ,"KSTRG" AS c ,"PAOBJNR" AS c ,"PRCTR" AS c ,"PS_PSP_PNR" AS c ,"NPLNR" AS c ,"AUFPL" AS c ,"APLZL" AS c ,"AUFPS" AS c ,"VPTNR" AS c ,"FIPOS" AS c ,"SAKTO" AS c ,"BSTMG" AS c ,"BSTME" AS c ,"XWSBR" AS c ,"EMLIF" AS c ,"EXBWR" AS c ,"VKWRT" AS c ,"AKTNR" AS c ,"ZEKKN" AS c ,"VFDAT" AS c ,"CUOBJ_CH" AS c ,"EXVKW" AS c ,"PPRCTR" AS c ,"RSART" AS c ,"GEBER" AS c ,"FISTL" AS c ,"MATBF" AS c ,"UMMAB" AS c ,"BUSTM" AS c ,"BUSTW" AS c ,"MENGU" AS c ,"WERTU" AS c ,"LBKUM" AS c ,"SALK3" AS c ,"VPRSV" AS c ,"FKBER" AS c ,"DABRBZ" AS c ,"VKWRA" AS c ,"DABRZ" AS c ,"XBEAU" AS c ,"LSMNG" AS c ,"LSMEH" AS c ,"KZBWS" AS c ,"QINSPST" AS c ,"URZEI" AS c ,"J_1BEXBASE" AS c ,"MWSKZ" AS c ,"TXJCD" AS c ,"EMATN" AS c ,"J_1AGIRUPD" AS c ,"VKMWS" AS c ,"HSDAT" AS c ,"BERKZ" AS c ,"MAT_KDAUF" AS c ,"MAT_KDPOS" AS c ,"MAT_PSPNR" AS c ,"XWOFF" AS c ,"BEMOT" AS c ,"PRZNR" AS c ,"LLIEF" AS c ,"LSTAR" AS c ,"XOBEW" AS c ,"GRANT_NBR" AS c ,"ZUSTD_T156M" AS c ,"SPE_GTS_STOCK_TY" AS c ,"KBLNR" AS c ,"KBLPOS" AS c ,"XMACC" AS c ,"VGART_MKPF" AS c ,"BUDAT_MKPF" AS c ,"CPUDT_MKPF" AS c ,"CPUTM_MKPF" AS c ,"USNAM_MKPF" AS c ,"XBLNR_MKPF" AS c ,"TCODE2_MKPF" AS c ,"/BEV2/ED_KZ_VER" AS c ,"/BEV2/ED_USER" AS c ,"/BEV2/ED_AEDAT" AS c ,"/BEV2/ED_AETIM" AS c ,"OINAVNW" AS c ,"OICONDCOD" AS c ,"CONDI" AS c FROM "MSEG" WHERE "MANDT" = @P1 AND "XBLNR_MKPF" = @P2

/* R3:/1BCDWB/DBMSEG:1298 T:MSEG */

</value>

  </action>

</event>

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on December 2013.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on January 2014.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on February 2014.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on March 2014.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on April 2014.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

Previous month: KBAs/Notes released/updated on March 2014

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on May 2014.

BC-DB-MSS*

BW-SYS-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

Previous month: KBAs/Notes released/updated on April 2014

Hi experts,

  I experienced a poor performance issue recently. I want to share my troubleshooting procedure and hope someone could give me some feedback.

Part one: The whole system is slow. This is a problem mostly a Basis guy should be responsible for.

1. Check OS07 or perfmon to see if there is any SQL server memory trimmed out or external programs have very high CPU utilization. Also check page life expectency is not below 300 seconds constantly. It indicates a memory pressure. SQL server performance decreases dramatically when Data cache hit ratio decreases because too much data has to be read from physical disks instead of memory.

2. Check DBACockpit -> Performance -> History -> DB Collector History to see if "PAGEIOLATCH_SH [ms] / request" and "WRITELOG [ms] / request" increase. If it happens, you need to check out expensive SQL statements in DBACockpit -> Performance -> History -> SQL statement history or if a full backup occurs or a checkdb is running(Check SQL server agent -> jobs or exec sp_WhoIsActive, you can search and download  this stored procedure using google). You can trigger the job: SAP_<sid>_<SID>_MSSQL_COLLECTOR in the SQL server agent -> Jobs to take a snapshot instead of waiting for 20 minutes.

ex: run this T-SQL script to check non-R3 processes

select * from sysprocesses where program_name not like 'R3%' and spid > 50 and status = 'runnable'

3. Check DBACockpit -> Performance -> Locks to see if there is any blocking locks. Sometimes this job executes for a long time and you might miss a lot of blocking locks information(including the active blocking locks). You can use exec sap_lock2 in SQL server management studio or download HangMan.vbs from a SAP note instead.

4. Run SE38 -> /SDF/RSMSSVSE to compare wait events by day or every 10 minutes. If you find a wait event you are not familiar, search its meaning here (sys.dm_os_wait_stats (Transact-SQL) ). Please refers to this customer message( How to identify which SQL statement contributes the largest percentage of wait time? ).

5. Check SM66 to see if there are too many programs running and are they all necessary? Check SM50 to see if the program is reading the data from SQL server. Normally, you should see sequential reads or other operations read, ex: more than 1600 records per second. If it reads just 200 records per second, something slows down SAP on SQL server. you should create a baseline(measure the read speed using SAT) when the system is normal.

ex:

<PRD>

DB: Fetch MSEG 9967 hits with 12 seconds(830 MSEG Fetch per second)

DB: Open MKPF 13554 hits with 8 seconds(1669 MKPF Open per second)

<QAS>

DB: Fetch MSEG 9787 hits with 64 seconds(152 MSEG Fetch per second)

DB: Open MKPF 13309 hits with 29 seconds(458 MKPF Open per second)

6. Eliminate unnecessary queries. Use DBACockpit -> Performance -> Database Processes, then un-check "Include SQL Engine Processes" and check "Active Request Only". Use Reset and Since Reset to check which program consumes the highest CPU and Reads. In production system, you might find dozens of running processes so it is difficult to identify which one should be terminated. Anyway, you can use step 2 first.

7. Check the bottleneck from ST03. Compare ST03 -> Detail Analysis -> Last minutes's Load with yesterday's load. Check if database time consumes more than 40% of total runtime. If the answer is yes, it indicates it is a database performance issue or a network performance issue(SQL server does not transfer the data to application servers fast enough) or the active programs request too much data.

Part two: A specific program is slow. This is a problem mostly a developer should deal with.

1. Check execution plan. Use  DBACockpit -> Performance -> Database Processes to see the execution plan SQL server is currently used. Does the variant select too many records? Is it an optimized plan? Is update statistics up to date? Is there a parameter sniffing?

2. If you see SQL server does not read the data in SM50 and there is no blocking locks, your next step is to use SAT to trace SAP ABAP codes. Is there an infinite loop or a long running RFC? Anyway, you have to identify what does SAP actually do in this time frame.

Frequently Asked Questions - SAP on SQL Server 2012

Which SAP products are supported on SQL Server 2012?

Currently, SAP supports the following SAP products on SQL Server 2012:

• SAP products based on SAP NetWeaver 7.0 including all EHPs

For installation restrictions, see SAP note 1651862  (SMP login required).

For more information about SAP products supported on SQL Server 2012, see the Product Availability Matrix (PAM) at http://service.sap.com/pam.

Which editions of Windows Server 2008 (R2) are supported with SQL Server 2012?

SAP supports the following 64-bit Windows Server 2008 (R2) editions:

• Standard edition, Enterprise edition, and Datacenter edition
• Windows Server 2008 (R2) Server Core is not supported by SAP.

You can find the information about supported Windows versions in the Product Availability Matrix (PAM) at: http://service.sap.com/pam.

With SQL Server 2012, SAP no longer supports 32-bit database servers, 32-bit application servers, Itanium-based database servers, or Itanium-based application servers. If you run your SAP system on 32-bit Windows or on Windows for Itanium-based systems, you cannot upgrade to SQL Server 2012. SAP does not plan to support 32-bit SQL Server 2012 in the future.

Where do I find information about installing and running an SAP system on SQL Server 2012?

Read the following document: Upgrade to and Installation of SQL Server 2012 in an SAP Environment.

You can download it at: http://service.sap.com/instguides -> Database Upgrades -> MS SQL Server (SMP login required).

In addition, read the following SAP notes (SMP login required):

• 1651862: Release planning for Microsoft SQL Server 2012
• 1676665: Setting Up Microsoft SQL Server 2012
• 62988:  Service Packs for Microsoft SQL Server

Are older SAP releases supported on SQL Server 2012?

SAP releases based on 4.6C, 6.20, and 6.40 are not supported on SQL Server 2012.

What are the benefits of using SQL Server 2012?

SQL Server 2012 introduces many new features and enhancements in all SQL Server components, including the following new features used by SAP:

• AlwaysOn – a new more comprehensive high-availability and disaster-recovery technology
• SQL Server Column-Store, which is implemented for SAP BW of the listed SAP NetWeaver releases
• Improved online index handling
• Enhanced monitoring already implemented in DBA Cockpit

Which SAP Products Are Supported On SQL Server 2008 (R2)?

SAP supports the following SAP products on SQL Server 2008 (R2):

• SAP products based on SAP NetWeaver 7.1 and higher
• SAP products based on SAP NetWeaver 7.0 SR3, or 7.0 EHP1 and  higher

For  installation restrictions, see SAP note1076022.

For more information about SAP products supported on SQL Server 2008 (R2), see the Product Availability Matrix (PAM) at http://service.sap.com/pam

Which Editions Of Windows Server 2008 (R2) Are Supported With SQL Server 2008 (R2)?

SAP supports the following 64-bit Windows Server 2008 (R2) editions:

• Standard edition, Enterprise edition, Datacenter edition, and for Itanium-Based Systems edition
• Windows Server 2008 (R2) Server Core is not supported by SAP.

You find the information for supported Windows version  in the Product Availability Matrix (PAM) athttp://service.sap.com/pam.

With SQL Server 2008, SAP no longer supports 32-bit database servers or 32-bit application servers. If you run your SAP system on 32-bit Windows, you are not able to upgrade to SQL Server 2008 (R2). SAP does not plan to support 32-bit SQL Server 2008 (R2) in the future.

Which Editions Of SQL Server 2008 (R2) Are Supported For Products Based on NetWeaver?

Please note that the Enterprise Edition is the only Edition supported by SAP for such products. This is explained in more detail in SAP note 62988.

Where Do I Find Information About Installing And Running An SAP System On SQL Server 2008 R2?

Besides the current installation guides for SAP NetWeaver 7.3 or SAP NetWeaver 7.0 EHP2 for SQL Server, you can also read the following document: Upgrade to and Installation of SQL Server 2008 (R2) in an SAP Environment. You can download it at:http://service.sap.com/instguides-> Database Upgrades -> MS SQL Server (SMP Login required).

In addition, read the following SAP notes (SMP Login required):

• 1076022: Release planning for Microsoft SQL Server 2008 (R2)
• 1152240: Setting Up Microsoft SQL Server 2008 (R2)
• 62988: Service Packs for Microsoft SQL Server

Are Older SAP Releases Supported On SQL Server 2008 (R2)?

SAP releases based on 4.6C, 6.20 and  6.40 are not supported on SQL Server 2008 (R2) and Windows Server 2008 R2. However, you can run the older releases on SQL Server 2008 R2 and Windows Server 2008 R2 to prepare for an upgrade to an SAP release based on SAP NetWeaver 7.0 SR3 and higher, or SAP NetWeaver 7.1 and higher.

For older SAP releases, you should perform the upgrade of the SAP system to newer SAP releases on SQL Server 2008 R2 after you migrated your operating system to Windows Server 2008 R2. To migrate the older SAP releases to SQL Server 2008 R2 and Windows Server R2, perform a system copy before you upgrade the system to newer SAP releases. For more information about the system copy procedure to move your older SAP releases to SQL Server 2008 R2, see SAP note1476928(SMP Login required).

SAP supports the upgrade of an older SAP release on Windows Server 2008 R2 with the following limitations:

• You do not run a high-availability SAP system.
• Your start release is 4.6C or  6.20 and 6.40. During the upgrade, the productive use of the SAP system is not allowed.

What Are The Benefits Of Using SQL Server 2008 (R2)?

SQL Server 2008 (R2) introduces many new features and enhancements in all SQL Server components.The following lists some of these new features used by SAP:

• Merge Command
• Backup Compression (optional)
• Transparent Data Encryption (optional)
• Changed Data Capture (optional)
• Star Join Optimization (BW)
• Grouping Sets (BW)
• Parallelism for partitions (BW)
• Row and Page compression
• increased speed of partition drop: 15000 Partitions (SQL Server 2008 SP2 - feature not yet available in SQL Server 2008 R2). For more information, see the followingblog.
• Unicode compression (SQL Server 2008 R2)

The purpose of this document is to provide a list of KBAs/Notes that were released/updated on June 2014.

BC-DB-MSS*

Please note, in order to view the contents of the guides and SAP Notes, you will need to be logged into Service Marketplace.

Previous month:  KBAs/Notes released/updated on May 2014