Single Person Security Example

In this example, a single person is responsible for all aspects of the database and will be the only person using it. The user must be able to create the database and its tables, write programs that interface with the data, load and maintain data, and produce reports.

This scenario presents the simplest possible security system. There is only a single user who needs full access to all activities and data in the database.

The first step is to add a Microsoft® SQL Server™ user account for LONDON\tombrown. This user account allows access to SQL Server. The predefined sysadmin role contains all permissions necessary for this user, so the LONDON\tombrown SQL Server user account should be added as a member of sysadmin. When LONDON\tombrown connects to SQL Server, SQL Server trusts that he has been authenticated by Microsoft Windows NT®, so his connection is accepted, and he is allowed to perform activities based on the permissions associated with sysadmin.

If SQL Server is running under Mixed Mode, a user account tombro could be added to SQL Server independent of the Windows NT user account, and tombro could then be added to sysadmin. When the user logs into Windows NT and attempts to connect with SQL Server, he must specify the tombro user account name and password.