skip to content »

Quickly validating sql server configuration settings

Today, SQL Server and Windows Authentication mode may be able to successfully compete with Windows Authentication mode.

Tip When you’re configuring auditing, it is a best practice to configure auditing to capture both failed and successful logins.The value 50 is ideal when a table has plenty of reads and writes.This setting is global to all tables within the Database Engine.Both of these authentication methods provide access to SQL Server and its resources.The Windows Authentication Mode setting is the default Authentication setting and is the recommended authentication mode.If the backup server fails for some reason, you can re-install the backup server and quickly restore its configuration from the configuration backup.

You can also use configuration backups to apply the configuration of one backup server to another backup server in the backup infrastructure.

Also worth mentioning, when Windows Authentication mode is active, user accounts are subject to enterprise-wide policies enforced by the Active Directory domain, such as complex passwords, password history, account lockouts, minimum password length, maximum password length, and the Kerberos protocol.

These enhanced and well-defined policies are always a plus to have in place.

These SQL Server settings include Server Authentication, Login Auditing, Server Proxy Account, and Options. The first section in the Security page focuses on server authentication.

At present, SQL Server 2005 continues to support two modes for validating connections and authenticating access to database resources: Windows Authentication Mode and SQL Server and Windows Authentication Mode.

For more information on fill factors, refer to Chapter 8, “SQL Server 2005 Maintenance Practices” and Chapter 9, “Managing and Optimizing SQL Server 2005 Indexes.” Figure 1.6.