Skip to Content

Performance - DBMS on each system (iSCSI) or one DBMS for multiple systems (LAN)


we have four servers running Microsoft Hyper-V, which are used to host virtual servers for our SAP systems (Virtualized system landscape).
Each virtual SAP system system is a NetWeaver system running Windows 2008 R2 x64 with a Microsoft SQL Server Instance running on it. The Hyper-V hosts are connected via iSCSI (4 x 1GBit) to a SAN (Dell MD3000i). Currently each Hyper-V host is running three to four SAP systems (1-2 NW ABAP, 1-2 NW JAVA). So overall we have about 15 systems (ABAP/Java+DBMS) up and running, which are using a iSCSI connection.

Unfortunately we are also facing some bad system performance, which seams to be related to bad SQL Server Performance (most of the time long waits - as reported by t-code ST04). In detail:
- Latch Wait Time per Request (ms) exceeds 40 milliseconds
- Wait Time per Log Write (ms) exceeds 10 milliseconds

So I think(!) the bottle-neck could be the iSCSI connection (15 virtual servers share that 4x1 GBit line to the SAN). What if we use a single DMBS (with a database instance for each SAP SID) on one "big" physical server, with physical attached hard disks (so no I/O bottle-neck, because SAS and not iSCSI) and let the SAP systems then connect to this DBMS via GBit-LAN? Do you think this will be even more worse or would it be an performance improvement? Note: Most of the time we are not dealing with large data, most requests are just small updates. I am also aware that having a single DBMS host is a single point of failure, but my question is just regarding the Database Performance for a NetWeaver system. Or do you know another way to have an performance improvement?

Thanks and best regards,

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 19, 2012 at 07:24 AM

    Hi Markus,

    The iSCSI connection may be the bottleneck, but I'd focus on tuning in other areas before migrating 15 DB instances to one physical server. What kind of drives are in the SAN? SATA will have noticeably slower I/O. If possible, ensure the LUNs that house the DBs are on SAS.

    Are you over committing your CPU and memory on the hosts? I've seen this as a common problem when running SAP in a virtual environment. SAP recommends reserving the resources for each VM.

    Take a look at the following note:

    Note 1409608 - Virtualization on Windows


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.