Sybase database user Management basic concept (HOWTO)

In Sybase databases, user management is an important part of system management, but its importance is often overlooked. Many times, the operation of the database command is often not successful with user management, and many of the occurrence of misoperation can also be avoided by user management. Therefore, to clarify some basic concepts of user management, the successful management of the database system has an important role.
Below we will explain the basic concepts of Sybase database users. SQL Server registered users and database users
when we first came into contact with these two concepts, we might be confused, but as long as you understand the structure of Sybase SQL Server, it becomes clear. SYBASE SQL Server is a process, and the process itself can manage multiple databases. Some databases are independent and some databases are shared, such as the tempdb and Sysbsystemprocs databases. SQL Server's relationship with its own database is like the relationship between a city and a building, when entering a city requires a certain legal identity, but not every building into the city can enter, even if allowed to enter also can not do something. This is true for SQL Server registered users and database users. When SQL Server creates a registered user, the user can legitimately enter SQL Server, where the registered user information is placed in the syslogins table in the master database. However, only the registered user becomes a database user, and the registered user can use the tables in the database under restricted conditions when certain permissions are granted to that user.

Two, SQL Server database user classification
Users in SQL Server generally fall into the following four types: SA user, database owner, database object and database normal user. The SA user is the highest level user in SQL Server, and all commands in SQL Server can be executed. A database owner (dbo) user can have all objects in this database, such as tables, views, stored procedures, and so on, generally there are three ways to create: 1. For users of the system administrator; 2. The user of the system administrator assigns the right to create the database to a registered user in a SQL Server. When the database is created by the user, the database owner is formed naturally. 3. After the user of the system administrator creates the database, the registered user in a SQL Server becomes the owner of the database. The database object belongs to the user who created the object, and in the actual database management, it is the database owner. Ordinary users of a database must have certain permissions on certain objects in the database, such as tables, views, processes, and so on, to allow operations on certain objects in the database. A few of the relationships are mutually inclusive: The system administrator's user enters a database, naturally becomes the owner of the database, the database owner can be viewed as a special database of ordinary users.

Iii. aliases (aliases) and groups (group)
Aliases (aliases) and groups (group) are frequently used in database management, which simplifies database user management and facilitates user monitoring. The so-called alias (aliases) will access the database as a registered user in SQL Server to the same database user and have the same permissions as the user. That is, you have the same permissions for a database user as long as you set up a user for that database, and you have the same rights as the user in SQL SERVER that has already defined a registered user as the alias user of that database user. This allows registered users to access the database without becoming a user of the database, and the control of all alias users is achieved only through the control of a database user. For example, there is a SQL Server named Test.ser, there is a example database, there is an OK table, when the system administrator for Test.ser to create a registered user named John and Kate, example database has a Ok_ The database user of Select, who has query permissions on the OK table. After the two registered users of John and Kate become ok_select aliases, John and Kate can enter the database and have the same permissions as the Ok_select database users. Groups (group) is a collection of database users that control the database users in the group by controlling the permissions of the group, but can also have special permissions control over certain users of the database in that group. In the example database in the example above, there is a ok_insert group that has inserted permissions on the OK table, two users in the database: Marry and Kity, when the two users join the Ok_insert group, marry and Kity have the right to insert the OK table. The same permission actions for marry and kity are available through control of the Ok_select group. And make marry to OK table have query permission, only to marry user empowerment can be. And the alias is not.

Four, the role of SYBASE SQL Server
Typically in a database system with a finer management division, SA users are often divided into three roles: the System Administrator role (SA roles) system Security agent role (SSO role), operator roles (OPER). SA users are often locked in and their power is partitioned by the above three roles. These three roles will be registered with a different database for each user. Because of the three kinds of role tasks more, so not to introduce.

The user management of Sybase SQL Server is complex, but the first of these is the basics of user management for Sybase SQL Server.