5/21/2011 6:26:18 AM
Vasudev Menon -
Please do bear with me as I am going to cover this topic in 3 parts.
Part 1 – To give a background on “why was this exercise initiated, to collect performance counter values and then to study and analyse the memory pressure on the current SQL instance(s)”
Part 2 – How we went about setting up the performance counters to be collected for a duration of 18 hours and which counters were used.
Part 3 – Analysing the values captured and then based on the results, arriving to a conclusion on the new “minimum and maximum memory settings” to be proposed for the SQL instance(s) concerned.
Our department’s infrastructure team has decided to upgrade the specs of systems hosting the SQL instances and web applications on the TESTING and DEVELOPMENT environments. This is as part of their objective to improve performance and resilience of some our critical web applications on the TESTING and DEVELOPMENT environments.
The decision was to implement a new 2 node active-active cluster for the SQL instance(s) that host the database(s) for some of the critical web applications on the TESTING environment. The new infrastructure proposed for hosting the identified existing SQL instances were 2 new servers [2x HP XXXXX XX blades, 24GB RAM, 2x Intel XXXXX 2.4 GHz 6-core processors, dual port 4Gb Xxxxxx HBA, Quad Port 1Gb NIC, 512MB Flash Backed Cache].
We had already identified 5 SQL instances on the TESTING environment that needed to be migrated on to these new infrastructure.
As part of the design stage, our DBA team was entrusted with the responsibility of analysing &recommending:
A simple straight forward request, but this meant:
Vasudev Menon (Member since: 4/26/2011 5:00:57 AM)
View Vasudev Menon 's profile
Leave a comment