| |
Home |
![[Table of Contents]](/dwicons/b_toc.gif)
|
Enterprise SQL Server Manager Reference Manual |
![[-]](/dwicons/i_colpse.gif)
| Glossary |
Login name mapped to one or more users in addition to their personal login. When a user logs in using an alias, the user gains the privileges assigned to that login.
ESSM provides the ability to record and produce reports on security-related server and database activity. The information is recorded in a traceable audit trail.
The sysaudits table contains one row for each audit record in the table.
ESSM includes commands and a graphical user interface for creating and verifying the identity of logins, database users, and remote SQL Servers.
ESSM provides lets you assign roles to specific users that bestow automatic privileges. ESSM also lets you grant and revoke permission to users, groups, and roles to control use of specific commands and objects in a database.
A copy of a database or transaction log, used to recover from a media failure.
One or more Transact-SQL statements submitted as a group to SQL Server for processing and terminated by an end-of-batch signal.
The utility for copying data in and out of databases, called bcp.
A storage buffer used to reduce access time for frequently accessed data or procedures.
A set of specific characters with an encoding scheme that uniquely defines each character. ASCII is a common character set.
The point at which all changed data pages are guaranteed to be written to the database device.
ESSM offers a complete set of commands for managing SQL Servers and databases in the enterprise. These commands are compatible with the Tivoli commands and can be entered from the UNIX command line or from scripts. Scripts can be defined as tasks in the Tivoli task library and scheduled as jobs in the Tivoli scheduler.
A customized grouping of SQL Server and database objects. You can organize objects into groups that are most useful to you, such as a collection of database users for each department. You can put collections within collections.
A statement that instructs the computer to perform an operation. The command begins with a word, often a verb, that names the operation. In addition, the command can include one or more keywords with or without variable values that tailor the command.
Permission to use specific commands. Some command permissions are implicitly granted by a database user's role, other command permissions are explicitly granted with the grant command. See also object permissions.
A set of related data tables with a given structure for accepting, storing, and providing data for one or more users. Objects relative to using the database, such as users, indexes, rules, and so on are also considered part of the database.
A device dedicated to the storage of the objects that make up databases. A device can be all or part of a disk or file used to store databases and database objects.
One of the components of a database: table, view, index, procedure, trigger, column, default, or rule.
The system administrator who creates a database is automatically the Database Owner. The system administrator can assign ownership of a database to another user. The owner controls all the objects in the database. In a user's own database, SQL Server recognizes the user as dbo.
An attribute, condition, value, or option that is assumed when none is explicitly specified.
The database that a user gets by default when he or she logs in.
The language used to display prompts and messages within SQL Server.
A duplicate SQL Server database device. All writes to the primary device are copied (mirrored) to a separate secondary device. Writes can be either serial (consecutive) or parallel (simultaneous). If one device fails, the other contains an up-to-date copy of all transactions.
An environment comprising a variety of platforms and applications connected by one or more networks.
The process of copying SQL Server or database information to other managed SQL Servers or profile managers in the distributed computing environment.
A single tape, partition, or file used for a database or transaction dump. A dump can span many volumes, or many dumps can be made to a single volume.
See distributed computing environment.
A message that SQL Server issues, usually to the user's terminal, when it detects an error condition.
An application that provides centralized control of SQL Server installations in a distributed computing environment. ESSM runs within the Tivoli Management Environment (TME).
A system administrator managing SQL Server installations within the TME enterprise. The administrator must have appropriate SQL Server roles, ESSM roles, and TMR roles. See roles.
See Event Monitoring Services.
The user interface that lets you monitor generic events, process events, and error events. You can specify levels at which you are notified of an event and a variety of actions that are triggered by an event.
A user-specified threshold that specifies the amount of space on a segment, and the action to be taken when the amount of space available on that segment is less than the specified space.
ESSM provides a windows environment with menus, icons, and dialog boxes for managing SQL Server installations and databases in a distributed computing environment. These graphic elements are compatible with and exist within the Tivoli Desktop.
See Event Monitoring Services.
The process of restricting access to resources, such as logins or system tables, in a multi-user environment to maintain security and prevent concurrent access problems.
A login consists of a login name and a password that gives a user access to a specific system, SQL Server, database, and so forth. In addition, each ESSM administrator has a SQL Server login account.
A SQL Server that is in a policy region's managed resource list.
A specific resource that has a default policy defined in a policy region. For example, a SQL Server can be defined as a managed resource in a TME policy region. A specific managed resource can belong to only one policy region at a time. Each resource is one of several types. The policy region must contain the resource type in its type list before a specific resource can be added to the policy region.
Controls the user databases, system tables, and the operation of SQL Server as a whole. This database keeps track of such things as user accounts, ongoing processes, and system error messages.
See disk mirror.
The default template for a new SQL Server database. Each time a database is created, SQL Server makes a copy of model and extends it to the size requested.
A message concerning some operation or change in the distributed system. Messages can be notices on the TME Bulletin Board, e-mail messages, pop-up dialog boxes, and so on.
Having no explicitly assigned value. Null is not equivalent to zero nor to blank. A value of null is not greater than, less than, or equivalent to any other value, including another value of null.
Permission to use and modify specific tables, views, or procedures (such as permission to update a table). Some object permissions are implicitly granted by a database user's role, other object permissions are explicitly granted with the grant command. See also command permissions.
The SQL Server operator role, oper_role. See roles.
A variable value used in conjunction with a command or a stored procedure. Also a keyword and value that defines a SQL statement.
See command permissions, object permissions, and roles.
A collection of TME resources that are governed by a common set of policies. ESSM administrators are given the authority to manage resources in one or more policy regions. A policy region contains a list of resource types that are valid for that policy region. You can add or remove resource types from the list so that you can control the kinds of resources the policy region will govern.
Rule that governs the management of resources, such as requiring login accounts to have passwords. ESSM policy methods take the form of shell scripts. Default policy methods govern default characteristics of resources. Validation policy methods protect the integrity of resources.
A collection of object-specific information. Each profile is one of several types. There are nine ESSM profile types. For example, a user profile might contain information on the name, login, group, permissions, and ownership for each user defined in the profile. Profile information can be distributed across an environment that contains multiple platforms.
A SQL Server or profile manager that subscribes to a profile; the endpoint is the final destination of data distributed from a profile manager.
A window used to manage a group of profiles that are subscribed to as one unit by individual profile endpoints. An ESSM profile manager is associated with a specific SQL Server or a specific database. All profiles in the profile manager relate to the associated SQL Server or database.
The process of rebuilding one or more databases from database dumps and transaction log dumps.
A stored procedure executed in a different SQL Server from the server the user is logged into.
A system, device, service, or facility in a distributed system. For example, file systems, workstations, administrators, and SQL Server installations can be resources in the Tivoli Management Environment. A directly managed resource is a resource that can be created and managed within a policy region. A validation resource has policy validation applied before each operation performed on the resource. You can modify a policy region's list of managed resource types.
Roles assigned to ESSM administrators enable administrators to manage SQL Servers on the enterprise. There are three categories of roles to consider when using ESSM.
TMR roles
ESSM roles
SQL Server roles
user
space
sa_role
admin
server
sso_role
senior
load
oper_role
super
security
restore
dump
install_product
schema
install_client
backup
An ESSM administrator must have the appropriate Tivoli, ESSM, and SQL Server roles to carry out a desired task. For example, an ESSM administrator must have both the ESSM security role and the SQL Server sso_role in order to create logins. All administrators must have the Tivoli user role to access their desktop.
The login name for the SQL Server system administrator. Also the SQL Server system administrator role, sa_role. See System Administrator and see roles.
The TME service that enables ESSM administrators with the TME admin role to schedule and run tasks and jobs. The scheduler is represented by a clock icon on the TME Desktop.
As used in this manual, schema refers to database objects such as tables, procedures, views, and indexes.
A named subset of database devices available to a particular database. A segment is a label that points to one or more database devices. Segments can be used to control the placement of tables and indexes on specific database devices.
The original SQL Server or database which is being copied or compared to another SQL Server or database. Also the SQL Server or database associated with a profile manager. Also the profile manager which is being distributed to another profile manager or SQL Server.
A SQL Server or profile manager that receives profile information from a profile manager.
The server in the Sybase client/server architecture. SQL Server manages multiple databases and multiple users, keeps track of the actual location of data on disks, maintains mapping of logical data description to physical data storage, and maintains data and procedure caches in memory.
See login accounts.
The SQL Server system security officer role, sso_role. See roles.
See command.
A collection of SQL statements and optional control-of-flow statements stored under a name. SQL Server-supplied stored procedures are called system procedures.
See login accounts.
A user in charge of SQL Server system administration, including creating user accounts, assigning permissions, and creating new databases. See also ESSM administrator.
The four databases in a newly installed SQL Server: the master database (master), that controls user databases and the operation of the SQL Server; the temporary database (tempdb) used for temporary tables; the system procedures database (sybsystemprocs); and the model database (model) used as a template to create new user databases.
The system tables keep track of information about SQL Server as a whole and about each user database. The master database contains some system tables, such as sysalternates, sysaudits, sysconfigures, and syscurconfigs, that are not in user databases.
The SQL Server or database to which the source server or database is being copied or compared. Also the profile manager or SQL Server that is receiving distributed information from a source profile manager.
The Tivoli Management Environment lets you create a task library in which you can create and store tasks and jobs. These tasks and jobs can be run immediately or scheduled to run at a specific time. A task is a TME resource that encapsulates daily operations, such as clearing the printer queue. Jobs are created from tasks. A job lets you specify details of task execution, such as where to display output.
The temporary database in SQL Server, tempdb, that stores temporary tables and other temporary data such as intermediate results of group by and order by.
A limit to monitor space usage on a database segment. When the available space is below the limit, SQL Server executes a user-specified stored procedure.
Contains the name and object ID of all objects in the TME database, including the SQL Server login name (same as the UNIX login name) and encrypted password information for each ESSM administrator.
A software environment providing centralized control of integrated software products for a distributed system.
The window containing menu bars and icons that let you visualize and control the various elements of the distributed environment.
The foundation for managing resources in a distributed environment. The TMP is the runtime platform for TME applications and provides the administrator with a view into the network and a set of tools that are applicable across functions and applications in the TME.
A TME server and the set of clients it serves. A single TMR can contain a maximum of 200 clients. If your network contains more than 200 clients, you can create several TMRs and connect them.
A mechanism for ensuring that a set of actions is treated as a single unit of work.
A system table (syslogs) in which all changes to the database are recorded.
The name by which a login is known in a database.
An alternative way of looking at the data in one or more tables. Usually created as a subset of columns from one or more tables.
A special character used to represent one or more characters in a pattern-matching string. Any character or set of characters can replace a wildcard character. Use the
-wildcard option, in commands that support it, to specify wildcard names.
|
|