We even saw that the total Server Memory was lower than the Target Server Memory. SQL Server:Memory Manager –> Target Server Memory.SQL Server:Memory Manager –> Total Server Memory.Since the Java stack was running in another VM, there should have been plenty of memory for SQL Server to leverage. It had 6GB of the 16GB VM allocated for it. Once we had Terminal Server access, everything looked normal on a first glance. The website or at least parts of it were relying on the SAP Netweaver Java stack which was running on top of SQL Server 2008R2. When analyzing the outages, SAP Support found that the VM which ran SQL Server had on two occasions completely hung and the VM had to be restarted. Lately our SAP colleague Leslie Moser and myself got involved in a support case where a company had severe problems to keep their website up and running for days and weeks.
0 Comments
Leave a Reply. |