SQL Server - SPLessons

SQL Server Postponing the Scaling Decision

Home > Lesson > Chapter 7
SPLessons 5 Steps, 3 Clicks
5 Steps - 3 Clicks

SQL Server Postponing the Scaling Decision

Postponing the Scaling Decision

shape Description

Postponing the Scaling Decisions consisting of many things that can postpone or avoid the time and expense of scaling up or scaling out. And all most each and every  system has an opportunities for performance improvements, regardless of what else make a sense in terms of scalability  and checking out to find the key measurements for improving the performance that depends on the applications which may not be able to make certain types of changes. And depending upon the types of applications which make a sense to make certain types of changes. For example, like third party applications that can automatically sense with the application and the same application can be developed with legacy internally and can easily improve the performance at certain criteria, which make sure all the problems will be verified at all the stages with an appropriate time frame. Starting from the application design to database design with the instance level settings and database properties that go beyond the storage subsystems and hardware.The following are the measures for postponing the scalability decisions,such as:
  • Availability - Failover clustering solution that is build on windows server cluster.
  • Demand - Are the server skills.
  • Analysis - Describes the services.
  • Decision making - Taking an appropriate decision for performing a specific task.

Preventing the scaling problems

shape Description

Preventing the scalability problems start with the refactor and optimize the applications that quite often doesn't have the option with the third party applications or with the internal applications where the resources available for executions. And next step is to go beyond the database architecture and design level  and have control over all the applications that are even with the third party applications with some of the conditions. And all this scalability will improve the index situations by carefully checking the index tuning  and proper index by maintenance are very effectively. And the next stage is to make sure that all the operating systems and instances levels settings are set with an appropriately for the best performance and scalability that really efficient to use and is under the control even with the third party applications and making sure all the database properties are configured properly and can have definitely have control over that in almost every single case. And at the same point of time time the storage subsystem and make sure that all the configuration are properly configured or not. And has to be enabled with the hyper threading and modern Intel processors.

Improving the  performance of scaling

shape Description

The most common belief for improving the performance of scaling in the database or database server is always depends on the execution and scalability with bottleneck. The database is guilty until for the proven innocent and it may or may not be true, but generally used in the standardized assumptions. For improving the scaling all the tools and techniques have to been determined with the actual performance based on the bottle necks and has to be performed in an emergency stage only with out staying calm.And the idea exists to have an 911 emergency script and all the procedure are in the ready mode with all the required standard criteria's. Once the user is dealing with more then one emergencies that will gain confidence and improve the skills diagnostics with various techniques that are letting the user for better results.And at the same time the developer has to improve the personal script collections  and have  to maintain good set of baseline metrics.

Summary

shape Key Points

  • Postponing the Scaling Decision -Means postpone or avoiding the time and expanse of scaling.
  • Preventing The Scaling Problems - Begins from refactor and with the third part applications.
  • Improving The Performance Of Scaling - Basically  depends on the execution and scalability issues.