Server Uniform Ideas
|
|
Fox Sports: Soccer ’99 $0.95 This software is BRAND NEW. Packaging may differ slightly from the stock photo above. Please click on our logo above to see over 15,000 titles in stock…. |
Scaling and SQL Server Optimization
DBAs have the responsibility of maintaining and improving database production environments. This includes making the decision of whether or not they will scale the hardware systems. There are variables such as time frames and budgets that make this decision very difficult. One of the most important decisions is whether to scale up or scale out.
To scale up means moving databases and applications to bigger and better hardware with more powerful processors, greater amounts of memory, and faster disk drives. Increased levels of system resource use might necessitate a scaled up production environment to be sure that end users are getting the best possible experience.
Get additional SQL Server Optimization information.
To scale out basically means using federated servers to partition and replicate data across them. Examples include functional partitioning of CRM or ERP functionality on different servers and horizontal data partitioning across multiple databases.
Consider SQL Server Performance Tuning
Ensure that scaling up or scaling out is a necessity. Sufficient SQL server performance tuning could be a great help when making that decision. Most performance and scalability issues can be resolved through SQL server optimization. You should optimize SQL server databases and applications with wait time performance data and historical trend data before you decide to scale up or scale out.
A majority of performance bottlenecks such as inefficient locking, bad indexes, and unprepared SQL statements that cause overloaded CPUs, and disk input/output utilization can be resolved with SQL server optimization instead of scaled up hardware.
Should You Scale Up Or Scale Out?
When each application and database has been optimized and performance issues still arise, you must then determine if it is time to scale up or out. It is common to scale up first. Even though scaling up may require significant expenditures, it is easier and more efficient than scaling out. Scaling up is essentially upgrading slower hardware with new, fast equipment and/or adding additional hardware components to the current configuration.
If, once you have scaled up on hardware, your system is still experiencing performance issues, you should consider scaling out and implementing a federated server environment. Cutting back on the work each individual server must do will probably eliminate any performance issues that still occur.
If you don't have the funding to purchase new hardware (scale up), scaling out becomes a viable option. If you already have sufficient server capacity, your expenditures will be decreased dramatically. You must, however, determine whether the cost savings is worth the added complexity of running a federated server environment.
Discover more benefits of SQL Server Optimization.
Optimize First, Scale Later
It is imperative to repeat that proper optimization at the database and application levels is the least expensive and most efficient way to enhance performance. You should be able to eliminate the need for scaling up or out if you focus server performance tuning on the database and application levels. Make sure that you have tried every performance optimization option before you decide that scaling is the only way to solve your performance issues.