|MS SQL Server Administration: Introduction
A database administrator (DBA) has to focus on keeping the SQL server running and doing it fast. Configuration of the server and the software is the prime responsibility of database administrator. Mere installing of the server software is not an end in itself. More important is the pre-installation decisions like layout of the drive, number of servers, schemes for replication, etc. The role of the SQL server towards proper sizing and configuration of the hardware is also required to be determined.
Space management is one of the most pressing issues after installation of the server. An administrator may adopt an approach of setting the server and leaving it like that since SQL server can grow or reduce any database automatically. Instead the administrator should follow any of the many appropriate strategies to monitor and notify the server space.
The DBA is mainly responsible for taking regular backups and this is one thing a DBA cannot afford to ignore. Lack of such backups could spell disaster in the event of a crisis of meltdown of the SQL server in which situation not even the best SQL skill can help if there is no backup. There are wizards and tools to help in such situation but that does not take away the necessity for the DBA to understand what the wizard has chosen to do.
Knowing performance of recovery steps is very important. Although for recovery of database up to the last known good state, necessary tools are available with the Enterprise Manager of SQL server, yet understanding the performance by the DBA is always desirable.
The DBA has to learn the server environment that changes with time. It is always better to maintain service pack installation log and security accounts.
Performance on each database needs to be actively monitored and performance optimized for the server to run and run fast. The internal SQL server tools like Query Analyzer and Enterprise Manager as also external tools help a DBA in this task.