However one thing showed up as suspicious. A first assumption would indicate, that SQL Server didn’t need more memory due to low workload and hence it didn’t even reach the maximum of what it could allocate. Means according to the configuration settings of ‘min server memory’ and ‘max server memory’ for SQL Server, SQL Server could have allocated more (Target Server Memory) than it really allocated. We even saw that the total Server Memory was lower than the Target Server Memory.
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 kommentar(er)
