ZSBD 4

SQL Server and in all databases. It is provided for backward compatibility and

should not be used routinely. This account is only enabled when SQL Server is using Mixed Modę authentication.

When using Mixed Modę, ensure that the sa password is not blank;

otherwise, your SQL Server will not be secure.

Mą, J/p UA⁽t}( fyjnj o^do^i    ufyrftourtUh- cCo bw    -

To ada a user account to a database, you can use SQL Server

Enterprise

Manager or execute the sp_grantdbaccess system stored procedurę. You can    ^:

also add user accounts to databases when creating login accounts. Only

database owners or database access administrators can execute sp_grantdbaccess.

sp_revokedbaccess Removes a security account from the current database

sp_change_users_login Changes the relationship between a SQL Server login

account and a SQL Server user in the current database

Use SQL Server Enterprise Manager or the sp_addrolemembgr. system stored

procedurę to add a security account as a member of a fixed database role. Only

members of the db_owner role can execute the sp_addrolemember system

stored procedurę for any role in the database.

□    Fixed database roles cannot be added, modified, or removed.

□    Any member of a fixed database role can add other login

accounts to that

role.

You also can use the sp_droprolemember system stored procedurę to remove

a security account from a role.

Use SQL Server Enterprise Manager or the sp_addrole system stored

procedurę to create a new database role. An entry is added to the s^susers table tfohtc io

of the current database for each user-defined role. Only members of the    /o cMst/te

db_securityadmin or db_owner role can execute sp_addrole.

After you create a role, use SQL Server Enterprise Manager or the