Each instance of the Database Engine must be configured to meet the performance and availability requirements defined for the databases hosted by the instance. The Database Engine includes configuration options that control behaviors such as resource usage and the availability of features such as auditing or trigger recursion.
When a database is deployed into production there is often a service level agreement (SLA) defining areas such as the levels of performance required from the database and the required availability level of the database. The terms of the SLA typically drive configuration requirements for the instance.
An instance is usually configured immediately after it has been installed. The initial configuration is usually determined by the SLA requirements of the types of databases planned to be deployed to the instance. After the databases have been deployed, the database administrators monitor the performance of the instance and adjust the configuration settings as needed if the performance metrics show the instance is not meeting the SLA requirements.
|Describes the various instance configuration options and how to view or change these options.||Server Configuration Options (SQL Server)|
|Describes how to view and configure the default locations of new data and log files in the instance.||View or Change the Default Locations for Data and Log Files (SQL Server Management Studio)|
|Describes how to configure SQL Server to use soft-NUMA.||Soft-NUMA (SQL Server)|
|Describes how to map a TCP/IP port to non-uniform memory access (NUMA) node affinity.||Map TCP IP Ports to NUMA Nodes (SQL Server)|
|Describes how to enable the Windows Lock Pages In Memory policy. This policy determines which accounts can use a process to keep data in physical memory, preventing the system from paging the data to virtual memory on disk.||Enable the Lock Pages in Memory Option (Windows)|