Many users are now plagued by slow database problems and are struggling to pay for a professional DBA that is too expensive. Software maintenance personnel on the database is not so deep understanding, so that the problem can not be resolved, or can only be temporarily resolved can not be cured. Developers to solve data problems are basically searching Baidu various methods to try again, may miss the best time to diagnose problems and may try a bunch of methods at last helpless give up.
This series of articles is mainly shared with enterprise IT operations or database practitioners, how to solve the problem of database in the quickest way? When the problem arises, there should be some solution and instinctive judgment. Let the database problem arise, we are no longer so flustered, no longer have no clue.
In addition, in view of the current enterprise application to the database, elaborated some best practices, 90% of the system problems, caused by 10% of the problem, there is no high-tech, and some only to solve the 10% problems of experience.
This series is mainly explained by the Expert for SQL Server tool and is divided into the following chunks:
Expert Diagnostic Optimization Series------------------is your CPU high?
Expert Diagnostic Optimization Series------------------not enough memory?
Expert Diagnostic Optimization Series------------------wronged the disk.
Expert Diagnostic Optimization Series------------------statement tuning kick
Expert Diagnostic Optimization Series------------------through the waiting to see the system
For further articles, please look forward to:
tempdb analysis
Cache Schedule
Lock analysis
Backup Strategies for Databases
SQL SERVER General Configuration Best Practices
Discussion on advantages and disadvantages of high availability and read/write separation technology
Comprehensive database optimization------------Expert for SQL Server Diagnostic series