When you are planning data platform consolidation, it is very important to track down the changes in the overall system performance after the actual migration is done. You should understand the differences in the configurations and performance of the instances and databases. Then you will also understand better how well the actual planning work went, and which are the possible challenges in the data platform.
Having a scattered Microsoft SQL Server database platform is cumbersome to maintain, as you continue to accumulate waste capacity to your database servers. Therefore, you should consider consolidating your platform to make it more manageable. Let us learn about Why is SQL Server Consolidation Better Than Having a Scattered Environment?
Have you ever imagined how often SQL Server performance issues are actually caused by poor capacity planning? Sometimes a SQL Server database has insufficient storage performance, an instance is running out of memory, or the server level CPU is skyrocketing to an unhealthy level.
If you have ever needed to implement a large-scale data platform migration or consolidation project, you are definitely familiar with many of the pain points faced during the process. Firstly, manual data collection is very tricky to arrange and demands lots of work. Secondly, the planning of the capacity is a complex and detailed process – you need to take all the performance counters, their threshold levels and SLA’s, trends, different server benchmarks and such into account. When it comes to the consolidation effort, it is impossible to try to rearrange the SQL Server instances into a most optimal target server setup with manual work. All this takes a lot of time and is prone to human error.