Windows Authentication
Windows authentication uses Windows NT user account and security mechanisms. This type of security, with the SQL server for your username and password for Windows NT and allows the user to circumvent the application of SQL Server. Users with a valid Windows NT can connect to SQL server without a username and password.
Some advantages of Windows authentication are:
* A user does not remember a password and user name.
* If the password in Windows NT, the user does not change the password in SQL Server.
How does Windows authentication work? If a user has access to an SQL Server, SQL Server, the user information and password of the user's NT security attributes. These properties, when the user logs on to Windows NT. If the user access to SQL Server, the user automatically to SQL Server. With Windows authentication, you can take advantage of Windows NT features such as password aging and access.
Windows NT authentication requires more practical experience and in close collaboration with the NT system administrator when creating user accounts and groups. Configuring Windows Authentication requires some further steps towards implementation of the SQL Server authentication, but the benefits outweigh the additional configuration steps.
Mixed Security
Mixed Mode security, both Windows Authentication and SQL Server authentication are enabled. When using SQL Server authentication, an individual access to SQL Server must have a user name and password that validates against a SQL Server system table. When using Windows authentication (see "Windows Authentication" for more information), users can access SQL Server without being prompted for a username and password.
User Database
The database user defined database (s) a person can access. After an individual access to SQL server, either Windows Authentication or SQL Server authentication, SQL Server determines whether the user is a valid user name for the database that you access. Regardless of the safety mode, a user should access the database. If the user is not allowed in the database, SQL Server returns an error message.
The only exception to the user database is the concept of "guest" user. See the following topic for more information about the user guest.
Guest User
Username guest, you can in a database so that anyone with a valid connection to SQL Server to access the database. The username is a member of the public service. According to the "guest" user is in a database, anyone with a valid connection to SQL Server [MD], regardless of how security [MD] can access the database when the user is visiting. A guest user works as follows:
1. SQL Server checks whether the login ID is in possession of a valid user name or alias assigned. If so, SQL Server provides the user access to the database as the user name or alias. If not, proceed to Step 2
2. SQL Server checks whether a user name guest. If this is the case, the login ID is the access to the database as a guest. If the guest account does not exist, SQL Server denied access to the database.
Permits
A permit may be someone to do something in a database. There are two types of permissions: object and statement. Object permissions control who has access and manipulate data in tables and views, and that can execute stored procedures. Statement permissions control who can create and drop objects in a database.
SQL Server uses the GRANT, revoke, and refuse to manage permissions.
GRANT - in the authorization to an object, can anyone against the object (eg, SELECT, UPDATE, INSERT, DELETE, or EXECUTE). In granting permission for an explanation, with someone who makes the statement (eg CREATE TABLE).
REVOKE - To revoke a permit for an object, preventing someone from an action against the object (eg, SELECT, UPDATE, INSERT, DELETE, or EXECUTE). If you revoke a permit statement, you take a user is able to execute the statement (eg CREATE TABLE).
DENY - The denial of a permit for an object, some of the explicit use of the authorization (eg SELECT, UPDATE, INSERT, DELETE, or EXECUTE), while in reality REVOKE removes permission.
Object Permissions
Object permissions to access objects in the SQL Server. You can grant and revoke permissions for tables, columns, views, stored procedures and Enterprise Manager from the system or procedure. A user who wishes to object to have the appropriate authorization. For example, if a user wants, SELECT * FROM table1, they should have permission for the selection table.
Statement Permissions
Statement permissions control who can administrative measures such as the creation of backups or database. Only SA, members of the sysadmin role, or database owner permissions statement. I recommend caution in assigning access rights to the declaration, such as CREATE DATABASE, BACKUP DATABASE and BACKUP LOG. In general, the best solution is to establish the SA, a member of the System Administrator role or the owner of the database management of these statements. The following is a list of the statement that the permissions can be granted or revoked:
* CREATE DATABASE - create a database. This authorization may only be issued by the SA and only the master database.
DEFAULT * Create - Creates a default value for a column.
* CREATE PROCEDURE - Create a stored procedure.
* Create Articles - Creates a column of the table the rule.
* CREATE TABLE - Creates a table.
* CREATE VIEW - Creates a.
* BACKUP DATABASE - Back up the database.
* TRANSACTION backup - Back up the transaction log.
Features
Functions provide a logical way to group users with permissions. The following are the types of functions in SQL Server:
* Server functions
* Database Functions
Server roles
Server roles to access a level of server operations and tasks. If a person in a role that the task for the role. For example, a person who is a member of the sysadmin role can all actions in the SQL Server.
Server roles are predefined and serverwide. These functions are not specific to the database and can not be adjusted.
Database Functions
Database mapping functions from a number of database-specific permissions for an individual or a group of users. Database functions can be allocated to the Authenticated applications NT authenticated logins or SQL Server. Roles assigned to NT authenticated access can be assigned to users of Windows NT and NT groups. Functions can also be nested so that a hierarchical set of permissions can be used for logins.
Features include database-specific database. SQL Server provides three types of functions:
* Database of predefined functions
* Database user-defined functions
* Implicit Functions
Functions from a predefined database
Database of predefined functions are standard features of SQL Server database. Each database in SQL Server provides the following functions. Database functions, the predefined delegate responsibility. For example, a developer db_ddladmin could play a role in the development of databases. This feature allows a programmer to create and delete objects (tables, stored procedures, views, etc.) as needed.
Functions are database-specific pre-defined databases and can not be adjusted.
Windows authentication uses Windows NT user account and security mechanisms. This type of security, with the SQL server for your username and password for Windows NT and allows the user to circumvent the application of SQL Server. Users with a valid Windows NT can connect to SQL server without a username and password.
Some advantages of Windows authentication are:
* A user does not remember a password and user name.
* If the password in Windows NT, the user does not change the password in SQL Server.
How does Windows authentication work? If a user has access to an SQL Server, SQL Server, the user information and password of the user's NT security attributes. These properties, when the user logs on to Windows NT. If the user access to SQL Server, the user automatically to SQL Server. With Windows authentication, you can take advantage of Windows NT features such as password aging and access.
Windows NT authentication requires more practical experience and in close collaboration with the NT system administrator when creating user accounts and groups. Configuring Windows Authentication requires some further steps towards implementation of the SQL Server authentication, but the benefits outweigh the additional configuration steps.
Mixed Security
Mixed Mode security, both Windows Authentication and SQL Server authentication are enabled. When using SQL Server authentication, an individual access to SQL Server must have a user name and password that validates against a SQL Server system table. When using Windows authentication (see "Windows Authentication" for more information), users can access SQL Server without being prompted for a username and password.
User Database
The database user defined database (s) a person can access. After an individual access to SQL server, either Windows Authentication or SQL Server authentication, SQL Server determines whether the user is a valid user name for the database that you access. Regardless of the safety mode, a user should access the database. If the user is not allowed in the database, SQL Server returns an error message.
The only exception to the user database is the concept of "guest" user. See the following topic for more information about the user guest.
Guest User
Username guest, you can in a database so that anyone with a valid connection to SQL Server to access the database. The username is a member of the public service. According to the "guest" user is in a database, anyone with a valid connection to SQL Server [MD], regardless of how security [MD] can access the database when the user is visiting. A guest user works as follows:
1. SQL Server checks whether the login ID is in possession of a valid user name or alias assigned. If so, SQL Server provides the user access to the database as the user name or alias. If not, proceed to Step 2
2. SQL Server checks whether a user name guest. If this is the case, the login ID is the access to the database as a guest. If the guest account does not exist, SQL Server denied access to the database.
Permits
A permit may be someone to do something in a database. There are two types of permissions: object and statement. Object permissions control who has access and manipulate data in tables and views, and that can execute stored procedures. Statement permissions control who can create and drop objects in a database.
SQL Server uses the GRANT, revoke, and refuse to manage permissions.
GRANT - in the authorization to an object, can anyone against the object (eg, SELECT, UPDATE, INSERT, DELETE, or EXECUTE). In granting permission for an explanation, with someone who makes the statement (eg CREATE TABLE).
REVOKE - To revoke a permit for an object, preventing someone from an action against the object (eg, SELECT, UPDATE, INSERT, DELETE, or EXECUTE). If you revoke a permit statement, you take a user is able to execute the statement (eg CREATE TABLE).
DENY - The denial of a permit for an object, some of the explicit use of the authorization (eg SELECT, UPDATE, INSERT, DELETE, or EXECUTE), while in reality REVOKE removes permission.
Object Permissions
Object permissions to access objects in the SQL Server. You can grant and revoke permissions for tables, columns, views, stored procedures and Enterprise Manager from the system or procedure. A user who wishes to object to have the appropriate authorization. For example, if a user wants, SELECT * FROM table1, they should have permission for the selection table.
Statement Permissions
Statement permissions control who can administrative measures such as the creation of backups or database. Only SA, members of the sysadmin role, or database owner permissions statement. I recommend caution in assigning access rights to the declaration, such as CREATE DATABASE, BACKUP DATABASE and BACKUP LOG. In general, the best solution is to establish the SA, a member of the System Administrator role or the owner of the database management of these statements. The following is a list of the statement that the permissions can be granted or revoked:
* CREATE DATABASE - create a database. This authorization may only be issued by the SA and only the master database.
DEFAULT * Create - Creates a default value for a column.
* CREATE PROCEDURE - Create a stored procedure.
* Create Articles - Creates a column of the table the rule.
* CREATE TABLE - Creates a table.
* CREATE VIEW - Creates a.
* BACKUP DATABASE - Back up the database.
* TRANSACTION backup - Back up the transaction log.
Features
Functions provide a logical way to group users with permissions. The following are the types of functions in SQL Server:
* Server functions
* Database Functions
Server roles
Server roles to access a level of server operations and tasks. If a person in a role that the task for the role. For example, a person who is a member of the sysadmin role can all actions in the SQL Server.
Server roles are predefined and serverwide. These functions are not specific to the database and can not be adjusted.
Database Functions
Database mapping functions from a number of database-specific permissions for an individual or a group of users. Database functions can be allocated to the Authenticated applications NT authenticated logins or SQL Server. Roles assigned to NT authenticated access can be assigned to users of Windows NT and NT groups. Functions can also be nested so that a hierarchical set of permissions can be used for logins.
Features include database-specific database. SQL Server provides three types of functions:
* Database of predefined functions
* Database user-defined functions
* Implicit Functions
Functions from a predefined database
Database of predefined functions are standard features of SQL Server database. Each database in SQL Server provides the following functions. Database functions, the predefined delegate responsibility. For example, a developer db_ddladmin could play a role in the development of databases. This feature allows a programmer to create and delete objects (tables, stored procedures, views, etc.) as needed.
Functions are database-specific pre-defined databases and can not be adjusted.
