You may find it hard to believe, but it is possible to maintain SQL Server high availability and not spend a fortune. In fact, you can spend a fortune and still not get SQL Server high availability. Sound like a paradox? Not really. SQL Server high availability is not a direct function of how much you spend. Instead, high availability is more about what you do right and what you do wrong.
Identifying Long Running Queries is First Step
At this step in the SQL Server performance audit, you should have identified all the "easy" performance fixes.
Virtually every SQL Server runs one or more daily jobs. And most likely, runs many weekly jobs. Unfortunately, most DBAs set up jobs, and then forget about them, unless of course they break. But if they run day after day without any problems, most jobs are forgotten about.
Application and Transact-SQL Code Greatly Affect SQL Server Performance.
Auditing Index Use is Not an Easy Task, But Critical to Your Server's Performance.
Each Database Needs to Be Audited
As part of your performance audit, you need to examine each database located on your server and examine some basic database settings. When compared to some of our other performance audit tasks, you will find this audit one of the easiest. For convenience, you may want to consider photocopying a copy of the above chart, producing one copy for each database that you will be auditing.
Most SQL Server Configuration Settings Should Not Be Changed
Like SQL Server, Windows Server is mostly self-tuning. But like SQL Server, there are things we can do to help optimize Windows' performance.
Auditing SQL Server Hardware Is An Important Early Step
The best place to start your SQL Server performance audit is to begin with the Performance Monitor (System Monitor). By monitoring a few key counters over a 24 hour period, you should get a pretty good feel for any major hardware bottlenecks your SQL Server is experiencing.
iEntry 10th Anniversary
RSS
Newsletter
Advertising
