Basic concepts of SYBASE Database User Management

The following describes the basic concepts of SYBASE database users.

I. SQL SERVER registered users and database users

We may be confused when we get started with these two concepts, but it will be clear after we understand the structure of sybase SQL SERVER. Sybase SQL SERVER is a process that manages multiple databases. Some databases are independent of each other, and some databases can be shared, such as tempdb and sysbsystemprocs databases. The relationship between SQL SERVER and its own database is like the relationship between the city and its buildings. when you enter a city, you need a valid identity. However, not every building can enter the city, you cannot do something even if you are allowed to enter.

So is the relationship between SQL SERVER registered users and database users. After SQL server creates a registered user, the user can be legally added to SQL SERVER. The registered user information is stored in the syslogins table of the master database. However, only when a registered user becomes a database user and has certain permissions granted to the user can the user use the tables in the database under restrictions.

Ii. SQL SERVER database user categories

SQL SERVER users are generally divided into the following four types: sa users, database owners, database object owners, and common database users. The sa user is the highest level user in SQL server, and all commands in SQL SERVER can be executed. Database owner dbo) users can operate on all objects in the database, such as tables, views, and stored procedures. Generally, there are three ways to create a database: 1. users who are system administrators; 2. A user of the system administrator grants the database creation permission to a user registered in SQL SERVER. After the user creates a database, the database owner is naturally formed. 3. after a user of the system administrator creates a database, the user registered in an SQL SERVER is changed to the database owner.

The database object owner is the user who creates the object. In actual database management, it is generally the database owner. A common database user must grant certain permissions to certain objects in the database, such as tables, views, and processes, to the database owner to perform operations on certain objects in the database. The relationship between several users is mutual: After a user of the system administrator enters a database, it naturally becomes the owner of the database. The database owner can be seen as a special common database user.

Iii. Alias aliases) and group)

Alias aliases) and group are frequently used in database management. It simplifies database user management and facilitates user monitoring. The alias aliases) indicates that the registered user in SQL SERVER accesses the database as the same database user and has the same permissions as the user.

That is to say, once a database user is created in the database, all operations of the database user are defined, and the registered user in SQL SERVER is defined as the alias user of the database user, that is, you have the same permissions as this user. In this way, you do not have to become a database user to access the database. You only need to control the permissions of all alias users by controlling one database user. For example, there is an SQL SERVER named TEST. SER, there is a database named EXAMPLE, where there is a table named OK, when the system administrator is TEST. SER creates a registered user named JOHN and KATE. The database named OK _SELECT in EXAMPLE has the permission to query the OK table. After the two registered users JOHN and KATE are changed to the alias of OK _SELECT, JOHN and KATE can access the database and have the same permissions as the database users of OK _SELECT.

Group) is a collection of database users, that is, through the control of group permissions to control the database users in this group, however, you can also perform extra permission control on some database users in the group.

In the above EXAMPLE, the database named EXAMPLE has an OK _INSERT Group, which has the insert permission on the OK table. The database has two users: MARRY and KITY, after the two users are added to the OK _INSERT group, MARRY and KITY have the right to insert the OK table. You can control the OK _SELECT group for operations with the same permissions of MARRY and KITY. So that MARRY has the query permission on the OK table, only grant permissions to the MARRY user. The alias does not work.

Iv. Role of SYBASE SQL SERVER

Generally, sa users are divided into three roles: the system administrator role (SA role) and the operator role (SSO role ). Sa users are often locked and their powers are divided by the three roles listed above. These three roles will be assumed by different database registered users. The three roles have many tasks, so we will not describe them one by one.

User Management of sybase SQL server is very complicated, but first of all, it has a certain foundation for user management of sybase SQL SERVER.