Microsoft SQL Enterprise Manager Help Contents

	What's New in SQL Enterprise Manager? Highlights of new features, enhancements, and changes in SQL Enterprise Manager for SQL Server 6.5
	Servers Registering servers, setting server configurations, viewing server activity, viewing the server error log, managing messages, managing remote servers and logins, managing devices, managing SQL Server logins, configuring SQL Executive
	Databases Managing databases, setting database options, setting statement permissions, backing up and restoring databases, managing database users and groups
	Objects Managing objects, assigning object permissions, renaming objects, viewing object dependencies, generating scripts
	Transfer Transferring all or some objects from one database to another
	Alerts Managing alerts and operators
	Scheduled Tasks Managing scheduled tasks
	Replication Configuring servers for replication, adding publications, subscribing to publications
	Queries Querying a database, analyzing queries, setting query system options
	Other Tools Running a wizard, adding and running external tools


What's New in SQL Enterprise Manager?

For information about new and enhanced features in SQL Enterprise Manager for SQL Server 6.5, choose one of the following:

Alerts Enhancements

Backup and Recovery

Database Maintenance Plan Wizard

Display Refresh

Extended Stored Procedures Manager

External Tools

Graph Controls

Menu Changes

Microsoft Distributed Transaction Coordinator

Print Support

Remote Servers and Logins Manager

Remote SQL Enterprise Manager Registration

Replication

SERVERS.BIN File Replaced by Registry Entries

SNMP Support

SQL Executive

SQL Mail

SQL Query Tool

Tasks

Tip of the Day

Transfer


Alerts Enhancements

The alerts management interface in SQL Enterprise Manager contains the following enhancements:

SNMP traps can be raised as part of an alert response. Set SNMP traps for an alert response from the New Alert or Edit Alert dialog box. For more information, see Raising SNMP Traps From an Alert.

A Send Mail button has been added to the New Operator and Edit Operator dialog boxes. (Each box can be opened from the Operator tab in the Manage Alerts and Operators window, which appears after choosing Alerts/Operators from the Server menu.) The Send Mail button is available only when the local mail client is running.

Choosing the Send Mail button opens the Send Note window from the underlying mail system. The Send Mail button is useful for notifying operators about changes in their alert handling responsibilities.

SQLALRTR.EXE has a new parameter, -M, that you can use to supply parameters to errors.

Each error message parameter must be separated with a comma ( , ), but no spaces. Strings must be delimited with single quotation marks ( ' ). Messages containing the format string %.*s require two parameters: the length and the string (5 and alpha, respectively, in the preceding command).

For example, for a 50001 error defined as:

Testing the %s procedure for the %ldth time. Using test %.*s.

You would invoke SQLALRTR as follows:

sqlalrtr -E 5001 -M,'add',5,5,'alpha'

The first parameter required by the error message, represented by %S in the error message, would receive the value 'add '. The next parameter is represented by %ld and would receive the value 5. The final parameter, represented by %l.*s, requires a length followed by a string and would receive the 5 and 'alpha' values. The message would appear as follows:

Testing the add procedure for the 5th time. Using test alpha.

For more information about SQLALRTR.EXE parameters, see the Microsoft SQL Server Administrator's Companion.

When setting alerts on forwarded events, each server participating in event forwarding must have a non-null @@servername value; without this value, the forwarding process may not work correctly under all situations and cyclical forwarding may go undetected. You can set the @@servername value by executing the command sp_addserver servername [, Local] and then restarting SQL Server. For more information about using sp_addserver, see the Microsoft SQL Server Transact-SQL Reference.

Alert response tasks are supported by the following parameters: SVR, DBN, ERR, SEV, and MSG. See Tasks for more information.

See Also

Tasks

Raising SNMP Traps From an Alert

SNMP Terminology


SNMP Terminology

 SNMP

 SNMP Traps

 SNMP Alerts

 SNMP Agents


SNMP

SNMP stands for Simple Network Management Protocol (SNMP). You can use SNMP applications to monitor the status of SQL Server installations, monitor performance information, explore defined databases, and view server and database configuration parameters.


SNMP Traps

SNMP traps are conditions from the client or server that cause an alert message to be sent to the SNMP agent. These conditions are user-definable and are often related to error-condition handling but do not necessarily represent an error.


SNMP Alerts

An SNMP alert is a message that contains some kind of condition or status message that was raised at the server or client.


SNMP Agents

An SQL SNMP extension agent (SQLSNMP.DLL) is server software that extends the functionality of the Microsoft Simple Network Management Protocol service. The agent processes SNMP requests for data and data objects that reside on the local server. The agent can also send a trap, which alerts an operator and an SNMP console of an extraordinary event, such as a password violation.


Backup and Recovery

SQL Enterprise Manager provides enhanced backup and recovery capabilities. Individual tables can be backed up and restored; transaction logs can be recovered through a specified date and time; an individual history is maintained of backups from a particular database; and the Database Backup/Restore dialog box has been improved.

See Also

Table Backup and Restore

Point-in-Time Recovery

Other Backup and Recovery Changes


Table Backup and Restore

Tables can be backed up and restored individually. A table restore can be performed from a table backup or full database backup. Restoring a table is useful in a disaster recovery situation where restoring the entire database may be a poor solution.

Note that only full database and transaction log restores remain the basis of a proper backup strategy. Only a full database or transaction log restore ensures that all primary key to foreign key constraints are correct.

Table backup and restore operations have the following characteristics and limitations:

Table restores are not permitted for tables that have text or image columns or that are published for replication.

Triggers, rules, defaults, and declarative referential integrity (DRI) are not enforced for table restores.

Table restores are permitted only to user-defined tables. Source tables can be any table. That is, you can restore a system table into a user-defined table, but not into a system table.

Table restores can be performed from full database backups or from individual table backups.

The Select Into / Bulk Copy database option must be set to perform a table restore. To set this option, see "Setting Database Options" in SQL Server Books Online, or see the Manage Databases window.

A table restore disables the DUMP TRANSACTION statement until a full database backup is performed.

Source and target table schema must be identical in their nullability, length, and base-system types. User-defined types can be different, but the base types must be the same.

Using SQL Enterprise Manager, table backups and restores are performed from the Database Backup/Restore dialog box, which is accessed from the Tools menu. Table backups and restores can also be performed using Transact-SQL DUMP and LOAD statements. For more information, see "DUMP Statement" and "LOAD Statement" in What's New in Microsoft SQL Server 6.5.


Point-in-Time Recovery

Transaction logs can be recovered through a specified date and time. Transactions committed after the specified date and time will be rolled back. This allows you to restore only data you know is correct or data that existed before a particular event.

Point-in-time recovery applies to transaction log restores only (not to full database or table restores).

When a transaction log is not completely correct (usually because of user error) and you want to apply transactions to a certain point in time, use the Database Backup/Restore dialog box in SQL Enterprise Manager.

Point-in-time recovery can also be accomplished using the LOAD TRANSACTION statement with the WITH STOPAT option. For more information, see SQL Server Books Online.


Other Backup and Recovery Changes

The Backup and the Restore tabs increase the usability of the Database Backup/Restore dialog box. Options supporting table backup and restore and point-in-time recovery have been added.

Also, SQL Enterprise Manager maintains a history of database backups for each database. With this enhancement, you can restore a database or a table without knowing the backup device the backup was performed to. For backups from SQL Server 6.5 servers, SQL Enterprise Manager automatically presents a list of database backups, table backups, and transaction log backups for you to choose from in the Restore tab in the Database Backup/Restore dialog box. Backup information is maintained in tables in the msdb database.

Improvements to the Database Backup/Restore Dialog Box

You can perform a backup to a striped set using SQL Enterprise Manager. In the Database Backup/Restore dialog box, in the Backup tab, select multiple backup devices from the Backup Devices list.

Note that striped refers to data that is stored among several devices. Improvements in performance, particularly load balancing, can be achieved by backing up to a striped set.

You can select the From Device button in the Restore tab to display a window in which you can select backup devices to restore from. This is useful when attempting to restore backups that have no histories, such as backups from a previous version of SQL Server, or tape backups made on another machine and moved to the current machine.

You can choose the Database and Transaction Logs button in the Restore tab to populate the Backup History list with database backups and their associated transaction logs grouped together.


Database Maintenance Plan Wizard

SQL Enterprise Manager provides a database maintenance plan Wizard. A wizard is an online tool that is simple to use and focuses on results, not technique. Wizards help you complete a task by presenting a series of questions, which allows you to progress in an organized manner toward completing a goal.

With the Database Maintenance Plan Wizard, you can set up and schedule core maintenance activities for a selected database. The actions include checking data allocation, data and index linkages, and system data; updating optimizer information; reorganizing data and index pages; and performing database and transaction log backups. These actions can be scheduled for preset times using daily or weekly intervals.

Execute permission defaults to the system administrator.

For more information, see "Database Maintenance Plan Wizard" in SQL Server Books Online.

See Also

Running the Database Maintenance Plan Wizard


Display Refresh

The information displayed in the Server Manager window can be updated in two ways. Expand the tree for a server and then do one of the following:

Select a folder, click the View menu, and then choose the Refresh command.

Click the right mouse button on a folder, and from the shortcut menu choose Refresh.


Extended Stored Procedures Manager

SQL Enterprise Manager provides an extended stored procedures manager. An extended stored procedure dynamically loads and executes a function within a dynamic link library (DLL) in a manner similar to that of a stored procedure. Activity outside of SQL Server can be triggered, and external information can be returned to SQL Server.

With the extended stored procedures manager, you can add and drop extended stored procedures to a SQL Server. The extended stored procedures manager also supports return status codes and output parameters (identical to their counterparts in regular stored procedures).

To start the extended stored procedures manager, from the Manage menu, choose Extended Stored Procedures. The command can be used only when the master database is the current database.

Execute permission defaults to the system administrator.

For more information about extended stored procedures, see the Microsoft SQL Server Transact-SQL Reference.

See Also

Managing Extended Stored Procedures


External Tools

External applications can be added to SQL Enterprise Manager. They can be run from the Tools menu or from the floating, dockable Tools Bar. The Tools Bar can be displayed or hidden using the View menu Tools Bar command.

To add an external application, from the Tools menu choose External Tools.

Note that [SRV] and [DBN] can be used in the Parameters box to represent the current server and database. When the tool is run, SQL Enterprise Manager will substitue the current server and database names, passing them as parameters to the application.

See Also

Adding, Changing, or Removing an External Tool

Running an External Tool


Graph Controls

The following SQL Enterprise Manager windows and dialog boxes have enhanced charting capabilities. These windows and dialog boxes have Bar, Graph, and Print option buttons that you can use to control graph and print characteristics.

Dialog box/Window	Charting capability
Edit Database Device Dialog Box	Device Space Usage
Expand Database Dialog Box	Available Space on Database Devices
Manage Databases Window	Databases
Manage Database Devices Window	Devices
New Database Dialog Box	Available Space on Database Devices
New Database Device Dialog Box	Available Storage Space
To print a graph, configure the default printer by choosing the Print Setup command from the File menu.

For more information, choose one of the following:

Graph Properties

Bar Graph Options

Print Options


Graph Properties

Opens the Graph Properties dialog box, in which you can set graph label, solid color, legend display, and graph type properties. Use selectable to select an individual graph item. Use stretchable to view all graph items. In this mode you cannot select an individual item.


Bar Graph Options

Opens the Bar Graph Options dialog box, in which you can set the graph mode to stretched or selectable, and the orientation to vertical or horizontal.


Print Options

Opens the Print Options dialog box, in which you can set graph color, formatting, and font options, and print the graph.


Menu Changes

The following SQL Enterprise Manager menu commands have been moved and renamed, or are new.

Moved and renamed commands are as follows:

Old menu / Command	New menu / Command
Tools / Task Scheduling	Server / Scheduled Tasks
Tools / Query Analyzer	Tools / SQL Query Tool
New commands include:

New menu / Command	Description
File / (all)	Contains commands from the toolbar of the active window.
File / Print Setup	Specifies configurations for the default printer.
View / Tools Bar	Displays or hides the floating, dockable Tools Bar for external tools.
View / Refresh	Updates the information in the currently selected folder of a server in the Server Manager window.
Server / Remote Servers	Opens the Manage Remote Servers Dialog box, which is used to manage remote servers and logins, as well as subscribing servers (including ODBC subscribers).
Server / SQL Server	Opens a menu, which is used to start, pause, continue, stop, configure, and administer SQL Server. To open the menu, select a server and right-click the selection.
Server / SQL Mail	Opens a menu, which is used to start, stop, and configure SQL Mail. To open the menu, right-click the SQL Mail icon for the selected server.
Server / SQL Executive	Opens a menu, which is used to start, stop, and configure SQL Executive. To open the menu, right-click the SQL Executive icon for the selected server.
Server / Distributed Transaction Coordinator	Opens the MS DTC menu for servers with Microsoft Distributed Transaction Coordinator installed. From the menu, the Transactions, Trace, Statistics, or Configure window can be opened.
Tools / External Tools	Opens the External Tools dialog box, which is used to add or remove external tools that can be run in SQL Enterprise Manager.
Tools / Database/Object Transfer	Opens the Database/Object Transfer dialog box, with which you can move objects from one database to another.
Manage / Extended Stored Procedures	Opens the Manage Extended Stored Procedures dialog box, which is used to add or remove extended stored procedures from the master database only.
Help / Database Maintenance Wizard	Starts the Database Maintenance Plan Wizard.


Print Support

SQL Enterprise Manager supports printing from the following windows:

Manage Stored Procedures

Manage Triggers

Manage Views

To print the information from these windows, from the window's toolbar click the Print button.

The following dialog boxes and windows have graph options that support printing graphs:

Edit Database Device

Expand Database

Manage Databases

Manage Database Devices

New Database

New Database Device

To support printing, the default printer can be configured by choosing the Print Setup command from the File menu.

See Also

Graph Controls


Remote Servers and Logins Manager

SQL Enterprise Manager provides a way to manage remote servers and remote logins. One person can manage many remote servers and centralize adminstrative tasks. You can set distribution options for replication and configure ODBC subscribers.

A remote server is a SQL Server on the network that can be accessed through a user's local server, allowing the user to execute stored procedures on the remote server. Replication processes also establish remote server relationships. For example, where replication is set up between servers, a remote server relationship is established between the publisher and the subscriber.

Replicating to ODBC subscribers is new for SQL Server 6.5. This interface provides an alternative to the command line for managing and configuring remote servers and remote logins.

For information about remote servers and remote logins, see the Microsoft SQL Server Administrators Companion.

See Also

Managing Remote Servers and Logins


Remote SQL Enterprise Manager Registration

Generally, SQL Enterprise Manager uses server registration information that is stored locally (on the same server where SQL Enterprise Manager is installed).

Optionally, you can set SQL Enterprise Manager to use server registration information stored on a remote server. For example, you can configure SQL Enterprise manager on several computers to have identical configurations for enterprise-wide standardization and to ease administrative tasks. Identical configurations would have common program groups and common servers registered.

To set SQL Enterprise Manager to use registration information from a remote server

1.	Verify that the remote server saved its registration information locally in the Registry under HKEY_LOCAL_MACHINE.

2.	From the Tools menu, choose Preferences/Configure.

The Configure SQL Enterprise Manager dialog box appears.

3.	 Choose the Application tab.

4.	Select the Store Locally option.

5.	Select the Read From Remote option, and in the Server Name box type the remote server name.

6.	Click OK.

See Also

SERVERS.BIN File Replaced by Registry Entries


Replication

In SQL Enterprise Manager, text and image datatypes can be replicated, some subscribers other than SQL Server are supported, and several dialog boxes in the replication management interface have been enhanced.

For more information, choose one of the following:

text and image Datatype Replication

Replication to ODBC Subscribers

Other Replication Enhancements

Replicating between SQL Server 6.0 and SQL Server 6.5


text and image Datatype Replication

For SQL Server 6.5, text and image datatypes can be replicated, with the following considerations:

INSERT, UPDATE, and DELETE statements are supported.

Logged text operations can be replicated by using WRITETEXT and UPDATETEXT with the WITH LOG option on tables that are published for replication. A text or image column that is published for replication using WRITETEXT and UPDATETEXT operations with the WITH NO_LOG option are not supported, because the replication process monitors the transaction log.

UPDATETEXT operations can be performed for Microsoft SQL Server 6.0 and later subscribers (not for other SQL Server subscribers). Also, the UPDATETEXT option will fail if an ODBC subscriber has a subscription on the text or image column.

WRITETEXT operations are replicated as UPDATE statements, enabling replication of WRITETEXT to ODBC subscribers as well as to SQL Server. (UPDATETEXT operations are replicated as UPDATETEXT.)

Custom procedures are not used if multiple text columns are being modified, because the other text column values are not logged. A standard UPDATE statement is generated instead.

A configurable parameter, max text repl size, controls the maximum size (in bytes) of text and image data that can be replicated. This permits support of ODBC drivers and other SQL Server databases that cannot handle large text and image values, and distributors that have system resource (virtual memory) constraints. When a text or image column is published and an INSERT, UPDATE, WRITETEXT, or UPDATETEXT operation is run that exceeds the configured limit, the operation fails.

The max text repl size parameter is set by using the sp_configure system stored procedure or the Server Configuration/Options dialog box.

For more information on setting max text repl size, see sp_configure in "What's New for Transact-SQL" in SQL Server Books Online.

Because SQL Server is log-based, for text and image columns to be replicated, the text pointer must be retrieved within the same transaction as the UPDATETEXT or WRITETEXT operation.

Also, once the text pointer has been obtained, you should not perform any operations that can alter the location of the text pointed to by the text pointer (such as updating the primary key), before executing the UPDATETEXT or WRITETEXT statement.

This is the recommended way of using UPDATETEXT and WRITETEXT operations with data to be replicated:

1.	Begin the transaction.

2.	Obtain the text pointer.

3.	Use the text pointer in the UPDATETEXT or WRITETEXT operation.

4.	Commit the transaction.

To replicate a text or image column, publish the table using SQL Enterprise Manager and include the text or image column in the published article. For more information about publishing tables and columns, see the Microsoft SQL Server Administrators Companion.

text and image Replication Limits

An important consideration when sizing subscribing databases is that the text pointer for replicated text and image columns will be initialized on subscriber tables, even when uninitialized on the publisher. Consequently, each text and image column added to the subscriber table by the distribution task will consume a minimum of 2K database storage.


Replication to ODBC Subscribers

SQL Server 6.5 supports replication to heterogenous databases that are using ODBC. ODBC subscribers to SQL Server include:

Microsoft® Access databases

ORACLE® databases

Other databases on ODBC subscribers that comply with SQL Server ODBC subscriber requirements

See Also

Using an ODBC Subscriber

About Microsoft Access Subscribers

About ORACLE Subscribers

About Other ODBC Subscribers

Replication Restrictions for ODBC Subscribers

Datatype Mappings for ODBC Subscribers


Other Replication Enhancements

The following information describes enhancements and changes to replication other than text and image datatype replication and replication to ODBC subscribers:

The explicit (NOLOCK) optimizer hint is no longer needed in a replication filter. The lock manager has been updated to ignore table locks on the replicated base table during a replication filter.

NOT FOR REPLICATION can be added to foreign key constraint declarations. For more information, see Whats New in Microsoft SQL Server 6.5.

The Replication Topology window includes New Subscriber and Remove Subscriber buttons to add or remove subscribers. The window graphically indicates the type of subscriber (SQL Server, Microsoft Access ODBC, generic ODBC, and so on).

The functionality provided by DBREPL.SQL has been incorporated into the distribution process. The DBREPL.SQL script has been removed.

The following information describes enhancements to support replication to ODBC subscribers:

The Replication - Publishing dialog box includes a New Subscriber button, which opens the New Subscriber dialog box, which has an ODBC Subscriber button. The ODBC Subscriber button opens a dialog box that presents a list of system DSNs that are registered with the publisher.

You can enter a username and a password in this dialog box, if required by the ODBC subscriber, to connect to the ODBC subscriber. The username or password entered here overrides the username or password entered in the ODBC administration application for a registered DSN. Entering the username and the password in this dialog box may not be necessary. The username and the password are often entered and stored (depending on the ODBC driver) during the process of registering a system DSN with the ODBC administration application in Control Panel.

A Subscribers button has been added to the Edit Publications dialog box. With this button, you can do a push subscription of an entire publication. (In SQL Server 6.0, push subscriptions can be performed only for individual articles and not publications.)


Replicating between SQL Server 6.0 and SQL Server 6.5

SQL Server 6.5 supports replicating between 6.0 and 6.5 SQL Servers. Before setting up replication between servers of different versions, consider the following constraints:

The Publisher and Distributor must be the same version. Choose either 6.0 or 6.5 for both Publisher and Distributor.

Replication administration must be done from SQL Enterprise Manager on a SQL Server 6.5.

You must install the SQLOLE65.SQL script on the 6.0 server involved in replication. To install SQLOLE65.SQL, run the script for your platform found on the SQL Server CD-ROM. From the SQL Server CD-ROM, choose the subdirectory for your platform, and then choose the subdirectory for ODBC. The correct script resides in the ODBC subdirectory.

When replicating from a SQL Server 6.0 server to a SQL Server 6.5 server, the replication process works as a SQL Server 6.0 replication process. The enhanced replication features of SQL Server 6.5 will not be available. For more information about SQL Server 6.0 replication, see the Microsoft SQL Server Administrators Companion for 6.0.

When replicating from a SQL Server 6.5 server to a SQL Server 6.0 server, the SQL Server 6.0 server is treated as an ODBC server. You must set up a data source name (DSN) for the SQL Server 6.0 server.

To set up the SQL Server 6.0 server as a DSN:

1.	On the machine where SQL Server 6.5 resides, from the Main program group, click Control Panel.

2.	From Control Panel, run the ODBC Administration application, and add the subscribers DSN as a system DSN.

3.	Using SQL Enterprise Manager, configure the newly added system DSN as a subscribing server to the publishing server by choosing the New Subscriber button from the Replication - Publishing dialog box.

The New Subscriber dialog box appears.

4.	From the New Subscriber dialog box, choose the ODBC Subscriber button.
Complete the New ODBC Subscriber dialog box that appears.

Note  Only system DSNs are listed in the New ODBC Subscriber dialog box.

5.	While using SQL Enterprise Manager to create or edit a publication, perform a push subscription to the subscriber by choosing the Subscribers button from the Edit Publications or Edit Article dialog box.

Complete the dialog box that appears.


SERVERS.BIN File Replaced by Registry Entries

For Microsoft SQL Server 6.5, registration information for servers is maintained in the operating system Registry (for Windows NT- and Windows 95-based computers). For Microsoft SQL Server 6.0, SQL Enterprise Manager server registration information is maintained in a SERVERS.BIN file. Server registration information includes server groups in the Server Manager, servers registered with SQL Enterprise Manager, and associated data.

Centralizing server registration information improves security and allows servers to share the same registration tree. By sharing the same registration tree, each server in the group can access server registration information without having to perform separate setup tasks.

The first time SQL Enterprise Manager is run after upgrading SQL Server 6.0 to SQL Server 6.5, information from the existing SERVERS.BIN file is automatically moved to the Registry.

Using the Preferences/Configure command from the Tools menu, you can configure SQL Enterprise Manager to use server registration information that is stored locally (on the same server where SQL Enterprise Manager is installed) or that is stored in the Registry of a remote server. Also, you can configure SQL Enterprise Manager to use common registration information for all users or to maintain separate registration information for each user.

See Also

Remote SQL Enterprise Manager Registration


SNMP Support

SQL Server 6.5 supports Simple Network Management Protocol (SNMP) monitoring of SQL Server. A copy of the Microsoft SQL Management Information Base (MSSQL-MIB) file (MSSQL.MIB) and the SQL Server SNMP extension agent (SQLSNMP.DLL) are installed by SQL Server setup.

The Microsoft SQL Server Management Information Base (MSSQL-MIB) is based on the proposed Internet Engineering Task Force (IETF) SNMP Relational Database MS-MIB (RFC 1697), and it has been enhanced specifically for use with Microsoft SQL Server. IETF is the organization that oversees standards for the Internet. With SNMP applications, you can monitor the status of SQL Server installations, monitor performance information, explore defined databases, and view server and database configuration parameters.

In addition, you can specify that an alert response raise an SNMP trap when an alert occurs. An SNMP trap notifies the SNMP agent that a status or condition has occurred. The SNMP agent can then forward that notification to specified workstations that are running an SNMP monitoring application(s).

For SNMP applications to monitor the status of a SQL Server, a copy of the MSSQL-MIB file must be placed on the monitoring workstation and loaded into the SNMP application. The MSSQL.MIB file is in the C:\MSSQL\SNMP directory on the computer running SQL Server and can be copied to the appropriate directory on a monitoring workstation.

For information about loading the MSSQL-MIB file and monitoring SQL Server, see the documentation for your SNMP application.

See Also

Raising SNMP Traps From an Alert

SNMP Terminology


SQL Executive

Configuration parameters for SQL Executive can be set from SQL Enterprise Manager.

Executing procedures can now be run in the security context of the SQLExecutiveCmdExec account.

To configure SQL Executive

1.	From SQL Enterprise Manager, in the Server Manager window, select the server to set configuration parameters for.

2.	Click the right mouse button on the server's SQL Executive icon, and in the shortcut menu choose Configure.

The Configure SQL Executive dialog box appears.

3.	Complete the dialog box and click OK.

See Also

Configuring SQL Executive

SQLExecutiveCmdExec User Account


SQL Mail

SQL Server 6.5 provides enhancements to SQL Mail. SQL Enterprise Manager has been enhanced to:

Stop and start SQL Mail.

Configure SQL Mail.

SQL Mail has been enhanced to work with Microsoft Exchange.

To assign a mail login name and a password to SQL Mail from SQL Enterprise Manager

1.	In the Server Manager window, click the right mouse button on the SQL Mail icon.

2.	From the shortcut menu, choose Configure.

The SQL Mail Configuration dialog box appears.

3.	Complete the dialog box.

See Also

SQL Mail is Compatible With Microsoft Exchange


SQL Mail Icon is Compatible With Microsoft Exchange

To set up SQL Mail to work with Microsoft Exchange

1.	At the Microsoft Exchange server, set up a mailbox for the user account that will be used by the MSSQLServer service. This account must be a domain account that adheres to the requirements listed under Platform Support in Whats New for Setup, earlier in this document. For example:

Account:	DOMAIN1\SQLServerAccount
Mailbox:	SQL1
2.	At the SQL Server machine, log on to Windows NT using the same user account that will be used by the MSSQLServer service (DOMAIN1\SQLServerAccount in the example above).

3.	Install the Microsoft Exchange Client on the SQL Server machine.

4.	Start the Microsoft Exchange Client and use the Exchange Setup Wizard to configure the client to connect to Microsoft Exchange Server. After setup is complete, verify that you can send and receive mail interactively.

Note  You cannot use the Microsoft Exchange Client to connect SQL Server to Microsoft Mail post offices.

5.	Start the Microsoft Exchange Services application (also called the Mail and Fax application in Control Panel). Choose the Show Profiles button to find the name of the profile that the Exchange Setup Wizard has created (for example, SQL Server).

6.	From Control Panel, open the Services application and configure the MSSQLServer service to run under the same Windows NT user account that Microsoft Exchange is set to use. Start or restart the MSSQLServer service.

7.	In SQL Enterprise Manager, select a server and from the Server menu, choose SQL Mail/Configure or right-click the SQL Mail icon below the selected server and choose Configure. Type the profile name you found in step 5. You do not need to provide a password for Microsoft Exchange; it uses the account and password configured for the MSSQLServer service.

8.	In SQL Enterprise Manager, from the Server menu, choose SQL Mail/Start or right-click the SQL Mail icon and choose Start. The SQL Mail icon will become green if SQL Mail has started successfully.


SQL Query Tool

The query interface in SQL Enterprise Manager has been renamed. For SQL Server 6.5, the command on the Tools menu and the icon on the toolbar are called SQL Query Tool. For SQL Server 6.0, they are called Query Analyzer.

See Also

Setting Query System Options


Tasks

The task scheduling interface in SQL Enterprise Manager contains several modifications:

The Task Scheduling command on the Tools menu for SQL Server 6.0 is now Scheduled Tasks on the Server menu for SQL Server 6.5.

CmdExec tasks owned by users other than system administrators (SA) run in the security context of a Windows NT user account called SQLExecutiveCmdExec. For more information, see SQLExecutiveCmdExec User Account.

The command value for Transact-SQL tasks supports multiple Transact-SQL statements and procedures. For example:

sp_who
go
sp_help
go

A user can view tasks and task history for only those tasks the user created and owns. However, the system administrator can view all tasks.

Tasks return error messages (if encountered). Also, the last 230 bytes (approximately) of CmdExec task output can be viewed as part of the message shown in the Task History dialog box.

Scheduling support has been added for the following long-running operations: create database, expand database, create device, and expand device.

The Task History log can be cleared from the Task Engine Options dialog box by clicking the Clear Task History Log button.

The stored procedure sp_runtask can be used to invoke a task from Transact-SQL. For more information about sp_runtask, see SQL Server Books Online.

Commands such as COPY and RENAME do not work as CmdExec tasks, unless you carefully phrase the task. For example:

cmd /C copy d:\out.txt d:\outmore.txt

SQL Executive assumes the first white space-delimited token of the command specifies an EXE or CMD module name.

Programs that require user input as CmdExec tasks cannot be run, because by default they run on a virtual desktop and cannot be seen.

Tasks that are created to respond to alerts are supported by the following parameters, which can be set while creating a task:

Parameter	Represents
[SVR]	Server name
[DBN]	Database name
[ERR]	Error number
[SEV]	Severity
[MSG]	Message text
For example, five servers forward their events to a master alert management server. Each event causes an alert to fire; the user has associated a task with each alert. In response to the five alerts, the master server will run a user-defined task for each alert. The task could be defined to log back into the forwarding server, to use the database that caused the initial alert, and to address the problem. To do this, define the task command as:

isql /Usa /p /sairedale /daccounts /Q "sp_fixit"

See Also

SQLExecutiveCmdExec User Account


Tip of the Day

Tip of the Day presents information about using SQL Enterprise Manager. By default, the Tip of the Day window is displayed each time you start SQL Enterprise Manager.

To cancel the Tip of the Day feature, clear the Show Tips at Startup check box.

To display the Tip of the Day window, choose Tip of the Day from the Help menu.


Transfer

SQL Enterprise Manager includes a transfer management interface that can be used to transfer all or some objects from one database to another. The destination server must be Microsoft SQL Server version 6.5. The source server can be Microsoft SQL Server version 6.x or 4.x, or a server that is running a SYBASE System 10 server.

With the transfer management interface you can:

Copy all or some types of objects.

Copy all or some objects of a specific type.

Transfer schema and data, only schema, or only data.

Append or replace existing data.

Drop destination objects before copying schema.

Include dependent objects of a transferred object.

Use default scripting options, or customize the scripts that are used to copy objects and security information.

Execute a transfer immediately, or schedule it to execute one time or on a recurring basis.

The SQL Transfer Manager application is obsolete and is not provided in SQL Server 6.5.

See Also

About Transfer

Transferring Objects


Manage Remote Servers Dialog Box

Use this dialog box to manage remote servers and remote logins. A remote server is a SQL Server on the network that can be accessed through a user's local server, allowing the user to execute stored procedures on the remote server. Replication processes also establish remote server relationships.

For information about remote servers and remote logins, see the Microsoft SQL Server Administrators Companion. For more information about the Manage Remote Servers dialog box, choose one of the following:

 Server Name

 RPC

 Subscriber

 Distribution Options

 Publisher

 Distributor

 Distribution Publisher

 Translate All Remote Login Names To

 Trusted (check box)

 Remote Server Login Name

 Mapped Login Name

 Trusted (column)

 Add/Modify

 Drop

 Drop Login

See Also

Managing Remote Servers and Logins


Server Name

Specifies the name of the server to be configured as a remote server.


RPC

Specifies that the server listed in the Server Name box is a remote server. The remote server is a SQL Server on the network that can be accessed through a user's local server and is administered by the local SQL Enterprise Manager.

If the remote server will not participate in replication, RPC is the only option required.


Subscriber

Specifies that the remote server will have subscriber status for replication.


Publisher

Specifies that the remote server will have publisher status for replication.


Distributor

Specifies that the remote server will have distributor status for replication.


Distribution Publisher

Specifies the remote server as a publisher and a distributor for replication.


Distribution Options

Opens the Distribution Options dialog box, from which to set distribution options. This button is enabled only when the Subscriber check box is selected.


Translate All Remote Login Names to

Maps login IDs from the remote server to a login name from the local server. Choose a login name or Same Name from the list box.


Trusted (check box)

Specifies whether all remote logins will be validated by Windows NT security or by a password. If this box is selected, then the security will be handled by Windows NT and a password is not required. If this box is not selected, then standard security is used and a login ID and a password are required.


Remote Server Login Name

Specifies a login ID for the remote server.


Mapped Login Name

Specifies the local login ID that the remote login name will map to.


Trusted (column)

Specifies whether the name displayed in the Remote Server Login Name column is validated by Windows NT security or by a password. If this column is selected, the security will be handled by Windows NT and a password is not required. If this column is not selected, standard security is used, and a login ID and a password are required.


Add/Modify

Adds the server that is specified in the Server Name box as a remote server.

When an existing remote server is specified in the Server name box, the Add button is named Modify. Click Modify to accept changes that are made to the remote server configuration.


Drop

Removes the server from the list of known remote servers.


Drop Login

Drops the logins selected from the Remote Server Login Name column. Choosing this option prevents the login name from logging on to the local server.


Tip of the Day Window

This window presents information about using SQL Enterprise Manager.

To view additional tips, choose the Next Tip button.

To display Tip of the Day each time SQL Enterprise Manager starts, select the Show Tips at Startup check box. This is the default setting.

To prevent Tip of the Day from displaying each time SQL Enterprise Manager starts, clear the Show Tips at Startup check box.

To view tips at any time, choose Tip of the Day from the Help menu.


Query System Tab

Use this tab to set configuration preferences for the SQL Query Tool. To access this tab, from the Tools menu, choose Preferences/Configure.

For more information, choose one of the following:

 Undo Buffer Operations

 Font

 Display Message Boxes

 Default to Save

 Default to Discard

 File Extensions

 Prompt on Closure

 Switch to Result Tab on Execute

 Defaults


Undo Buffer Operations

Specifies the number of text actions to store in the buffer. SQL Enterprise Manager maintains a record of text actions, such as typing, deleting, or pasting text in the Query window. Text actions can be reversed in the query and result tabs by typing CTRL+Z or by choosing Undo from the Edit menu.

You can have a record of 2 to 32,000 text actions. However, text is stored in memory--the larger the number of text actions, the more memory used. The default number of stored text actions is 20.


Font

Displays the Font dialog box. Use this dialog box to change the font in which SQL Query Tool displays queries and results.


Display Message Boxes

Specifies that a verification message will be displayed before data in the undo buffer during a large paste or delete is handled.


Default to Save

Saves data in the undo buffer during a large paste or delete.


Default to Discard

Discards the data in the undo buffer during a large paste or delete. Does not remember the operation about to be done and discards all previous undo operations.


File Extensions

Query

Specifies the default file extensions to be used when saving queries. The default is .SQL.

Results

Specifies the default file extensions to be used when saving results. The default is .RPT.


Prompt on Closure

Specifies that when you close the Query window a message box will appear that asks you to confirm the closure.


Switch to Result Tab on Execute

Specifies that the Result tab will display automatically when a query is executed.


Defaults

Sets all options to their default values.


External Tools Dialog Box

Use this dialog box to add, change, or remove an external tool or utility that is on the Tools menu and on the floating, dockable Tools Bar of SQL Enterprise Manager.

For more information, choose one of the following:

 Current Tools

 Menu Text

 Command

 Parameters

 Add

 Change

 Remove

See Also

Adding an External Tool

Running an External Tool


Current Tools

Lists the external tools that are currently installed.


Menu Text

Specifies the name of the selected tool. To change the entry, edit the Menu Text entry and click the Change button.


Command

Specifies the command to be executed when the selected tool is run from the Tools menu or from the floating, dockable Tools Bar. The command is usually a fully qualified path (including filename) of an application. To change this entry, edit the Command entry and click the Change button.


Parameters

Specifies parameters to be passed to the application each time it is launched. Parameters is an optional entry. To change this entry, edit the parameter(s) and click the Change button. Note that [SRV] and [DBN] can be used in the Parameters box to represent the current server and database. When the tool is run, SQL Enterprise Manager will substitute the current server and/or database names, passing them as parameters to the application.


Add

Opens the Add External Tool dialog box, in which you can specify an application to add to the SQL Enterprise Manager window.


Change

Revises the selected tool by applying the current entries in the Menu Text, Command, and Parameters boxes.


Remove

Drops the selected tool.


Add External Tool Dialog Box

Use this dialog box to add an external tool or utility to the Tools menu and the floating, dockable Tools Bar of SQL Enterprise Manager.

For more information, choose one of the following:

 Command

 Browse

 Parameters

See Also

Adding, Changing, or Removing an External Tool

Running an External Tool


Command

Specifies the command to be executed when a selected tool is run from the Tools menu or from the floating, dockable Tools Bar. Usually, the command is a fully qualified path (including filename) of an application. You can type the command or click the Browse button to find the application.


Browse

Displays the Open dialog box, from which to locate an application to add as an external tool.


Parameters

Specifies command parameters for the external tool.

Note that [SVR] and [DBN] can be used in the Parameters box to represent the current server and database. When the tool is run, SQL Enterprise Manager will substitute the current server and/or database names, passing them as parameters to the application.


Open Dialog Box

Use this dialog box to locate and select a tool or utility to add to the Tools menu and to the floating, dockable Tools Bar of SQL Enterprise Manager.

For more information, choose one of the following:

 File Name

 List Files of Type

 Directories

 Drives

 Network


File Name

Displays the name of the file that is selected in the list box.


List Files of Type

Specifies the type of file to display in the list box.


Directories

Displays the currently selected directory.


Drives

Displays the currently selected drive.


Network

Opens the Connect Network Drive dialog box, from which to connect to a shared network directory.


Manage Extended Stored Procedures Dialog Box

Use this dialog box to add or remove extended stored procedures for the master database. For more information, choose one of the following:

 Procedure

 DLL Name

 Add

 Drop

See Also

Managing Extended Stored Procedures


Procedure

Specifies an extended stored procedure to add or remove. To add a procedure, type the name in the box. To remove a procedure, expand the list and select the name.


DLL Name

Specifies the dynamic-link library (DLL) name of an added extended stored procedure.


Add

Adds an extended stored procedure, as defined in the Procedure and DLL Name boxes.


Drop

Removes the specified extended stored procedure.


SQL Server Manager Window

Use this window to stop, pause, start, or continue SQL Server service to a server. To open this window, select a server in the SQL Enterprise Manager Server Manager window and click the traffic light button on the toolbar, or from the program window, click the SQL Service Manager icon.

To…	Double click the…
Stop a service	Red light or Stop
Pause a service	Yellow light or Pause
Start a service	Green light or Start/Continue
Continue a paused service	Green light or Start/Continue
When the light is…	The service is…
Red	Off
Yellow	Paused
Green	Running
See Also

Starting, Pausing, or Stopping a Server


Configure SQL Executive Dialog Box

Use this dialog box to set configurable parameters for SQL Executive. To access this dialog box, from the Server Manager window of SQL Enterprise Manager, right-click a server's SQL Executive icon.

For more information, choose one of the following:

 Auto-Start SQL Mail When SQL Executive Starts

 SQL Mail

 Auto-Restart Server After Unexpected Server-Down

 Unexpected Server-Down Detection Polling Interval (minutes)

 Local Host Server

 Error Log File

 Locate (button)

 View

 System Account

 This Account

 Password

 Confirm Password

 Reset CmdExec Account

 Reset CmdExec Password

See Also

Configuring SQL Executive


Auto-Start SQL Mail When SQL Executive Starts

Specifies that SQL Mail will start automatically when SQL Executive starts.


SQL Mail

Specifies SQL Mail startup options. Defining these options allows SQL Mail to automatically start up when SQL Executive starts.


Auto-Restart Server After Unexpected Server-Down

Specifies that SQL Server will restart automatically after an unexpected stop (if a stoppage is not due to a shutdown or a net stop mssqlserver command).


Unexpected Server-Down Detection Polling Interval (minutes)

Specifies the interval, in minutes, that SQL Executive will use between its checks of whether SQL Server has stopped unexpectedly.


Local Host Server

Specifies the name of the local SQL Server. Usually this parameter is set to (default). However, if the server is set to listen on an alternate named pipe, select the listen on name from the Local Host Server list.


Error Log File

Specifies the path and the name of a file to write SQL Executive troubleshooting information to. By default, this field is empty and information is not logged.

To log SQL Executive troubleshooting information, type the file drive, path, and filename in this box.

SQL Executive will use the specified error log when it next needs to write something to the error log. If an error log file is specified while SQL Executive is running, it will be used immediately. Once a file has been specified, the error log cannot be changed while SQL Executive is running. As much as a 60 second delay can occur before you can view the error log.

Specify an error log only to assist in troubleshooting, because the SQL Executive error log can grow quickly and to a large size.


Locate (button)

Opens the Error Log File Location window, from which to specify a file for the SQL Executive troubleshooting information to be written to.


View

Opens the SQL Executive Error Log window. This button is dimmed if the Error Log File box is empty.

You may experience a delay from the time you type in the file location to when you can view the file. The preferred view procedure is to complete the Configure SQL Executive dialog box, click OK, wait a few minutes, and then reopen the dialog box and click View.


System Account

Specifies that SQL Executive will run in the servers LocalSystem account.

Selecting the System Account parameter prevents using several features, such as replication and scheduled task runs involving other servers, because a service running under the LocalSystem account has no user account information associated with it. This prevents some network server software from allowing the Windows NT service to access resources.


This Account

Specifies that SQL Executive will run in the security context of the Windows NT user account that is displayed in this box. The account will usually be a domain user account (although it can also be a user account on the local server). The specified account should be reserved for use by SQL Executive (users should not use it to log on).

The account is assigned through the setup program when SQL Server is installed. If you must change the user account name or update the password, use the Configure SQL Executive dialog box. Do not use the Services application in Control Panel, because the necessary privileges can be granted only by completing the Configure SQL Executive dialog box.


Password

Specifies the password of the Windows NT user account displayed in the This Account box.


Confirm Password

Specifies the password of the Windows NT user account displayed in the This Account box.


Reset CmdExec Account

Reinstalls the SQLExecutiveCmdExec account with its default (minimum) level of access rights. Additional rights granted to the account are removed.

SQLExecutiveCmdExec is a local Windows NT account on the server that is being administered. CmdExec tasks owned by users other than system administrators run in the security context of this account.


Reset CmdExec Password

Automatically changes the Windows NT password used by the SQLExecutiveCmdExec account.

Do not use User Manager, under the Administrative Tools program group in Program Manager, to change the CmdExec password. If you do, then CmdExec tasks owned by users other than system administrators cannot run successfully.


Managing Remote Servers and Logins

A remote server is a SQL Server on the network that can be accessed through a user's local server, allowing the user to execute stored procedures on the remote server. Replication processes also establish remote server relationships. For more information about remote servers and remote logins, see the Microsoft SQL Server Administrators Companion.

To manage remote servers and logins

1.	From the Server Manager window, select a server.

2.	From the Server menu, choose Remote Servers.

3.	Complete the Manage Remote Servers Dialog Box.

4.	Click Add or Modify.


Setting Query System Options

You can configure the SQL Query Tool by modifying the Query System tab.

To configure the SQL Query Tool

1.	From the Tools menu, choose Preferences/Configure.

The Configure SQL Enterprise Manager dialog box appears.

2.	Choose the Query System tab.

3.	Adjust the configuration options as appropriate, then click OK.

See Also

Query System Tab

Setting Query Flag and Format Options


Managing Extended Stored Procedures

With the extended stored procedures manager, you can add and drop extended stored procedures to and from a SQL Server.

To open the extended stored procedures manager

1.	In the Server Manager window, select a server, open its Databases folder, and select the master database.

2.	From the Manage menu, choose Extended Stored Procedures.

The Manage Extended Stored Procedures dialog box appears.

To add an extended stored procedure

1.	In the Manage Extended Stored Procedures dialog box, in the Procedure box type the name of the procedure.

2.	In the DLL Name box, type the name of the procedure's dynamic-link library (DLL).

3.	Click Add.

To remove an extended stored procedure

1.	In the Manage Extended Stored Procedures dialog box, select a procedure from the list in the Procedure box.

2.	Click Drop.

See Also

Manage Extended Stored Procedures Dialog Box


Starting, Pausing, or Stopping a Server

You can start, pause, or stop a server directly from the Server Manager window, or by using the traffic light button on the toolbar.

To start, pause, or stop a server from the Server Manager window

1.	In the Server Manager window, click the right mouse button on the server name.

2.	From the shortcut menu, choose Start, Stop, Pause, or Continue.

To start, pause, or stop a server using the toolbar button

1.	In the Server Manager window, select a server.

2.	From the toolbar, click the traffic light button.

The SQL Server Manager window appears.

3.	Double-click the appropriate light.

See Also

SQL Server Manager Window


Other Tools

Running the Database Maintenance Plan Wizard

Adding, Changing, or Removing an External Tool

Running an External Tool


Running the Database Maintenance Plan Wizard

You can use the Database Maintenance Plan Wizard to set up and schedule core maintenance activities for a database. The SQL Executive service must be running to use the Database Maintenance Plan Wizard.

To run the Database Maintenance Plan Wizard

1.	From the toolbar, click the Database Maintenance Wizard icon. Or from the Help menu, choose Database Maintenance Wizard.

2.	Follow the on-screen instructions.

The Database Maintenance Plan Wizard executable file, SQLMAINT.EXE, can also be run from the command line. To view a list of command line parameters, type:

C:\MSSQL\BINN\SQLMAINT.EXE -?


Adding, Changing, or Removing an External Tool

You can add, change, or remove external applications with SQL Enterprise Manager. External tools can be run from the Tools menu or from the floating, dockable Tools Bar.

To add an external tool

1.	From the Tools menu, choose External Tools.

The External Tools dialog box appears.

2.	Click the Add button.

The Add External Tool dialog box appears.

3.	In the Command box, type the path and the filename of the application. Or, click the Browse button and complete the Open dialog box.

4.	In the Parameters box, type the parameters to pass to the application each time it is launched. (This is an optional entry.)

5.	Click OK.

To change an external tool

1.	In the External Tools dialog box, select a tool from the Current Tools list.

2.	In the Menu Text box, type the change.

3.	In the Command box, type a command. Generally, the command is a fully qualified path and includes the filename of an application.

4.	In the Parameters box, type the parameters to pass to the application each time it is launched. (This is an optional entry.)

5.	Click Change. The changed tool name will appear on the Tools menu and on the floating, dockable Tools Bar.

To remove an external tool

1.	In the External Tools dialog box, from the Current Tools list box select a tool.

2.	Click Remove.

See Also

Running an External Tool


Running an External Tool

External tools that have been added to SQL Enterprise Manager can be accessed two ways:

From the bottom of the Tools menu, choose the command for the selected tool.

From the floating, dockable Tools Bar, click the icon for the tool. The Tools Bar can be placed anywhere on your screen or can be docked to the toolbar. To hide the Tools Bar, from the View menu, cancel the Tools Bar selection.

See Also

Adding, Changing, or Removing an External Tool


Raising SNMP Traps From an Alert

Alert responses can include the option Raise an SNMP Trap When the Alert Occurs. An SNMP trap notifies the SNMP agent that a status or condition has occurred. The SNMP agent can then forward that notification to specified workstations that are running SNMP monitoring application(s).

To configure an alert to raise an SNMP trap

1.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators dialog box appears.

2.	With the Alerts tab active, click the New Alert or Edit Alert button.

The New or Edit Alert dialog box appears.

3.	Select the option Raise an SNMP Trap When Alert Occurs.

Important  If you will be raising SNMP traps in alert responses, you must define the workstations that will receive SNMP trap notifications. To do this, use the Networks application in Control Panel. For more information, see What's New in Microsoft SQL Server 6.5.

See Also

SNMP Support

SNMP Terminology


Configuring SQL Executive

SQL Executive configuration parameters can be set from SQL Enterprise Manager.

To configure SQL Executive

1.	From the Server Manager window, click the right mouse button on a servers SQL Executive icon.

2.	From the shortcut menu, choose Configure.

The Configure SQL Executive dialog box appears.

3.	Complete the dialog box and to apply the specified parameters, click OK.


SQLExecutiveCmdExec User Account

A Windows NT user account, SQLExecutiveCmdExec, is added by the SQL Server setup program when SQL Server 6.5 is installed. CmdExec tasks owned by users other than system administrators (SAs) run in the security context of this account. By default, this account is a member of the Users local group on the server.

CmdExec tasks owned by SAs run in the security context of the user account assigned to SQL Executive. Usually, this user account belongs to the Administrators local group on the server.

Windows NT SAs can control the operating system privileges of tasks owned by other users by controlling the rights, permissions, and group memberships of the SQLExecutiveCmdExec account. To configure the rights, permissions, and group memberships of the SQLExecutiveCmdExec account, use the User Manager application under Program Manager's Administrative Tools. For more information on administering Windows NT user accounts, see Windows NT documentation.

See Also

Configuring SQL Executive


Graph Properties Dialog Box

Use this dialog box to set graph properties from the following dialog boxes and windows:

Edit Database Device

Expand Database

Manage Databases

Manage Database Devices

New Database

New Database Device

For more information, choose one of the following:

 Title Label

 Units Label

 Display Solid Colors

 Display Legend Window

 Graph Types


Title Label

Specifies to display the title of the graph.


Units Label

Specifies to display text labels for the graph's numerical gradations.


Display Solid Colors

Specifies to display the graph in solid colors. If cleared, the graph will be displayed in patterns and colors on a 16 color display.


Display Legend Window

Specifies to display a legend near the graph that explains the graph elements.


Graph Types

Lists available graph types. The default is Bar Graph.


Bar Graph Options Dialog Box

Use this dialog box to set bar graph options for the following dialog boxes and windows:

Edit Database Device

Expand Database

Manage Databases

Manage Database Devices

New Database

New Database Device

For more information, choose one of the following:

 Graph Mode

 Orientation


Graph Mode

Specifies the graph's mode as Selectable or Stretched. With Selectable, you can select bar or legend text. You can then edit or delete the entity represented by the selected graph element.

With Stretched, you cannot select graph elements, and the proportion of bar sizes to the available screen area is optimized. Stretched gives you an overview of all elements.


Orientation

Specifies the orientation of bars in the graph as vertical or horizontal.


Print Options Dialog Box

Use this dialog box to print a graph using the server's default printer and to configure the printing options. For more information, choose one of the following:

 Use Colors/Shading

 Use Patterns

 Print Date/Time

 Print Legend

 Date/Time Font Size

 Legend Font Size

 Print


Use Colors/Shading

Specifies that the graph will be printed in color. If a monochrome printer is used and this option is selected, shading is used to represent screen colors.


Use Patterns

Specifies that patterns will be used to represent screen colors on the graph printout.


Print Date/Time

Specifies that the printing date and time be on the graph printout.


Print Legend

Specifies that legend text be included on the graph printout.


Legend Font Size

Specifies the size of the legend font: small, normal, or large. This option is available when the Print Legend check box is selected.


Date/Time Font Size

Specifies the size of the date and time font: small, normal, or large. This option is available when the Print Date/Time check box is selected.


Print

Prints the graph on the server's default printer using the settings selected in the Print Options dialog box.


About Transfer

SQL Enterprise Manager includes a transfer management interface that can transfer all or some objects from one database to another. Transfers can be scheduled for immediate, one-time, or recurring execution.

The destination server must be Microsoft SQL Server version 6.5. The source server can be Microsoft SQL Server version 6.x or 4.x, or a SYBASE System 10 server. If the source server is version 4.x, some stored procedures or views may contain Transact-SQL statements that are no longer accepted in version 6.x. Also, for a SQL Server 4.x acting as a source, primary and foreign keys will not be transferred to the destination. Also some object names may be reserved words in version 6.x. A transfer will fail for these objects and will not complete correctly for the objects that depend on them.

In addition, the destination database must exist and be large enough to contain all objects and data that you transfer. You must have SELECT permission in the source database, and you must own the destination database.

You can use the transfer management interface, for example, to transfer data from SQL Server running on one processor architecture (for example, Intel) to SQL Server running on a different processor architecture (for example, Power PC).

You can transfer data from a server with one sort order to a server with a different sort order. Note that extended characters are not converted, so you cannot use the transfer management interface to convert from one code page to another.

Also note that when transferring data between servers with different case sensitivities, errors will occur if case is applied inconsistently when you create objects and add data. For example, on a case-insensitive server, if you create a table called ABC and then create a view called xyz as SELECT * FROM abc, the CREATE VIEW statement will work. However, if you transfer the information to a case-sensitive server, the CREATE VIEW statement will fail.

If a large database with many dependencies is being transferred, verify that the tempdb database is large enough to handle the transfer process.

See Also

Transferring Objects


Transferring Objects

You can use the transfer management interface in SQL Enterprise Manager to transfer all or some objects from one database to another.

In addition to transferring objects from one SQL Server 6.5 server to another, transferring objects from the following server applications to SQL Server 6.5 is supported:

SQL Server 4.x

SQL Server 6.0

SYBASE System 10

Transferring objects from servers other than SQL Server 6.5 servers requires that a script be run first. The scripts for other applications are available on the SQL Server 6.5 installation CD-ROM as follows:

Application	Script
SQL Server 4.x	SQLOLE42.SQL
SQL Server 6.0	SQLOLE65.SQL
SYBASE System 10	SYBSYS.SQL
A log file that contains errors and warnings is generated on the source server with a filename template of:

source_server.source_database.log

A log file that contains errors and warnings is generated on the destination server with a filename template of:

destination_server.destination_database.log

Bulk copy operations generate a log file on the destination server. There is one log per table. The filename template is:

table_owner.table_name.bcp

To transfer objects between databases

1.	From SQL Enterprise Manager, in the Server Manager window select a server from which to transfer objects.

You must have SELECT permission in the source database.

2.	From the Tools menu, choose Database/Object Transfer.

The Database/Object Transfer dialog box  appears with the selected source server and database displayed.

3.	From the list in the Destination Server box, select a destination server. To add a server name to the list, click the New Destination button and complete the Register Server dialog box.

The source server and the destination server can be the same server.

4.	From the list in the Destination Database box, select a destination database. The database must already exist and must have enough space to contain the objects and data you are transferring. The destination database must be a different database than the source database.

5.	Select or clear the Transfer options. For more information, choose one of the following:

Copy Schema

Drop Destination Objects First

Include Dependency Objects

Copy Data

Replace Existing Data

6.	To transfer all objects in the database, select the Transfer All Objects check box. To transfer selected objects, clear the Transfer All Objects check box, click the Choose Objects button, and complete the Choose Objects to be Transferred dialog box.

Objects that can be transferred include tables, views, stored procedures, defaults, rules, and user-defined datatypes.

7.	To use default object and security scripting options, select the Use Default Scripting Options check box. To change the scripting selections, clear the Use Default Scripting Options check box, click the Scripting Options button, and complete the Transfer Scripting Options dialog box.

The object scripts transfer table triggers, table DRIs, table bindings, nonclustered and clustered indexes, and owner-qualified objects. The security scripts transfer users and groups, logins, and object and statement permissions.

8.	To change the transfer scripts storage location, type a new path in the Save Transfer Files in Directory box.

The default is C:\MSSQL\LOG. Note that scheduled transfers cause the directory to be located on the destination server. You should use an empty directory for each transfer; otherwise, it can be difficult to find all files from a particular transfer.

9.	To execute the transfer immediately, click Start Transfer. To schedule the transfer, click Schedule.

When the transfer is executed, several files are created in the transfer files directory, and the specified data and objects are transferred.

A transfer can be scheduled to occur immediately, one time, or on a recurring basis. Scheduling an immediate transfer (instead of choosing Start Transfer) provides the advantage of executing the transfer as a background task, instead of interactively. However, when you choose Start Transfer to execute the transfer, you can interrupt the transfer by clicking the Cancel button in the Scripting in Progress window that appears.

10.	After the transfer has executed, you can view the transfer log by clicking the View Logs button.

See Also

Choose Objects to be Transferred Dialog Box

Transfer Objects Dialog Box

Transfer Scripting Options Dialog Box

Schedule Dialog Box


Database/Object Transfer Dialog Box

Use this dialog box to transfer some or all objects from one database to another. The destination server must be running Microsoft SQL Server version 6.5. The source server can be running Microsoft SQL Server version 6.x or 4.x, or SYBASE System 10. Transfers can be performed immediately, or can be scheduled for immediate, one-time, or recurring execution. For more information, choose one of the following:

 Source Server

 New Source

 Foreign Source

 Source Database

 Destination Server

 New Destination

 Destination Database

 Copy Schema

 Drop Destination Objects First

 Include Dependency Objects

 Copy Data

 Replace Existing Data

 Transfer All Objects

 Choose Objects

 Use Default Scripting Options

 Transfer Scripting Options

 Save Transfer Files in Directory

 Start Transfer

 Schedule

 View Logs

See Also

Foreign Source Dialog Box

Transferring Objects


Source Server

Specifies the currently selected and registered server.


New Source

Specifies a server to register. This server becomes the source server.


Foreign Source

Opens the Foreign Source dialog box, in which you can specify a server not currently selected and not registered by SQL Enterprise Manager to use as the source server. This allows a SYBASE SQL server to be the source server.


Source Database

Specifies the database that contains the object(s) to transfer.


Destination Server

Specifies a server to transfer data to. The source server and the destination server can be the same server.

To add a server name to the list, click the New Destination button and complete the Register Server dialog box that appears.


New Destination

Adds a server name to the Destination Server list. Click this button and complete the Register Server dialog box that appears.


Destination Database

Specifies the database to transfer data to. The database must already exist and have enough space to contain the objects and data you are transferring. The destination database must be a different database than the source database.


Copy Schema

Specifies that the object schema from the source database will be copied to the destination database.


Drop Destination Objects First

Specifies that objects to be transferred will first be dropped (if they exist) from the destination database.


Include Dependency Objects

Specifies to include all objects that the object selected for transfer depends on.

It is recommended that this option be selected.


Copy Data

Specifies that table data from the source database be copied to the destination database.


Replace Existing Data

Specifies that existing data in the destination tables be replaced with transferred data. Clear this option to retain existing data and append transferred data.


Save Transfer Files in Directory

Specifies where transfer scripts are stored. The default is C:\MSSQL\LOG. To change the location, type a new path in this box.

Scheduled transfers always run on the destination server, which stores the scripts. If transfers between servers are done by a third server, the scripts are stored on the third server.

It is recommended that you use a different directory for each transfer. Because many files are created with each transfer, use separate directories to locate scripts.

The directory will reside on the destination server if the transfer is scheduled.


Transfer All Objects

Specifies that all objects in the database be transferred, including tables, views, stored procedures, defaults, rules, and user-defined datatypes.


Choose Objects

Displays the Choose Objects to be Transferred dialog box. Use this dialog box to transfer only selected objects, including tables, views, stored procedures, defaults, rules, and user-defined datatypes. You can transfer all or some objects of a particular type.


Use Default Scripting Options

Specifies that default object and security scripting options be used. The default object options automatically create scripts that re-create the following in the destination database: table triggers, table DRI, table bindings, nonclustered and clustered indexes, and owner-qualified objects from the source database. The default security options re-create users and groups, logins, and object and statement permissions.


Transfer Scripting Options

Displays the Transfer Scripting Options dialog box. Use this dialog box to specify which scripting options to use.

The default object options can automatically create scripts that re-create the following in the destination database: table triggers, table DRI, table bindings, nonclustered and clustered indexes, and owner-qualified objects. The default security options can re-create users and groups, logins, and object and statement permissions.

Transfer Scripting Options is an advanced option.


Start Transfer

Executes the transfer immediately, as defined by your selections in the Database/Object Transfer dialog box.

When you choose this option to execute a transfer, you can interrupt the transfer by clicking the Cancel button in the Scripting in Progress window that appears.


Schedule

Schedules the transfer to occur immediately, one time, or on a recurring basis.

Scheduling an immediate transfer (instead of choosing Start Transfer) provides the advantage of executing the transfer as a background task instead of interactively.


View Logs

Displays the Transfer Logs dialog box.


Transfer Logs Dialog Box

Use this dialog box to view logs generated during transfer events.

For more information, choose one of the following:

 Log Files

 Text Box


Log Files

Specifies the log file to view.


Text Box

Displays the contents of the log.


Foreign Source Dialog Box

Use this dialog box to specify a server that is not registered in SQL Enterprise Manager as the source server. For more information, choose one of the following:

 Foreign Server

 Login ID

 Password


Foreign Server

Specifies the name of the server.


Login ID

Specifies the login ID for the server named in the Foreign Server box.


Password

Specifies the password for the server named in the Foreign Server box.


Choose Objects to be Transferred Dialog Box

Use this dialog box to specify which objects to transfer. For more information, choose one of the following:

 All Tables

 All Views

 All Stored Procedures

 All Defaults

 All Rules

 All User-Defined Datatypes

 Add/Remove Objects

See Also

Database/Object Transfer Dialog Box


All Tables

Specifies that all tables be transferred from the source database to the destination database.


All Views

Specifies that all views be transferred from the source database to the destination database.


All Stored Procedures

Specifies that all stored procedures be transferred from the source database to the destination database.


All Defaults

Specifies that all defaults be transferred from the source database to the destination database.


All Rules

Specifies that all rules be transferred from the source database to the destination database.


All User-Defined Datatypes

Specifies that all user-defined datatypes be transferred from the source database to the destination database.


Add/Remove Objects

Specifies which object(s) to transfer. To transfer an individual object, select it from the list on the left and click Add to display it in the list on the right.

To prevent transferring an object, select it from the list on the right and click Remove. Also, after you select a check box in the Object Types frame, to remove one or more objects of that selected type from the list on the right, click the Remove button.


Transfer Scripting Options Dialog Box

Use this dialog box to specify transfer preferences. These transfer preferences are advanced options and should only be used when their effects are understood.

For more information, choose one of the following:

 Table Triggers

 Table DRI

 Table Bindings

 Owner Qualify Objects

 Use Base Types Only

 Use Quoted Identifiers

 All Users/Groups

 All Logins

 Object Permissions

 Statement Permissions

 Non-Clustered Indexes

 Clustered Indexes

 Create Clustered Keys/Indexes After Data Transfer With 'Sorted Data'

 Preserve Fill Factors


Table Triggers

Specifies that all table triggers from the source database be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the triggers in the destination database.


Table DRI

Specifies that all table declarative referential integrity constraints from the source database be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the constraints in the destination database.


Table Bindings

Specifies that all table bindings from the source database be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the table bindings in the destination database.


Non-Clustered Indexes

Specifies that all nonclustered indexes from the source database be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the nonclustered indexes in the destination database.


Clustered Indexes

Specifies that all clustered indexes from the source database be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the clustered indexes in the destination database.


Owner Qualify Objects

Specifies that a source database object that is not owned by the dbo be transferred to the destination database. The original owner retains ownership.

When this option is cleared, the object is transferred and the user performing the transfer becomes the owner of such objects in the destination database.


Use Base Types Only

Specifies that base datatypes will be substituted for user-defined datatypes that appear in the tables to transfer.


Use Quoted Identifiers

Specifies that quotation marks (") will delimit identifiers and single quotation marks (') will delimit string constants. This prevents object names that are keywords from being misinterpreted. When this option is selected, scripts generated with this option will set the destination environment appropriately so that the quotation marks can be processed correctly.

For more information, see information about the SET statement in the Microsoft SQL Server Transact-SQL Reference.


All Users/Groups

Specifies that all users and groups from the source database be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the users and groups in the destination database.


All Logins

Specifies that all login IDs from the source server be re-created on the destination server. SQL Enterprise Manager automatically generates a script that creates the login IDs on the destination server.


Object Permissions

Specifies that all object permissions of the transferred objects be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the object permissions in the destination database.


Statement Permissions

Specifies that all statement permissions of the transferred objects be re-created in the destination database. SQL Enterprise Manager automatically generates a script that creates the statement permissions in the destination database.


Create Clustered Keys/Indexes After Data Transfer With 'Sorted Data'

Specifies that clustered keys and indexes will be created by using the SORTED_DATA option after data is transferred.

If this option is not selected, clustered keys and indexes are created before data is transferred, and nonclustered indexes are created after data is transferred.


Preserve Fill Factors

Specifies that clustered keys and indexes will be created by using the SORTED_DATA_REORG option after data is transferred. The Create Clustered Keys/Indexes After Data Transfer With 'Sorted Data' option must be selected.


SQL Executive Error Log Window

Displays the contents of the SQL Executive error log. The list box displays each error by type, date, and time, and it includes an informative message. To filter the contents, you can use the following:

Only Include Lines of Type

Specifies the error types to be displayed. You can choose All Types, Error, Information, or Warning.

Containing Text

Specifies text to search for in the messages. Only those messages that contain the specified text will be displayed. The search is case-insensitive.


File Location window

Use this window to select the path for the file (the location on disk where the file will be stored). The path will become part of the physical name of the file.


Mirror/Re-Mirror Database Device Dialog Box

Use this dialog box to mirror or remirror a database device. This dialog box is named Re-Mirror Database Device dialog box after you have unmirrored a database device and from the Edit Database Device dialog box, have selected mirroring. For more information, choose one of the following:

 Mirror Device Filename

 Mirror Now

 Re-Mirror Now

See Also

Adding a Database Device

Modifying a Database Device


Mirror Device Filename

Displays the full qualified path where the device will be mirrored. To change the mirror name and path, type a different filename or path in this box.


Mirror Now

Mirrors the database device to the specified location.


Re-Mirror Now

Remirrors a database device to the specified location.


Unmirror Device Dialog Box

Use this dialog box to stop a database device from mirroring or to replace the original database device with the mirror device. For more information, choose one of the following:

 Switch to Mirror Device - Retain Original Device

 Switch to Mirror Device - Replace Original Device

 Turn off Mirroring - Retain Mirror Device

 Turn off Mirroring - Remove Mirror Device

 Mirror Device Filename

 Unmirror

See Also

Modifying a Database Device


Switch to Mirror Device - Retain Original Device

Specifies that the mirror device is the active database device and the previous database device is retained.


Switch to Mirror Device - Replace Original Device

Specifies that the mirror device is the active database device and replaces the other database device.


Turn off Mirroring - Retain Mirror Device

Pauses the mirroring and allows you to mirror at a later time. Also retains the mirror device.


Turn off Mirroring - Remove Mirror Device

Specifies to stop the mirroring and remove the mirror device.


Mirror Device Filename

Displays the fully qualified path of the mirrored device.


Unmirror

Stops the database device from mirroring as specified in the Unmirror Device dialog box.


Manage Triggers Window

Use this window to create, modify, or drop triggers for the database that is selected in the Server Manager window. For more information, choose one of the following:

 Table

 Trigger

 Execute

 Print

 Object Menu-Drop Command

See Also

Creating a Trigger

Dropping a Trigger

Modifying a Trigger


Table

Specifies the table to manage a trigger for.


Trigger

Displays the triggers for the specified table. Each table can have only one insert, one update, and one delete trigger. To create a trigger, select <new> and then type the text of the trigger in the box by using valid Transact-SQL syntax. To modify a trigger, select the trigger and change the text in the box. New triggers automatically replace old triggers of the same type.

For help with Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE TRIGGER.

Represents an INSERT trigger.

Represents an UPDATE trigger.

Represents a DELETE trigger.


 Execute

Saves the trigger to the SQL Server. Also, you can press CTRL+E to save a trigger.


 Print

Prints information about the selected trigger.


Object Menu-Drop Command

Drops the trigger that is selected in the Trigger box.


Manage Stored Procedures Window

Use this window to create, modify, and drop stored procedures for the database that is displayed in the Server Manager window. For more information, choose one of the following:

 Procedure

 Execute

 Print

 Object Menu-Drop Command

See Also

Creating a Stored Procedure

Dropping a Stored Procedure

Modifying a Stored Procedure


Procedure

Specifies whether to create, modify, or drop a stored procedure. To create a stored procedure, select <new> and type the text of the stored procedure in the window by using valid TransactSQL syntax. To modify a stored procedure, expand the box, select the name of the procedure, and edit the text in the window. To drop a stored procedure, expand the box, select the name of the procedure to drop, and from the Objects menu, choose Drop.

For help with Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and search for CREATE PROCEDURE.


 Execute

Saves the stored procedure to the SQL Server. Also, you can press CTRL+E to save a stored procedure.


 Print

Prints the text of the the selected stored procedure.


Object Menu-Drop Command

Drops the stored procedure that is displayed in the Procedure box.


Manage Views Window

Use this window to create, modify, and drop views for the database that is selected in the Server Manager window. For more information, choose one of the following:

 View

 Execute

 Print

 Object Menu-Drop Command

See Also

Creating a View

Dropping a View

Modifying a View


View

Specifies whether to create, modify, or drop a view. To create a view, select <new> and type the text of the view in the window by using valid Transact-SQL syntax. To modify a view, expand the View box, select the name of the view, and edit the text in the window. To drop a view, expand the view box, select the name of the view to drop, and from the Objects menu, choose Drop.

For help with Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE VIEW.


 Execute

Saves the view to the SQL Server. Also, you can press CTRL+E to save the view.


 Print

Prints the text of the selected view.


Object Menu-Drop Command

Drops the view that is displayed in the View box.


Application Tab

Use this tab to set application preferences for SQL Enterprise Manager. For more information, choose one of the following:

 Server State Poll Interval (seconds)

 Server Registration Information

 Store Locally

 Store User Independent

 Read From Remote

 Server Name

 Defaults


Server State Poll Interval (seconds)

Specifies the interval set for polling the server status, which is displayed in the Server Manager Window. Polling uses the Windows NT Service Control Manager.

Because the Service Control Manager is not available with Windows 95, no polling information is available on a client running Windows 95. Also, when an aliased server (using the SQL Client Configuration utility) is registered with SQL Enterprise Manager, server state polling is not supported. Status information (such as started, stopped, or paused) for these servers is not displayed in the Server Manager window.


Server Registration Information

Sets SQL Enterprise Manager to use server registration information that is stored on a remote server. For example, you can configure several computers so that their SQL Enterprise Manager installations have identical configurations (common program groups, common servers, and so on).


Store Locally

Specifies that SQL Enterprise Manager will use server registration information that is stored locally (on the same server that SQL Enterprise Manager is installed on).


Store User Independent

Specifies that SQL Enterprise Manager will use common registration information for all SQL Enterprise Manager users. If cleared, maintains separate registration information for each user (based on the user's Windows NT logon).


Read From Remote

Specifies that SQL Enterprise Manager will use server registration information that is stored in the Registry of the remote server.


Server Name

Specifies the name of a remote server from which SQL Enterprise Manager will access server registration information.


Defaults

Sets the options in this dialog box to their default settings. The Server State Poll Interval is set to 10, and the Store Locally and Store User Independent options are selected.


Manage Tables Window

Use this window to create and modify tables; to create identity columns; and to specify primary and foreign keys, UNIQUE constraints, and CHECK constraints. For more information, choose one of the following:

 Table

 Save Table

 Advanced Features

 Key

 Identity

 Column Name

 Datatype

 Size

 Nulls

 Default

See Also

Check Constraints Tab

Foreign Keys Tab

Primary Key/Identity Tab

Unique Constraints Tab


Table

Specifies whether to create or modify a table. To create a table, select <new>. To modify a table, select the name of the table to modify.


 Save Table

Saves information for a new table or changes to an existing table. To save a table that you have just created, in the Specify Table Name dialog box, type a name.


 Advanced Features

Displays Primary Key/Identity, Foreign Keys, Unique Constraints, and Check Constraints tabs.


Key

Specifies whether the column is part of a primary key. The Key column is read-only. To create a primary key, click the Advanced Features button and then supply the appropriate information in the Primary Key/Identity tab.


Identity

Specifies whether the column is an identity column. The Identity column is read-only. To create an identity column, click the Advanced Features button and then supply the appropriate information in the Primary Key/Identity tab.


Column Name

Specifies the name of the column. To create a table column, type a name for the column. To modify a table column, type a new name in the box. To modify a table column name, you must rebuild all views, stored procedures, or triggers that reference that column.


Datatype

Specifies the datatype for the column. When creating a table, expand the datatype box and select a datatype. When modifying a table, you cannot change the datatype.


Size

Specifies the datatype size when the datatype is char, varchar, binary, varbinary, numeric, or decimal. For numeric and decimal datatypes, you must specify precision and scale separated by a comma. If you are modifying the table, you cannot change the datatype size.


Nulls

Specifies whether the column allows null values. If you are creating a table and the column you are adding will allow null values, select the Nulls box. If you are modifying a table, you cannot change an existing column's null values and all new columns must allow null values.


Default

Specifies a default for the column. The default is to be used if a value is not provided when data is inserted into the table. To create a default, type the default text in the box. For example, to provide the current date for a datetime column as a default, type getdate( ) in the Default box.


Primary Key/Identity Tab

Use this tab to specify information for a primary key and an identity column for a table. When creating a table, you can create a primary key or an identity column. When modifying a table, you can create or drop a primary key. You cannot modify identity column information for an existing table. For more information, choose one of the following:

 Column Name

 Type

 Fill Factor

 Add

 Remove

 Identity Column

 Seed Value

 Increment

See Also

Manage Tables Window


Column Name

Specifies the column(s) (up to 16) to associate with the primary key. The Column Name box lists only those columns that are valid primary key candidates. For example, columns that allow null values cannot be associated with a primary key.


Type

Specifies whether to create the primary key index as clustered or nonclustered. When you create a primary key, a unique index is automatically created. Only one clustered index can be created per table.


Fill Factor

Specifies a fill factor when you are creating a primary key index on an existing table.


Add

Associates the information that is entered in this tab with the table. Information is not saved to SQL Server until you click the Save Table button.


Remove

Removes the primary key that is displayed in the Column Name box. Information is not saved to SQL Server until you click the Save Table button.


Identity Column

Specifies the column to create as an identity column. You can add an identity column only when creating a table.


Seed Value

Specifies the initial (seed) value for the identity column.


Increment

Specifies a value to add to the last identity value to get the new identity value. For example, if you specify a seed value of 5 and an increment of 5, the first row will contain 5, the second 10, and so on.


Foreign Keys Tab

Use this tab to specify information for a foreign key for a table. You can add foreign keys when you create or modify a table. For more information, choose one of the following:

 Foreign Key

 Referenced Table

 Key Columns

 Foreign Key Columns

 Add

 Remove

See Also

Manage Tables Window


Foreign Key

Specifies whether to create or drop a foreign key. To create a foreign key, select <new> and type a name for the key. A name is optional. If you do not provide a name, SQL Server automatically generates one. To drop a foreign key, select the key name in this box and then click Remove.


Referenced Table

Specifies the table that contains the primary key or UNIQUE constraint the foreign key is associated with.


Key Columns

Displays the columns in the primary key or UNIQUE constraint of the referenced table.


Foreign Key Columns

Specifies columns of the current table to associate with key columns of the referenced table. The datatype and the size of the Foreign Key column must match the datatype and the size of the Key column.


Add

Associates foreign key information with the table. Information is not saved to SQL Server until you click the Save Table button.


Remove

Removes the foreign key selected in the Foreign Key box. Information is not saved to SQL Server until you click the Save Table button.


Unique Constraints Tab

Use this tab to specify UNIQUE constraints for a table. For more information, choose one of the following:

 Unique Constraint

 #

 Column Name

 Type

 Fill Factor

 Add

 Remove

See Also

Manage Tables Window


Unique Constraint

Specifies whether to create or drop a unique constraint. To create a constraint, select <new> and provide a name for the constraint. A name is optional. If you do not provide a name, SQL Server will automatically generate one. To drop a constraint, select the name of the constraint to drop.


#

Specifies a number that is automatically generated for each constraint column.


Column Name

Specifies the column(s) to create a UNIQUE constraint for.


Type

Specifies whether to create a clustered or nonclustered index. An index is automatically created when you create a UNIQUE constraint. Only one clustered index can be created per table.


Fill Factor

Specifies a fill factor for the index when you are creating a UNIQUE constraint on an existing table.


Add

Adds the information specified in this tab. Information is not saved to SQL Server until you click the Save Table button.


Remove

Removes the selected constraint in the Unique Constraint box. Information is not saved to SQL Server until you click the Save Table button.


Check Constraints Tab

Use this tab to specify CHECK constraints for a table. You can specify CHECK constraints when you create or modify a table. For more information, choose one of the following:

 Check Constraint

 Not for Replication

 Constraint

 Add

 Remove

See Also

Manage Tables Window


Check Constraint

Specifies whether to create or drop a check constraint. To create a constraint, select <new> and type a name for the constraint. A name is optional. If you do not provide a name, SQL Server automatically generates a name. To drop a constraint, select the name of the constraint to drop.


Not for Replication

Specifies that the CHECK constraint will not be replicated.


Constraint

Specifies text for the constraint.


Add

Adds the constraint. Information is not saved to SQL Server until you click the Save Table button.


Remove

Removes the constraint selected in the Check Constraint box. Information is not saved to SQL Server until you click the Save Table button.


Manage Databases Window

Use this window to view information about the size of a server's databases, and to add, modify, and delete databases. You can view databases you have access to. For more information, choose one of the following:

 New Database

 Edit Database

 Delete Database

 Databases

 Graph Controls

See Also

Dropping a Database

Modifying a Database

New Database Dialog Box


 New Database

Displays the New Database dialog box, which is used to create databases.


 Edit Database

Displays the Edit Database dialog box, which includes the Database, Options, and Permissions tabs. Use these tabs to expand or shrink databases and to set database options and statement permissions. Select a database in the Manage Databases window before you click the Edit Database button.


 Delete Database

Deletes a database. Select a database from the Manage Databases window before you click this button.


Databases

Shows the selected server's databases, the size of each database, and the free space on each.


Graph Controls

Are three buttons in the lower left of the window. Use the following buttons to configure and print information that is displayed in the graph:

Graph Properties

Bar Graph Options

Print Options


New Database Dialog Box

Use this dialog box to create a database immediately or to schedule creating a database.

 Name

 Create for Load

 Data Device

 Size (MB)

 Log Device

 Size (MB)

 Available Space on Database Devices

 Graph Controls

 Create Now

 Schedule

See Also

Manage Databases Window

New Database Device Dialog Box


Name

Specifies a name for the database.


Data Device

Specifies the device on which to allocate space for the new database. To create a device, select <new> and complete the information in the New Database Device dialog box.


Size (MB)

Specifies the amount of space, in megabytes (MB), to allocate for the database on the selected device.


Log Device

Specifies the device on which to allocate space for the transaction log. To create a device, select <new> and complete the information in the New Database Device dialog box.


Size (MB)

Specifies the amount of space, in MB, to allocate for the transaction log on the selected device.


Create for Load

Specifies that pages will not be zero-initialized when the database is created. With this option selected, the database is created more quickly.

Select this option if you plan to load a backup into the database you are creating before you use the database. However, users other than database owners (DBOs) cannot access the database until a backup is loaded and the database option DBO Use Only is turned off.


Available Space on Database Devices

Shows the server's database devices, the size of each device, and the free space on each.


Graph Controls

Are three buttons in the lower left of the dialog box. Use the following buttons to configure and print information that is displayed in the graph:

Graph Properties

Bar Graph Options

Print Options


Create Now

Creates the database as you have defined it in the New Database dialog box.


Schedule

Opens the Schedule dialog box, in which you can schedule creating the database.


Expand Database Dialog Box

Use this dialog box to allocate more space for a database or transaction log. You can schedule the expansion to be performed immediately or schedule it.

 Data Device

 Size (MB)

 Log Device

 Size (MB)

 Available Space on Database Devices

 Graph Controls

 Expand Now

 Schedule

See Also

Manage Databases Window

New Database Device Dialog Box


Data Device

Specifies the device on which to allocate additional space for the selected database. To create a device, select <new>.

Log devices dedicated to the selected server no longer appear in the Data Device list, because they are not available to the expand database process.


Size (MB)

Specifies the amount of space, in megabytes (MB), to allocate on the selected device for the database.


Log Device

Specifies the device on which to allocate additional space for the transaction log. To create a device, select <new>.


Size (MB)

Specifies the amount of space, in MB, to allocate on the selected device for the transaction log.


Available Space on Database Devices

Shows the server's database devices, the size of each device, and the free space on each.


Graph Controls

Are three buttons in the lower left of the dialog box. You can use the following buttons to configure and print information that is displayed in the graph:

Graph Properties

Bar Graph Options

Print Options


Expand Now

Expands the database or transaction log immediately, as specified in the Expand Database dialog box.


Schedule

Opens the Schedule dialog box, in which you can schedule the expansion.


Manage Database Devices Window

Use this window to view the logical names of a selected server's database devices, and the size of and the space used on each device. You can add, modify, and remove devices.

 New Device

 Edit Device

 Delete Device

 Devices

 Graph Controls

See Also

Edit Database Device Dialog Box

New Database Device Dialog Box


 New Device

Displays the New Database Device dialog box, which is used to create database devices.


 Edit Device

Displays the Edit Database Device dialog box, which is used to modify database devices. You must select a device from the graph before you click this button.


 Delete Device

Deletes a device. You must select a device from the graph before you click this button.


Devices

Shows the server's devices, the size of each device, and the free space on each.


Graph Controls

Are three buttons in the lower left of the window. You can use the following buttons to configure and print information that is displayed in the graph:

Graph Properties

Bar Graph Options

Print Options


New Database Device Dialog Box

Use this dialog box to add a database device. The device can be created immediately or scheduled.

 Name

 Default Device

 Location

 Path

 Locate

 Size (MB)

 Available Storage Space

 Graph Controls

 Create Now

 Schedule

 Mirroring

See Also

Manage Database Devices Window


Name

Specifies a name for the device.


Default Device

Sets the device as a default device to be used when no device is specified for a database.


Location

Specifies a drive on which to place the device.


Path

Specifies a path for the new device. The path is set automatically based on the device name. The path defaults to the location of the MASTER device. To change the path, type a new path or click the Locate button.


 Locate

Displays the Database Device Location dialog box, which is used to select a different path for the device.


Size (MB)

Specifies the size for the device, in megabytes (MB). To change the size, type a new number or move the slider.


Available Storage Space

Shows the amount of storage space, in MB, that is available on the server disk drives.


Graph Controls

Are three buttons in the lower left of the dialog box. You can use the following buttons to configure and print information that is displayed in the graph:

Graph Properties

Bar Graph Options

Print Options


Create Now

Creates the device immediately, as specified in the New Database Device dialog box.


Schedule

Opens the Schedule dialog box. Click this button to schedule creating the device.


Mirroring

Displays the Mirror Database Device dialog box, which is used to mirror the device.


Edit Database Device Dialog Box

Use this dialog box to set a device as the default device, or to handle mirroring for a device. You can also expand the size of a device. The changes can be made immediately or scheduled for later.

 Name

 Location

 Size (MB)

 Default Device

 Device Space Usage

 Graph Controls

 Change Now

 Schedule

 Mirroring

See Also

Manage Database Devices Window


Name

Displays the name of the database device that is selected in the Manage Database Devices window. You cannot change a device name.


Location

Displays the path for the database device. You cannot change the location of the selected device.


Size (MB)

Displays the device size, in megabytes. To increase the device size, type a number in this box. You cannot reduce the size of a device.


Default Device

Sets the device as a default device to be used when no device is specified for a database.


Device Space Usage

Shows the device size and the amount of space currently used on the device.


Graph Controls

Are three buttons in the bottom left of the dialog box. You can use the following buttons to configure and print information that is displayed in the graph:

Graph Properties

Bar Graph Options

Print Options


Change Now

Modifies the device immediately as specified in the Edit Database Device dialog box.


Schedule

Opens the Schedule dialog box. Click this button to schedule modifying the device.


Mirroring

Displays the Mirror Database Device dialog box, which is used to mirror, unmirror, or remirror a database device.


Managing SQL Server Messages

You can view a list of available messages on SQL Server; search for messages by message text, severity, and/or error number; and search for messages that are always written to the Windows NT application event log. You can select an option to always write a message to the Windows NT application event log, and create or edit user-defined messages.

To select a message to set an alert on

1.	While creating or editing an alert in the New or Edit Alert dialog box, under Alert Definition, select Error Number and then click the Locate button.

The Manage SQL Server Messages dialog box appears.

2.	To view all available messages, leave the default setting as is and click the Find button. A list of all messages appears.

To view a subset of all available messages, complete the Search Parameters options and then click the Find button. A list of all messages that fit the profile appears.

To sort the list of messages by a column attribute, click the heading for that column. The sort option is not available if the list contains more than 750 rows. The default sort order is by error number.

3.	Select the message to define an alert for, and then click the Select button. The New or Edit Alert dialog box returns. The selected message number is automatically entered in the Error Number box.

To create a user-defined message

1.	From the Server menu, choose Messages.

The Manage SQL Server Messages dialog box appears.

2.	Click the New button.

The New Message dialog box appears.

3.	In the Error Number box, type an error number for the user-defined message. Error numbers for user-defined messages begin at 50001.

4.	In the Severity box, select a severity level for the message.

5.	In the Message Text box, type the message text.

6.	In the Language box, select a language to display the message in.

7.	To always write the message to the Windows NT application event log, select the Always Write to Windows NT Eventlog box.

8.	Click OK.

To edit a message

1.	From the Server menu, choose Messages.

The Manage SQL Server Messages dialog box appears.

2.	Define the search criteria for the message and then click the Find button.

3.	Select the message from the list and then click the Edit button.

The Edit Message dialog box appears.

4.	Edit the appropriate information.

For user-defined messages, all options except Error Number can be changed. For other messages, if severity is less than 19, only the option Always Write to Windows NT Eventlog can be changed.

5.	Click OK.

To delete a message

1.	From the Server menu, choose Messages.

The Manage SQL Server Messages dialog box appears.

2.	Define the search criteria for the message and then click the Find button.

3.	Select the message from the list and then click the Delete button. Only user-defined messages can be deleted.

See Also

Alerts Overview


Manage Scheduled Tasks Window

Use this window to view the list of tasks that are scheduled and the list of tasks that are currently running for a selected server. You can add, modify, or remove a task and view task history information from this window.

A user can view tasks and task histories for only those tasks the user created and owns. The system administrator can view all tasks.

For more information choose one of the following:

 New Task

 Edit Task

 Delete Task

 Run Task

 Task History

 Stop Task

 Refresh

 Task Engine Options

 Task List Tab

 Running Tasks Tab

See Also

Deleting a Scheduled Task

Editing a Scheduled Task

New/Edit Task Dialog Box

Scheduling a Task

Task Engine Options Dialog Box

Task History Dialog Box


 New Task

Displays the New Task dialog box, which you can use to create and schedule a task.


 Edit Task

Displays the Edit Task dialog box, which you can use to change options for a tab. Select the Task List tab to make this option available.


 Delete Task

Removes the selected task. Displays a message that asks you to confirm this selection. Select the Task List tab to make this option available.


 Run Task

Immediately starts the task that is selected in the Task List tab. The task must be enabled and the SQL Executive service must be running before selecting this option.


 Task History

Displays the Task History dialog box, which provides a history for the selected task. Select the Task List tab to make this option available.


 Stop Task

Stops the running task.


 Refresh

Updates the Task List and Running Tasks tabs.


 Task Engine Options

Displays the Task Engine Options dialog box, which you can use to limit the size of or clear the task history log.


Task List Tab

Displays a list of scheduled tasks for the server that is selected in the Server Manager window.

Name

Is the task name.

Enabled

Indicates whether the task is enabled or disabled.

Owner

Specifies the task owner.

Type

Specifies the type of task. CmdExec is an operating system command or executable file. TSQL is a Transact-SQL statement. Distribution, LogReader, and Sync are replication tasks.

Frequency

Specifies the type of schedule for a task.

Last Run

Is the day the task last ran.

Last Run Status

Specifies the status of the task. A task that ran without problems will have a Successful status. A task that fails during execution will have a Failed status followed by a stop sign icon and will be highlighted in red.


Running Tasks Tab

Displays a list of tasks that are running or about to run. Queued tasks are also shown in this tab. For subsystem task types (other than TSQL), a task can be queued if it is scheduled to run but the subsystem has no free threads available.

Name

Is the task name.

Owner

Specifies the task owner.

Type

Specifies the type of task. CmdExec is an operating system command or executable file. TSQL is a Transact-SQL statement. Distribution, LogReader, and Sync are replication tasks.

Start Date

Is the time and the day the task began.

Status

Displays status information, either Failed or Successful, about the task.


Task Engine Options Dialog Box

Use this dialog box to limit the size of the history log for a task. The history log contains the information for the task that is selected in the Task List tab. By managing the size of the history log, you control how long task history information is retained. For more information, choose one of the following:

 Limit Size of Task History Log

 Maximum Task History Log Size (rows)

 Maximum Task History Rows Per Task

 Current Task History Log Size (rows)

 Clear Task History Log

See Also

Manage Scheduled Tasks Window


Limit Size of Task History Log

Specifies whether to limit the size of the history log for the specified task. If you clear this option, the size of the history log is not limited and the number in the Maximum Task History Log Size box has no effect. Depending on the activity level of the server, clearing this option can cause the size of the msdb.dbo.syshistory table to increase rapidly. In some cases, it can increase until the msdb database is full and subsequent tasks and alerts fail. If you need to retain large amounts of task history information, expand the msdb database size to accommodate the rapid growth of the syshistory table.


Maximum Task History Log Size (rows)

Specifies the maximum number of rows to be kept in the history log. The history log will retain the most recent rows entered. When the number of rows exceeds the entry in this box, the oldest row in the log is purged to make room for the newest row. The default number of rows is 1,000. This option applies only if the Limit Size of Task History Log box is selected.


Current Task History Log Size (rows)

Displays the actual size, in rows, of the history log.


Clear Task History Log

Empties the history log.


Maximum Task History Rows Per Task

Specifies the maximum number of rows kept per task. When the number is exceeded, the oldest row in the log for the task is purged to make room for the newest row.


Task History Dialog Box

Use this dialog box to view a history for the task that is selected in the Task List tab. For more information, choose one of the following.

 Run At

 Result

 Operator Emailed

 Run Duration

 Last Error/Message

 Refresh

 Clear All

See Also

Scheduling a Task


Run At

Shows the date and the time the task ran.


Result

Shows whether the task completed successfully.


Operator Emailed

Indicates whether e-mail was sent after running a task if task scheduling was configured for email notification.


Run Duration

Shows how long the task ran.


Last Error/Message

Shows messages that resulted from the task run.

For a CmdExec task, the process exit code and the last 230 bytes (approximately) of that CmdExec task's output is included in the message. The information can assist in determining the cause of a task failure or can be useful in confirming that the task functioned correctly. If output is more than can be displayed, the displayed output is preceded by an ellipsis (...).


Refresh

Updates the information displayed in the Task History dialog box.


Clear All

Removes history information for selected tasks. Only the task owner can clear history information.


New/Edit Operator Dialog Boxes
New/Edit Operator Dialog Box

Use this dialog box to add an operator or to modify operator information for the server that is selected in the Server Manager window. Operators are users of SQL Server who are notified when an alert occurs.

For more information, choose one of the following:

 ID

 Name

 Enabled

 Email Notifications

 Pager Notifications

 Alerts Assigned to This Operator

 Most Recent Notifications

 Send Mail

See Also

Creating an Operator

Editing Operator Information

Pager Email Tab


ID

Is the operator ID that is automatically generated by SQL Server.


Name

Is the name of the operator. If you are creating an operator, type the name of the operator in this box.


Enabled

Specifies whether an operator can receive alerts by default. To create an operator or modify the operator information without enabling the operator to receive notifications, clear this check box.


Email Notifications

Specifies e-mail information for the operator.

Email-Name

Specifies the e-mail name of the operator.

Test

Sends a test message to the e-mail name that is specified in the Email-Name box. If the mail client is running, SQL Enterprise Manager will attempt to match the e-mail name or pager e-mail name to the closest existing friendly e-mail name. Note that the Test option is available only on computers that are running the 32-bit version of the Microsoft Mail client.


Pager Notifications

Specifies a pager e-mail name and schedule for the operator. To specify the pager schedule, select the appropriate check boxes and workday begin and end times.

Pager Email-Name

Specifies a valid pager e-mail name for the operator.

Test

Sends a test message to the pager e-mail name that is specified in the Pager Email-Name box. Note that you must define a template for the paging information in the Pager Email tab of the Alert Engine Options dialog box before you can send a test message to the pager.

Days of the Week

Specifies which days the operator is available to receive pages.

Workday Begin

Specifies the time an operator can start receiving pages. You can set a separate time for weekdays, Saturday, and Sunday.

Workday End

Specifies the time an operator stops receiving pages. You can set a separate time for weekdays, Saturday, and Sunday.


Alerts Assigned to This Operator

Specifies the alerts that are assigned to the specified operator. To assign an alert to the operator, select the alert and then select the notification method: e-mail and/or pager. A solid envelope or telephone icon indicates that the alert already has the selected notification defined on it. An outline of an envelope or telephone icon indicates that the alert does not have the selected notification defined for it. You can create an operator even if you have not yet created alerts.


Most Recent Notifications

Provides information about the most recent notifications the operator has received.


Send Mail

Opens the Send Note window from the underlying mail system and uses the value in the Email-Name box as the e-mail recipient. This feature is useful for notifying operators about changes in their alert-handling responsibilities.

This button is enabled only when the mail client is running.


New/Edit Alert Dialog Box

Use this dialog box to create or modify an alert for the server that is selected in the Server Manager window. For more information, choose one of the following:

 ID

 Name

 Enabled

 Alert Definition

 Response Definition

 Operators to Notify

 Most Recent Occurrences

See Also

Creating an Alert

Manage SQL Server Messages Dialog Box


ID

Is the ID of the alert that is automatically generated by SQL Server.


Name

Is the alert name. If you are creating an alert, type a name for the alert in this box.


Enabled

Specifies whether the alert will occur by default. To create an alert without enabling it, clear this check box.


Alert Definition

Defines the conditions that will cause an alert. Specify an error number or a severity level.

Error Number

Raises an alert when a specific error message is entered in the Windows NT application event log. Type the error message number. To select from a list of error messages or to create a custom error message, click the Locate button.

 Locate

Displays the Manage SQL Server Messages dialog box, which you can use to find error messages.

Severity

Specifies a level of severity that will raise an alert for any error of that specified severity that is entered in the Windows NT application event log.

Database Name

Specifies that an alert will occur only when an error is received from a specific database. Database Name is optional.

Error Message Contains This Text

Specifies that an alert will occur only when the error message contains the string that is entered in this box. This is optional.


Response Definition

Specifies the action the system will take when the defined alert occurs.

Task to Execute

Specifies that a task will run when the defined alert occurs. To create a task, select (New Task). The task must be a non-replication task, and it must be scheduled to occur on demand. Running a task is optional.

Raise an SNMP Trap When Alert Occurs

Specifies that an SNMP trap will be raised when the defined alert occurs. The SNMP trap notifies the SQL Server SNMP agent that a status or condition has occurred.

Alert Notification Message to Send to Operator

Specifies that additional information will be sent to the operator when the defined alert occurs. This information is in addition to the text of the error message, which can also be sent in the alert notification message by selecting the Include Error Message Text In check box. You can enter up to 255 characters. You do not need to type the error message text. Sending an alert notification message is optional.

Include Error Message Text In

Includes the error message text as part of the notification message that is specified in the Alert Notification Message to Send to Operator box.

Delay Between Responses for Recurring Alert (seconds)

Specifies the interval of time to wait for notifying an operator of recurring alerts. If you specify a delay, the operator will be notified of the first alert and if a subsequent alert is the same, then the operator only will be notified if the specified delay has elapsed. For example, if you type 8 in this box, and later five alerts that meet the alert definition occur within a period of 8 seconds or less, only one alert will be sent to the operator.


Operators to Notify

Specifies which operator(s) to notify when a defined alert occurs. Select Email and/or Pager for each operator to notify. A solid envelope or telephone icon indicates that the operator already has address information of that type defined. An outline of an envelope or telephone icon indicates that the alert does not have operator address information of that type defined. You can create an alert even if you have not yet added operators.


Most Recent Occurrences

Provides information about the most recent occurrences for the defined alert.

Alert

Specifies the date and the time the alert message occurred. If the alert has never occurred, (Never Occurred) appears in the box.

Response

Specifies the date and the time of the response to the alert. If the response has never occurred, (Never Occurred) appears in the box.

Count Reset

Specifies the last time the date and the time were reset. Once an alert cause has been fixed, an operator resets the count.

Reset Count

Resets the Count Reset date and time and the Alert Count number. Once an operator has solved the cause of the alert, the operator can reset these boxes to capture information about new alerts.


Schedule Dialog Box

Use this dialog box to schedule database events. For more information, choose one of the following:

 Task Name

 SQL Command

 Immediately

 One Time

 Recurring

 Change

 Options

See Also

Task Schedule Dialog Box

TSQL Task Options Dialog Box


Task Name

Displays the task name to create a schedule for.


SQL Command

Displays the task text.


Immediately

Specifies that the task will run immediately as a background task in SQL Enterprise Manager. To start the backup, click OK.


One Time

Specifies that the task will run once at the date and the time that are specified in the On Date and At Time boxes. Note that the time is based on the time at the server, not at the client.


Recurring

Specifies that the task will run on a recurring schedule as specified in the Recurring box. To set the schedule, choose Change. The Task Schedule dialog box appears. Complete the options and click OK.


Change

Displays the Task Schedule dialog box, which you can use to set the schedule that is displayed in the Recurring box.


Options

Displays the TSQL Task Options dialog box, which you can use to set task options for sending e-mail notification about the task, to write an entry to the Windows NT application event log, and to specify the number of retry attempts if the task fails.


TSQL Task Options Dialog Box

Use this dialog box to specify where to route notification that a task is completed and to set the number of retries for a given task. For more information choose one of the following:

 Task Name

 Notifications

 Retries

 Replication


Task Name

Displays the name of the task you are setting options for.


Notifications

Specifies whether to notify an operator by e-mail of the task run status and whether to record information about the task run in the Windows NT application event log.

Email Operator

Specifies whether to notify a user on task success and/or failure. In the Email Operator box, select the name of the operator to notify, and then select the appropriate check boxes. To specify a new operator, select <New Operator>. To remove an assigned operator, select <No Operator>.

Write To Windows NT Application Event Log

Specifies whether to record task success and/or failure information in the Windows NT application event log. Note that all events are logged in the SQL Executive Task History table.

On Success

Performs the specified action (send e-mail to an operator, write to the Windows NT application event log) when the task successfully runs.

On Failure

Performs the specified action (send e-mail to an operator, write to the Windows NT application event log) when the task fails.


Retries

Sets the number of retry attempts for a failed task. Note that you cannot set retry attempts for Transact-SQL tasks.

Retry Attempts

Specifies the number of retry attempts. Can be from 0 to 256.

Retry Delay (minutes)

Specifies the amount of time, in minutes, to wait before retrying the task.


Replication

Specifies a remote target server and a database for logreader and distribution tasks only.

Server

Specifies the remote target server.

Database

Specifies the remote target database.


Server Legend

Available from the Server Manager window, the server legend displays the possible statuses for servers, SQL Executive, SQL Mail, and databases. The legend window also provides lists of possible types of system accounts, backup devices, and database objects. These states, types, and values are listed below:

SQL Server component	Status values
Server	Unknown Running Paused Stopped Connected
SQL Mail	Unknown  Running  Stopped
SQL Executive	Unknown Running Stopped
MS DTC States	Unknown  Running  Stopped
Database	Active Single User/DBO Only/Read Only Offline/Suspect/Loading Publishing
SQL Server component	Type values
System Account	Login Database User Database Group
Backup Device	Disk Device Tape Device Floppy Device Pipe Device
Database Object	Publication Table View Stored Procedure Extended Stored Procedure Rule Default User-Defined Datatype Database User
To access the server legend

1.	From the Server Manager window, click on the legend icon at the top of the window.

2.	The Server Legend appears.

To use the arrow keys on your keyboard to scroll up and down the legend list, type CTRL+L.


New Subscriber Dialog Box

Use this dialog box to add the server as a subscriber to the local server or to add an ODBC subscriber.

For more information, choose one of the following:

 Name

 New Server

 ODBC Subscriber

See Also

New ODBC Subscriber Dialog Box

Register Server Dialog Box


Name

Specifies the name of the server to add. To display a new subscriber name, click the New Server or ODBC Subscriber button and complete the dialog box that appears.


New Server

Specifies a server to register with SQL Enterprise Manager. When you click this button, the Register Server dialog box appears. The registered server can then become a subscriber.


ODBC Subscriber

Specifies an ODBC server to add as a subscriber. When you click this button, the New ODBC Subscriber dialog box appears.


Install Replication Publishing Dialog Box

Use this dialog box to install a distribution database for replication.

For more information, choose one of the following:

 Local - Install New Local Distribution Database

 Remote - Use Existing Remote Distribution Server

 OK

See Also

Manage Remote Servers Dialog Box

New Database Dialog Box

Replication Overview


Local - Install New Local Distribution Database

Installs the distribution database on the local server that is selected in the Server Manager window.

Database Name

Specifies a name for the distribution database on the local (publication) server. The default is distribution.

Data Device

Specifies a device on which to store the distribution database. You can select an existing device, or <new> to create a device. When you choose <new>, the New Database dialog box appears, in which you can create a database device.

Size (MB)

Specifies the amount of space to allocate for the distribution database on the specified device. The recommended minimum size is 30 megabytes (MB).

Log Device (MB)

Specifies the device on which to store the transaction log for the distribution database. You can select an existing device, or <new> to create a device. When you choose <new>, the New Database dialog box appears, in which you can create a device for the transaction log.

Size (MB)

Specifies the amount of space to allocate for the transaction log on the specified log device. The recommended minimum size is 15 MB.


Remote - Use Existing Remote Distribution Server

Installs the distribution database on the remote server that is specified in this box. Expand the box to select a remote server. The remote server must already be created; you cannot add a remote server.


OK

Installs the distribution database as defined. Before you choose OK, verify that distribution database options are set appropriately. Once a distribution database is selected, a significant reconfiguration is required to change to a different distribution database.


Replication - Publishing Dialog Box

Use this dialog box to specify which servers are authorized to subscribe to the publications of the server that is selected in the Server Manager window. You can also specify the replication schedule and whether the local server will be used by remote servers as a distributor.

For more information, choose one of the following:

 Enable Publishing to These Servers

 New Subscriber

 Distribution Options

 Distribution Publishers

 Publishing Databases

 Distribution Configuration

See Also

Distribution Options Dialog Box

New ODBC Subscriber Dialog Box

New Subscriber Dialog Box

Replication - Distribution Dialog Box

Replication Overview


Enable Publishing to These Servers

Specifies which servers can subscribe to the publications of the local server. To grant a server access, select Enable. Only servers that are registered in SQL Enterprise Manager are listed. To register a server, click New Subscriber.


New Subscriber

Displays the New Subscriber dialog box, which you can use to register a subscriber with SQL Enterprise Manager or, displays the New ODBC Subscriber dialog box, which you can use to add an ODBC subscriber.


Distribution Options

Displays the Distribution Options dialog box, which you can use to set the distribution schedule, the transaction batch size, and the number of hours after distribution that transactions will be retained in the distribution database.


Publishing Databases

Specifies which databases will publish data. To specify that a database be published, select Enable.


Distribution Configuration

Displays the name and the working directory of the distribution database. The working directory stores schema scripts and data synchronization files. Providing a path that directly maps to the root of the appropriate hard drive will result in significant performance enhancements during initial synchronization. Provide a path to \\servername\<drive letter>$. If the drive letter cannot be determined, then synchronization will use the network share for writing files on the local distributor. The default is \\servername\C$\MSSQL\REPLDATA, which maps to C:\MSSQL\REPLDATA on the local computer. To change the working directory, type a new UNC path in the Working Directory box.


Distribution Publishers

Displays the Replication - Distribution dialog box, which you can use to specify which remote servers can use the local server as their distributor.


Replication - Distribution Dialog Box

Use this dialog box to designate which servers can use the local server as a distributor.

For more information, choose one of the following:

 Distribution Publishers

 New Server

See Also

Register Server Dialog Box


Distribution Publishers

Lists the servers that can be permitted to use the local server as a distributor. To allow a server to use the local server as a distributor, select Enable.

Only servers that are registered with SQL Enterprise Manager are listed. To register a server, click New Server and complete the Register Server dialog box that appears.


New Server

Displays the Register Server dialog box, which is used to register a server in SQL Enterprise Manager.


Distribution Options Dialog Box

Use this dialog box to set up or change information about a distribution schedule for a selected subscriber.

For more information, choose one of the following:

 Commit Every <x> Transactions to Subscriber

 Distribution Schedule

 Retention Period after Distribution (hours)

 ODBC Options

See Also

New ODBC Subscriber Dialog Box

Task Schedule Dialog Box


Commit Every <x> Transactions to Subscriber

Specifies the number of transactions to send to a subscriber as one unit. Type the maximum number of transactions to send to the subscriber as one number. If the number of transactions that are marked for replication exceeds the number you enter in this box, several units will be sent. Adjusting this number can improve your distribution throughput.


Distribution Schedule

Specifies the distribution schedule for the selected subscriber, which is the interval at which transactions are replicated to the subscriber.

Continuous

Specifies that transactions are distributed continuously.

Scheduled

Specifies that transactions are distributed based on a schedule. To change the schedule, choose Change.

Change

Displays the Task Schedule dialog box, which is used to change the distribution schedule for a subscriber.


Retention Period after Distribution (hours)

Specifies how long transaction information is retained in the distribution database after the information is replicated to the subscriber.


ODBC Options

Specifies login information for ODBC subscribers, if required by the specified ODBC driver.

SQL Server

Specifies that the subscriber is a Microsoft SQL Server. ODBC login information is not required.

Other

Specifies that the subscriber is not a Microsoft SQL Server ODBC subscriber. Login information may be required.

Login Name

Specifies the login name that is used to connect to the specified ODBC subscriber. Enter this information only if required by the ODBC subscriber. The username and the password are used by the distribution server to connect to the ODBC subscriber. In many cases, entering a username or password is not necessary, because they are often entered and stored (depending on the ODBC driver) during the process of registering a system DSN with the ODBC administration application in Control Panel.

Password

Specifies the password for the login name of the specified ODBC subscriber. Enter this information only if required by the ODBC subscriber. The username and the password are used by the distribution server to connect to the ODBC subscriber. In many cases, entering a username or password is not necessary, because they are often entered and stored (depending on the ODBC driver) during the process of registering a system DSN with the ODBC administration application in Control Panel.

Description

Is a read-only description of the selected ODBC subscriber. The description matches the options that were specified in the New ODBC Subscriber dialog box.


New ODBC Subscriber Dialog Box

Use this dialog box to select an ODBC data source name (DSN) to become a subscriber to the server that is selected in the Server Manager window. For more information, choose one of the following:

 Distributor's DSNs

 Description

 User Name

 Password

See Also

About Microsoft Access Subscribers

About ORACLE Subscribers

About Other ODBC Subscribers

Datatype Mappings for ODBC Subscribers

Replication Restrictions for ODBC Subscribers

Using an ODBC Subscriber


Distributor's DSNs

Specifies a DSN to add as a subscriber to the local server. Expand this option to display a list of DSNs that are known to the distribution server. Use the ODBC administration application in the distributor's Control Panel to add a DSN to the list.


Description

Provides a description of the selected DSN.


User Name

Specifies the login name that is used to connect to the selected ODBC subscriber. Enter this information only if required by the ODBC subscriber. The username and the password are used by the distribution server to connect to the ODBC subscriber. In many cases, entering a username or password is not necessary, because they are often entered and stored (depending on the ODBC driver) during the process of registering a system DSN with the ODBC administration application in Control Panel.


Password

Specifies the password that is associated with the selected username. Enter this information only if required by the ODBC subscriber. The username and the password are used by the distribution server to connect to the ODBC subscriber. In many cases, entering a username or password is not necessary, because they are often entered and stored (depending on the ODBC driver) during the process of registering a system DSN with the ODBC administration application in Control Panel.


Replication - Subscribing Dialog Box

Use this dialog box to specify which publishers can replicate data to the local server and which databases on the local server can receive data from the publisher.

For more information, choose one of the following:

 Enable Subscribing From These Servers

 New Server

 Subscribing Databases

See Also

Register Server Dialog Box


Enable Subscribing From These Servers

Specifies which servers can publish data to the local server. To allow the server to publish data, select Enable. Only servers that are registered in SQL Enterprise Manager or included in sysservers are listed. If a server is not listed, click New Server to add the server.


New Server

Displays the Register Server dialog box, which is used to register a server in SQL Enterprise Manager.


Subscribing Databases

Specifies which databases on the local server are permitted to subscribe to publications. To allow the database to subscribe to publications, select Enable.


Manage Publications Dialog Box

Use this dialog box to set up, modify, or remove publications for a server.

For more information, choose one of the following:

 Publications

 New

 Change

 Remove

 More Info

See Also

Creating Publications

Edit Publications Dialog Box

Publication Info Dialog Box

Remove Article Dialog Box

Remove Publication Dialog Box


Publications

Displays a list of current publications and articles for databases on the server. Also displays current subscribers. To display the publications for a database list, click the plus sign (+) next to the database name. A publication with a key on its icon is restricted.


New

Displays the Edit Publications dialog box, which is used to create a publication or article.


Change

Displays the Edit Publications dialog box, which is used to modify the publication or article that is selected in the Publications box.

You cannot modify a publication or article that is subscribed to. Before you modify a publication or an article, you must drop all subscriptions. After you modify a publication or article, re-subscribe the appropriate servers.


Remove

Displays the Remove Publication or Remove Article dialog box, which is used to remove the publication or article that is selected in the Publications box.


More Info

Displays the Subscription Info dialog box, which is used to provide information about the publication, including the publication's title, description, synchronization schedule, replication frequency, and articles.


Subscription Info Dialog Box

Displays information about the subscription, including details about the publication and the subscriber. The information in this box cannot be changed.

For more information, choose one of the following:

 Publication Title

 Description

 Sync Schedule

 Replication Frequency

 Sync Method

 Sync Status

 Source Database

 Source Table

 Article Name

 Destination Database

 Destination Table

 Subscriber Info


Publication Title

Specifies the name of the publication.


Description

Describes the publication.


Sync Schedule

Specifies the schedule used to update the publication at the subscriber.


Replication Frequency

Specifies how often the publication is replicated.


Sync Method

Specifies the method of synchronizing the subscriber's database.

BCP - Character

Specifies that the initial synchronization use the character format BCP method. Character format BCP uses the character (char ) format for all columns, providing tabs between fields in a row and a new line at the end of each row.  Storing information in character file format is useful when the data is used with another application, such as a spreadsheet, or when the data is to be copied into SQL Server from another database.

BCP - Native

Specifies that the initial synchronization use native format BCP. Native format BCP uses the datatypes from the publisher's database. Storing information in native format is useful when information is to be copied from one SQL Server into another SQL Server. Using native format saves time, preventing unnecessary conversion of datatypes into and out of character format.


Sync Status

Specifies the state of the subscriber's data

Synced

Specifies that the initial synchronization has occurred.

Unsynced

Specifies that the database has not initially synchronized.

Inactive

Specifies that the database had subscribed in the past, but is not a current subscribing participant.


Source Database

Specifies the database that the publication is created on.


Source Table

Specifies the table that the publication is based on.


Article Name

Specifies the name of the article belonging to the publication.


Destination Database

Specifies the name of the subscriber's database.


Destination Table

Specifies the name of the subscriber's table that will receive the publication named in the Publication Title box.


Subscriber Info

Specifies whether the type of subscriber is SQL Server or ODBC. Details about the subscriber type are displayed in the text box.


Article/Publication Subscribers Dialog Box

Use this dialog box to enable a server to receive an article or publication, or to remove the subscriber status of a server.

For more information, choose one of the following:

 Subscription Servers

 Subscribe

 Un-Subscribe

See Also

Edit Publications Dialog Box

Subscription Options Dialog Box


Subscription Servers

Displays the servers that are available for subscribing, each server's subscription status, the database the article subscribed to will be placed in, and the type of synchronization event.


Subscribe

Displays the Subscription Options dialog box, which is used to enable the server that is displayed in the Article/Publication Subscribers dialog box to receive the article or publication.


Un-Subscribe

Removes the selected server's subscription for the article or publication. Displays the Unsubscribe From Publication dialog box, which displays a message that asks you to confirm this selection.


Edit Publications Dialog Box

Use this dialog box to create or modify a publication for replication.

For more information, choose one of the following:

 Publication Title

 Description

 Replication Frequency

 Articles Tab

 Synchronization Tab

 Security Tab

 Add

 Modify

 Subscribers

See Also

Manage Article Dialog Box

Security Tab

Synchronization Tab


Publication Title

Specifies the name of the publication. The name must be unique for the database it is to be placed in.


Description

Describes the publication. The description can have as many as 255 characters.


Replication Frequency

Specifies the method to use to replicate data.

Transaction Based

Specifies that each transaction that is marked for replication will be read from the transaction log of the source database and applied to the destination databases.

Scheduled Table Refresh

Specifies that at scheduled intervals all articles in the publication will be refreshed. Each time a refresh occurs, all table data (and optionally, table schemas) will be applied to all destination tables. Data is not changed between scheduled refresh intervals. Transaction-based replication does not occur.


Articles Tab

Specifies which database tables will be published as articles in the publication. To publish a table, in the Database Tables box select the table and click Add, or double-click the table name to move the table to the Articles in Publication box.

Edit

Displays the Manage Article dialog box, which is used to customize data to be included in an article. For each article, you can set the article name, the article description, and the destination name; exclude rows and columns from published articles (horizontal and vertical partitioning); and customize the synchronization schema script and the data replication mechanism.


Synchronization Tab

Specifies the method for initially synchronizing the selected publication to a destination database, and a schedule for subsequent synchronization.

Initial synchronization determines the method by which output data files are created for automatically or manually synchronizing the destination database. The method can be bcp, native format (the default), or bcp, character format.

The schedule determines how frequently new subscriptions will be automatically synchronized. Because automatically synchronizing databases or tables requires an appreciable amount of system overhead, by scheduling automatic synchronization you can set an interval between the time a server subscribes to a publication and the time a server is synchronized to that publication. Scheduling allows synchronization to occur during low activity periods on the publication and subscription servers.


Security Tab

Specifies that the publication is unrestricted or restricted. Subscribers can see and subscribe to publications that are marked unrestricted. Publications that are marked restricted are visible only to subscribers with access permissions to those publications.


Add

Creates the publication as defined.


Modify

Modifies the publication as specified.


Subscribers

Adds or removes subscribers for the publication. The Subscribers button is available only when an existing publication is being edited.


Synchronization Tab

Use this tab to specify the synchronization method and the schedule for replication.

For more information, choose one of the following:

 Method

 Schedule

 Change

See Also

Replication to ODBC Subscribers

Task Schedule Dialog Box


Method

Indicates the method by which the destination database will be synchronized.

Bulk Data Copy - Native Format

Specifies to use the native format of bcp to transfer the data for synchronization. The bcp native format is the default synchronization method for replicating data.

Bulk Data Copy - Character Format

Specifies to use the character format of bcp to transfer the data for synchronization. Use this option when replicating to ODBC subscribers.


Schedule

Specifies how frequently new subscriptions will be synchronized. Because synchronizing individual tables requires a fairly high amount of system overhead, by scheduling synchronization SQL Server allows an interval between the time a server subscribes to a publication and the time a server is synchronized to that publication. Scheduling allows synchronization to occur during low activity periods on the publication and subscription servers. To change the schedule, click Change.


Change

Displays the Task Schedule dialog box, which is used to change the schedule for automatic synchronization.


Security Tab

Use this tab to restrict replication to selected servers.

For more information, choose one of the following:

 Unrestricted

 Restricted To


Unrestricted

Specifies that the publication can be seen and subscribed to by any subscriber.


Restricted To

Specifies that the publication is visible only to subscribers that have been granted access. To grant a server access, select the Allow Access check box next to the server name.


Manage Article Dialog Box

Use this dialog box to specify information for an article. For each article, you can set the article name, description, and destination table name; exclude rows and columns from published articles (horizontal and vertical partitioning); and customize the synchronization schema script and the data replication mechanism. Note that you cannot modify an article that has subscribers.

For more information, choose one of the following:

 Name

 Description

 Destination Table

 Owner-Qualify Table Name

 Use Column Names in SQL Statements

 Filters Tab

 Scripts Tab

 Subscribers

 Advanced

See Also

Article Subscribers Dialog Box

Edit Publications Dialog Box

Manage Article - Advanced Dialog Box

Scripts Tab


Name

Displays the default name of the article that is selected in the Edit Publications dialog box. To change the default name, type a new name. Names must be unique to each publication.


Description

Describes the article. The description can be up to 255 characters.


Destination Table

Specifies the table to which data should be replicated. The name of the destination table defaults to the name of the publication table.


Owner-Qualify Table Name

Specifies that the ownership of a table will remain the same after the table is replicated. Users can maintain table ownership in different databases and servers.


Use Column Names in SQL Statements

Specifies that replication INSERT statements that contain columns that do not match the order of the subscribing table can execute successfully. This is achieved by replication INSERT statements including a column list.


Filters Tab

Specifies a filter for the data that is replicated.

Replicated Columns

Specifies that the article be partitioned vertically, that is, only selected columns are replicated. To specify a column for replication, select the Replicate check box for that column. Clear the Replicate check box for each column that will not be replicated. Columns that contain a primary key (indicated with a key icon) must be replicated.

Restriction Clause

Specifies that the article be partitioned horizontally, that is, only selected rows are replicated. Type a valid WHERE clause in the Restriction Clause box. For example, if the table you are replicating data from contains information for all states, but you want to publish information for California only, type state = 'CA'.


Scripts Tab

Specifies the data replication mechanism and the synchronization schema script that are used to insert data into the destination table.


Subscribers

Displays the Article Subscribers dialog box, which is used to specify subscribers for the article. The Subscribers button is available only when an existing article is being edited.


Advanced

Displays the Manage Article - Advanced dialog box, which is used to specify custom filtering.


Scripts Tab

Use this tab to customize the data replication mechanism or the synchronization schema script.

For more information, choose one of the following:

 Data Replication Mechanism

 Initial Table Synchronization Script

 Edit

 Generate

See Also

Auto-Generate Sync Scripts Dialog Box

Edit Publications Dialog Box

Manage Article - Creation Script Dialog Box


Data Replication Mechanism

Specifies the action SQL Server takes when the log reader process encounters INSERT, UPDATE, or DELETE transactions that are marked for replication in the transaction log of the publication database.

To use the default, do not change the selected options for the commands. When the log reader process encounters an INSERT, UPDATE, or DELETE transaction that is marked for replication in the transaction log of the publication database, the SQL statement will be reconstructed and applied to the destination database.

To specify custom processing for one or more of the command types, select the Custom option and enter one of the two possible custom commands, NONE or CALL stored_procedure_name, in the Custom box. If you enter NONE, transactions of the selected command type will not be replicated. If you enter CALL stored_procedure_name, when the transaction log reader encounters the selected command in a transaction that is marked for replication, it will pass column parameters from that transaction to the referenced stored procedure. The referenced stored procedure must exist in the destination database of each subscriber.


Initial Table Synchronization Script

Specifies the schema script for the initial table synchronization. When you define a new article, the Creation Script box is blank. Schema scripts are automatically generated when a publication is created. When editing an existing article, the box contains the full path to the schema script in the distribution working directory.


Edit

Displays the Manage Article - Creation Script dialog box, which is used to view and/or edit an existing schema creation script.


Generate

Displays the Auto-Generate Sync Scripts dialog box, which is used to generate a schema script immediately.


Manage Article - Creation Script Dialog Box

Use this dialog box to edit the creation script that is used to synchronize a table for use with replication.

Creation Script

Specifies the path and the contents of the creation script. To change the script, edit the appropriate information in the box.


Auto-Generate Sync Scripts Dialog Box

Use this dialog box to generate a schema script immediately.

For more information, choose one of the following:

 If Existing Table Detected in Subscriber

 Transfer Clustered Index

 Transfer non-Clustered Index

 Convert UDDT to Base Datatype

 Include DRI - PK

 Auto-Generate


If Existing Table Detected in Subscriber

Specifies how to handle an existing table of the same name in a subscribing database before applying synchronization.

Do Nothing

Specifies that rows will not be dropped, truncated, or deleted from the destination table before synchronization is applied.

DROP Table First

Specifies that the existing table be dropped before synchronization is applied.

Truncate Table Only

Specifies that rows of the table be deleted before synchronization is applied, but leaves the table structure in place.

DELETE DATA Using Restriction Clause

Specifies that only the rows be removed that match the restriction clause that is defined in the Filters tab. For example, if the replicated data is restricted to rows that contain the state "CA", then rows where state is "CA" will be deleted.


Transfer Clustered Index

Creates a clustered index in the destination table that is identical to that for the published table.


Transfer non-Clustered Index

Creates nonclustered indexes in the destination table that are identical to those for the published table.


Convert UDDT to Base Datatype

Converts user-defined datatypes (UDDTs) from the published table to base system datatypes in the destination table.


Include DRI - PK

Copies the declared primary key (PK) to the destination table.


Auto-Generate

Creates the schema script for the initial table synchronization.


Manage Article - Advanced Dialog Box

Use this dialog box to specify a filter stored procedure and a synchronization object.

For more information, choose one of the following:

 Filter Stored Procedure

 Synchronization Object

See Also

Edit Publications Dialog Box


Filter Stored Procedure

Specifies a stored procedure that was previously created in the publication database to use as a user-defined filter.


Synchronization Object

Specifies a database object to be used as the source of the schema and the data for the initial synchronization of the destination table. By default, the synchronization object is the article's base table. If the article has been horizontally and/or vertically partitioned, SQL Server automatically creates a view of the partitioned table, which becomes the synchronization object. Generally, the synchronization object is specified automatically and changing the default is not necessary.


Subscription Options Dialog Box

Use this dialog box to specify options for a subscription.

For more information, choose one of the following:

 Destination Database

 Sync Method


Destination Database

Specifies a database for the subscriber in which to place replicated tables. The database must already exist; SQL Enterprise Manager will not create it. By default, the publication database name is assigned to the destination database.


Sync Method

Specifies whether the initial synchronization of table schema and data will be automatic (by SQL Enterprise Manager) or manual (by a user).

Data Synchronization Automatically Applied

Specifies that SQL Server replication will automatically synchronize for the selected subscriber following the distribution schedule that is set on the publisher.

Data Synchronization Manually Applied by Operator

Specifies that a user will manually synchronize replication outside of the administrative interface for replication. The user must obtain schema and data files from the distributor, manually synchronize the tables, and then inform SQL Server that the synchronization is complete.

If you choose to manually synchronize for a subscription, you must manually synchronize the published tables on the publisher with the destination tables in the destination database before replication can begin for that subscription. The synchronization file will be automatically created as part of the synchronization event, but the file will not be distributed to the subscriber.

Selecting manual synchronization can affect replicated data that is being sent to a destination database. When synchronization becomes the next task in the distribution database queue, replication to the entire subscription database is paused until the manual synchronization is completed and SQL Server is informed that the synchronization is complete.

No Data Synchronization

Specifies that SQL Server will immediately begin sending modifications to published data to the destination database. SQL Server assumes that the publication and destination tables are already synchronized. The No Data Synchronization option is for advanced users who will be implementing a custom replication.


Remove Publication Dialog Box

Use this dialog box to confirm the removal of a publication. This box lists articles in the publication.

Yes

Removes the publication.

No

Closes the dialog box without removing the publication.


Remove Article Dialog Box

Use this dialog box to confirm the removal of a published article. This box lists subscribers to the article.

Yes

Removes the article from a publication.

No

Closes the dialog box without removing the article.


Unpublish Dialog Box

Use this dialog box to confirm that publishing is to be disabled for a selected database.

For more information, choose one of the following:

 Publications

 Yes

 No


Publications

Lists the publications and articles that are being published for the selected database.


Yes

Disables publishing for the selected database.


No

Closes the dialog box without disabling publishing for the selected database.


Publication Info Dialog Box

Use this dialog box to view information about a selected publication. You cannot change information that is displayed in this dialog box.

For more information, choose one of the following:

 Publication Title

 Description

 Sync Schedule

 Replication Frequency

 Sync Method

 Articles


Publication Title

Specifies the title of the publication.


Description

Describes the publication, as specified when the publication was created.


Sync Schedule

Specifies the schedule of synchronization events.


Replication Frequency

Specifies the replication frequency of either continuous or snapshot.


Sync Method

Specifies the synchronization method to be used to initially set up the subscriber with data from the publisher.


Articles

Displays a list of articles within the publication.

Table

Specifies the table from which the article is built.

Article Title

Specifies the name of the article.

Destination Table

Specifies the table to receive the article(s).


Manage Subscriptions Dialog Box

Use this dialog box to subscribe servers to publications, to unsubscribe servers from publications, and to indicate that a manual synchronization event has occurred.

For more information, choose one of the following:

 Publications

 Subscribe

 Un-Subscribe

 Sync Completed

 More Info

See Also

Publication Info Dialog Box

Subscription Options Dialog Box


Publications

Displays a list of publishers, and publications and articles that are available for publication. To expand the list, click the plus sign (+) next to a list item.


Subscribe

Displays the Subscription Options dialog box, which is used to subscribe the server to the selected publication or article.


Un-Subscribe

Removes a subscription to the selected article or publication. Displays the Un-Subscribe - Publication Article dialog box, which asks you to confirm the removal.


Sync Completed

Indicates that you have manually synchronized the selected article or publication. Replication can then resume.

This button is only enabled when the distribution process is waiting for the manual synchronization job within the distribution database that corresponds to the selected publication or article.


More Info

Displays the Publication Info dialog box, which provides information about a selected publication or article.


Un-Subscribe - Publication Article Dialog Box

Use this dialog box to confirm that you want to un-subscribe from an article.

Yes

Un-subscribes the server from the article.

No

Closes the dialog box without un-subscribing the server from the article.


Remove Subscribers Dialog Box

Use this dialog box to confirm the removal of subscriptions from a publisher. You must remove subscriptions from a publisher before you can remove that publisher.

Yes

Removes the specified subscriptions.

No

Closes the dialog box without removing subscriptions.

See Also

Replication Topology Window


Replication Overview

Replication is the process of duplicating table schema and data from a source database to a destination database. With replication, you can automatically distribute copies of transactional data from a single source server to one or more destination servers at one or more remote locations. SQL Server 6.x replication is transaction-log based: transactions that are marked for replication are read from the transaction log of the source database and applied to the destination databases.

Replication uses terminology that is based on a publishing/subscribing metaphor. Replication employs servers in three different roles: publisher, distributor, and subscriber. Replication uses a dedicated SQL Server database as a reliable queue for replicated data. Replication offers flexibility in selecting data to be replicated to each destination database. And, it enhances security by limiting which users can set up and administer replication, and which destination servers can view and receive tables that are available for replication.

Replicated data moves in one direction--from the publisher to the subscriber. The log reader process moves transactions that are marked for replication from the publisher transaction log into the distribution database, where the transactions wait for distribution to subscribers. The synchronization process prepares initial synchronization files that contain published table schema and data, stores the files in the SQL Server working directory on the distributor, and records synchronization jobs in the distribution database. Synchronization affects new subscribers only.

The distribution process moves the transactions and initial synchronization jobs that are held in the distribution database tables to the subscribers.

For a detailed overview of the replication process, see the Microsoft SQL Server Administrator's Companion.

For more information on replication for SQL Server 6.5, see "What's New for Administrators" in books online.

See Also

About Microsoft Access Subscribers

About ORACLE Subscribers

About Other ODBC Subscribers

Replication - Subscribing Dialog Box

Setting Up Pull Subscriptions

Setting Up Push Subscriptions

text and image Datatype Replication

Uninstalling Replication

Using an ODBC Subscriber


Uninstalling Replication

Uninstalling replication will cause the distribution database to be dropped and all publications to be eliminated. After selecting this option, the current session will be disconnected from SQL Server.


Setting Up DBOs to Manage Publications and Subscriptions

When you set up publishers, distributors, and subscribers for replication, permissions are automatically set that allow the SAs to manage publications and subscriptions. However, before the DBOs of the publication and subscription databases can manage publications or subscriptions, permissions must be set.

Permissions are set by creating necessary SQL Server login IDs, database users, and remote login mappings. Permissions are set separately for the DBOs of publication and subscription databases. For the DBO of a publication database, permissions are set one of two ways depending on whether that publisher uses a remote distributor or acts as its own combined publisher/distributor.

For more information, choose one of the following:

 A DBO on a Combined Publisher/Distributor

 A DBO on a Publisher That Uses a Remote Distributor

 A DBO on a Subscriber

 Manage Logins Dialog Box


A DBO on a Combined Publisher/Distributor

When a publisher is configured as a combined publisher/distributor, to allow the DBO of a publication database to manage publications, you must add a database user to the publisher's msdb and distribution databases that specifies the login ID of the user who is the DBO of the publication database.

If several users of the publication database are aliased to the DBO, you must repeat the process for each aliased user. All users can be aliased to one user in the msdb database and to one user in the distribution database.


A DBO on a Publisher That Uses a Remote Distributor

When a publisher is configured to use a remote distributor, the DBO of a publication database must be granted permission to manage publications.

To allow the DBO of a publication database to manage publications through a remote distributor

1.	On the remote distributor from the Manage menu, choose Logins.

The Manage Logins dialog box appears.

2.	Add a login ID for the user who is the DBO of the publication database. If the user has a login ID on the remote distributor already, skip this step.

3.	To the msdb database, add a database username for the login ID that was added in step 2.

4.	To the distribution database, add a database username for the login ID that was added in step 2.

5.	Use sp_addremotelogin to map the login ID from the publisher to the login ID on the remote distributor.


A DBO on a Subscriber

To allow the DBO of a destination database to manage subscriptions, you must map the login ID of the DBO on the subscriber to the repl_subscriber login ID on the publisher. To map the login IDs, from the Server menu choose Remote Servers. In the Manage Remote Servers dialog box, map the login IDs under Remote Logins. To use integrated security, the Trusted check box must be selected.

Repeat this step for each publication server that the destination database will subscribe from. If several users in that destination database are aliased to DBO, repeat the step for each aliased user.


Setting Up the Replication Distribution Database

If a server will participate in replication as a publisher, before any other replication options are set, you must define the distribution database information. You can set up replication distribution so that the publisher will act as its own distributor or will use a remote distributor. If the publisher will use a remote distributor, the remote distributor must be set up first.

The distribution database options must be set appropriately. Once a distribution database is selected, significant reconfiguration is required to change to a different distribution database.

To set up the replication distribution database

1.	In the Server Manager window, select the server to set up the distribution database for.

2.	From the Server menu, choose Replication Configuration/Install Publishing.

The Install Replication Publishing dialog box appears.

3.	To configure the server to be its own distributor or to act as a remote distributor for other publishers, select Local, type the name of the distribution database, and then select the devices to place the database and its log on.

Replicating published data requires extensive use of the distribution database. A minimum of 30 megabytes (MB) for the database and 15 MB for the log is recommended for initial implementation.

4.	To configure the server to use a remote distribution server, select Remote and then select the remote server from the server list. Selecting the remote option requires that the remote distribution server already has a distribution database installed.

5.	Click OK.

After the distribution database is installed, you are prompted to add publishing databases and subscribers. If you choose Yes, the Replication - Publishing dialog box appears to enable publishing. If you choose No, you must set up publishing to enable replication. You can set up publishing at any time by selecting Replication Configuration/Publishing from the Server menu.

See Also

Replication Overview


Setting Replication Publishing Information

You can specify the servers that are authorized to subscribe to the local server's publications, the replication schedule, databases that are authorized to publish data, and the directory to be used as the distribution working directory. You can also configure the local server to act as a remote distributor for other publishers.

To set replication publishing information

1.	In the Server Manager window, select the server to set publishing information for.

2.	From the Server menu, choose Replication Configuration/Publishing.

The Replication - Publishing dialog box appears.

3.	Complete the dialog box and click OK to set the selected options.

See Also

About Microsoft Access Subscribers

About ORACLE Subscribers

About Other ODBC Subscribers

Datatype Mappings for ODBC Subscribers

Replication Restrictions for ODBC Subscribers

Using an ODBC Subscriber


Using an ODBC Subscriber

You can publish to the following ODBC subscribers that are not SQL Servers: Microsoft Access, ORACLE, and subscribers that meet the replication restrictions for ODBC subscribers.

SQL Server 6.5 provides the following stored procedures and extended stored procedures to support replication to ODBC subscribers:

sp_enumdsn

Reports all defined ODBC DSNs in the same user context as the server. If the server is running in its default system account, only system DSNs will be reported. A server can be run in a Windows NT account; if the sp_enumdsn stored procedure is called, all DSNs for the system account are returned. When running as a service under a private user's Windows NT account, only those DSNs that are defined under the user's account are returned.

sp_dsninfo

Retrieves ODBC DSN information from the replication distributor that is associated with the current server if replication is installed.

For more information about these replication stored procedures, see "What's New for TransactSQL" in SQL Server Books Online.

ODBC subscriptions must be set up by administering the publisher (using the push subscription model). You cannot set up ODBC subscriptions by administering a subscriber (the pull subscription model). For subscribers other than SQL Server ODBC subscribers, the subscribing database has no administrative capabilities for the replication being performed.

Also, while administering a publication that will be replicated to ODBC subscribers, verify that the Bulk Data Copy - Character Format option is selected in the Synchronization tab of the Edit Publications dialog box.

Note that replication creates tables on the ODBC subscribers using quoted identifiers (for example, "authors" rather than authors).

To publish to a subscriber other than a SQL Server ODBC subscriber

1.	From Control Panel, run the ODBC administration application and add the subscribers data source name (DSN) as a system DSN.

For more information about adding system DSNs, see the online Help for the ODBC administration application.

2.	Using SQL Enterprise Manager, configure the new system DSN as a subscribing server to the selected publisher. From the server menu, select Replication Configuration/Publishing.

The Replication - Publishing dialog box appears.

3.	Click the New Subscriber button.

The New Subscriber dialog box appears.

4.	Click the ODBC Subscriber button and complete the New ODBC Subscriber dialog box that appears.

5.	From the Manage menu, choose Replication/Publications.

The Manage Publications dialog box appears.

6.	Click the New or Change button to create or edit a publication.

The Edit Publications dialog box appears.

7.	Click the Subscribers button and complete the Publication or Article Subscribers dialog box that appears.

See Also

About Microsoft Access Subscribers

About ORACLE Subscribers

About Other ODBC Subscribers

Datatype Mappings for ODBC Subscribers

Replication Restrictions for ODBC Subscribers


About Microsoft Access Subscribers

SQL Server 6.5 includes an ODBC driver that supports Microsoft Access subscriptions to SQL Server replication. The driver is only supported for Intel-based computers. To install the driver, run SETUP.EXE from the \MSSQL\BINN directory on the SQL Server CD-ROM drive.

Note that when registering a Microsoft Access DSN on a remote server, you must supply a UNC path (not a redirected drive letter).

Replication Restrictions for Microsoft Access

SQL Server datetime, numeric, decimal, and many other datatypes are mapped to char. Numeric and decimal datatypes that are converted to char cause some precision loss.

Some character datatypes in SQL Server are not supported in Microsoft Access.

See Also

Replication to ODBC Subscribers

Replication Restrictions for ODBC Subscribers


About ORACLE Subscribers

SQL Server 6.5 includes an ODBC driver that supports ORACLE subscriptions to SQL Server replication. The driver is redistributed by Microsoft from Visigenic®. The driver is only supported for Intel-based computers. To install the driver, run SETUP.EXE from the \MSSQL\BINN directory on the SQL Server CD-ROM drive.

Note that to replicate to ODBC subscribers, you must also obtain the ORACLE SQL*Net driver from your vendor.

When using the ODBC administration application in Control Panel to register an ORACLE data source name (DSN), you must enter a username. The username is stored by the system and is used by the distributor to connect to the ODBC subscriber.

The ODBC driver for ORACLE also creates a password key in the Registry. You can edit the Registry to provide a value for the password. If the Registry password key is edited, the ORACLE ODBC driver will connect to ORACLE without requesting a password. If the Registry key is not edited, while setting up subscriptions for ORACLE you must enter a username and a password for the ODBC DSN when specifying the DSN in the New ODBC Subscriber dialog box of SQL Enterprise Manager.

The Registry key for the ODBC driver password is:

HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\ORACLE\PWD:REG_SZ:password

If a password is provided in the Registry, then the ORACLE ODBC driver will connect to ORACLE without requesting a password.

If a password is not provided in the Registry, then when setting up subscriptions for ORACLE, you must enter a username and a password for the ODBC data source when specifying the DSN in the New ODBC Subscriber dialog box of SQL Enterprise Manager.

Note that the ODBC driver for ORACLE that is provided with SQL Server 6.5 is not double-byte character set (DBCS) enabled.

Replication Restrictions for ORACLE Subscribers

Following are known restrictions when replicating to an ORACLE ODBC subscriber:

The date datatype is a small datetime (the range is 4712 b.c. to 4712 a.d.). If you are replicating to an ORACLE subscriber, verify that the SQL Server datetime entries in a replicated column are within the range.

Only one text or image column can exist per replicated table.

The datetime datatype is mapped to CHAR 4.

The SQL Server ranges for float and real datatypes are different than the ranges of ORACLE.

See Also

Datatype Mappings for ODBC Subscribers

Replication Restrictions for ODBC Subscribers


About Other ODBC Subscribers

To replicate to ODBC subscriber types other than SQL Server, drivers for other ODBC subscriber types must conform to the following SQL Server replication requirements:

The ODBC driver must be ODBC Level 1 compliant.

The ODBC driver must be 32-bit, thread-safe, and for the processor architecture (Intel, PPC, MIPS, Alpha) that the distribution process runs on.

The ODBC driver cannot be read-only.

The ODBC driver must be transaction capable.

The ODBC driver must support DDL.

See Also

Replication to ODBC Subscribers

Replication Restrictions for ODBC Subscribers


Replication Restrictions for ODBC Subscribers

The following known restrictions apply to replication processes for all ODBC subscriber types:

Batched statements to ODBC subcribers are not supported. (The distribution task -c option is ignored.)

The ODBC data source name (DSN) must conform to SQL Server naming conventions (because it is stored in the sysservers table).

If the ODBC DSN is not a SQL Server DSN, the publication option to truncate before synchronization is not supported. ODBC subscribers will not be allowed to subscribe to publications that have this option selected.

The target source's quoted identifier character (as reported by the ODBC driver) is used.

The Character Format bulk copy method must be selected for synchronization (in the Edit Publications dialog box). ODBC subscribers cannot subscribe to publications that have selected the Native Format bulk copy method for synchronization.


Datatype Mappings for ODBC Subscribers

When replicating to ODBC subscribers, the distribution task maps SQL Server datatypes to the closest datatype on the target database. The following table lists the datatype mappings for replication to Microsoft Access subscribers.

Microsoft SQL Server Datatype	Maps to Microsoft Jet Datatype
bit	BIT
tinyint	BYTE
image	LONGBINARY
varbinary	VARBINARY
binary	BINARY
timestamp	BINARY
text	LONGTEXT
char	CHAR
numeric	CHAR
decimal	CHAR
money	CHAR
smallmoney	DOUBLE
int	LONG
smallint	SHORT
float	DOUBLE
real	SINGLE
datetime	CHAR
smalldatetime	DATETIME
varchar	VARCHAR2
The following table lists the datatype mappings for replication to ORACLE subscribers.

Microsoft SQL Server Datatype	Maps to ORACLE Datatype
bit	NUMBER
tinyint	NUMBER
image	LONG RAW
varbinary	RAW
binary	RAW
timestamp	RAW
text	LONG
char	CHAR
numeric	NUMBER
decimal	NUMBER
money	NUMBER
smallmoney	NUMBER
int	NUMBER
smallint	NUMBER
float	FLOAT
real	FLOAT
datetime	CHAR
smalldatetime	DATE
varchar	CHAR


Replication Topology Window

Use this window to view the replication relationships of the server that is selected in the Server Manager window. Each subscriber type is indicated by an icon that is specific to the subscriber type (SQL Server, Microsoft Access, ODBC, and so on). You can also use this window to perform replication tasks for the servers that appear in this window.

To manage replication for a publisher or a subscriber, click the right mouse button on the publisher or the subscriber's icon, and from the shortcut menu, select a command.

To add or remove subscribers, refresh the relationships that are displayed in the window, and adjust the size of the information that is displayed, choose one of the following:

 New Subscriber

 Remove Subscriber

 Refresh

 Zoom In

 Zoom Out

See Also

New Subscriber Dialog Box

Setting Up the Replication Distribution Database

Setting Replication Publishing Information

Viewing Replication Topology


Zoom In

Enlarges the relationship diagram that is displayed in the window.


Zoom Out

Shrinks the relationship diagram that is displayed in the window.


Refresh

Updates the view with current information.


New Subscriber

Opens the New Subscriber dialog box, from which you can add a SQL Server subscriber or another type of ODBC subscriber.

You can also add a subscriber by selecting a server from the Server Manager window and dragging it into the Replication Topology window.


Remove Subscriber

Displays the Remove Subscribers dialog box, which confirms removing the subscriber configuration of the server selected in the window.


Setting Subscriber Information

You can set information for a subscriber by specifying which publishers can replicate to the local server and which destination databases on the local server can receive publications.

To set subscriber information

1.	In the Server Manager window, select the server to set subscribing information for.

2.	From the Server menu, choose Replication Configuration/Subscribing.

The Replication - Subscribing dialog box appears.

3.	Complete the dialog box and click OK to set the selected options.

See Also

Replication Overview


Viewing Replication Topology

You can view the replication relationships of a server, add subscribers, and set other replication information.

To view replication relationships

1.	In the Server Manager window, select the server to view replication information for.

2.	From the toolbar, choose the Replication Topology icon. Or, from the Server menu, choose Replication Configuration/Topology.

The Replication Topology window appears.

See Also

Replication Overview


Creating Publications

You can create one or more publications for a database, but each publication can contain data from only one database. Before you create publications, you must set options for the server that will be publishing information.

To create a publication

1.	In the Server Manager window, select the server to create a publication for.

2.	From the Manage menu, choose Replication Configuration/Publications.

The Manage Publications dialog box appears.

3.	Under Publications, select a database to create a publication for and then click New.

The Edit Publications dialog box appears.

4.	Complete the dialog box and click Add to set the specified options.

The Manage Publications dialog box reappears. The new publication and its articles are listed under the published database.

5.	When you are finished creating publications, click Close.

See Also

Replication Overview


Setting Up Push Subscriptions

A push subscription is performed from the publisher by pushing out a publication or an article to one or more subscribers. A push subscription simplifies and centralizes subscriber administration by setting up many subscribers for an article at one time. However, a push subscription is only possible after a user with privileges on the subscriber has enabled the user's publisher (in the Replication - Subscribing dialog box).

Before a server can subscribe to publications or articles, destination databases must be created on the subscriber and authorized to subscribe to a publication.

To set up a push subscription

1.	In the Server Manager window, select the publisher.

2.	From the Manage menu, choose Replication/Publications.

The Manage Publications dialog box appears.

3.	Under Publications, select the publication to add subscribers to and then click Change.

The Edit Publications dialog box appears.

4.	To perform a push subscription for the selected publication, click the Subscribers button.

To perform a push subscription for an article, select an article from the Articles in Publication box, click Edit, and then click Subscribers.

The Article Subscribers dialog box appears.

5.	Under Subscription Servers, select a server and then click Subscribe.

The Subscription Options dialog box appears.

6.	Select a destination database and the synchronization method, and click OK.

See Also

Replication Overview

Setting Up Pull Subscriptions


Setting Up Pull Subscriptions

A pull subscription is performed from the subscriber. One or more publications are pulled from publishers to the subscriber. The SA or DBO for the subscriber decides which publications will be received.

With a pull subscription, the process of publishing is separate from the process of subscribing, and the user who administers the subscriber need not be the same user who administers the publisher.

Before a server can subscribe to publications or articles, destination databases must be created on the subscriber and designated to receive publications.

To set up a pull subscription

1.	In the Server Manager window, select the subscriber.

2.	From the Manage menu, choose Replication/Subscriptions.

The Manage Subscriptions dialog box appears.

3.	Under Publications, click the + next to the server with the publications or articles to subscribe to.

A list of databases that contain publications appears.

4.	Click the + next to the database that holds the publications or articles.

A list of the database's publications appears.

5.	To subscribe to a publication, select the publication or article and then click Subscribe.

The Subscription Options dialog box appears.

6.	Select a destination database and a synchronization method, and then click OK.

See Also

Replication Overview

Setting Up Push Subscriptions


Manually Synchronizing Database Tables for Replication

Before a subscriber can receive replicated transactions from an article or a publication, the publication and destination tables must contain schema and data. This process is called synchronization. When setting up subscriptions, if you choose automatic synchronization, synchronization occurs automatically and without special action. If you choose manual synchronization, before replication can begin for the selected subscriber, you must manually synchronize the destination tables on the subscriber with the published tables.

Note that when a destination database is waiting for manual synchronization to occur, it cannot receive any updates to any other publications it is subscribed to.

To manually synchronize the data, you can use the synchronization files SQL Server automatically creates. Apply the .SCH and .TMP extensions to create the destination table and then populate the table with data. Inform SQL Server that the manual synchronization is complete.

To acknowledge that a manual synchronization is completed

1.	In the Server Manager window, select the subscriber.

2.	From the Manage menu, choose Replication/Subscriptions.

The Manage Subscriptions dialog box appears.

3.	Under Publications, select the publisher and then choose the appropriate database, publication, and/or article.

The Sync Completed button will be enabled when the distribution process encounters the manual synchronization task within the distribution database.

4.	Click Sync Completed.

A confirmation dialog box appears.

5.	Click Yes. SQL Server has been informed that the subscriber's destination database is synchronized with the publication or article(s). The replication processes can now send replication transactions (changes to data in the synchronized articles) to the destination database.

See Also

Replication Overview


Stopping Replication from a Publisher

You can remove a publication to cancel replication of that publication's tables, or you can remove an article from a publication to cancel replication of that article. However, you cannot remove a publication or an article that has an existing subscriber. Before you can remove a publication or an article, you must drop all subscribers. While managing publications on the publication server, you can un-subscribe one or more subscribers from a publication or article by using the Edit Publications dialog box.

To remove a publication

1.	In the Server Manager window, select the publication server.

2.	From the Manage menu, choose Replication/Publications.

The Manage Publications dialog box appears.

3.	Click the + next to the database to remove a publication from.

A list of that database's publications appears.

4.	Select a publication and then choose Remove.

See Also

Replication Overview


Stopping Replication from a Subscriber

You can un-subscribe from selected publications or articles. You can also remove permission for a publisher to send publications to a subscriber.

To stop replication from a subscriber

1.	In the Server Manager window, select the subscriber.

2.	From the Manage menu, choose Replication/Subscriptions.

The Manage Subscriptions dialog box appears.

3.	Under Publications, select the server and the database that contain the publication to cancel subscription to.

4.	Select the publication or article name, and then click Un-Subscribe.

The Un-Subscribe - Publication Article dialog box appears.

5.	Click Yes.

To remove permissions that allow a publisher to send publications to the subscriber

1.	In the Server Manager window, select the subscriber.

2.	From the Server menu, choose Replication Configuration/Subscribing.

The Replication - Subscribing dialog box appears.

3.	To remove permissions for a server(s), under Enable Subscribing From These Servers, clear the Enable check box for that server(s).

Removing permissions does not stop transactions from being placed in the distribution database for the selected server. To stop transactions, first un-subscribe from the publication. This action should only be taken as an emergency measure to stop unwanted data from being replicated to a subscriber.

4.	Click OK.

See Also

Replication Overview


Restore From Device On Server Dialog Box

Use this dialog box to restore from a selected backup device(s) to a selected database(s). For more information, choose one of the following:

 Destination Database

 Devices and Files

 Single Table

 Until Time

 Backup Information

 Restore Now

 Add File

 Add Device

See Also

New Backup Device Dialog Box


Destination Database

Displays a list of the selected server's databases. Select the database you will restore to.

Note that if you are restoring the msdb database, you must first stop the SQL Executive service.


Devices and Files

Displays backup devices for the selected server.


Backup Information

Specifies restore, backup type, database, table, start and finish, size, and current and new sequence information for a backup.

A database backup restores the entire database. A transaction log backup restores the transaction log information, re-executes the changes it contains, and rolls back any transactions that were uncommitted when the transaction log was backed up. A table backup restores that table.


Add File

Opens the Add Backup Disk File dialog box, which you can use to add a backup disk file. Type a logical name in the Name box. Modify the entry in the Location box, if necessary, to change the placement of the file. The Locate button is available to help you find the directory you prefer.


Add Device

Opens the New Backup Device dialog box, in which to specify a device to restore from.


Single Table

Specifies to restore only one table from a full database backup. Select the database backup from the Backup Information list, select the Single Table option, and then select a table from the Single Table list.


Until Time

Specifies to restore a transaction log through a specific point in time. Select a transaction log backup from the Backup Information list, then select the Until Time option and adjust the displayed date and time appropriately. Any transactions committed after that time will be rolled back.

Point-in-time recovery applies to transaction log restores only (not to full database restores).


Restore Now

Performs the restore immediately.


Backup Tab for Databases, Transaction Logs, and Tables

Use this tab to back up databases, tables, or transaction logs for the server that is selected in the Server Manager window.

Note that the Database Backup/Restore dialog box is available for SQL Server 6.0 and later.

For more information, choose one of the following:

 Database Backup

 Initialize Device

 Eject Tape at End of Backup

 Skip Tape Header

 Backup Devices

 New

 Delete

 Info

 Backup Now

 Schedule

See Also

Backing Up a Database, Transaction Log, or Table

Backup Device Information Dialog Box

New/Delete Backup Device Dialog Box

Table Backup and Restore


Database Backup

Specifies the database to back up.

Entire Database

Backs up the entire database.

Transaction Log

Backs up the transaction log. To use this option, the transaction log must be on a separate device from the database and the database must have the Truncate Log on Checkpoint option enabled. (To enable the Truncate Log on Checkpoint option, in the Manage Databases window, click Edit Database and select the Options tab.)

Table

Backs up the table specified in the box.


Initialize Device

Specifies to add the backup to the device. The backup will not overwrite what is on the device. To overwrite existing backups on the device, clear this option.

For SQL Server version 6.0 or later, backups can be appended to any disk or tape backup device. You can keep backups of a database and its transaction logs in one physical location. If you are using a tape that contains data in a foreign format (not SQL Server backup files), you must clear the Initialize Device option or the tape will be rejected.

No expiration date

Specifies that the backup will have no expiration date and can be overwritten at any time.

Expires after

Specifies that the backup will expire after a specified number of days has elapsed. If you select this option, you must also type the number of days in the adjacent box.

An existing backup cannot be overwritten until it expires. However, when Initialize Device is selected, the Expires After option is informational only.

Expires on

Specifies the specific date a backup will expire. If you select this option, you must type the number of days in the adjacent box.

An existing backup cannot be overwritten until it expires. However, when Initialize Device is selected, the Expires On option is informational only.


Eject Tape at End of Backup

Specifies that the tape will automatically rewind and unload when the backup completes. If you will be performing multiple backups to a single tape, clear this option. If you will be performing a single backup or the last backup of several to a tape, select this option.


Skip Tape Header

Specifies that the server should not read the ANSI header on a tape. For example, if the ANSI label of a tape warns that it has not expired or that you do not have permission to write to it, selecting this option causes SQL Server to ignore the warning. Or if the tape you are writing to is new (and has no ANSI label), SQL Server writes a new label. Selecting this option prevents unnecessary retries as SQL Server searches for a label. To tell SQL Server to read any existing ANSI tape labels on the tape(s) you are writing, clear this option.

Setting this option for a specified backup overrides the setting that is defined for the tape backup device when it was created.


Backup Devices

Lists available backup devices for the database specified in the Database Backup box. You can select one or more devices to back up to. You can also add or drop devices.

Note that you cannot back up to floppy disk devices using SQL Enterprise Manager.


New

Opens the New Backup Device dialog box, which you can use to add a new backup device or specify a backup path.


Delete

Opens the Delete Backup Device dialog box, which you can use to remove a device.


Info

Displays the Backup Device Information dialog box, which you can use to view information for a selected backup device.


Backup Now

Specifies to perform the backup immediately. The backup runs as a foreground task.


Schedule

Specifies a schedule for the backup for immediate, one time, or recurring execution.

Scheduling an immediate backup (instead of choosing Backup Now) provides the advantage of running the backup as a scheduled (background) task, instead of interactively.


Restore Tab for Databases, Transaction Logs, and Tables

Use this tab to restore databases, transaction logs, or tables.

Note that the Database Backup/Restore dialog box is available for SQL Server 6.0 and later.

For more information, choose one of the following:

 Database

 Restore

 Database and Transaction Logs

 Single Table

 Backup History

 Until Time

 Restore Now

 From Device

 Refresh

 Info

See Also

Point-in-Time Recovery

Restoring a Database, Transaction Log, or Table

Table Backup and Restore


Database

Specifies the database to restore from.


Restore

Specifies whether to restore a database and transaction log, or a table.


Database and Transaction Logs

Specifies whether to restore a full database backup.


Single Table

Specifies to restore a single table. A table restore can be performed from a table backup or from a full database backup.

If you select this option, select the destination table from the Single Table list.


Backup History

Displays backups available for restoration from the selected source database.

You can also select a database backup plus one or more of its transaction log backups for restoration.

Selecting a database backup restores the entire database. Selecting a transaction log backup restores the transaction log information, re-executes the changes it contains, and rolls back transactions that were uncommitted when the transaction log was backed up. Selecting a table backup restores that table.


Until Time

Specifies to restore transaction logs or databases through a specific point in time. Select this option and adjust the displayed date and time appropriately. Transactions committed after that time will be rolled back.

Point-in-time recovery applies to transaction log restores only.


Restore Now

Restores the selected database, transaction log, or table backup immediately.


From Device

Opens the Restore From Device On Server dialog box. Use this dialog box to restore from a device.


Info

Displays the Backup History Information dialog box, which provides more information.


Refresh

Updates information displayed in the Backup History box.


New/Delete Backup Device Dialog Box

Use this dialog box to add or delete a backup device. For more information, select one of the following:

 Name

 Location

 Locate

 Type

 Create

 Delete

See Also

Creating a Backup Device

Dropping a Backup Device


Name

Specifies the logical name for the new backup device. This name will be used when you back up to or restore from the device. The name must follow the rules for identifiers and can be up to 30 characters. If you specify a name longer than 30 characters, the name is truncated.

If you are deleting a backup device, this option cannot be edited.


Location

Specifies the physical name for the backup device. The physical name is an operating system filename that includes the full path. Physical names must follow the rules for operating system filenames or UNC (names for network disk devices). Names that contain nonalphanumeric characters must be enclosed in quotation marks.

If you are deleting a backup device, this option cannot be edited.


 Locate

Displays a directory tree. From the tree, select a path for location.

If you are deleting a backup device, the Locate button cannot be selected.


Type

Specifies whether the backup device is a disk or tape. If you are deleting a backup device, this option cannot be changed.

Disk Backup Device

Specifies that a backup device file will be created on a hard disk or other disk media. Note that you cannot back up to floppy disk devices using SQL Enterprise Manager.

Tape Backup Device

Specifies that a backup device will be created for a tape drive.

Skip Headers

Specifies whether to read or ignore ANSI tape labels. If you select this option and you selected Tape Backup Device, the ANSI tape label on the tape you are writing to will be ignored. If you clear this option, SQL Enterprise Manager will recognize all existing ANSI tape labels on the tape you are writing to.


Create

Creates the backup device. Backups to that device can then be performed.

Note that a disk backup device will not appear as a file in the specified directory until a backup has been performed to that device.


Delete

Drops the selected backup device. Displays a message that asks you to confirm this selection.


Creating a Backup Device

When you create a backup device, you provide a logical and a physical name. The logical name must follow SQL Server rules for identifiers and can be up to 30 characters. The physical name is an operating system filename that includes the full path and that follows the rules for operating-system filenames or the universal naming convention (UNC) for network devices.

SQL Enterprise Manager supports local and network disk backup devices. A local disk backup device is created on a disk drive that is attached to the local computer. A network disk backup device is created on a shared network directory. When you create a network disk backup device, specify a UNC name for the physical name.

SQL Enterprise Manager also supports local tape backup devices (on tape drives attached to the local computer). Network tape backup devices are not supported. To create a tape backup device, you must first install a tape drive using Windows NT. When you create a tape backup device for SQL Server, you must use the physical name that is assigned to the tape drive by Windows NT. For example, \\.\TAPE0.

You cannot use SQL Enterprise Manager to create, edit, delete, back up to, or restore from disk backup devices, or to create named pipe backup devices.

To create a backup device

1.	In the Server Manager window, select the server to create a backup device for.

2.	From the Tools menu, choose Database Backup/Restore.

The Database Backup/Restore dialog box appears.

3.	In the Backup Tab, under Backup Devices click the New button.

The New Backup Device dialog box appears.

4.	Complete the dialog box and click Create.

See Also

Backup Progress Dialog Box

Backup Volume Labels Dialog Box

Dropping a Backup Device

Viewing Backup Devices


Viewing Backup Devices

You can view a list of backup devices, information about backups that are stored on a device, and the physical name of a device.

To view backup devices

1.	In the Server Manager window, select a server to view backup devices for.

2.	To display the list of backup devices on the selected server, click the plus (+) sign that is next to the Backup Devices folder for the selected server.

3.	To view information about backups that are stored on a specific device, click the plus (+) sign that is next to that device. Full database backups are indicated by a database icon. Transaction log backups are indicated by a page icon.

To view the physical name of a backup device

1.	In the Server Manager window, select the server to view backup devices for.

2.	From the Tools menu, choose Database Backup/Restore.

The Database Backup/Restore dialog box appears.

3.	Select the Backup tab.

4.	In the Backup Devices box, select a backup device and click Delete.

The Delete Backup Device dialog box appears. The Location box displays the physical name of the backup device.

See Also

Creating a Backup Device

Dropping a Backup Device


Dropping a Backup Device

When you drop a backup device, data that is backed up to that device is also dropped.

To drop a backup device

1.	In the Server Manager window, select the server to drop a backup device from.

2.	From the Tools menu, choose Database Backup/Restore.

The Database Backup/Restore dialog box appears.

3.	Select the Backup tab.

4.	In the Backup Devices box, select a backup device to drop and click Delete.

The Delete Backup Device dialog box appears.

4.	Click Delete.

After you delete a disk backup device, delete the device's file using Windows File Manager or Explorer.

See Also

Creating a Backup Device

Viewing Backup Devices


Backup Device Information Dialog Box

Use this dialog box to view information for a backup device on the server selected in the Server Manager window. For more information, choose one of the following:

 Backup Device

 Device Type

 Device Size

 Volume Label

 Expiration Date

 Striped

 Members

 ID

 Database

 Backup Type

 Table

 Backup Start

 Backup Finish

 Backup Size (Kb)

 Current Sequence

 New Sequence

See Also

Backup Tab for Databases, Transaction Logs, and Tables


Backup Device

Specifies the name of the backup device to view information for. Expand the list to select a different name.


Device Type

Specifies whether the backup device is Disk or Tape.


Device Size

Specifies the size, in kilobytes, of the backup device.


Volume Label

Specifies the volume label of the backup device.


Expiration Date

Specifies the expiration date, if any. A backup device with an expiration date cannot be overwritten until that date expires. A backup device without an expiration date can be overwritten at any time.


Striped

Specifies the name of the stripe set (if applicable).


Members

Lists members (if any) of the stripe set. Select a device from the list to display information about that device.


ID

Specifies the volume ID of the backup.


Database

Specifies the name of the source database for the backup.


Backup Type

Specifies whether the backup type is Table, Database, or Transaction Log.


Table

Specifies the name of the table, if a table backup.


Backup Start

Specifies the date and time the backup began.


Backup Finish

Specifies the date and the time the backup was completed.


Backup Size (Kb)

Specifies the size, in kilobytes, of the backup pages.


Current Sequence

Specifies the current or old sequence number of the backup. The sequence number indicates the position of the backup in the volume.


New Sequence

Specifies the new sequence number of the backup.


Backup Volume Labels Dialog Box

Use this dialog box to confirm or change the volume label for a backup device or for backup devices in a stripe set. Volume labels can be up to six characters long.

The function of this dialog box varies, as follows:

To review the volume labels for removable media backup devices to verify they are correct, in the Backup tab, select the Initialize Device option and click the Backup Now button.

The Backup Volume Labels dialog box appears.

To accept the default labels for the new backups or supply new ones, clear the Initialize Device option and click the Backup Now button. The Backup Volume Labels dialog box appears. Make changes if necessary and click OK. Volume labels can be up to six characters long.

To check volume labels during a scheduled backup, in the Backup Volume Labels dialog box, enter the volume labels to be checked or leave the Volume column entries blank.

See Also

Backup Tab for Databases, Transaction Logs, and Tables

Scheduled Dialog Box


Backup Progress Dialog Box

Use this dialog box to monitor a backup.


Backing Up a Database, Transaction Log, or Table

Backing up a database, a transaction log, or a table copies system tables and user-defined objects to a specified backup device. You can back up a database to multiple devices and specify a variable path name to back up to.

You can also back up multiple databases or transaction logs to a single file or tape. You cannot back up to floppy disk backup devices using SQL Enterprise Manager.

Back up your database on a set schedule. If you store the transaction log on a different disk device from the database, back up the log frequently to record changes made since the last database backup.

The SQL Server process of backing up is a dynamic backup that can occur while the database is active. The backup captures the data as it is at the moment the statement is executed; no partial transactions are reflected in the backup database.

Performing a backup can slow the system, so you may want to execute a backup when the database is not being updated.

To back up a database, transaction log, or individual table

1.	In the Server Manager window, select the server to back up from.

2.	From the Tools menu, choose Database Backup/Restore.

The Database Backup/Restore dialog box appears. Note that the Database Backup/Restore dialog box is available for SQL Server 6.0 and later.

3.	In the Backup tab, select a database and specify the options.

4.	Click Backup Now, or click Schedule to specify a time for the backup.

See Also

Restoring a Database, Transaction Log, or Table

Table Backup and Restore


Add Backup Disk File

Adds a backup disk file.

Name

Specifies the logical name for the disk file.

Location

Specifies the physical path name and filename for the disk file.


Restoring a Database, Transaction Log, or Table

You can restore a database, transaction log, or table.

You can restore a database by loading the most recent database backup and its subsequent transaction log backups to recover as much of a database as possible in case of system failure or database damage. A record of database backups, including backups made through other applications, is maintained.

If you are restoring a database because of media failure, run DBCC, drop the damaged database, re-create the database, and load it. When a database is restored from a backup, that database must not be in use. All data in the database to be restored is replaced by the backup data.

Restoring a transaction log results in re-executing the changes the transaction log contains and rolling back transactions that were uncommitted when the transaction log was backed up. Transaction log backups must be restored in the sequence in which they were made. SQL Server checks the timestamps on each database backup and each transaction log backup to verify that the sequence is correct. When the entire sequence of transaction log backups has been restored, the database is restored to its state at the time of the last transaction log backup (minus active transactions).

Transaction logs can be restored to a date and time you specify. Transactions committed after that date and time will be rolled back.

To restore a database, transaction log, or individual table

1.	In the Server Manager window, select the server to restore to.

2.	From the Tools menu, choose Database Backup/Restore.

The Database Backup/Restore dialog box appears. Note that the Database Backup/Restore dialog box is available for SQL Server 6.0 and later.

3.	In the Restore tab, specify the options.

4.	Click Restore Now.

See Also

Backing Up a Database, Transaction Log, or Table

Creating a Database

Dropping a Database

Point-in-Time Recovery

Restore From Device On Server Dialog Box

Table Backup and Restore


Microsoft Distributed Transaction Coordinator

The Microsoft Distributed Transaction Coordinator (MS DTC) manages transactions across a network of Windows NT- and Windows 95-based systems. MS DTC provides:

Distributed transaction support for Microsoft SQL Server, which makes it easy to reliably update data that resides on two or more Microsoft SQL Server systems.

An easy-to-use graphical user interface for distributed transactions.

By using the MS DTC interface in SQL Enterprise Manager, you can:

Start and stop MS DTC (as a Windows NT service).

Open the MS DTC Transactions window, where you can view the status of all the currently running transactions and force the outcome of in-doubt transactions.

Open the MS DTC Trace window, where you can view MS DTC trace information.

Open the MS DTC Statistics window, where you can view statistics about MS DTC transactions and performance.

Open the MS DTC Configuration dialog box, where you can set display parameters for the MS DTC Transactions, Trace, and Statistics windows and change the size and location of the MS DTC log file.

To start, stop, and administer MS DTC

1.	Using SQL Enterprise Manager, in the Server Manager window, a Distributed Transaction Coordinator icon displays in the expanded tree under the name of each server that has MS DTC installed.

2.	Expand the tree for the appropriate server.

3.	Right-click on the Distributed Transaction Coordinator icon and select the appropriate command from the menu.

You can also administer MS DTC by using the Distributed Transaction Coordinator command from the Server menu.

When Microsoft SQL Server 6.5 is installed, the MS DTC service is added to the Services application in Control Panel.

For more information about configuring and using MS DTC, see the Guide to Microsoft Distributed Transaction Coordinator.

See Also

Using MS DTC from SQL Enterprise Manager

MS DTC Transactions Window

MS DTC Trace Window

MS DTC Statistics Window


Using MS DTC from SQL Enterprise Manager

The Microsoft Distributed Transaction Coordinator (MS DTC) can be started, stopped, and administered through SQL Enterprise Manager. A Distributed Transaction Coordinator icon appears in the expanded tree under the name of each server that has MS DTC installed.

To start, stop, or administer MS DTC, select a server and expand its tree, click the right mouse button on the Distributed Transaction Coordinator icon, and select the appropriate command from the menu. For more information, choose one of the following:

 Start

 Stop

 Transactions

 Trace

 Statistics

 Configuration

You can also administer MS DTC by using the Distributed Transaction Coordinator command from the Server menu.

See Also

Microsoft Distributed Transaction Coordinator


Start

Starts MS DTC as a Windows NT service.


Stop

Stops MS DTC as a Windows NT service.


Transactions

Opens the MS DTC Transactions window. Use this window to display all transactions currently running and the status of each transaction.

You can force in-doubt transactions to commit or abort. You can also force MS DTC to forget a transaction from its log.


Trace

Opens the MS DTC Trace window, which displays MS DTC error, warning, information, and trace messages. You can use the Trace slider in the MS DTC Configuration dialog box to filter the displayed information by severity level.


Statistics

Opens the MS DTC Statistics window. Use this window to display statistics about MS DTC transactions and performance, including: the current number of active transactions; the peak number of concurrent transactions; the numbers of committed, aborted, in-doubt, and administratively resolved transactions; the total number of transactions processed; transaction response times; and the date and time that the current MS DTC session started.


Configuration

Opens the MS DTC Configuration dialog box. Use this dialog box to set display parameters for the MS DTC Transactions, Trace, and Statistics windows and to change the size and location of the MS DTC log file.


MS DTC Transactions Window

Use this window to monitor the status of a transaction or to manually resolve a transaction. For more information, see the following:

 Monitoring a Transaction

 Changing the View Options

 Manually Resolving a Transaction


Monitoring a Transaction

Transactions are displayed in the window by icons that represent the current state of each transaction. For a list of icons and the transaction states they represent, see the Guide to Microsoft Distributed Transaction Coordinator.


Changing the View Options

You can right-click any transaction icon to display a menu that allows you to change the way the icons are displayed in the window:

Large Icon

Displays transactions in large icons that are arranged sequentially in rows across the screen.

Small Icon

Displays transactions in small icons arranged sequentially in rows across the screen.

Details

Lists transactions in a single column and provides an additional two columns of information:

The current MS DTC's parent MS DTC; that is, the current MS DTC's immediate predecessor in the transaction's path across the network.

The unit of work ID associated with each transaction. This is the transaction's global unique identifier, which is generated by MS DTC when the transaction begins.

List

Displays transactions sequentially in columns down the screen.

Small Icon and List display the most transactions at any one time. Details provides the most information about the transactions, and Large Icon displays transactions in the most readable format.


Manually Resolving a Transaction

You can right-click a transaction's icon to display a menu that allows you to manually resolve the transaction.

Commit

Commits the transaction on the local MS DTC.

Abort

Aborts the transaction on the local MS DTC.

Forget

Deletes the transaction record from the log file of the local MS DTC.


MS DTC Trace Window

Use this window to list current trace messages issued by the MS DTC. Tracing allows the system administrator to view the current status of various MS DTC activities, such as startup and shutdown, and to track potential problems by viewing additional debugging information. You can filter the displayed information by severity level by adjusting the Trace slider in the MS DTC Configuration dialog box. For more information, see the following:

 Trace Severity Levels

 Trace Sources

 Clearing the MS DTC Trace Window

See Also

Microsoft Distributed Transaction Coordinator

Using MS DTC from SQL Enterprise Manager


Trace Severity Levels

MS DTC tracing supports the following levels of severity:

Errors

Messages about problems, such as a corrupt log file, which cause MS DTC to malfunction or need a restart.

Warnings

Information about something that might go wrong soon.

Information

Useful information about infrequent events, such as startup and shutdown.

Trace

Debugging information about events such as new client connections or resource manager enlistments.

All error, warning, and informational traces are routed to the Windows NT event logger, regardless of whether SQL Enterprise Manager is running and regardless of the trace view slider setting.


Trace Sources

The tracer and the Windows NT event logger tag each message with its source.

Source	Description
SVC	The MS DTC Service
LOG	The MS DTC log
CM	The MS DTC network connection manager


Clearing the MS DTC Trace Window

To clear all messages from the MS DTC Trace window, right-click anywhere inside the window; from the View menu, choose Clear.


MS DTC Statistics Window

Use this window to view statistical information about the transactions in which a server participated. Some of the statistics are cumulative, others reflect current performance. It is important to remember that if you stop the MS DTC, the values of all cumulative statistics will reset to zero when you restart the MS DTC. For more information, see the following:

 Current

 Aggregate

 Response Times

 DTC Started

See Also

Microsoft Distributed Transaction Coordinator

Using MS DTC from SQL Enterprise Manager


Current

In Current are the following:

Active

The current number of transactions that have not yet completed the two-phase commit protocol.

Max. Active

The highest number of active transactions at any time during the period in which the MS DTC was operational.

In Doubt

The current number of in-doubt transactions. In-doubt transactions may require administrator intervention. In-doubt transactions can be viewed and managed in the MS DTC Transactions window.

The size of the MS DTC log file determines the maximum allowable number of concurrent transactions. Once a transaction has committed or aborted, it is deleted from the log file. However, should the log file at any point become full, the MS DTC on the local server will refuse to accept any new transaction until sufficient space has been cleared in the log file to record the new transaction.

Together the Active and Max.Active statistics measure the transaction load on a particular MS DTC. If, for example, the number of current transactions approaches the historical maximum, the system administrator may decide to increase the size of the log file to allow for more transactions. If on the other hand, the number of current transactions is well below the maximum, the administrator may decrease the size of the log file to conserve resources such as memory.

You can increase or decrease the size of the log file by using the MS DTC Configuration dialog box.


Aggregate

In Aggregrate are the following:

Committed

The cumulative total of committed transactions. This number does not include forced (manually resolved) commits.

Aborted

The cumulative total of aborted transactions. This number does not include forced (manually resolved) aborts.

Forced Commit

The cumulative total of committed transactions that were manually resolved.

Forced Abort

The cumulative total of aborted transactions that were manually resolved.

Total

The cumulative total of all transactions.


Response Times (milliseconds)

Shows the minimum, average, and maximum transaction response times in milliseconds. Response time refers specifically to the duration of a transaction from the point that it began to the point that its outcome is known - that is, the point at which it is definitively committed by the commit coordinator (aborted transactions and transactions whose outcomes were forced are not taken into account).


DTC Started

Shows the date and time that the current MS DTC started.


MS DTC Configuration Dialog Box

Use this dialog box to change MS DTC display parameters, reset the MS DTC log and timers, or start and stop the MS DTC. For more information, see the following:

 View

 Log

 Status

See Also

Microsoft Distributed Transaction Coordinator

Using MS DTC from SQL Enterprise Manager


View

Display Refresh controls how often trace messages, statistical information, and the transaction list are sent from the MS DTC process to the graphical interface. More frequent updates increase administrative overhead on the running transactions but also provide more accurate information on the running MS DTC. The slider positions (left to right) are as follows:

Update the display every 20 seconds.

Update the display every 10 seconds.

Update the display every 5 seconds (default).

Update the display every 3 seconds.

Update the display every 1 second.

Transactions Shown controls how long a transaction must be active before being displayed in the MS DTC Transactions window. The slider positions (left to right) are as follows:

Show 5 minute-old transactions.

Show 1 minute-old transactions.

Show 30 second-old transactions (default).

Show 10 second-old transactions.

Show 1 second-old transactions.

Trace controls the level of traces sent to the MS DTC Trace window. The slider positions (left to right) are as follows:

Send no tracing.

Send only error traces to.

Send error and warning traces.

Send error, warning, and informational traces (default).

Send all traces.


Log

The MS DTC log file is always called MSDTC.LOG. Before changing the size or location of the log file, you must use the Stop button to stop the MS DTC. After changing the size or location of the log file, click the Reset Log button. You can then use the Start button to restart the MS DTC.

Location

The location of the MS DTC log file.

Drive

The drive on which the MS DTC log file is located.

Directory

The directory on which the log file is located.

Capacity

The current size of the MS DTC log file. The slider can be used to change the size of the MS DTC log file.


Status

Shows the current status of MS DTC. Choose from: Start, Stop, Close, and Help.


Servers

Getting Started with SQL Enterprise Manager

Registering a Server

Creating a Server Group

Renaming a Server Group

Removing a Server Group

Removing a Server

Modifying Server Information

Starting, Pausing, or Stopping a Server

Setting Server Options

Setting Security Options

Setting Server Configuration Information

Managing SQL Server Messages

Viewing Server Attributes Information

Viewing Server Current Activity

Viewing Detail Activity

Viewing Object Locks

Viewing the Error Log

Changing Servers or Databases

Setting SQL Enterprise Manager Configuration Information

Configuring SQL Executive

Adding a SQL Server Login

Modifying a Login

Dropping a Login

Managing Remote Servers and Logins

Adding a Database Device

Dropping a Database Device

Modifying a Database Device

Creating a Backup Device

Viewing Backup Devices

Dropping a Backup Device


Databases

Creating a Database

Modifying a Database

Setting Database Options

Setting Statement Permissions

Dropping a Database

Adding or Modifying Database Users

Using Aliases

Dropping a Database User

Creating Groups

Modifying Groups

Dropping a Group

Backing Up a Database, Transaction Log, or Table

Restoring a Database, Transaction Log, or Table


Objects

Granting Object Permissions

Revoking Object Permissions

Viewing Object Permissions

Creating a Table

Modifying a Table

Dropping a Table

Creating an Index

Modifying an Index

Renaming an Index

Updating Index Statistics

Viewing Index Distribution Information

Checking the Size of an Index

Dropping an Index

Creating a Trigger

Modifying a Trigger

Dropping a Trigger

Creating a Stored Procedure

Modifying a Stored Procedure

Dropping a Stored Procedure

Managing Extended Stored Procedures

Creating a View

Modifying a View

Dropping a View

Creating a Rule

Binding a Rule to a Column

Binding a Rule to a Datatype

Unbinding a Rule from a Column

Unbinding a Rule from a Datatype

Dropping a Rule

Creating a Default

Binding a Default to a Column

Binding a Default to a Datatype

Unbinding a Default from a Column

Unbinding a Default from a Datatype

Dropping a Default

Creating User-Defined Datatypes

Viewing User-Defined Datatype Information

Dropping a User-Defined Datatype

Generating SQL Scripts

Viewing Object Dependencies

Dropping Objects

Renaming Objects


Alerts

Alerts Overview

Viewing Alerts

Creating an Alert

Editing an Alert

Deleting an Alert

Raising SNMP Traps From an Alert

Viewing Operators

Creating an Operator

Editing Operator Information

Deleting an Operator

Setting Alert Engine Options


Scheduled Tasks

Scheduling a Task

Editing a Scheduled Task

Deleting a Scheduled Task

Viewing Task History

Viewing a List of Scheduled Tasks Currently Running


Replication

Replication Overview

Setting Up the Replication Distribution Database

Setting Replication Publishing Information

Setting Server Subscribing Information

Setting Up DBOs to Manage Publications and Subscriptions

Viewing Replication Topology

Using an ODBC Subscriber

About Microsoft Access Subscribers

About ORACLE Subscribers

About Other ODBC Subscribers

Replication Restrictions for ODBC Subscribers

Datatype Mappings for ODBC Subscribers

Creating Publications

Setting Up Push Subscriptions

Setting Up Pull Subscriptions

Manually Synchronizing Database Tables for Replication

Stopping Replication from a Publisher

Stopping Replication from a Subscriber


Queries

Querying a Database

Editing Query Results

Saving a Query to a File

Saving Query Results

Starting a New Query

Using a Saved Query

Removing a Query/Result Set

Setting Query Flag and Format Options

Setting Query System Options

Searching and Replacing Text

Using Graphical Statistics I/O


Getting Started with SQL Enterprise Manager

This Help topic briefly describes SQL Enterprise Manager. For detailed information about how to perform tasks using SQL Enterprise Manager, see the Help Contents or the Online Help available in each window and dialog box.

What is SQL Enterprise Manager?

SQL Enterprise Manager provides powerful administration tools that you can use to manage multiple servers. With SQL Enterprise Manager you can configure, start, pause, and stop SQL Servers, monitor current server activity, and view the SQL Server error log. You can create and manage devices, databases, and database objects. You can manage security, including logins, database users, and permissions. SQL Enterprise Manager and the SQL Executive service provide a way to set alerts for various server events and to schedule server tasks. SQL Enterprise Manager also provides a graphical way to set up and manage replication, and enables you to execute and analyze queries, back up and restore databases, and generate SQL scripts.

Who can use SQL Enterprise Manager?

Anyone who can access SQL Server can use SQL Enterprise Manager; no permission is needed. Access to objects and tasks within SQL Enterprise Manager is controlled by permissions of the login ID. If you log on as the system administrator (SA), you can access all tasks and objects. If you log on as the database owner (DBO), you can access tasks and objects permitted to the DBO. If you log on as a user, you can access all objects you have created and perform tasks you have permission for.

Note that for SQL Server 6.5, SQL Enterprise Manager administers SQL Server 6.0 and 6.5 servers. SQL Enterprise Manager for SQL Server 6.0 cannot administer SQL Server 6.5 servers. To connect to a SQL Server 6.5 server, you must upgrade to a SQL Server 6.5 client installation.

How do I start using SQL Enterprise Manager?

First you must register the server(s) you will be managing with SQL Enterprise Manager. Each server you register will appear in the Server Manager window when SQL Enterprise Manager is started. While you are registering servers, you may want to create groups to better organize how your servers appear in the Server Manager window.

You can immediately begin to perform tasks for a registered server. Initially, you may want to verify that SQL Server configuration options are set appropriately, create devices and databases, create login IDs, and configure the SQL Server for replication. For more information about these tasks, choose from the following:

Adding a Database Device

Adding a SQL Server Login

Creating a Database

Creating a Server Group

Registering a Server

Replication Overview

Server Manager Window

Setting Server Configuration Information


Registering a Server

To manage a server with SQL Enterprise Manager, you must first register the server. Registering a server includes providing the server name, and your login ID and password for that server. You must also assign the server to a server group.

SQL Enterprise Manager works with SQL Server versions 4.2x, 6.0, and 6.5. However, to use SQL Enterprise Manager with SQL Server version 4.2x, you must first load the SQL script SQLOLE42.SQL into the 4.2x server. You can find a copy of the script in the \INSTALL directory of the computer that contains SQL Server 6.0 or 6.5. Note that not all features of SQL Enterprise Manager are enabled for use with SQL Server version 4.2x.

To register a server

1.	From the Server menu, choose Register Server.

The Register Server dialog box appears.

2.	In the Server box, type the name of the server.

3.	In the Server Group box, select a group to place the server in.

4.	Click Register.

If you receive the message "Unable to Connect to Server. Register anyway?", the server you are registering is not started or the login information you provided is invalid.

See Also

Removing a Server

Modifying Server Information


Creating a Server Group

Server groups provide a way for you to organize SQL Servers in the Server Manager window. For example, you can create a group of servers that are used for development (Development Servers) or that have a specific location (North American Servers). By default, SQL Enterprise Manager is installed with a server group named SQL 6.5.

The groups you create in SQL Enterprise Manager are private and are only at the computer they were created on. If you have several computers with SQL Enterprise Manager installed on them and you want those computers to display identical server groups, you must create those groups on each computer or duplicate the SQL Enterprise Manager server registration configuration by copying the \MSSQL\BINN\SERVER.BIN file from one computer to another.

To create a server group

1.	From the Server menu, choose Server Groups.

The Manage Server Groups dialog box appears.

2.	In the Name box, type a name for the server group.

3.	Under Level, select Top Level Group or Sub-Group Of. If you select Sub-Group Of, select a group from the window below.

4.	Choose Add.

See Also

Renaming a Server Group

Removing a Server Group


Renaming a Server Group

You can change the name of a server group to reflect changes in how you organize your servers (for example, North American Servers to U.S. Only Servers).

To rename a server group

1.	From the Server menu, choose Server Groups.

The Manage Server Groups dialog box appears.

2.	In the box under Sub-Group Of, select the group to rename.

3.	In the Name box, type a new name for the specified group.

4.	Click Rename.

See Also

Creating a Server Group

Removing a Server Group


Removing a Server Group

You can remove a server group by removing affected servers and subgroups.

To remove a server group

1.	From the Server menu, choose Server Groups.

The Manage Server Groups dialog box appears.

2.	In the box under Sub-Group Of, select the name to remove.

3.	Click Remove.

See Also

Creating a Server Group

Renaming a Server Group


Removing a Server

You can remove a server from SQL Enterprise Manager. The server remains installed.

To remove a server

1.	From the Server menu, choose Register Server.

The Register Server dialog box appears.

2.	In the Server box, expand the list and select the server to remove.

3.	Choose Remove.

See Also

Registering a Server

Modifying Server Information


Modifying Server Information

You can change information about a registered server. You can change the login information, the group the server belongs to, and whether to display server status in the Server Manager window.

To modify server information

1.	From the Server menu, choose Register Server.

The Register Server dialog box appears.

2.	In the Server box, expand the list and select the server to modify.

3.	Modify as necessary.

Note that server status cannot be displayed on Windows 95based computers because polling uses Windows NT Service Control APIs, which are unavailable on Windows 95.

4.	Choose Modify.

See Also

Registering a Server

Removing a Server


Setting Server Options

You can configure several server options after installing SQL Server 6.5. You can configure SQL Server file paths, the master database, and the error log. You can set options to automatically start SQL Server or SQL Executive whenever you boot the server. You can view whether SQL Server events are being registered in the Windows NT application event log, and whether SQL Server performance statistics are being integrated with the Windows NT Performance Monitor. You can set startup parameters, tape support, and mail client information.

To set server options

1.	In the Server Manager window, right-click the server and from the shortcut menu that appears choose Configure, or from the Server menu choose SQL Server/Configure.

The Server Configuration/Options dialog box appears.

2.	Select the Server Options tab.

3.	Set the appropriate options.

4.	Click Apply Now.

See Also

Setting Security Options

Setting Server Configuration Information


Setting Security Options

SQL Server provides a way to integrate SQL Server login security with Windows NT security. Integrated security enables SQL Server applications to take advantage of Windows NT security features, including encrypted passwords, password aging, domain-wide user accounts, and Windows NT-based user administration. With integrated security, authorized users can bypass the SQL Server login process.

To set security options

1.	In the Server Manager window, right-click the server and from the shortcut menu that appears choose Configure, or from the Server menu choose SQL Server/Configure.

The Server Configuration/Options dialog box appears.

2.	Select the Security Options tab.

3.	Set the appropriate options.

4.	Click Apply Now.

See Also

Setting Server Options

Setting Server Configuration Information

Viewing Server Attributes Information


Setting Server Configuration Information

SQL Server configuration options control various aspects of SQL Server performance and memory allocation. You can configure many options to optimize SQL Server performance.

To set server configuration information

1.	In the Server Manager window, right-click the server and from the shortcut menu that appears choose Configure, or from the Server menu choose SQL Server/Configure.

The Server Configuration/Options dialog box appears.

2.	Select the Configuration tab.

3.	Select a configuration option, and in the corresponding Current column, type a new value for that option.

Some SQL Server configuration options are advanced options. To view these options, in the Configuration tab, set the value for Show Advanced Options to "1", click OK, and then return to the Server Configuration/Options dialog box.

4.	Repeat step 3 for each option to change.

5.	Click Apply Now.

Except where noted otherwise in the Description box, to apply the new configuration values you must stop and restart the server.

See Also

Setting Server Options

Setting Security Options

Viewing Server Attributes Information


Viewing Server Attributes Information

You can view (but not change) information about a SQL Server. Information is available about the server version and various environment variables, the database gateway, and the underlying data source.

To view server attribute information

1.	In the Server Manager window, right-click the server and from the shortcut menu that appears choose Configure, or from the Server menu choose SQL Server/Configure.

The Server Configuration/Options dialog box appears.

2.	Select the Attributes tab.

See Also

Setting Server Options

Setting Security Options

Setting Server Configuration Information


Viewing Server Current Activity

You can view information about current server activity, including current user connections. You can view the process numbers, statuses, locks, and commands the active users are running. You can determine which objects are locked and the kinds of locks that are present. You can also send a message to a connected server and close a process. Only the system administrator can view server activity.

To view server connection activity

1.	In the Server Manager window, select the server to view connection activity for.

2.	From the Server menu, choose Current Activity.

The Current Activity window appears.

3.	In the User Activity tab, to view a legend for the icons in the tab, click the Display Legend button.

To view more information about a process

1.	In the Detail Activity tab, select the process to view more information for.

2.	Click the View Details button, or right-click the selected server and from the shortcut menu that appears, choose View Details.

The Process Details dialog box appears. Information is displayed about the last statement that the process ran and the resource usage for that process.

To refresh connection information

In the Current Activity window, from the toolbar click the Refresh button.

See Also

Sending a Message to a Connected Server

Terminating a Process

Viewing Detail Activity

Viewing Object Locks

Viewing the Error Log


Sending a Message to a Connected Server

You can send a message to a selected server that is connected or to all users that are currently connected.

To send a message to a connection

1.	In the Server Manager window, select the server to send a message to.

2.	From the Server menu, choose Current Activity.

The Current Activity window appears.

3.	From the toolbar click Send Message, or in any of the tabs, right-click the selected connection and in the shortcut menu that appears, choose Send Message.

The Send Message dialog box appears.

4.	Complete the dialog box and click Send.

See Also

Terminating a Process

Viewing Detail Activity

Viewing Object Locks

Viewing the Error Log

Viewing Server Current Activity


Terminating a Process

You can terminate a process for a currently connected server.

To terminate a process

1.	In the Server Manager window, select the server to view connection activity for.

2.	From the Server menu, choose Current Activity.

The Current Activity window appears.

3.	In any of the tabs, select the process to end.

4.	Click the Kill Process button, or right-click the selected process and in the shortcut menu that appears, choose Kill Process.

See Also

Sending a Message to a Connected Server

Viewing Detail Activity

Viewing Object Locks

Viewing the Error Log

Viewing Server Current Activity


Viewing Object Locks

You can view information about object locks for a selected SQL Server, processes that hold the locks, and statements that are being executed. You can also view more information about a process, terminate a process, or send a message to a connection. Only the system administrator can view object lock information.

To view object locks

1.	In the Server Manager window, select the server to view object locks for.

2.	From the Server menu, choose Current Activity.

The Current Activity window appears.

3.	Select the Object Locks tab.

To view a legend for the icons in the tab, click the Display Legend button.

To refresh lock information

Click the Refresh on-screen information button.

See Also

Sending a Message to a Connected Server

Terminating a Process

Viewing Server Current Activity

Viewing Detail Activity

Viewing the Error Log


Viewing Detail Activity

You can view information about the process numbers, statuses, blocks, and commands the active users are running. You can also view more information about a process, terminate a process, or send a message to a connection. Only the system administrator can view detail activity.

To view detail activity

1.	In the Server Manager window, select the server to view detail activity for.

2.	From the Server menu, choose Current Activity.

The Current Activity window appears.

3.	Select the Detail Activity tab.

To view a legend for the icons in the tab, click the Display Legend button.

To refresh activity information

Click the Refresh on-screen information button.

See Also

Sending a Message to a Connected Server

Terminating a Process

Viewing Server Current Activity

Viewing Object Locks

Viewing the Error Log


Viewing the Error Log

You can view the error log for a selected SQL Server.

To view the error log

1.	In the Server Manager window, select the server to view the error log for.

2.	From the Server menu, choose Error Log.

The Server Error Log window appears.

A new log is created each time SQL Server is started. The current log is labeled Current. The previous six logs are maintained and are labeled Archive followed by a number. The lowest number is the most recently archived log.

3.	To update information in the log, click the Refresh button.

See Also

Viewing Server Current Activity

Viewing Detail Activity

Viewing Object Locks


Setting SQL Enterprise Manager Configuration Information

You can set server connection and application preferences for SQL Enterprise Manager.

To set SQL Enterprise Manager configuration information

1.	From the Tools menu, choose Preferences/Configure.

The Configure SQL Enterprise Manager dialog box appears.

2.	To set application-related preferences, choose the Application tab and set the appropriate preferences.

To reset all application-related preferences to their defaults, choose Defaults.

3.	To set connection-related preferences, choose the Connection tab and set the appropriate preferences.

To reset all connection-related preferences to their defaults, choose Defaults.

4.	To set query system preferences, choose the Query System tab and set the appropriate preferences.

5.	Click OK.


Changing Servers or Databases

Using the Server Manager window or the Select Server/Database dialog box, you can change to a different server and/or database or disconnect from a server.

To change to or disconnect from servers or to change databases in the Server Manager window

To change to a server or database, select the server or database.

To disconnect from a server, click the server with the right mouse button and choose Disconnect.

To change to or disconnect from servers or to change databases in the Select Server/Database dialog box

From the Tools menu, choose Set Server/Database.

Complete the Select Server/Database dialog box that appears.


Adding a SQL Server Login

Before a user can access a SQL Server, the system administrator (SA) must add the user's login ID to the server. The SA can also assign the user a password, a username, a default database, and a default language. The master database is the default database. If the user is not assigned a username in the default database, the user's login ID is used as the username. Only the SA can add SQL Server logins.

If the SQL Server is configured for integrated security, a login ID for each user is not necessary. Instead, use the SQL Security Manager utility to automatically map Windows NT-based usernames to SQL Server login IDs.

When you add a SQL Server login, you can also select databases to permit access to.

To add a SQL Server login

1.	In the Server Manager window, select the server to add logins to.

2.	From the Manage menu, choose Logins.

The Manage Logins dialog box appears.

3.	Complete the dialog box and click Add.

See Also

Modifying a Login

Dropping a Login


Modifying a Login

If you are the system administrator (SA), you can change the password, the default language, and the database access for any login. If you are not the SA, you can modify only your own password.

To modify a login

1.	In the Server Manager window, select the server to modify a login for.

2.	From the Manage menu, choose Logins.

The Manage Logins dialog box appears.

3.	Complete the dialog box and click Modify.

See Also

Adding a SQL Server Login

Dropping a Login


Dropping a Login

To prevent a user access to a SQL Server, the system administrator (SA) must remove the user's login ID from the server.

You cannot drop the login ID of a user who owns a database or database objects in the current database. You must transfer ownership of a database owned by the login ID and drop owned objects from the database before you can drop the owner's login ID.

To drop a login ID

1.	In the Server Manager window, select the server to drop a login ID for.

2.	From the Manage menu, choose Logins.

The Manage Logins dialog box appears.

3.	Complete the dialog box and click Drop.

See Also

Adding a SQL Server Login

Modifying a Login


Adding a Database Device

Databases and transaction logs are stored in files called database devices. Before you can create a database, you must first create a device in which to store the database. A device can store many databases, and a database can be stored in several devices.

In addition to database devices, you can create backup devices in which to store a database and its transaction log backups. Only the system administrator can create devices.

To add a database device

1.	In the Server Manager window, select the server to add a device to.

2.	From the Manage menu, choose Database Devices.

The Manage Database Devices window appears.

3.	Click the New Device button.

The New Database Device dialog box appears.

4.	In the Name box, type a name for the device.

5.	To specify the device as the default device, select the Default Device check box.

6.	In the Location box, select a drive to place the device on.

The device location automatically appears in the adjacent path box. To change the location, click the Locate button and select a different location.

7.	In the Size (MB) box, type a size, in megabytes, for the device.

Under Available Space on Database Devices, a graph of available drive space is displayed. To graphically display different size allocations in the Available Space on Database Devices box, move the slider.

8.	To mirror the device, click the Mirroring button. The Mirror Database Device dialog box appears and displays a mirror name automatically. To change the name, type a new name in the Mirror Device Filename box. Click OK.

9.	Click Create Now.

See Also

Dropping a Database Device

Modifying a Database Device

Creating a Backup Device


Dropping a Database Device

Dropping a database device frees storage space on the server. When you drop a device, all databases on it are also dropped. After you drop a device, the file handle and the device number are freed. You can then delete the physical file from the hard disk without shutting down SQL Server. You can also immediately create a new device with the same device number and logical name as the dropped device.

To drop a database device

1.	In the Server Manager window, select the server to remove a device from.

2.	From the Manage menu, choose Devices.

The Manage Database Devices window appears.

3.	From the graph, select the database device to drop.

4.	Click the Delete Device button.

The Delete Non-Empty Device dialog box appears and lists all databases on the selected device. To confirm deletion, click Delete Device. If the device does not contain databases, the Delete Device dialog box appears. Click Yes.

See Also

Adding a Database Device

Modifying a Database Device

Dropping a Backup Device


Modifying a Database Device

You can specify a database device as the default device; mirror, unmirror, or remirror a device; and increase the device size. Only the system administrator can modify database devices.

To modify a database device

1.	In the Server Manager window, double-click the device to modify.

The Edit Database Device dialog box appears.

2.	To expand the database device size, type a larger number in the Size (MB) box. Note that the device size can be increased, but not reduced.

3.	To specify the device as the default device, select the Default Device check box.

4.	To modify the device mirroring, choose Mirroring.

The Mirror Database Device dialog box appears. Modify as appropriate.

5.	To modify the device immediately, in the Edit Database Device dialog box, click Change Now. To schedule device modification, click Schedule.


Creating a Database

When you create a database, you allocate storage space for the database on a device. You must create a device on which to store a database before you can create a database.

When you create a database, a transaction log is also created to record all transactions performed on that database. Store the transaction log on a different device from the database to simplify recovery and improve performance. If you do not specify a different device, the transaction log is created as part of the database.

To create a database

1.	In the Server Manager window, select the server to create a database for.

2.	From the Manage menu, choose Databases.

The Manage Databases window appears.

3.	Click the New Database button.

The New Database dialog box appears.

4.	In the Name box, type a name for the database.

5.	In the Data Device box, select the device on which to place the database.

You can create a device for the selected database by choosing <new> and completing the information in the New Database Device dialog box.

6.	In the Size (MB) box, type the amount of space, in megabytes (MB), to allocate on that device for the database.

7.	In the Log Device box, select the device on which to place the transaction log.

You can create a device for the transaction log by selecting <new> and completing the information in the New Database Device dialog box.

8.	In the Size (MB) box, type the amount of space, to allocate on that device for the transaction log.

The graph of Available Space on Database Devices shows all available devices and the current space allocated on each device.

9.	If you plan to load a backup into the selected database before using it, choose the Create for Load check box, which will create the database more rapidly. With this option the pages are not zero-initialized when the database is created. However, users other than the DBO cannot access the database until a backup is loaded into the database and the database option DBO Use Only is cleared. (In the Edit Database dialog box in the Options tab, clear the DBO Use Only check box.)

10.	To create the database immediately, click Create Now. To schedule creating the database, click Schedule.

See Also

Adding a Database Device

Modifying a Database


Modifying a Database

You can increase the space allocated for a database or its transaction log by allocating more space on its current device or on a different device. You must increase the size by at least 1 megabyte. You can shrink the size of the database to reclaim unused space.

You can also set database options and statement permissions for the databases that you have access to.

To expand a database

1.	In the Server Manager window, double-click the database to modify.

The Edit Database dialog box appears.

2.	In the Database tab, click the Expand button.

The Expand Database dialog box appears.

3.	To make the change immediately, complete the dialog box and click Expand Now. To expand the database at a specified time or on a recurring basis, click Schedule.

To recalculate or shrink a database

1.	To verify the space available in a database, in the Database tab, click the Recalculate button. You should recalculate before you shrink a database or its transaction log.

2.	To reduce the size of a database or its transaction log, in the Database tab, click the Shrink button. The Shrink Database dialog box appears and displays the minimum size the database can be reduced to.

To set database options

In the Edit Database dialog box, in the Options tab, specify the options and click OK.

See Also

Setting Database Options

Setting Statement Permissions


Setting Database Options

You can customize a database. You can set database options for user databases and the Truncate Log on Checkpoint option for the master database.

To set database options

1.	In the Server Manager window, double-click the database to modify.

The Edit Database dialog box appears.

2.	Select the Options tab.

3.	Set the appropriate options.

4.	Click OK.


Setting Statement Permissions

You can assign permissions that allow individual users or groups to perform various database tasks, such as creating databases, rules, defaults, tables, views, stored procedures, and backing up the database.

To set statement permissions

1.	In the Server Manager window, double-click the database to set permissions for.

The Edit Database dialog box appears.

2.	Select the Permissions tab.

Note that CREATE DATABASE permissions can only be set from the master database.

3.	Set the appropriate options.

4.	Click OK.


Dropping a Database

When you drop a database, that database and its objects are removed. Dropping a database frees the storage space that was allocated for it. After you drop a database, the login IDs that used that database as the default database will use master as the default database instead.

You cannot drop the master, model, or tempdb databases. You cannot drop a database that is open for reading or writing to by any user. You cannot drop a database that is participating in replication by publishing some or all of its tables.

Only the DBO and the system administrator (SA) have permission to drop databases. This permission cannot be transferred.

To drop a database

1.	From the Manage menu, choose Databases.

The Manage Databases window appears.

2.	From the graph, select the database to drop.

3.	Click Delete Database.


Adding or Modifying Database Users

Before a user can access a database, the system administrator (SA) must add the user's login ID to the SQL Server and assign the user a username for that database. The SA can also add a user to a group or alias the user to another user in the database. If a group name is not specified, the user is added only to the public group, which includes all users. The SA can modify the login ID and the group or alias of a user in SQL Server.

To add a database user

1.	In the Server Manager window, select the server and the database to add the user to.

2.	From the Manage menu, choose Users.

The Manage Users dialog box appears.

3.	Complete the dialog box and click Add.

To modify a database user

1.	In the Manage Users dialog box, expand the User Name list and select the user to modify.

2.	Complete the dialog box and click Modify.

See Also

Using Aliases

Creating Groups

Dropping a Database User


Using Aliases

You can create an alias for a database user. With an alias, a user can access the database through an already existing username. For example, aliasing several logins to the DBO username allows those users access to the DBO's permissions.

To create an alias

1.	In the Server Manager window, select the server and the database to create an alias for.

2.	From the Manage menu, choose Users.

The Manage Users dialog box appears.

3.	In the User Name box, select a username to create an alias for.

4.	Under Aliases from the Available Logins box, select a login to map to the username.

5.	Click Add.

6.	Repeat steps 4 and 5 for each login that you want to associate with the selected username.

7.	Click Modify.

To remove an alias

1.	In the Server Manager window, select the database to remove an alias from.

2.	From the Manage menu, choose Users.

The Manage Users dialog box appears.

3.	In the User Name box, select the username that you want to remove aliases from.

4.	Under Aliases from the Aliased Logins box, select the login(s) to remove from the alias.

5.	Click Remove.

6.	Click Modify.

See Also

Adding or Modifying Database Users

Manage Users Dialog Box


Dropping a Database User

Dropping a user removes the user from a database. Before dropping a user, you must drop all database objects the user owns.

To drop a database user

1.	In the Server Manager window, select the server and the database to remove a user from.

2.	From the Manage menu, choose Users.

The Manage Users dialog box appears.

3.	In the User Name box, select the username to drop.

4.	Click Drop.

See Also

Adding or Modifying Database Users


Creating Groups

Groups provide a convenient way to grant and revoke permissions to more than one user at the same time. Each user belongs to the public group, and can be placed in only one additional group at any time.

If you are using integrated security and have created groups with Windows NT, those groups are not automatically associated to database groups. If you want all members of a Windows NT group to be assigned to a database group, you must first assign explicit login IDs to all users in the Windows NT group, add those login IDs as users in the database, and then assign those users to the database group you create. Use SQL Security Manager to automatically create login IDs and a SQL Server group for a selected Windows NT group.

To create a group

1.	In the Server Manager window, select the server and the database to add a group to.

2.	From the Manage menu, choose Groups.

The Manage Groups dialog box appears.

3.	Complete the dialog box, click Add, and then click Close.

See Also

Modifying Groups

Dropping a Group


Modifying Groups

Groups can be modified by adding or removing users. Each user belongs to the public group and can be placed in only one additional group at any time. When you remove a username from a group, that user no longer has permissions assigned to the group. You cannot remove a user from the public group.

To modify a group

1.	In the Server Manager window, select the server and that database that contain the group to modify.

2.	From the Manage menu, choose Groups.

The Manage Groups dialog box appears.

3.	Complete the dialog box, click Modify, and then click Close.

See Also

Creating Groups

Dropping a Group


Dropping a Group

When you drop a group, all users in that group remain members of the public group.

To drop a group

1.	In the Server Manager window, select the server and the database that contain the group to drop.

2.	From the Manage menu, choose Groups.

The Manage Groups dialog box appears.

3.	In the Group box, select the group to drop.

4.	Click Drop and then click Close.


Querying a Database

Using Transact-SQL statements, you can query a database while performing other administrative tasks. You can configure SQL Enterprise Manager to display query results automatically, or you can choose the Results tab in the Query window to view the results.

To query a database

1.	In the Server Manager window, select the server to query.

2.	From the Tools menu, choose SQL Query Tool. Or, from the toolbar, click the SQL Query Tool button.

The Query window appears.

3.	Expand the DB box, and select the database to query.

4.	In the Query tab, type the query using Transact-SQL syntax or select a saved query from the Queries box.

For help with Transact-SQL syntax, select the syntax and press SHIFT+F1, or from the Help menu, choose Transact-SQL Help. For help with specific objects, select the object name and press ALT+F1.

5.	To execute the query, click the Execute Query button (an arrow on the toolbar pointing right) or press ALT+X.

To view query results

In the Query window, choose the Results tab.

To make the Results tab active automatically each time a query is completed

1.	In SQL Enterprise Manager, from the Tools menu choose Preferences/Configure.

The Configure SQL Enterprise Manager dialog box appears.

2.	In the Query System tab, select the Switch to Result Tab on Execute check box.

See Also

Setting Query System Options


Editing Query Results

You can cut, copy, paste, and delete the text displayed in the Results tab.

To edit query results

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool. Or, from the toolbar, click the SQL Query Tool button.

The Query window appears.

3.	In the Query tab, type or enter a saved query, and then execute the query.

4.	In the Results tab, select the text to edit. Then, from the Edit menu, choose the appropriate editing task.

See Also

Querying a Database


Saving a Query to a File

You can save a query to a file to execute at a later time.

To save a query

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool. Or, from the Toolbar, click the SQL Query Tool button.

The Query window appears.

3.	In the Query tab, type the query.

4.	Click the Save Query/Result button. Or, from the File menu, choose Save As.

Queries are saved with the default file extension .SQL. To change the file extension for the query results you are saving, in the Save File dialog box in the File Name box, type a new extension. To change the default file extension for all queries, in the Configure SQL Enterprise Manager dialog box in the Query System tab, under File Extensions change the extension.

See Also

Setting Query System Options

Saving Query Results

Querying a Database


Saving Query Results

You can save query results to a file, and you can edit the text before saving it.

To save query results

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool or from the toolbar, click the SQL Query Tool button.

The Query window appears.

3.	In the Query tab, enter a query and execute it.

4.	Select the Results tab to view the query results. With the Results tab displayed, click the Save Query/Result button. Or, from the File menu, choose Save As.

Queries are saved with the default file extension .RPT. To change the file extension for the query results you are saving, in the Save File dialog box, in the File Name box, type a new extension. To change the default file extension for all query results, in the Configure SQL Enterprise Manager dialog box, in the Query System tab, under File Extensions change the extension.


Starting a New Query

After you have executed a query, you can start a new query. Queries are listed in the Queries box. You can switch among the query windows at any time.

To start a new query

Click the New Query button.

Or

From the File menu, choose New.

Or

Type CTRL+N.


Using a Saved Query

You can execute saved queries. Verify that the Query tab is active.

To use a saved query

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool.

The Query window appears.

3.	Click the Load SQL Script button. Or, from the File menu, choose Open.

4.	Select the file and click OK.

5.	To execute the query, click the Execute Query button (an arrow pointing right on the toolbar) or press ALT+X.


Removing a Query/Result Set

You can remove a query that is listed in the Queries box of the Query window.

To remove a query and its results

1.	In the Queries box, select the query to remove.

2.	Click the Remove Current Query Set button.


Setting Query Flag and Format Options

You can set options to control how a query is processed each time you execute the query.

To set query options

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool. Or from the toolbar, click the SQL Query Tool button.

The Query window appears.

3.	Click the Query Options button.

The Query Options dialog box appears.

4.	In the Query Flags tab, select the appropriate options.

5.	Under Limits, in the Row Count box, type the number of rows the server should return before ending a query.

The default (0) returns all rows.

6.	Select the Format Options tab.

7.	Expand the Result Output Format box and select the format for results.

If you choose Other Delimiter, in the Delimiter box, specify the delimiter.

If you choose Column Aligned, to align numeric output to the right, select the Right Align Numerics check box.

8.	To display the PRINT statements output in the Results tab, select the Verbose Prints box. This option is only useful if you are running Graphical Statistics I/O.

9.	To eliminate column headers from the query results, clear the Print Headers check box.

10.	To display the first three lines of the query in the Results tab, select Output Query.

11.	Click OK.

See Also

Setting Query System Options


Searching and Replacing Text

You can use the SQL Query Tool to search for and replace text in the Query or Results tabs. You can also repeat the last search you made.

To search for text

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool. Or from the toolbar, click the SQL Query Tool button.

The Query window appears.

3.	In the Query tab, enter and then execute the query.

4.	Select the Query or Results tab.

5.	From the Edit menu, choose Find.

The Find dialog box appears.

6.	In the Find What box, type the text to find, select whether to match the case, and choose a search direction. The first text that matches the search string will be highlighted.

7.	Click Find Next.

To repeat the last search

1.	Select the Query or Results tab.

2.	From the Edit menu, choose Repeat Last Find or press F3.

To replace text

1.	Select the Query or Results tab.

2.	From the Edit menu, choose Replace.

The Replace dialog box appears.

3.	In the Find What box, type the text to find. In the Replace With box, type the new text. Select whether to match the case, and then choose a search direction.

4.	Click Find Next.

5.	To replace text, click Replace. To replace all specified text at one time, click Replace All.


Using Graphical Statistics I/O

Graphical Statistics I/O depicts the amount of disk input/output required to access data for a query. A query must be executed to obtain Statistics I/O information, which includes Scan Count, Logical Reads, and Physical Reads.

To use Graphical Statistics I/O

1.	In the Server Manager window, select the server and the database to query.

2.	From the Tools menu, choose SQL Query Tool. Or from the toolbar, click the SQL Query Tool button.

The Query window appears.

3.	In the Query tab, enter a query.

4.	Click the Display Statistics I/O button.

5.	Press ALT+X.

6.	Select the Statistics I/O tab.

To generate a text description of Statistics I/O

1.	In the Query tab, click the Query Options button.

The Query Options window appears.

2.	In the Query Flags tab, select the Show Stats I/O option.

3.	Click OK. The text description is displayed on the Results tab after the query is executed.


Scan Count

Indicates the number of times a table was accessed for information during a query. Generally, for queries on a single table, the table is scanned once. For queries on tables that are joined during processing to provide more information, the scan count indicates the number of times the table was accessed.


Logical Reads

Indicates the number of index and data pages that were required to obtain data for the query. This number is not equal to the number of rows retrieved for a table, because a page of data can contain many rows.


Physical Reads

Indicates the number of logical reads that actually resulted in data access on the disk. The difference between the number of logical reads and the number of physical reads indicates the amount of data that was cached. Tables and worktables can appear multiple times to process all the data required for the query.


Scheduling a Task

With SQL Enterprise Manager and the SQL Executive service, you can schedule server tasks, including replication, command execution, and Transact-SQL statement execution. You can schedule a task to occur one time, on a recurring schedule, or when initiated by an alert. You can also schedule a task to run immediately. For a task to run, SQL Executive must be running on the target server.

In addition, SQL Server processes automatically create and schedule tasks. The system administrator can use SQL Enterprise Manager to modify, disable, delete, and immediately run user-created and SQL Server-created tasks. Other users can manage only the tasks they own.

To schedule a task

1.	In the Server Manager window, select the server to schedule a task for.

2.	From the Server menu, choose Scheduled Tasks.

The Manage Scheduled Tasks window appears.

3.	Click the New Task button.

The New Task dialog box appears.

4.	In the Name box, type a unique name for the task.

5.	To create a task, but not enable it to run, clear the Enabled check box.

6.	In the Type box, select the type of task you are creating.

Note that if you choose TSQL, the statement is limited to 255 characters and cannot contain embedded go commands.

7.	In the Database box, select the database the task will be run against.

8.	In the Command box, type the text of the task. The text can be a valid operating system command, the filename (including path) of an .EXE file, or a Transact-SQL statement.

9.	Schedule the task.

To create the task but not schedule it for a specific time, under Schedule, select On Demand.

To run a task once, select the One Time option and in the On Date and At Time boxes, specify the date and time.

To schedule a task to recur, select Recurring.

The Auto Start option is used by replication processes to have SQL Server automatically start a task when the SQL Executive service starts.

10.	If you chose Recurring in step 9, click Change and select a schedule.

The Task Schedule dialog box appears. Set the appropriate information, and then click OK.

11.	To set options for the task, including e-mail notification, Windows NT application event log messages, and retry attempts, click Options.

The TSQL Task Options dialog box appears.

12.	Set the appropriate information, and then click OK.

Note that you cannot set retry attempts for Transact-SQL tasks.

13.	Click Add.

See Also

Tasks

Viewing Task History


Editing a Scheduled Task

You can modify information about a scheduled task, including task name, type, command information, schedule, and options. The task ID is displayed at the top of the window.

SQL Server processes that are created automatically can be modified by the system administrator. Other users can modify only the tasks they own.

To edit a scheduled task

1.	In the Server Manager window, select the server to edit a task for.

2.	From the Server menu, choose Scheduled Tasks.

The Manage Scheduled Tasks window appears.

3.	In the Task List tab, select the task.

4.	Click the Edit Task button, or right-click the selected task and from the shortcut menu that appears, choose Edit.

The Edit Task dialog box appears.

5.	Change the appropriate information.

6.	Click Modify.

See Also

New/Edit Task Dialog Box

Tasks

Viewing Task History


Deleting a Scheduled Task

You can delete or temporarily disable a scheduled task.

To delete a scheduled task

1.	In the Server Manager window, select the server to delete a task from.

2.	From the Server menu, choose Scheduled Tasks.

The Manage Scheduled Tasks window appears.

3.	In the Task List tab, select the task to remove.

4.	Click the Delete Task button, or right-click the selected task and from the shortcut menu that appears, choose Delete.

To disable a scheduled task

1.	In the Server Manager window, select the server to disable a task for.

2.	From the Server menu, choose Scheduled Tasks.

The Manage Scheduled Tasks window appears.

3.	In the Task List tab, select the task to disable.

4.	Click the Edit Task button.

The Edit Task dialog box appears.

5.	Clear the Enabled check box.

Task information will be retained, but SQL Executive will not execute the task.

6.	Click Modify.

See Also

New/Edit Task Dialog Box

Tasks

Viewing Task History


Viewing Task History

You can view information about a task. Information includes the date the task was last run, its status, whether e-mail notification was sent, the duration of the last run, and messages encountered while running the task.

To view task history

1.	In the Server Manager window, select the server to view task history for.

2.	From the Server menu, choose Scheduled Tasks.

The Manage Scheduled Tasks window appears.

3.	In the Task List tab, select the task to view history for.

4.	Click the Task History button, or right-click the selected task and from the shortcut menu that appears, choose History.

The Task History dialog box appears.

5.	To clear the task history information, click Clear All. (Only the task owner can do this.)


Viewing a List of Scheduled Tasks Currently Running

You can view a list of tasks that are currently running for a selected server.

To view a list of currently running scheduled tasks

1.	In the Server Manager window, select the server to view tasks for.

2.	From the Server menu, choose Scheduled Tasks.

The Manage Scheduled Tasks window appears.

3.	Select the Running Tasks tab.

Queued tasks are also shown in the Running Tasks tab. For subsystems (task types) other than Transact-SQL, a task may be queued if it is scheduled to run but no free threads are available in the subsystem.


Creating a Trigger

A trigger is a stored procedure that is automatically invoked when a database changes. Triggers are frequently used to maintain the integrity of a database. A trigger executes automatically when a user attempts to modify data on a table specified in the trigger. Only one insert, one update, and one delete trigger can exist per table. If a trigger exists for the table and you create another trigger, the existing trigger is replaced. You can also print a trigger.

To create a trigger

1.	In the Server Manager window, select the server and the database to create a trigger for.

2.	From the Manage menu, choose Triggers.

The Manage Triggers window appears.

3.	In the Table box, select the table to create the trigger for.

4.	In the Trigger box, select <new>.

5.	Complete the Transact-SQL syntax in the window as appropriate, adding a trigger name and the text.

For help on Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE TRIGGER.

6.	 To save the new trigger, click the Execute button (the right-pointing arrow on the toolbar).

7.	To print the trigger, from the toolbar, click the Print icon.

See Also

Modifying a Trigger

Dropping a Trigger


Modifying a Trigger

You can change an existing trigger. Also, you can print the trigger.

To modify a trigger

1.	In the Server Manager window, select the server and the database to modify a trigger for.

2.	From the Manage menu, choose Triggers.

The Manage Triggers window appears.

3.	In the Table box, select the table that contains the trigger to modify.

4.	In the Trigger box, select the trigger to modify.

5.	Modify the Transact-SQL syntax in the window as appropriate.

For help on Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE TRIGGER.

6.	To save the modified trigger, click the Execute button (the right-pointing arrow on the toolbar).

7.	To print the trigger, from the toolbar, click the Print icon.

See Also

Creating a Trigger

Dropping a Trigger


Dropping a Trigger

You can remove an existing trigger.

To drop a trigger

1.	In the Server Manager window, select the server and the database to drop a trigger from.

2.	From the Manage menu, choose Triggers.

The Manage Triggers window appears.

3.	In the Table box, select the table to drop the trigger from.

4.	In the Trigger box, select the trigger to drop.

5.	From the Object menu, choose Drop. The Drop Objects dialog box appears.

6.	Click Drop All.

See Also

Creating a Trigger

Modifying a Trigger


Creating a Stored Procedure

A stored procedure is a collection of SQL statements and optional control-of-flow language. Stored procedures are compiled the first time they are executed; their execution plans are stored so that subsequent execution is fast. Once defined, a stored procedure can be executed by name. You can also print a selected stored procedure.

To create a stored procedure

1.	In the Server Manager window, select the server and the database to create a stored procedure for.

2.	From the Manage menu, choose Stored Procedures.

The Manage Stored Procedures window appears.

3.	In the Procedure box, select <new>.

4.	Complete the Transact-SQL syntax in the window as appropriate, adding a stored procedure name and text.

For help on Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE PROCEDURE.

5.	Click the Execute button (the right-pointing arrow on the toolbar) to save the stored procedure.

6.	Click the Print icon at the top of the window to print the stored procedure.

See Also

Modifying a Stored Procedure

Dropping a Stored Procedure

Managing Extended Stored Procedures


Modifying a Stored Procedure

You can change the Transact-SQL language statements in a stored procedure. You can also print a selected stored procedure.

To modify a stored procedure

1.	In the Server Manager window, select the server and the database to modify a stored procedure for.

2.	From the Manage menu, choose Stored Procedures.

The Manage Stored Procedures window appears.

3.	In the Procedure box, select the stored procedure to modify.

4.	Modify the Transact-SQL syntax in the window as appropriate.

For help on Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE PROCEDURE.

5.	To save the stored procedure, click the Execute button (the right-pointing arrow on the toolbar).

6.	To print the stored procedure, from the toolbar, click the Print icon.

See Also

Creating a Stored Procedure

Dropping a Stored Procedure


Dropping a Stored Procedure

You can drop a stored procedure.

To drop a stored procedure

1.	In the Server Manager window, select the server and the database to drop a stored procedure from.

2.	From the Manage menu, choose Stored Procedures.

The Manage Stored Procedures window appears.

3.	In the Procedure box, select the stored procedure to drop.

4.	From the Object menu, choose Drop. The Drop Objects dialog box appears.

5.	Click Drop All.

See Also

Creating a Stored Procedure

Modifying a Stored Procedure

Managing Extended Stored Procedures


Creating a View

A view is another way of looking at data in one or more tables. A view is usually a subset of columns from one or more tables in a database. You can also print a selected view.

To create a view

1.	In the Server Manager window, select the server and the database to create a view for.

2.	From the Manage menu, choose Views.

The Manage Views window appears.

3.	In the View box, select <new>.

4.	Complete the Transact-SQL syntax in the window as appropriate, adding a view name and text.

For help on Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE VIEW.

5.	Click the Execute button (the right-pointing arrow on the toolbar) to save the view.

6.	To print the view, from the toolbar, click the Print icon.

See Also

Modifying a View

Dropping a View


Modifying a View

You can change a view by adding or removing columns, or by changing the SELECT statement on which an existing view is based. You can also print a selected stored procedure.

To modify a view

1.	In the Server Manager window, select the server and the database to modify a view for.

2.	From the Manage menu, choose Views.

The Manage Views window appears.

3.	In the View box, select the name of the view to modify.

4.	Modify the Transact-SQL syntax in the window as appropriate.

For help on Transact-SQL syntax, from the Help menu, choose Transact-SQL Help and then search for CREATE VIEW.

5.	To save the view information, click the Execute button (the right-pointing arrow on the toolbar).

6.	To print the view, from the toolbar, click the Print icon.

See Also

Creating a View

Dropping a View


Dropping a View

You can drop a view.

To drop a view

1.	In the Server Manager window, select the server and the database to drop a view from.

2.	From the Manage menu, choose Views.

The Manage Views window appears.

3.	In the View box, select the name of the view to drop.

4.	From the Object menu, choose Drop. The Drop Objects dialog box appears.

5.	Click Drop All.

See Also

Creating a View

Modifying a View


Creating an Index

Indexes are created on columns to speed the process of retrieving data and to impose uniqueness constraints. Two types of indexes can be created: clustered and nonclustered. You must be the table owner to create an index.

You can create indexes while creating or modifying a table by creating a primary key or a unique constraint. For help on how to create a primary key or a unique constraint, see Creating a Table.

You can also create indexes by using the Manage Indexes dialog box.

To create an index using the Manage Indexes dialog box

1.	In the Server Manager window, select the server and the database to create an index for.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table to create an index for.

4.	In the Index box, select (New Index) and then type a name for the index.

5.	Under Available Columns in Table, select the table column(s) to create the index(es) for and then click Add.

To remove a column, under Columns in Index [Key], select the column to remove and click Remove.

6.	Under Index Attributes, select the appropriate attributes for the index. Each table can have only one clustered index.

You can adjust the Fill Factor % box to see the estimated size of the index (shown under Index Size).

7.	Click Build. You can build the index immediately or you can schedule the task.

See Also

Modifying an Index


Modifying an Index

You can change columns that are indexed or the index options. You can rebuild an index at any time. When an index is rebuilt, SQL Server drops the existing index and creates the new one. You can also view and update distribution statistics for an index.

You must be the table owner to modify an index. You cannot modify primary key or unique constraints in the Manage Indexes dialog box.

To modify an index

1.	In the Server Manager window, select the server and the database to modify an index for.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table that contains the index to modify.

4.	In the Index box, select the index to modify.

5.	Make the appropriate modifications.

You can adjust the entry in the Fill Factor % box to see the estimated size of the index (shown under Index Size).

6.	Click Rebuild. You can rebuild the index immediately, or you can schedule the task.

See Also

Creating an Index


Renaming an Index

You can rename an index that you have created.

To rename an index

1.	In the Server Manager window, select the server and the database to rename an index for.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table to rename an index for.

4.	In the Index box, select the index to rename.

5.	Click Rename.

The Rename Index dialog box appears.

6.	In the New Index Name box, type a name for the index.

7.	Click OK.


Updating Index Statistics

You can update statistics and information about the distribution of key values in specified indexes. Information for primary key and unique constraints can be updated while you create or modify a table. For more information, see Creating a Table.

You can also update information for indexes by using the Manage Indexes dialog box.

To update index statistics from the Manage Indexes dialog box

1.	In the Server Manager window, select the server and the database to update index statistics for.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table that contains the index to update statistics for.

4.	In the Index box, select the index to update statistics for.

5.	Click Distribution.

The Index Distribution Statistics dialog box appears.

6.	Click Update.

The Update Distribution Statistics dialog box appears, in which you can update the index statistics immediately or schedule the task.


Viewing Index Distribution Information

You can view information about the number of rows in a table, the number of steps in an index, the average number of times a row was scanned, and the date of the last update. You can also view the distribution steps for the index, the statistics for the update index distribution, and distribution information for primary key and UNIQUE constraints.

To view index distribution information

1.	In the Server Manager window, select the server and the database to view index distribution information for.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table that contains the index to view distribution information for.

4.	In the Index box, select the index to view distribution information for.

5.	Click Distribution.

The Index Distribution Statistics dialog box appears.

See Also

Updating Index Statistics


Checking the Size of an Index

You can update information about the size of an index for more accurate index size.

To check the size of an index

1.	In the Server Manager window, select the server and the database that contains the index to check the size of.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table that contains the index to check the size of.

4.	In the Index box, select the index.

5.	Click Check Size.

The Check Actual Size dialog box appears. You can check the size immediately, or you can schedule the task.

See Also

Updating Index Statistics


Dropping an Index

When you remove an index, SQL Server removes that index from the database and reclaims the associated storage space. If you have created a primary key or unique constraint while creating or modifying a table, you can drop the constraint using the Manage Tables window.

To drop an index

1.	In the Server Manager window, select the server and the database that contains the index to drop.

2.	From the Manage menu, choose Indexes.

The Manage Indexes dialog box appears.

3.	In the Table box, select the table that contains the index to drop.

4.	In the Index box, select the index to drop.

5.	Click Remove.

The Index Removal dialog box appears. You can drop the index immediately, or you can schedule the task.


Granting Object Permissions

Object permissions regulate the use of certain statements on certain database objects. You can grant permissions to users and groups for tables, views, and stored procedures. These permissions will be added to existing permissions already granted to the user or group.

You can grant object permissions by user and group, and by object. You can grant permissions for only objects you own.

To grant object permissions by user and group

1.	In the Server Manager window, select the server and the database to grant object permissions for.

2.	From the Object menu, choose Permissions.

The Object Permissions dialog box appears.

3.	Select the By User tab.

4.	Select the object to assign permission for and then select permissions to grant for that object. Repeat for each user or group to grant permission to.

5.	Click Set.

To grant object permissions by object

1.	In the Server Manager window, select the server and the database to grant object permissions for.

2.	From the Object menu, choose Permissions.

The Object Permissions dialog box appears.

3.	Select the By Object tab.

4.	Select the object to assign permission for, select the user or group to grant permission to, and select permissions to grant. Repeat for each object to grant permission for.

5.	Click Set.

See Also

Revoking Object Permissions

Viewing Object Permissions


Revoking Object Permissions

You can withdraw object permissions from a user. You can revoke those permissions by user and group, or by object.

To revoke object permissions by user and group

1.	In the Server Manager window, select the server and the database that contains the object permissions to revoke.

2.	From the Object menu, choose Permissions.

The Object Permissions dialog box appears.

3.	Select the By User tab.

4.	Select the user or group to withdraw permission from, select the object, and then select the permissions to revoke. Repeat for each user or group to revoke permission from.

5.	Click Set.

To revoke object permissions by object

1.	In the Server Manager window, select the server and the database that contains the object permissions to revoke.

2.	From the Object menu, choose Permissions.

The Object Permissions dialog box appears.

3.	Select the By Object tab.

4.	Select the object to revoke permissions for, select a user or group, and then select the permissions to revoke. Repeat for each object to revoke permissions for.

5.	Click Set.

See Also

Granting Object Permissions

Viewing Object Permissions


Viewing Object Permissions

You can view existing object permissions by user or group, or by object.

To view object permissions by user or group

1.	In the Server Manager window, select the server and the database that contains the object permissions to view.

2.	From the Object menu, choose Permissions.

The Object Permissions dialog box appears.

3.	Select the By User tab.

4.	In the User/Group box, select a user or group to view permissions for.

Existing object permissions for this user or group are displayed.

5.	Repeat step 4 for each user or group to view permissions for.

To review object permissions by object

1.	In the Server Manager window, select the server and the database that contains the object permissions to view.

2.	From the Object menu, choose Permissions.

The Object Permissions dialog box appears.

3.	Select the By Object tab.

4.	In the Object box, select the object to view permissions for.

Permissions granted to users or groups are displayed below.

5.	Repeat step 4 for each object to view permissions for.

See Also

Granting Object Permissions

Revoking Object Permissions


Generating SQL Scripts

You can generate SQL scripts for an entire database or for individual database objects. SQL scripts are the text of statements that are used to create database objects. You can run SQL scripts against other databases to re-create the database objects. You can also generate scripts to create a record of how a database was created.

To generate SQL scripts

1.	In the Server Manager window, select the server and the database to generate SQL scripts for.

2.	From the Object menu, choose Generate SQL Scripts.

The Generate SQL Scripts dialog box appears.

3.	Complete the dialog box.

4.	To generate the script, click Script.

The Save As dialog box appears.

5.	Name the script and specify a directory to store the script in.

6.	Click OK.


Viewing Object Dependencies

You can view the objects that a selected object depends on, and the objects that depend on the selected object.

To view object dependencies

1.	In the Server Manager window, select the object to view dependencies for.

2.	From the Object menu, choose Dependencies.

The Object Dependencies dialog box appears.

3.	To view another object's dependencies, in the Subject Object box select the object to view dependencies for.

See Also

Dropping Objects

Renaming Objects


Dropping Objects

You can remove an object if you have permission for that object. You can drop multiple objects at one time by selecting them in the Server Manager window.

To drop an object

1.	In the Server Manager window, select the object(s) to drop. You can select multiple objects by using SHIFT+Click or CTRL+Click.

2.	From the Object menu, choose Drop.

The Drop Objects dialog box appears.

3.	Click Drop All.

See Also

Viewing Object Dependencies

Renaming Objects


Renaming Objects

You can change the name of any object, except system tables and system objects. When you change the name of an object, you must rebuild the views, stored procedures, and triggers that reference that object.

To rename an object

1.	In the Server Manager window, select the object to rename.

2.	From the Object menu, choose Rename.

The Rename Object dialog box appears.

3.	In the New Name box, type a name for the object.

4.	Click OK.

See Also

Viewing Object Dependencies

Dropping Objects


Creating a Rule

You can determine which data can be entered in a particular column of a table by creating a rule. You can bind the rule to a user-defined datatype, so that columns that use the datatype will automatically have the rule.

In addition to rules, you can create constraints while creating and modifying a table. Constraints will enforce rules for a column. For details about creating constraints, see Creating a Table.

To create a rule

1.	In the Server Manager window, select the server and the database that contains the table column to create a rule for.

2.	From the Manage menu, choose Rules.

The Manage Rules dialog box appears.

3.	Select the Rules tab.

4.	In the Rule box, type a name for the rule (for example, Age).

5.	In the Description box, type the condition for the rule (for example, @age > 0).

6.	Click Add.

See Also

Binding a Rule to a Column

Binding a Rule to a Datatype

Dropping a Rule


Binding a Rule to a Column

You can bind a rule to a table column so that data entered into the column adheres to that rule or is not added.

To bind a rule to a column

1.	In the Server Manager window, select the server and the database that contains the table column to bind the rule to.

2.	From the Manage menu, choose Rules.

The Manage Rules dialog box appears.

3.	Select the Column Bindings tab.

4.	In the tab, specify the table that contains the column to bind a rule to, the column, and the rules.

5.	Click Bind.

See Also

Creating a Rule

Unbinding a Rule From a Column


Binding a Rule to a Datatype

You can bind a rule to a user-defined datatype. You can also specify that the rule be bound only to future columns the user-defined datatype will be associated with.

To bind a rule to a datatype

1.	In the Server Manager window, select the server and the database that contains the datatype to bind a rule to.

2.	From the Manage menu, choose Rules.

The Manage Rules dialog box appears.

3.	Select the Datatype Bindings tab.

4.	In the tab, select the datatype to bind the rule to, and select the rule.

5.	Click Bind.

See Also

Creating a Rule

Unbinding a Rule from a Datatype


Unbinding a Rule From a Column

You can unbind a rule from a table column.

To unbind a rule from a column

1.	In the Server Manager window, select the server and the database that contains the table column to unbind the rule from.

2.	From the Manage menu, choose Rules.

The Manage Rules dialog box appears.

3.	Select the Column Bindings tab.

4.	In the tab, select the table that contains the column to unbind the rule from and the column.

5.	Under Binding, select (none).

6.	Click Bind.

See Also

Creating a Rule

Binding a Rule to a Column


Unbinding a Rule From a Datatype

You can unbind a rule from a user-defined datatype. If you unbind the rule with the Future Only option selected, the rule will not be bound to future columns created with that user-defined datatype, but the rule will continue to be bound to existing columns.

To unbind a rule from a datatype

1.	In the Server Manager window, select the server and the database that contains the datatype to unbind the rule from.

2.	From the Manage menu, choose Rules.

The Manage Rules dialog box appears.

3.	Select the Datatype Bindings tab.

4.	In the tab, select the datatype to unbind the rule from.

5.	Under Binding, select (none).

6.	Click Bind.

See Also

Creating a Rule

Binding a Rule to a Datatype


Dropping a Rule

You can remove a rule after you unbind it from all columns and user-defined datatypes.

To drop a rule

1.	In the Server Manager window, select the server and the database that contains the column or datatype to drop the rule from.

2.	From the Manage menu, choose Rules.

The Manage Rules dialog box appears.

3.	Select the Rules tab.

4.	In the Rule box, select the rule to drop.

5.	Click Drop.

See Also

Creating a Rule


Creating a Default

You can create a default for a column or user-defined datatype that causes SQL Server to automatically supply a specified value for the column or the user-defined datatype if the user does not explicitly provide the value. You can create a default while creating or modifying a table. For more information about creating a default while creating or modifying a table, see Creating a Table.

You can also create a default by using the Manage Defaults dialog box.

To create a default using the Manage Defaults dialog box

1.	In the Server Manager window, select the server and the database that contains the column or datatype to create a default for.

2.	From the Manage menu, choose Defaults.

The Manage Defaults dialog box appears.

3.	Select the Defaults tab.

4.	In the Default box, type a name for the default (for example, datedefault).

5.	In the Description box, type the condition for the default (for example, getdate( )).

6.	Click Add.

See Also

Binding a Default to a Column

Binding a Default to a Datatype

Dropping a Default


Binding a Default to a Column

You can bind a default to a table column. When no data is entered in that column, SQL Server supplies the default value.

To bind a default to a column

1.	In the Server Manager window, select the server and the database that contains the table column to bind a default to.

2.	From the Manage menu, choose Defaults.

The Manage Defaults dialog box appears.

3.	Select the Column Bindings tab.

4.	In the tab, specify the table that contains the column to bind the default to, the column, and the default.

5.	Click Bind.

See Also

Creating a Default

Unbinding a Default From a Column


Binding a Default to a Datatype

You can bind a default to a user-defined datatype. You can also specify that the default be bound only to future columns the user-defined datatype will be associated with.

To bind a default to a datatype

1.	In the Server Manager window, select the server and the database that contains the datatype to bind the default to.

2.	From the Manage menu, choose Defaults.

The Manage Defaults dialog box appears.

3.	Select the Datatype Bindings tab.

4.	In the tab, specify the datatype to bind the default to and the default.

5.	Click Bind.

See Also

Creating a Default

Unbinding a Default From a Datatype


Unbinding a Default From a Column

You can unbind a default from a table column.

To unbind a default from a column

1.	In the Server Manager window, select the server and the database that contains the table column to unbind the default from.

2.	From the Manage menu, choose Defaults.

The Manage Defaults dialog box appears.

3.	Select the Column Bindings tab.

4.	In the tab, specify the table that contains the column to unbind the default from and the column.

5.	Under Binding, select (none).

6.	Click Bind.

See Also

Creating a Default

Binding a Default to a Column


Unbinding a Default From a Datatype

You can unbind a default from a user-defined datatype. If you unbind the default with the Future Only option selected, the default will not be bound to future columns that are created with that user-defined datatype, but will remain bound to existing columns.

To unbind a default from a datatype

1.	In the Server Manager window, select the server and the database that contains the datatype to unbind the default from.

2.	From the Manage menu, choose Defaults.

The Manage Defaults dialog box appears.

3.	Select the Datatype Bindings tab.

4.	In the tab, select the datatype to unbind the default from.

5.	Under Binding, select (none).

6.	Click Bind.

See Also

Creating a Default

Binding a Default to a Datatype


Dropping a Default

You can drop a default after you unbind it from all columns and user-defined datatypes.

To drop a default

1.	In the Server Manager window, select the server and the database that contains the column or datatype to unbind a default from. Or double-click the default to drop.

The Manage Defaults dialog box appears.

2.	In the Defaults tab, in the Default box, select the default to drop.

3.	Click Drop.

See Also

Creating a Default


Creating User-Defined Datatypes

You can create a user-defined datatype to specify what type of data a column can contain. You can then bind rules and defaults to the datatype.

To create a user-defined datatype

1.	In the Server Manager window, select the server and the database to create a user-defined datatype for.

2.	From the Manage menu, choose User-Defined Datatypes.

The Manage User-Defined Datatypes dialog box appears.

3.	In an empty row, complete the column boxes. Repeat for each new datatype.

4.	Click Apply Now or OK.

See Also

Viewing User-Defined Datatype Information

Dropping a User-Defined Datatype


Viewing User-Defined Datatype Information

You can view information about columns currently associated with a specified user-defined datatype.

To view user-defined datatype information

1.	In the Server Manager window, double-click the user-defined datatype to view information for.

The Manage User-Defined Datatypes dialog box appears.

2.	Select the datatype to view information for, and then click Info.

The User Datatype Info dialog box appears.

See Also

Creating User-Defined Datatypes

Dropping a User-Defined Datatype


Dropping a User-Defined Datatype

You can drop a user-defined datatype. However, you cannot drop a user-defined datatype already in use in a table.

To drop a user-defined datatype

1.	In the Server Manager window, double-click the user-defined datatype to drop.

The Manage User-Defined Datatypes dialog box appears.

2.	Select the datatype to drop.

3.	Click Drop.

See Also

Creating User-Defined Datatypes

Viewing User-Defined Datatype Information


Viewing Alerts

You can view information about alerts, including the alert name, whether the alert is enabled, whether the alert is based on an error number or a severity level number, and when the alert last occurred. You can also view how alert notification is to be handled, the task associated with the alert, and the number of times the alert occurred.

To view alert information

1.	In the Server Manager window, select the server to view alerts for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	To view alert information, select the Alerts tab.

See Also

Alerts Overview

Creating an Alert

Deleting an Alert


Creating an Alert

With SQL Enterprise Manager and SQL Executive, you can set alerts on errors that occur in SQL Server. If a specified error occurs, SQL Enterprise Manager will respond automatically to that error by running a defined task, and/or by sending an e-mail and/or pager message to a specified operator.

The alerts capability is supported for Microsoft SQL Server version 6.0 or later. You must be the system administrator to manage alerts.

To create an alert

1.	In the Server Manager window, select the server to create an alert for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	Select the Alerts tab.

4.	Click the New Alert button.

The New Alert dialog box appears.

5.	Complete the dialog box.

6.	Click OK.

See Also

Alerts Overview

Editing an Alert

Deleting an Alert


Editing an Alert

You can change information about an alert, including whether it is enabled, which operators to notify, and the method used to send a response notification. You can also redefine the alert or view information about the most recent alert occurrences.

To edit an alert

1.	In the Server Manager window, select the server to edit an alert for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	In the Alerts tab, select the alert to edit.

4.	Click the Edit Alert button, or right-click the selected alert and from the shortcut menu that appears, choose Edit.

The Edit Alert dialog box appears.

5.	Change the appropriate information.

6.	Click OK.

See Also

Alerts Overview

Deleting an Alert


Deleting an Alert

You can delete an alert, or you can temporarily disable an alert.

To delete an alert

1.	In the Server Manager window, select the server to delete an alert from.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	In the Alerts tab, select the alert to remove.

4.	Click the Delete Alert button, or right-click the selected alert and from the shortcut menu that appears, choose Delete.

To temporarily stop an alert from occurring

1.	In the Server Manager window, select the server to disable an alert for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	In the Alerts tab, select the alert to drop.

4.	Click the Edit Alert button.

The Edit Alert dialog box appears.

5.	Clear the Enabled check box.

6.	Click OK.

See Also

Alerts Overview

Creating an Alert


Viewing Operators

You can view information about the operators. Operators are the people designated to receive an alert notification defined for a server. You can view the operator name, whether the operator is enabled for alert notifications, the operator e-mail address and pager number, and the last e-mail and/or pager notification the operator received.

To view operator information

1.	In the Server Manager window, select the server to view operator information for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	To view information about operators, select the Operators tab.

See Also

Creating an Operator

Deleting an Operator


Creating an Operator

Operators are notified of alerts through e-mail and/or a pager (via e-mail). When you create an operator, you include an e-mail address, a pager e-mail name, and the schedule of times the operator is available to respond to a notification. In addition, you can assign specific alerts to an operator.

To create an operator

1.	In the Server Manager window, select the server to create an operator for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	Select the Operators tab.

4.	Click the New Operator button.

The New Operator dialog box appears.

5.	Complete the dialog box.

6.	Click OK.

See Also

Editing Operator Information

Deleting an Operator


Editing Operator Information

You can modify information for an established operator. You can change the operator name, whether the operator is enabled to receive alert information, the operator's e-mail address and pager e-mail name, the operator schedule, and the alerts assigned to that operator. You can also view information about the most recent notifications sent to the operator.

To edit operator information

1.	In the Server Manager window, select the server to edit operator information for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	Select the Operators tab.

4.	Select the operator to modify information about.

5.	Click the Edit Operator button, or right-click the selected operator and from the shortcut menu that appears, choose Edit.

The Edit Operator dialog box appears.

6.	Modify the appropriate information.

7.	Click OK.

See Also

Creating an Operator

Deleting an Operator


Deleting an Operator

You can remove an operator, or you can temporarily disable an operator from receiving alert notifications.

To delete an operator

1.	In the Server Manager window, select the server to remove an operator from.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	Select the Operators tab.

4.	Select the operator to delete.

5.	Click the Delete Operator button, or right-click the selected operator and from the shortcut menu that appears, choose Delete.

To temporarily stop an operator from receiving alerts

1.	In the Server Manager window, select the server to remove an operator from.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	Select the Operators tab.

4.	Select the operator.

5.	Click the Edit Operator button.

The Edit Operator dialog box appears.

6.	Clear the Enabled check box.

7.	Click OK.

See Also

Creating an Operator

Editing Operator Information


Setting Alert Engine Options

Alert engine defaults include designating a fail-safe operator and specifying an unhandled event-forwarding server. A fail-safe operator is a person who is notified if all attempts to notify other operators via pager fail. An unhandled event-forwarding server allows you to set alerts on one main server to receive SQL Server Windows NT application event logs forwarded by other servers. You can also specify the format of the To, CC, and Subject lines of pager e-mail messages by defining templates.

To set alert engine options

1.	In the Server Manager window, select the server to set alert engine options for.

2.	From the Server menu, choose Alerts/Operators.

The Manage Alerts and Operators window appears.

3.	From the Alerts tab, click the Alert Engine Options button.

The Alert Engine Options dialog box appears.

4.	To designate a fail-safe operator, select the Fail-Safe tab, select the operator to notify, and then specify the method to use to notify the operator.

5.	To specify an unhandled event-forwarding server, select the server to receive forwarded events, and specify the type of events to forward to that server.

6.	Click OK.

See Also

Alerts Overview


Creating a Table

A table contains database data. When you create a table, you name its columns and supply a datatype for each column. You also specify a primary key, foreign keys, whether the table has an identity column, and UNIQUE or CHECK constraints.

SQL Server can have as many as 2 billion tables per database and 250 columns per table. The number of rows and the total size of a table are limited only by the storage space that is available.

To create a table

1.	In the Server Manager window, select the server and the database to create a table for.

2.	From the Manage menu, choose Tables.

The Manage Tables window appears.

3.	In the Table box, select <new> and then complete the Column Name, Datatype, Size, Nulls, and Default columns. The column name must follow the rules for identifiers and must be unique to a table.

4.	To specify the primary key, foreign keys, and unique and check constraints, click the Advanced Features button.

5.	To save the new table, click the Save Table button.

The Specify Table Name dialog box appears.

6.	In the New Table Name box, type a name for the table.

7.	Click OK.

See Also

Modifying a Table

Dropping a Table


Modifying a Table

You can add new columns to an existing table, rename a table column, add a column default, or create unique constraints or check constraints. You can also add or remove primary and foreign keys.

To modify a table

1.	In the Server Manager window, select the server and the database to modify a table for.

2.	From the Manage menu, choose Tables.

The Manage Tables window appears.

3.	In the Table box, select the name of the table to modify.

4.	Modify the appropriate information.

5.	Click the Save Table button.

See Also

Creating a Table

Dropping a Table


Dropping a Table

Dropping a table removes the table, its contents, and all indexes and permissions associated with the table. You must own the table or database to drop it. You cannot drop a table while it is being read or written to by a user or a front-end program.

To drop a table

1.	In the Server Manager window, select the server and the database to drop a table from.

The Manage Tables window appears.

2.	In the Table box, select the table to drop.

3.	From the Object menu, choose Drop.

The Drop Objects dialog box appears.

4.	Click Drop All.

See Also

Creating a Table

Modifying a Table


Running a Task Immediately

A task in the task list can be run immediately by the task owner. For the task to run, the SQL Executive service must be running on the target server.

To run a task immediately

1.	In the Task List, select the task to run.

2.	Click the Run Task button, or right-click the selected task and from the shortcut menu that appears, choose Run.

See Also

Scheduling a Task

Editing a Scheduled Task

Deleting a Scheduled Task


Alerts Overview

With SQL Enterprise Manager and SQL Executive, you can set alerts on specified SQL Server events. If a specified event occurs, SQL Executive will automatically respond by running a task that you have defined or by sending an e-mail and/or a pager message (via e-mail) to an operator you have specified.

If the proper SQL Server options are set, SQL Server events are written to the Windows NT application event log. SQL Executive constantly monitors the Windows NT application event log for events from SQL Server. When an event occurs, SQL Executive compares the event details against the alerts previously defined by the SQL Server administrator. If SQL Executive finds a match, it carries out the defined response.

When you create an alert, you can specify that SQL Executive respond by sending e-mail and/or pager notifications to one or more operators. You can also specify that SQL Executive run a task, if appropriate. The task can be a Transact-SQL command, a batch file, or a Windows NT program.

If you use paging as a notification method, Microsoft Mail (provided with Windows NT) must be configured to send an e-mail that results in a page being sent. To use e-mail or pager notifications, you must be running Microsoft Mail on the same computer as SQL Server. For information on setting up Microsoft Mail, see your manuals for Microsoft Windows NT and the Microsoft SQL Server Administrator's Companion in SQL Server Books Online.

E-mail interfaces to pager services are provided by many telecommunications companies and generally require only the ability to route e-mail messages (for example, using Microsoft Mail's External Mail program) to a post office at the pager provider's site. For more information, contact your telecommunications provider.

SQL Server events can be handled by the local SQL Executive service or can be forwarded (by the local SQL Executive service) to the Windows NT application event log on another computer that is running SQL Server version 6.0 or later. SQL Server events can also be handled both locally and remotely: for example, some events are processed locally and some are processed remotely.

For more information on alerts, and on tips and troubleshooting, see the Microsoft SQL Server Administrator's Companion.

See Also

Alerts

Editing an Alert

Deleting an Alert

Setting Alert Engine Options


Register Server Dialog Box

Use this dialog box to register a server in SQL Enterprise Manager. Once a server is registered, its name appears in the Server Manager window and you can perform tasks for that server. For more information, choose one of the following:

 Server

 Login Information

 Server Group

 Display Server Status in Server Manager

 Register

 Remove

 Servers

 Groups

See Also

Manage Server Groups Dialog Box

Server Manager Window


Server

Specifies the server name. The server must already be installed, and you must have permission to access the server. All servers you have registered are listed in the Server box. If you are running both 4.2x and 6.x SQL Servers at the same time on the same machine, the servers must use different names to be supported by SQL Enterprise Manager.

SQL Enterprise Manager works with SQL Server versions 4.2x and later. However, to use SQL Enterprise Manager with SQL Server version 4.2x, you must first load the SQL script SQLOLE42.SQL into the 4.2x server. You can find a copy of this script in the \INSTALL directory of the computer that contains SQL Server version 6.0 or later. Note that not all features of SQL Enterprise Manager are enabled for use with SQL Server version 4.2x.


Login Information

Specifies the login information SQL Enterprise Manager should use when logging in to the server.

Use Trusted Connection

Uses Windows NT security to validate the user; a password is not necessary. This option requires SQL Server to be configured for integrated or mixed security.

Use Standard Security

Uses standard security for the server. A login ID and a password are required to connect to the server in the Server Manager window. SQL Enterprise Manager stores the login ID and the password. You need not provide them each time you connect to the server.


Server Group

Specifies a group for the server. Server groups provide a convenient way to organize servers for administration. If you do not select a group, the server becomes a member of the default group (SQL Server 6.5). You can create a new group by clicking the Groups button.


Groups

Displays the Manage Server Groups dialog box, which is used to add a server group.


Display Server Status in Server Manager

Displays the status of the server (started, paused, stopped, or undetermined) in the Server Manager window. To set the polling interval for the status information, from the Tools menu, choose Preferences/Configure. Note that polling uses the Windows NT Service Control Manager, which is unavailable on Windows 95. To not display the status, clear the check box.


Register

Registers the server with SQL Enterprise Manager. The server is displayed in the Server Manager window.

If you receive the message "Unable to Connect to Server. Register anyway?" the server you are registering may not be started or the login information you provided is invalid.

Select OK to register the server. From the Server Manager window, right-click the server and from the shortcut menu, choose start to administer the server.


Remove

Removes the server from the list of servers in the Server Manager window. When you remove a server, you cannot use SQL Enterprise Manager to administer that server.


Servers

Displays the Select Server dialog box, which lists the servers in your domain. (Note that you cannot list servers on Windows 95.)


Manage Server Groups Dialog Box

Use this dialog box to add, rename, or remove a server group. Server groups provide a convenient way to organize SQL Servers in the Server Manager window. For more information, choose one of the following:

 Name

 Level

 Add

 Remove

 Rename


Name

Specifies the name of the server group. To create a server group, type the name of the new group. You can create more than one group with the same name.


Level

Specifies whether the group will appear at the top level of the tree in the Server Manager window or as a subgroup of another server group. To create a subgroup, select Sub-Group Of and then select the group the server group you are creating will be a subgroup of.


Add

Adds the group.


Remove

Removes the group. To remove a group, you must remove servers and subgroups from that group first.


Rename

Changes the name of the group selected in the Level box to the name you type in the Name box.


Server Options Tab

Use this tab to modify server options. For more information, choose one of the following:

 Root Directory

 Master Database Path

 Error Log Path

 Auto Start Server at Boot Time

 Auto Start Executive at Boot Time

 Auto Start Mail Client

 Auto Start License Logging

 Windows NT Event Logging

 Performance Monitor Integration

 xp_cmdshell - Use SQLExecutiveCmdExec Account for Non SA's

 Parameters

 Tape Support

 Mail Login

 Apply Now

See Also

Tape Support Options Dialog Box

Server Parameters Dialog Box

SQL Mail Configuration Dialog Box


Root Directory

Displays the path for the root directory containing SQL Server files.


Master Database Path

Displays the directory path and the file name for the MASTER database device (MASTER.DAT).


Error Log Path

Displays the path and the filename of the SQL Server error log file. To use the SQL Server error log instead of or in addition to the Windows NT application event logging service, type the directory path for the error log file. If this entry is blank, a SQL Server error log is not written.


Auto Start Server at Boot Time

Specifies that SQL Server will start automatically whenever you boot the server computer.


Auto Start Executive at Boot Time

Specifies that SQL Executive will start automatically whenever you boot the server computer.


Auto Start Mail Client

Displays whether a mail client session starts automatically whenever SQL Server starts. This option is set using the setup program and cannot be changed in SQL Enterprise Manager.


Auto Start License Logging

Turns on logging information for licensing purposes.


Windows NT Event Logging

Displays whether SQL Server and SQL Executive events are logged in the Windows NT application event log. This option is set using the setup program and cannot be changed in SQL Enterprise Manager.


Performance Monitor Integration

Displays whether performance statistics for SQL Server are available to the Windows NT Performance Monitor. This option is set using the setup program and cannot be changed in SQL Enterprise Manager. However, you can select the method of integration: Direct Response Mode or On Demand Mode. When using either mode, make the Performance Monitor Refresh Interval long enough to avoid overloading SQL Server with requests.

Direct Response Mode

Specifies that SQL Server statistics are gathered separately from the SQL Server statistics display. When this option is selected, data is available immediately to the Performance Monitor and response time is optimized; however, the statistics display is one period behind the statistics that have been retrieved.

On Demand Mode

Specifies that the Performance Monitor requests and waits for the latest data from SQL Server during each refresh period. When this option is selected, you receive the latest data, but response time for the Performance Monitor is slower than with Direct Response Mode.


xp_cmdshell - Use SQLExecutiveCmdExec Account for Non SA's

Specifies that when a user other than a system administrator (SA) invokes xp_cmdshell, the supplied command (for example, dir C:\ ) will be issued in the security context of the SQLExecutiveCmdExec account. For SAs who invoke xp_cmdshell, the command will continue to execute in the security context of the MSSQLServer Service startup account.

If this check box is cleared, for users other than SAs who have been granted execute permission, the command will execute in the security context of the MSSQLServer Service startup account. By default, execute permission on xp_cmdshell defaults to the SA.

For more information about the SQLExecutiveCmdExec account, see SQL Server Books Online.


Parameters

Displays the Server Parameters dialog box, which is used to set startup options for SQL Server.


Tape Support

Displays the Tape Support Options dialog box, which is used to set the retry interval when attempting to read a tape.


Mail Login

Displays the SQL Mail Configuration dialog box, which is used to provide a mail login name and a mail login password to allow the system to auto start the mail client.


Apply Now

Applies the information you have specified in the Server Options tab.


Tape Support Options Dialog Box

Use this dialog box to set tape support options for SQL Server. For more information, choose one of the following:

 Wait Indefinitely

 Try Once Then Quit

 Try For


Wait Indefinitely

Specifies to wait indefinitely when trying to read a tape that has not been loaded in the drive.


Try Once Then Quit

Specifies to try once and then quit when trying to read a tape that has not been loaded in the drive.


Try For

Specifies how many minutes to wait when trying to read a tape that has not been loaded in the drive.


Server Parameters Dialog Box

Use this dialog box to set startup parameters for SQL Server. For more information, choose one of the following:

 Parameter

 Existing Parameters

 Add

 Remove


Parameter

Specifies the parameter to add.


Existing Parameters

Lists the startup parameters that are already set.


Add

Adds the parameter entered in the Parameter box.


Remove

Removes the parameter selected in the Existing Parameters box.


SQL Mail Configuration Dialog Box

Use this dialog box to configure SQL Mail for Exchange or Windows NT. When you configure SQL Mail for Exchange, provide a profile in the Profile Name box. When you configure SQL Mail for Windows NT, use this dialog box to specify your Windows NT mail client login name and password so that you can use SQL Server's SQL Mail. To better identify the origin of SQL Server mail messages, you can set up a mail account for the SQL Server with a descriptive name such as SQL Server Mail.

If you plan to use SQL Mail, first set up your Windows NT-based mail client and verify that it works. For more information about setting up mail, see the Microsoft SQL Server Administrator's Companion. Then you can configure SQL Server to start a SQL Mail session automatically, or you can use extended stored procedures to start SQL Mail from the command line. If you are configuring SQL Server to start a mail client session automatically, you must supply a mail login name and password. If you are starting a mail client session from the command line, you can supply your login name and password in this dialog box to avoid having to type them at the command line. Note that SQL Mail will "piggyback" an existing mail client session, if one is running.

Use this dialog box to change your saved password whenever you change your password on the mail client. For more information, choose one of the following:

 Mail Login Name

 Mail Password

 Confirm Password


Mail Login Name

Specifies the name used to log on to the Windows NT-based mail client.


Mail Password

Specifies the password used to log on to the Windows NT-based mail client. Note that if you change your Windows NT-based mail client password, you must also change your password here.


Confirm Password

Verifies the password you typed in the Mail Password box.


Security Options Tab

Use this tab to change login security configuration options for SQL Server. For more information, choose one of the following:

 Login Security Mode

 Standard

 Windows NT Integrated

 Mixed

 Default Login

 Default Domain

 Set HostName to UserName

 Audit Level

 Mappings

 Apply Now


Login Security Mode

Specifies the security mode for the SQL Server.


Standard

Sets the login security mode to standard. In standard mode, SQL Server manages its own login validation process for all connections (except client applications that explicitly request integrated security over trusted connections).


Windows NT Integrated

Sets the login security mode to Windows NT integrated. In this mode, SQL Server uses Windows NT authentication mechanisms for all connections. Only trusted connections are allowed into SQL Server. The login name and the SQL Server password submitted in the login request from a DB-Library or Open Database Connectivity (ODBC) client application are ignored by SQL Server. Network users assigned user-level privileges to SQL Server log in using their network username or the default login ID (if the network username is not found in syslogins). Network usernames assigned system administrator-level privilege log in as SA. With this option, only named pipes or multiprotocol clients are supported. If you have installed additional Net-Libraries, this option is not available.


Mixed

Sets the login security mode to mixed. In this mode, SQL Server allows trusted and nontrusted connections. For trusted (named pipes or multiprotocol) connections, SQL Server examines the requested login name as specified by the client DB-Library or ODBC application. If the login name matches the user's network username, or if the login name is null or blank spaces, SQL Server first tries the rules for Windows NT Integrated login security mode. If this fails, SQL Server uses the Standard login security rules. If the requested login name is any other value, the user must supply the correct SQL Server password, and SQL Server handles the login using the Standard rules. All login requests from nontrusted connections are handled using the Standard security rules.


Default Login

Specifies the SQL Server login name for an authorized user on trusted connections when the user's network username does not appear in syslogins. If this box is left blank, users with no network usernames in syslogins will be denied access to the server, even if they have user privileges. Note that the SA must add a login ID of the name specified as the default login; the login ID is not automatically created.


Default Domain

Specifies the Windows NT domain name that is the default for matching network usernames to SQL Server login names. Because the same network username can be defined in two different domains for two different users and both can be authorized to access SQL Server, SQL Server must distinguish between the two names in the login process for a trusted connection. For network usernames that are defined in domains other than the specified default, SQL Server adds the domain name and a map character such as an underscore (_) to the network username before checking in syslogins.


Set HostName to UserName

Replaces the host name from the client login record with the Windows NT network username for users under trusted connections. If this box is selected, for example, the network username will appear in the output of the sp_who system stored procedure.


Audit Level

Specifies the audit trail for successful or failed logins, or both.

Successful Login

Records successful login attempts along with other SQL Server information in the Windows NT application event log, the SQL Server error log, or both, depending on how you configure logging for your SQL Server.

Failed Login

Records failed login attempts along with other SQL Server information in the Windows NT application event log, the SQL Server error log, or both, depending on how you configure logging for your SQL Server.


Mappings

Specifies how to map special characters to valid SQL Server characters. Windows NT usernames include certain characters that are not valid in SQL Server login IDs, such as hyphens, spaces, and periods. When you use integrated security options or client-requested trusted connections, you must indicate how to map these characters in SQL Server.

Map _

Specifies which special Windows NT character will be mapped to the valid SQL Server character underscore (_).

Map #

Specifies which special Windows NT character will be mapped to the valid SQL Server character number sign (#).

Map $

Specifies which special Windows NT character will be mapped to the valid SQL Server character dollar sign ($).


Apply Now

Applies the information specified in the Security Options tab.


Configuration Tab

Use this tab to set configuration options (sp_configure) for a selected server. You can also set these options using the sp_configure stored procedure. For more information, choose one of the following:

 Configuration

 Minimum

 Maximum

 Running

 Current

 Description

 Apply Now


Configuration

Lists configuration options that can be set.


Minimum

Displays the minimum value for the configuration option.


Maximum

Displays the maximum value for the configuration option.


Running

Displays the value that is currently set for the configuration option.


Current

Specifies the value that is currently set for the configuration option. To change the value, type a new value in the box.


Description

Describes how a selected configuration option is used. Also notes whether a new value set for the selected option takes effect immediately, or whether you must restart the server to set the new value.


Apply Now

Applies the information you have specified. For values that take effect immediately, you must close the Server Configuration/Options dialog box to set the new value.


Attributes Tab

Use this tab to view the attributes of a selected SQL Server. You cannot change the information displayed in this tab. For more information, choose one of the following:

 Attribute

 Value


Attribute

Lists information about the selected SQL Server, including product, file, and processor information.


Value

Displays the current value for each attribute.


Current Activity Window

Use this window to view information about current connections and object locks for a selected SQL Server. You can view detailed information about the statement a process is running, send a message to the process owner, or end a process. For more information, choose one of the following:

 User Activity Tab

 Detail Activity Tab

 Object Locks Tab

 Status

 Process ID

 Login ID

 Database

 User Name

 Command

 Host

 Application

 Blocked By

 Blocking

 Lock Type

 Locked Object

 Group Name

 CPU Usage

 Physical I/O

 Host Process

 View Details

 Send Message

 Kill Process

 Refresh

 Display Legend

See Also

Process Details Dialog Box

Send Message Dialog Box

Viewing Detail Activity

Viewing Object Locks

Viewing Server Current Activity


User Activity Tab

Displays information about current connections and locks. The items in the User Activity tab are grouped by login ID. Each item displays an icon that indicates the type of activity, the process ID, the user name, the status, the name of the connected computer, and (if present) locks. A red background indicates a blocking lock.

To view a legend for the icons, click the Display Legend button.


Detail Activity Tab

Displays detailed information about the process numbers, statuses, locks, and commands the active users are running.


Status

Displays an icon that indicates the status of the activity. To view a legend for the icons, click the Display Legend button.


Process ID

Displays the process identification number (spid) of the process.


Login ID

Specifies the login ID of the user executing the command. System indicates SQL Server.


Database

Displays the name of the database the process is running against.


User Name

Displays the database username of the user executing the command.


Command

Specifies the command that is currently being executed.


Host

Specifies the computer from which the command was initiated.


Application

Names the application program.


Blocked By

Specifies the process ID of a blocking process, if any. A blocking process (which can have an exclusive lock) holds resources that another process needs.


Blocking

Shows whether or not the process is blocking another process. A zero indicates that the process is not blocking; any other number indicates that the process is blocking.


Lock Type

Specifies the type of lock. The (No Locks) entry indicates that no locks are present. To view a legend for lock type icons, click the Display Legend button.


Locked Object

Specifies the name of the locked object.


Group Name

Specifies the database group the user belongs to.


CPU Usage

Specifies the cumulative CPU time for the process.


Physical I/O

Specifies the cumulative number of disk reads and writes.


Host Process

Specifies the process ID number of the workstation.


Object Locks Tab

Displays information about which objects are locked, the types of locks being used, the process ID of the process holding the lock, the user name, the type of statement that is being executed against the locked object, and the name of the connected computer. A red background indicates a blocking lock.


 View Details

Displays the Process Details dialog box, which provides more information about a selected process.


 Send Message

Displays the Send Message dialog box, which is used to send a message to the selected user.


 Kill Process

Ends the selected process. Displays a message that asks you to confirm this selection.


 Refresh

Refreshes all lists that are in the Current Activity window.


 Display Legend

Displays or hides a legend for the icons in the lists.


Send Message Dialog Box

Use this dialog box to send a message to a selected user. For more information, choose one of the following:

 Message

 Destination

 Send


Message

Displays the message text that you type in the box.


Destination

Specifies where the message will be sent. Note that this option is available for only Microsoft networks. The Net Send command is used to send the message.

Using Username

Specifies the message will be sent to the computer with the username that is specified.

Using Hostname

Specifies the message will be sent to the computer with the hostname that is specified. You can send the message to a different computer by typing another name in the Hostname box.

To send a message to all currently logged on users, type an asterisk (*). The message will be sent to each computer that has a network connection to the current server.

Note that Hostnames are limited to 10 characters. If the connection you selected supplied its computer name as its hostname, only the first 10 characters of the computer name will be shown. As a result, the message may not be sent or may be sent to the wrong computer.


Send

Sends the message. Displays a dialog that confirms the message was sent.


Process Details Dialog Box

Use this dialog box to view detailed process information about a selected process. For more information, choose one of the following:

 Last TSQL Command Batch

 Cumulative Resource Usage

 Send Message

 Kill Process

 Refresh

See Also

Send Message dialog box


Last TSQL Command Batch

Displays the first 255 bytes of the text of the most recent statement run by the selected process.


Kill Process

Stops the process. Displays a message that asks you to confirm this selection.


Send Message

Displays the Send Message dialog box, which is used to send a message to the selected user.


Cumulative Resource Usage

Displays the cumulative CPU time used for the process and the cumulative number of disk reads and writes.


Refresh

Updates the information that is displayed in the dialog box.


Connection Tab

Use this tab to set connection preferences for SQL Enterprise Manager. For more information, choose one of the following:

 Login Timeout

 Query Timeout

 Packet Size (bytes)

 ANSI -> OEM

 Disconnect After Exec

 Defaults


Login Timeout

Specifies the time, in seconds, the server should wait before ending a login attempt.


Query Timeout

Specifies the time, in seconds, to wait for query results. If the query results are not retrieved within the time specified, you will be prompted to wait for another period.


ANSI -> OEM

Activates the automatic ANSI-to-OEM conversion.


Disconnect After Exec

Disconnects the SQL Query Tool server connection after each query.


Packet Size (bytes)

Sets the network packet size for the client connection to the server that is used by SQL Enterprise Manager.


Defaults

Sets the options on this tab to their default values.


Select Server/Database Dialog Box

Use this dialog box to change to a different server or database. For more information, choose one of the following:

 Server

 Connect

 Disconnect

 Database

See Also

Changing Servers or Databases


Server

Specifies the SQL Server to change to.


Connect

Connects to the selected SQL Server.


Disconnect

Disconnects from the selected SQL Server.


Database

Specifies the database to change to. You must first select a server in the Server box.


Manage Logins Dialog Box

Use this dialog box to manage SQL Server logins. If you are the system administrator (SA), you can add, modify, and remove logins. If you are not the SA, you can modify only your password. For more information, choose one of the following:

 Login Name

 Password

 Default Language

 Database Access

 Add

 Modify

 Drop

See Also

Adding a SQL Server Login

Managing Remote Servers and Logins


Login Name

Specifies a login ID to add to SQL Server. To add a login ID, expand the Login Name box and select <New Login>, then type the name in this box. To modify information about a login ID, expand the Login Name box and select the login ID to modify. A login ID can have up to 30 characters and must be unique for the server.


Password

Specifies the password for the login ID. To change the password, in the Password box, type the password. If you are not the SA, to modify your own password type your old password.


Default Language

Specifies a default language for the login ID. To change the default language, expand the box and choose a default language. Only languages that are available to the server are available to the user. If you do not specify a language, the server default language is assigned.


Database Access

Specifies the login ID's access to databases.

Permit

Grants access to a selected database.

Default

Sets the database as the login ID's default database (the database of focus when the user first logs in to SQL Server). To discourage users from creating database objects in the master database, assign a default database other than master.

User

Specifies the username for a selected database. The default username is the login name. To modify the default username, in the User box type another name.

Alias

Links the login ID to another user within a database. Select an alias in the Alias box. If you specify an alias, you cannot provide a username or group.

Group

Specifies the group in the selected database for the user to belong to. You can place users into groups for easier management. To add the user to a group within the database, click the Group box and expand the box, then select a group.


Add

Adds the login.


Modify

Makes changes to the selected login.


Drop

Drops a selected login and the corresponding username.


Confirm Password Dialog Box

Use this dialog box to confirm the password that is entered in the Password box. For more information, choose one of the following:

 Old Password

 Confirm New Password

See Also

Manage Logins Dialog Box


Old Password

Specifies the old password for the login ID. If you are the system administrator, you do not need to type the old password.


Confirm New Password

Specifies the new password. The entry in this box must match the password that is in the Password box.


Database Tab

Use this tab to view information about the selected database. In this tab, you can expand or shrink the database, recalculate the space available in the database, and truncate the transaction log. For more information, choose one of the following:

 Information

 Expand

 Shrink

 Recalculate

 Truncate

See Also

Expand Database dialog box

Manage Databases Window

Shrink Database dialog box


Information

Displays current information for the database.

Create Date

Displays the date and the time the database was created.

Owner

Displays the database owner.

Data Size

Displays the amount of space, in megabytes, that is allocated for the database.

Data Space Available

Displays the amount of space, in megabytes, that is available in the database.

Log Size

Displays the size of the transaction log, in megabytes. If the log is not on a separate device, "Shared with data" is displayed.

Log Space Available

Displays the amount of space, in megabytes, that is available on the transaction log device. If the log is not on a separate device, "Shared with data" is displayed.

Version

Displays the version of SQL Server code that was used to create the database.


Expand

Displays the Expand Database dialog box, which is used to increase the space that is allocated for a selected database.


Shrink

Displays the Shrink Database dialog box, which is used to reduce the space that is allocated for a selected database. You should recalculate before you shrink a database.


Recalculate

Recalculates the amount of space that is available for the database. You should recalculate before you shrink the database.


Truncate

Truncates the transaction log. The inactive part of the log is removed without making a backup copy. Space is saved by not logging the removal.


Options Tab

Use this tab to set options for the selected database. For more information, choose one of the following:

 Select Into / Bulk Copy

 Columns Null by Default

 No Checkpoint on Recovery

 Truncate Log on Checkpoint

 Single User

 DBO Use Only

 Read Only

 Description

See Also

Manage Databases Window


Select Into / Bulk Copy

Specifies that operations that are not logged can be performed.


DBO Use Only

Specifies that only the database owner can access a database.


No Checkpoint on Recovery

Prevents a checkpoint from being recorded on recovery.


Read Only

Specifies that users can view but not change the database contents.


Single User

Specifies that only one user at a time can access the database.


Columns Null by Default

Specifies whether database columns are defined as NULL or NOT NULL by default.


Truncate Log on Checkpoint

Specifies that the transaction log will be truncated each time the CHECKPOINT process occurs. Note that this is the only option you can set for the master database; however, this option should be selected to avoid filling up the transaction log for the master database.


Description

Provides a description for the selected option.


Permissions Tab

Use this tab to grant and revoke statement permissions for database users and groups. For more information, choose one of the following:

 Group\User

 Create and Dump Statements

See Also

Manage Databases Window


Group\User

Specifies the group or user to add or remove permissions for.


Create and Dump Statements

Specifies whether to add or remove permissions for each statement. You can add or remove permissions for the CREATE DATABASE statement only from within the master database.

Create DB

Specifies that the user selected in the User column can create a database. Only the system administrator can grant this permission.

Create Table

Specifies that the user selected in the User column can create a table.

Create View

Specifies that the user selected in the User column can create a view.

Create SP

Specifies that the user selected in the User column can create a stored procedure.

Create Default

Specifies that the user selected in the User column can create a default.

Create Rule

Specifies that the user selected in the User column can create a rule.

Dump DB

Specifies that the user selected in the User column can back up the database.

Dump Trans

Specifies that the user selected in the User column can back up the transaction log.


Shrink Database Dialog Box

Use this dialog box to reduce the database size. For more information, choose one of the following:

 Minimum Size (MB)

 Database Size (MB)


Minimum Size (MB)

Specifies the minimum size the database can be reduced to.


Database Size (MB)

Specifies the size, in megabytes, to reduce the database to.


Manage Users Dialog Box

Use this dialog box to add or drop database users, and to create or drop user aliases. For more information, choose one of the following:

 User Name

 Login

 Group

 Aliases

 Add

 Modify

 Drop

See Also

Manage Databases Window


User Name

Specifies the name of the user to add, drop, or alias other logins to.


Login

Specifies the login ID to map to the username.


Group

Specifies a group for the user. Each user belongs to the public group by default, and can be placed in only one other group.


Aliases

Associates other login IDs with the specified user.

Available Logins

Specifies the login IDs to map to the username displayed in the User Name box.

Aliased Logins

Specifies whether to create or remove an aliased login. To create an aliased login, from the Available logins list, select a login and click Add. To remove the login from an alias, from the Aliased Logins list, select a login and click Remove.


Add

Adds the user to the specified database.


Modify

Makes the changes that are specified in the Manage Users dialog box.


Drop

Drops the username selected in the User Name box. Displays a message that asks you to confirm this selection.


Manage Groups Dialog Box

Use this dialog box to add and drop groups, and to add and remove users from groups. For more information, choose one of the following:

 Group

 Database Users

 Add

 Modify

 Drop


Group

Specifies the name of the group to add or modify.


Database Users

Specifies users to add or remove from the group.

Users

Lists current database users who are not in the group that is specified in the Group box. To add a user, in the Users list, select a user and click Add.

Users in Group

Lists database users who are currently in the group specified in the Group box. To remove a user, in the Users in Group box, select a user and click Remove.


Add

Adds the group you have created.


Modify

Modifies the group that is displayed in the Group box as specified.


Drop

Drops the group that is selected in the Group box. Displays a statement that asks you to confirm this selection. Note that dropping a group causes users within the group to be moved to the public group.


Query Window

Use this window to query a database, and to view query results and Statistics input/output (I/O) results. You can also save queries and results, and set query options. For more information, choose one of the following:

 New Query

 Load SQL Script

 Save Query/Result

 Query Options

 DB

 Queries

 Remove Current Query Set

 Execute Query

 Cancel Executing Query

 Query Tab

 Results Tab

 Statistics I/O Tab

 No Execute

 Display Statistics I/O

See Also

Querying a Database

Query Options Dialog Box

Query System tab


 New Query

Displays the Query tab, in which you can enter a query.


 Load SQL Script

Displays the Open File dialog box, which you can use to open a saved query.


 Save Query/Result

Displays the Save File dialog box, which you can use to save a query or result.


 Query Options

Displays the Query Options dialog box, which you can use to set query options.


DB

Specifies which database to query.


Queries

Contains one entry for each query. You can switch between the queries that are displayed in the list. To start a new query, click the New Query button.


 Remove Current Query Set

Removes the current query/result set from the Queries box.


 Execute Query

Executes the query. Also, you can press CTRL+E to execute a query.


 Cancel Executing Query

Cancels the query execution.


Query Tab

Specifies the Transact-SQL text for the query. For help on Transact-SQL syntax, select the syntax and press SHIFT+F1, or from the Help menu, choose Transact-SQL Help. For help on specific objects, select the object name and press ALT+F1.


Results Tab

Displays the query results. To display the Results tab automatically when a query is completed, in the Configure SQL Enterprise Manager dialog box, in the Query System tab, select the Switch To Result Tab On Execute option.


Statistics I/O Tab

Displays the scan count, logical reads, and physical reads of the query. To display the results, click the Display Statistics I/O button.


 No Execute

Displays the execution plan for a query in the Results tab without executing the query. The Show Query Plan check box in the Query Flags tab must be selected for the plan to appear. Click the Query Options button to access the Query Flags tab.


 Display Statistics I/O

Generates statistics for a query in the Statistics I/O tab.


Query Options Dialog Box

Use this dialog box to set query options and format options. For more information, choose one of the following:

Query Flags Tab

Format Options Tab


Query Flags Tab

Use this tab to set options for processing a query. For more information, choose one of the following:

 Query Options

 Limits

See Also

Query Window


Query Options

Specifies options for processing a query.

Abort on Arithmetic Error

Specifies to end a query when an overflow or divide-by-zero error occurs during a query. You cannot select Abort on Arithmetic Error and Ignore Arithmetic Error options at the same time.

Ignore Arithmetic Error

Specifies that NULL is returned when an overflow or divide-by-zero error occurs during a query. You cannot select Abort on Arithmetic Error and Ignore Arithmetic Error options at the same time.

No Count Display

Specifies that the message that appears at the end of each query result that tells how many rows were affected by the query statement will not be displayed.

No Execute

Specifies that an execution plan for a query will be compiled, but the query will not be executed.

Parse Query Only

Specifies that the syntax of each query will be checked and that error messages will be returned without executing the query.

Show Query Plan

Specifies to generate a text description of the processing plan for the query as the query is processed.

Show Stats Time

Specifies to display the time it took to parse and compile each query statement, and the time it takes to execute each step of the query statement.

Show Stats I/O

Specifies to display the number of scans, logical reads, and physical reads for each table referenced in a query statement. (To generate a graphical description of the processing plan, click the Statistics I/O button on the Query window toolbar. If both the Statistics I/O button and this check box are selected, a text and a graphical description are generated.)


Limits

Specifies a limit to the row count.

Row Count

Specifies the number of rows the server should return before ending a query. The default (0) returns all rows.


Format Options Tab

Use this tab to set formatting options for query results. For more information, choose one of the following:

 Result Output Format

 Right Align Numerics

 Verbose Prints

 Print Headers

 Output Query

See Also

Query Window


Result Output Format

Specifies the format type for query results. The choices are Column Aligned, Comma Separated (CSV), Tab Delimited, and Other Delimiter. If you select Other Delimiter, in the Delimiter box enter the delimiter. The default is Column Aligned.


Right Align Numerics

Specifies to align numeric values in the query results to the right. This option is available only if you have selected Column Aligned in the Result Output Format box.


Verbose Prints

Displays the output for PRINT statements with the query results. This option is only useful if you have selected the Showplan and/or Statistics I/O options.


Print Headers

Specifies that column headers will be displayed in query results. If you do not want column headers to appear in the query results, clear this check box.


Output Query

Specifies that the first three lines of a query will be displayed with the query results.


New/Edit Task Dialog Box

Use this dialog box to create and schedule a task. For more information, choose one of the following:

 Name

 Type

 Enabled

 Database

 Command

 Schedule

 Add

 Options

See Also

Scheduling a Task

TSQL Task Options Dialog Box


Name

Specifies a name for the task.


Enabled

Specifies whether the task is created and scheduled, or created but not scheduled. To create and schedule a task, select this option. To create but not schedule a task, clear this option.

You can create and schedule a task, but not run the task as scheduled, by clearing the Enabled check box after you have created and scheduled the task. At a later time, select Enabled to run the task as scheduled.


Type

Specifies the task type.

CmdExec

Specifies an operating-system command, or a .CMD or .EXE file to run. The command cannot contain user interface components such as Microsoft Notepad® or Paint®.

Distribution

Specifies a distribution process command for replication.

LogReader

Specifies a log reader process command for replication.

Sync

Specifies a synchronization process command for replication.

TSQL

Specifies a Transact-SQL statement to be run against the selected database. The statement is limited to 255 characters and cannot contain embedded go commands.


Database

Specifies the database to run the task against.


Command

Specifies the task text. The text can be a valid operating system command, the filename (including path) of an .EXE file, a Transact-SQL statement, or a command to one of the replication processes.


Schedule

Sets the task schedule.

On Demand

Specifies that the task will run only when requested. Tasks that are created in association with alerts are created as On Demand.

One Time

Specifies that the task will occur only once at a specified date and time. After running, the task will be disabled, but not deleted.

On Date

Specifies a date to run the task one time.

At Time

Specifies a time to run the task one time.

Recurring

Specifies a schedule for the task to run more than once. The default for a recurring task is once a week on Sunday. To change the schedule, click Change. Complete the Task Schedule dialog box that appears

Change

Displays the Task Schedule dialog box, in which you can change a task schedule. Specifies changes to the task's recurring schedule.

Auto Start

Specifies that SQL Server will automatically start the task when the SQL Executive service starts. This option is used for replication processes.


Add

Adds a task as specified in the New Task dialog box.


Options

Displays the TSQL Task Options dialog box. Use this box to specify options about e-mail and Windows NT application event log notification, retry attempts for a selected task, and a remote target server and a database for log reader and distribution tasks only.


Task Schedule Dialog Box

Use this dialog box to change a schedule for a task. For more information, choose one of the following:

 Occurs

 Daily Frequency

 Duration

See Also

Scheduling a Task


Occurs

Sets the task frequency.

Daily

Displays the Daily frame. To specify a daily schedule, type the frequency of the task. For example, 3 means the task will run every third day. The default is Every 1 Day(s).

Weekly

Displays the Weekly frame. To specify a weekly schedule, type the frequency of the task. For example, 3 means the task will run every third week. Then select the days on which the task should occur. The default is every 1 Week(s) on Sunday.

Monthly

Displays the Monthly frame. To specify a monthly schedule, select a specific day and month frequency, or a specific day of the week and month frequency. For example, to run a task the third day of every third month, select Day and type 3 in the Day and Month(s) boxes. Or to run a task the third Monday of every other month, select The, select 3rd and Monday in the two boxes, then type 2 in the Month(s) box.


Daily Frequency

Specifies how frequently the task should run. The task can be scheduled to run once at a specific time, or to recur every certain number of hours during a specified range of hours.


Duration

Specifies a start and an end date for the task schedule. The Start Date is the first day the task will run (the default is the current date). You can specify an end date, which is the last day the task will run, or No End Date, for the task to recur indefinitely.


Manage Indexes Dialog Box

Use this dialog box to create, modify, rename, and drop indexes, and to update statistics for indexes you created while creating or modifying a table. You can manage indexes for version 4.2x servers, but some options are not available.

For more information, choose one of the following:

 Table

 Index

 Available Columns in Table

 Columns in Index [Key]

 Add

 Remove

 Table Size

 Index Size

 Index Attributes

 Unique Keys

 Ignore Duplicate Keys

 Clustered

 Ignore Duplicate Rows

 Allow Duplicate Rows

 Sorted Data

 Sorted Data Reorg

 Fill Factor %

 Build

 Rebuild

 Remove

 Rename

 Distribution

 Check Size

See Also

Creating an Index

Index Distribution Statistics Dialog Box


Table

Specifies the table to manage indexes for. To refresh the list of tables, close the Manage Indexes dialog box. In the Server Manager window, expand the database to display Tables. Select Tables, right-click on Tables, then select Refresh.


Index

Specifies the index to create, modify, rename, or update statistics for. To create an index, choose (New Index). Declarative Referential Integrity (DRI) indexes are indicated with "PKC" for PRIMARY KEY constraint or "UKC" for UNIQUE KEY constraint.

Note that for DRI indexes, you can only rebuild, check size, or view distribution statistics. You cannot add or remove columns or change index attributes, except for fill factor.

Also, when you rebuild a clustered DRI index, all nonclustered indexes will be rebuilt using the same fill factor value specified for the clustered index.


Available Columns in Table

Lists the possible columns to create an index on.


Columns in Index [Key]

Lists the columns in the index.


Add

Moves a selected column from the Available Columns in Table box to the Columns in Index [Key] box. You can also add a column by double-clicking the column name.


Remove

Moves a selected column from the Columns in Index [Key] box to the Available Columns in Table box. You can also remove a column by double-clicking the column name.


Table Size

Displays information about the number of rows and the space used, in kilobytes, for a table. Does not include the space used by any indexes on the table.


Index Size

Displays information about the size of the index.

Actual Size (KB)

Displays the size of an existing index, in kilobytes. Excludes all data pages, but includes the distribution page.

Estimated Min. / Avg. / Max. Potential Size (KB)

Displays the expected size of a new index, or of an existing index with a changed definition. For indexes that are defined on columns of fixed-size datatypes only, Min./Avg./Max. is always the same. For indexes with definitions that include one or more variable-length columns, Min. assumes these columns are empty, Avg. assumes they are half full, and Max. assumes they are completely full.

Estimated Min. / Avg. / Max. Rows per Leaf : Node

Displays the number of index rows that are expected to occupy the interior (node) and the exterior (leaf) pages of the B-Tree for a new index, or for an existing index with a changed definition. (Note that a clustered index has no leaf pages, because the data is excluded from the numbers.)

Estimated Min. / Avg. / Max. Index B-Tree Levels

Displays the expected depth of the B-Tree for a new index, or for an existing index with a changed definition. Deeper trees require longer times to access data, because more index pages must be traversed to reach the data.


Index Attributes

Specifies attributes for an index.


Unique Keys

Specifies that a unique index (an index in which no two rows are permitted to have the same key values) will be created. A unique index serves as an integrity check.


Ignore Duplicate Keys

Specifies that an INSERT or UPDATE statement that attempts to insert rows that violate the uniqueness constraint will execute, although rows that contain duplicate information will not be inserted and a warning message will appear.


Clustered

Specifies that a clustered index will be created. With a clustered index, SQL Server sorts rows on an ongoing basis so that their physical order is the same as their logical (indexed) order. By definition, only one clustered index can exist per table.


Ignore Duplicate Rows

Specifies that duplicate rows are not allowed in a table. When a duplicate row is entered, the row is ignored, the INSERT action is canceled, and an error message is displayed. Unique rows are inserted normally. This option is relevant only for non-unique clustered indexes.


Allow Duplicate Rows

Specifies that a table can contain duplicate rows. If this option is set, you can create a non-unique clustered index on a table that includes duplicate rows. You can subsequently create duplicate rows with the INSERT or UPDATE statement.


Sorted Data

Eliminates the sort from the index build process. Verifies that the data has been sorted by checking each index value against the previous one. If any row fails this check, the CREATE INDEX statement execution is stopped.


Sorted Data Reorg

Specifies that the data should be sorted during the index build process.


Fill Factor %

Specifies how full SQL Server should make each index page. The amount of empty space on an index page is important, because when an index page is full, the system must take time to split the page to make room for new rows. Allowable values are 1 (almost empty) through 100 (completely full). The default is 0. The fill factor is not maintained over time and is valid only when creating an index. Adjusting the fill factor affects the index size information.


Build

Creates the index as specified in the Manage Indexes dialog box.


Rebuild

Rebuilds the index as specified in the Manage Indexes dialog box.


Remove

Drops the index specified in the Index box. Displays a statement that asks you to specify whether to schedule the task or run the task immediately.


Rename

Renames the index. Displays the Rename Index dialog box, in which you can enter a new name.


Distribution

Displays the Index Distribution Statistics dialog box, which provides information about the distribution of key values in the specified index. Optimizing your queries depends on the accuracy of the distribution steps. If the number of rows in the table has changed significantly, click Update to update on all indexes on that table. Also choose Update if data in indexed columns has changed significantly.


Check Size

Checks the size of the index and verifies that the current size that is displayed under Index Size is correct. Displays a statement that asks you whether to schedule this task or to run this task immediately, and whether to apply Check Size to all indexes of the table. This operation requires a table scan, which takes time to complete.


By User Tab

Use this tab to grant, revoke, or view object permissions by user or group. For more information, choose one of the following:

 User/Group

 Member Of/Group Members

 Object Filters

 Column Level Permissions

 Object Table

 Set

 Grant All

 Revoke All

See Also

Granting Object Permissions


User/Group

Specifies the user or group to grant, revoke, or view permissions for. Note that the DBO is not displayed, because you cannot grant or revoke permissions from the DBO.


Member Of/Group Members

Displays the group the selection in the User/Group box belongs to. Displays members of the group when a group is selected in the User/Group box.


Object Filters

Specifies which objects are displayed in the Object list.

Tables

Specifies to display tables.

Views

Specifies to display views.

Stored Procedures

Specifies to display stored procedures.

All Objects

Specifies to display all objects.

Objects Granted to User/Group

Specifies to display only the objects granted to a user or group.


Column Level Permissions

Specifies column-level permissions for tables only. To grant or revoke Select or Update permission on specific column(s), select the Column Level Permissions check box, and then select the appropriate column(s) and the appropriate permissions.


Object Table

Specifies objects and indicates the owner, the permission available to the selected user or group, and whether column-level permissions have been granted to the selected user or group.

Stored procedures can only have the Execute permission granted.


Set

Sets the permission information specified in the By User tab.


Grant All

Specifies that all permissions be granted to all users or groups.


Revoke All

Specifies that all permissions be removed from all users or groups.


By Object Tab

Use this tab to grant, revoke, or view permissions by object. You can set permissions for objects you own. For more information, choose one of the following:

 Object

 Group/User

 Column Level Permissions

 Set

 Grant All

 Revoke All

See Also

Granting Object Permissions


Object

Specifies the object to grant, revoke, or view permissions for.


Group/User

Displays the groups and users in the selected database. Select the group or user to grant permission to or revoke permission from, then select the appropriate permission(s). To grant or revoke column-level permissions, select the Column Level Permissions check box and then select the appropriate columns and permissions.


Column Level Permissions

Specifies whether to grant or revoke Select or Update permission on specific column(s). Select the Column Level Permissions check box, and then select the appropriate column(s) and the appropriate permissions.


Set

Sets the permissions specified in the By Object tab.


Grant All

Specifies that all users and groups be granted permission for the selected object.


Revoke All

Specifies that permission for the selected object be removed from all users and groups.


Generate SQL Scripts Dialog Box

Use this dialog box to generate the scripts that are used to create database objects. For more information, choose one of the following:

 Scripting Objects

 Scripting Options

 Object Creation

 Object Drop

 Object Dependencies

 Table Indexes

 Table Triggers

 Table Keys/DRI

 Use Quoted Identifiers

 Security

 Object

 Owner

 Type

 Script

 Preview

 Single File

 Per Object

See Also

Generating SQL Scripts


Scripting Objects

Specifies the objects to generate a script for. You can select all objects or specific objects. To generate a script for an entire database, select All Objects. To generate a script for specific types of objects, select the individual objects. To generate a script for an individual object(s), in the box below, select the object(s).

Note that if you generate a script for user-defined datatypes and you run the script in a non-empty database that already contains those datatypes, you may encounter errors.


Scripting Options

Specifies the options for the script.


Object Creation

Specifies that object-creation statements will be added to the script.


Object Drop

Specifies that statements will be added that drop objects before creating objects.


Object Dependencies

Adds dependent objects to the script for the selected objects. The script will appear in order of dependents. This option is recommended if you have selected an object that has dependent objects. This option will ensure that the script is built in the correct procedural order.


Table Indexes

Specifies that statements will be added that create indexes for a table. Provides the CREATE INDEX statement.


Table Triggers

Specifies that statements will be added that create triggers for a table. Provides the CREATE TRIGGER statement.


Table Keys/DRI

Specifies that statements will be added that create declarative referential integrity (DRI) statements for a table. Provides the CREATE TABLE statement with the constraint information.


Use Quoted Identifiers

Specifies that quotation marks ( " ) will delimit identifiers and single quotation marks ( ' ) will delimit string constants. This prevents object names that are keywords from being misinterpreted. When this option is selected, scripts generated with this option will set the destination environment appropriately so that the quotation marks can be processed correctly.

For more information, see information about the SET statement in the Microsoft SQL Server Transact-SQL Reference.


Security

Specifies the user information options to be generated with the script. You can generate statements that add all users and groups to the database, that add to SQL Server all logins of users associated with that database, and/or that add permissions for the database. Note that the SA login and the repl_subscriber/publisher logins and users are not scripted.


Object

Specifies objects to generate scripts for. To specify an object, select the object, and then click Add to move it to the box to the right. To cancel the selection, in the box on the right, select the object and click Remove.


Owner

Specifies the owner of the object to generate scripts for.


Script

Generates a script for the objects you have selected.


Preview

Displays the Object Scripting Preview dialog box, which is used to view and change the script before generating it. To change the text of the script, and/or save the script to disk, click Save As.


Per Object

Saves the scripts to a filename of the form:

owner.objectname.objecttype

where

owner

Specifies the owner of the database object.

objectname

Specifies the name of the object.

objecttype

Specifies the type of object.


Object Types

Valid object types are:

Type	Description
bnd	Specifies a table bindings script.
def	Specifies a default objects script.
dp1	Specifies a script that drops objects on the source database that depended on the transferred objects but were not themselves transferred.
dp2	Specifies a script that drops transferred objects on the destination database before transfer is performed.
dr1	Specifies that declarative referential integrity (DRI) is created on the destination database before the transfer is performed. Includes clustered primary keys and clustered unique keys.
dr2	Specifies that DRI is created on the destination database after the transfer is completed. Includes a nonclustered primary key, a nonclustered unique key, DRI checks, and DRI defaults.
fky	Specifies a table foreign keys script.
grp	Specifies a groups script.
id1	Specifies that clustered indexes are created on the destination database before the transfer is performed.
id2	Specifies that nonclustered indexes are created on the destination database after the transfer is performed.
lgn	Specifies a logins script.
prc	Specifies a stored procedures script.
prv	Specifies a table privileges script.
rul	Specifies a rules script.
tab	Specifies a tables script.
trg	Specifies a triggers script.
udt	Specifies a user-defined datatypes script.
usr	Specifies a users script.
viw	Specifies a views script.
Note that the dp2 script is run automatically on the destination database if the Drop Destination Objects First check box is selected.

To clean up the source database after a transfer is performed, run the dp1 script followed by the dp2 script.


Single File

Saves a script for all objects to a single file of the form:

name.sql

where

name

Is the user-specified name.

sql

Is the default suffix to the filename. This may be modified.


Object Dependencies Dialog Box

Use this dialog box to view the object that another object depends on, and the objects that depend on the selected object. For more information, choose one of the following:

 Subject Object

 Objects That 'object_name'  Depends On

 Objects That Depend on 'object_name'

See Also

Viewing Object Dependencies


Subject Object

Specifies the object to view dependencies for.


Objects That 'object_name' Depends On

Displays the objects that the object you are viewing depends on.


Objects That Depend on 'object_name'

Displays the objects that depend on the object displayed in the Subject Object box.


Drop Objects Dialog Box

Use this dialog box to drop the object(s) selected in the Server Manager window. For more information, choose one of the following:

 Object

 Owner

 Type

 Show Dependencies

 Drop All

See Also

Viewing Object Dependencies


Object

Specifies the name of the object(s) to drop.


Owner

Specifies the owner of the object to be dropped. You must own an object (or be a system administrator) to drop that object.


Type

Shows the object type.


Show Dependencies

Displays the Object Dependencies dialog box, which displays the dependencies for a selected object.


Drop All

Drops the selected object(s).


Rename Object Dialog Box

Use this dialog box to rename an object. In the New Name box, type a name for the selected object.


Rules Tab

Use this tab to create, modify, or drop rules for the database that is selected in the Server Manager window. For more information, choose one of the following:

 Rule

 Description

 Add

 Drop

 Bindings

See Also

Unbinding a Rule from a Column

Unbinding a Rule from a Datatype


Rule

Specifies a name for the rule you are creating, or the names of existing rules to modify or drop.


Description

Specifies the conditions of the rule. For example, @value > 1 or @state in ("WA", "OR", "CA").


Add

Creates the rule.


Drop

Drops the rule that is displayed in the Rule box. Before you can drop a rule, you must unbind the rule from all columns and datatypes.


Bindings

Displays binding information for the rule that is displayed in the Rule box.


Column Bindings Tab for Rules

Use this tab to bind a rule to or unbind a rule from a table column. For more information, choose one of the following:

 Table

 Column

 Binding

 Bind

See Also

Binding a Rule to a Column


Table

Specifies the table that contains the column to bind a rule to or unbind a rule from.


Column

Specifies the column to bind a rule to or unbind a rule from.


Binding

Specifies the rule to be bound or unbound. To bind a rule, select the name of that rule. To unbind a rule, select (none).


Bind

Binds the rule to or unbinds the rule from the table column.


Datatype Bindings Tab for Rules

Use this tab to bind a rule to or unbind a rule from a user-defined datatype. For more information, choose one of the following:

 User-Defined Datatype

 Binding

 Future Only

 Bind

See Also

Binding a Rule to a Datatype


User-Defined Datatype

Specifies the user-defined datatype to bind the rule to or unbind the rule from.


Binding

Specifies the rule to be bound or unbound. To bind a rule, select the rule to bind. To unbind a rule, select (none).


Future Only

Specifies that the rule is bound to or unbound from only future columns that have the specified datatype. Existing columns that use the datatype are unaffected.


Bind

Binds the rule to or unbinds the rule from the selected user-defined datatype.


Manage Rule/Default Info Dialog Box

Use this dialog box to view binding information, and to unbind rules or defaults from a table column or user-defined datatype. For more information, choose one of the following:

 Bound Columns

 Bound Datatypes

 Unbind

See Also

Column Bindings Tab for Rules

Datatype Bindings Tab for Rules


Bound Columns

Displays the table columns a selected rule or default is bound to.


Bound Datatypes

Displays the user-defined datatypes a selected rule or default is bound to.


Unbind

Specifies the column or datatype to unbind the rule or default from. You can select more than one item to unbind at a time.


Defaults Tab

Use this tab to create, modify, or drop defaults for the database that is selected in the Server Manager window. For more information, choose one of the following:

 Default

 Description

 Add

 Drop

 Bindings

See Also

Unbinding a Default from a Column

Unbinding a Default from a Datatype


Default

Specifies a name for a default you are creating, or the names of existing defaults to modify or drop.


Description

Specifies the condition of a default.


Add

Creates the default as specified in the Defaults tab.


Drop

Removes the default that is selected in the Default box. Note that before you can drop a default, you must unbind the default from all columns and datatypes.


Bindings

Displays binding information for the selected default in the Default box.


Column Bindings Tab for Defaults

Use this tab to bind a default to or unbind a default from a table column for the database selected in the Server Manager window. For more information, choose one of the following:

 Table

 Column

 Binding

 Bind

See Also

Binding a Rule to a Column


Table

Specifies the table that contains the column to bind a default to or unbind a default from.


Column

Specifies the column to bind a default to or unbind a default from.


Binding

Specifies the default to bind or unbind. To bind a default, select the name of that default. To unbind a default, select (none).


Bind

Binds the default to or unbinds the default from the table column.


Datatype Bindings Tab for Defaults

Use this tab to bind a default to or unbind a default from a user-defined datatype for the database selected in the Server Manager window. For more information, choose one of the following:

 User-Defined Datatype

 Binding

 Future Only

 Bind

See Also

Unbinding a Default from a Datatype


User-Defined Datatype

Specifies the user-defined datatype to bind the default to or unbind the default from.


Binding

Specifies the name of the default to bind or unbind. To bind a default, select the name of that default. To unbind a default, select (none).


Future Only

Specifies that the default will be bound to or unbound from only future columns that have the specified datatype. Existing columns that use the datatype are unaffected.


Bind

Binds the default to or unbinds the default from the user-defined datatype.


Manage User-Defined Datatypes Dialog Box

Use this dialog box to create, modify, and drop user-defined datatypes for the database selected in the Server Manager window. For more information, choose one of the following:

 Name

 Owner

 Base Datatype

 Length

 Allow Nulls

 Default

 Rule

 Drop

 Info

 Apply Now

See Also

Creating User-Defined Datatypes


Name

Specifies the name of a user-defined datatype. To name a datatype, select an empty row and type the name in the box in the Name column.


Owner

Displays the owner of the user-defined datatype. This information cannot be changed.


Base Datatype

Displays the system-defined datatype on which to base the user-defined datatype. This information cannot be changed after a datatype is created.


Length

Displays the length of the user-defined datatype, if necessary. This information cannot be changed after a datatype is created.


Allow Nulls

Specifies that columns with the new user-defined datatype can contain null values. This information cannot be changed after a datatype is created.


Default

Binds a default to or unbinds a default from the selected datatype. To bind a default, select the row with the user-defined datatype to bind a default to, then click the Default box and select a datatype. To unbind a default, in the Default box select (none).


Rule

Binds a rule to or unbinds a rule from the selected datatype. To bind a rule, select the row with the user-defined datatype to bind a rule to, then click the Rule box and select a rule. To unbind a rule, in the Rule box select (none).


Drop

Drops the selected datatype. You cannot drop a datatype while it is in use.


Info

Displays the User Datatype Info dialog box, which displays information about the columns and tables that are associated with the selected datatype.


Apply Now

Makes the specified changes and leaves the dialog box open.


User Datatype Info Dialog Box

Use this dialog box to view information about which tables and columns are associated with a specified user-defined datatype.


Manage Alerts and Operators Window

Use this window to view information about server alerts and operators. You can add, edit, and remove alerts and operators, set alert engine defaults, and manage SQL Server messages. For more information, choose one of the following:

 Alerts Tab

 Operators Tab

 New Alert

 Edit Alert

 Delete Alert

 New Operator

 Edit Operator

 Delete Operator

 Refresh

 Alert Engine Options

 Manage Messages

See Also

Creating an Alert

Fail-Safe Tab

New/Edit Alert Dialog Box

New/Edit Operator Dialog Box

Pager Email Tab

Setting Alert Engine Options


Alerts Tab

Displays a list of alerts for the server that is selected in the Server Manager window.


Operators Tab

Displays a list of operators for the server that is selected in the Server Manager window.


 New Alert

Displays the New Alert dialog box, which you can use to create an alert. The Alerts tab must be selected for this button to be available.


 Edit Alert

Displays the Edit Alert dialog box, which you can use to modify an alert. The Alerts tab must be selected for this button to be available.


 Delete Alert

Removes the alert that is selected in the Alerts tab. Displays a message that asks you to confirm this selection. The Alerts tab must be selected for this button to be available.


 New Operator

Displays the New Operator dialog box, which is used to create an operator. The Operators tab must be selected for this button to be available.


 Edit Operator

Displays the Edit Operator dialog box, which you can use to modify an operator selected in the Operators tab. The Operators tab must be selected for this button to be available.


 Delete Operator

Removes the operator that is selected in the Operators tab. Displays a message that asks you to confirm this selection. The Operators tab must be selected for this button to be available.


 Refresh

Updates the lists of alerts and operators.


 Alert Engine Options

Displays the Alert Engine Options dialog box, which you can use to configure activity for the alert engine.


 Manage Messages

Displays the Manage SQL Server Messages dialog box, which you can use to find or create error messages.


Fail-Safe Tab

Use this tab to designate an operator to notify when all pager or e-mail notifications for an alert fail, to specify an unhandled event-forwarding server, and to restrict forwarded events. For more information, choose one of the following:

 Operator to Notify

 Server to Forward Events To

 Forward Events for Errors With Severity of or Above

See Also

Pager Email Tab

Viewing Alerts


Operator to Notify

Specifies an operator to notify when an alert fails. An alert can fail because of an incorrect pager address, a problem with the e-mail system, or a gap in the pager schedules. Select the operator to notify and then select the method for notifying that operator: E-mail and/or Pager. E-mail messages or pages that are sent to the fail-safe operator have Fail-Safe_ at the beginning of the Subject line to distinguish them from ordinary messages.

To add a new operator, choose (New Fail-Safe Operator). To specify no operator, choose (No Fail-Safe Operator).


Server to Forward Events To

Specifies a remote server to handle all alerts for the server selected in the Server Manager window. All unhandled events on the current server (events without locally defined alerts) will be sent to the Windows NT application event log on the remote server. The remote server will handle the event as if it were a local event on that server, and will raise an alert that is already set for that event.

With this option, you can centralize alert handling for a group of servers. You can have locally defined alerts and a specified remote server to handle all alerts that are not locally defined. When an event is registered in the Windows NT application event log, SQL Executive determines whether any alerts are defined locally and responds to those alerts as defined. If no alerts are defined locally, SQL Executive checks for a remote server to forward the event log to. Then SQL Executive on the remote server determines whether an alert is defined for the event and responds to the alert as defined.


Forward Events for Errors With Severity of or Above

Restricts the events that are forwarded to the remote server. Because forwarded events can cause additional network load, you can limit the load by specifying a higher severity level so fewer events will be forwarded. A severity of 001 causes all SQL Server events to be forwarded.


Pager Email Tab

Use this tab to specify the formats of the To, CC, and Subject lines of a pager e-mail message. This tab is useful if the pager e-mail requires special addressing to integrate with a pager service provider's e-mail system. For more information, choose one of the following:

 To Line

 CC Line

 Subject

 Include Body of Email in Notification Page

See Also

Fail-Safe Tab

Viewing Alerts


To Line

Creates the To Line template of a pager e-mail message. Specify the prefix, whether to include the pager address, and the suffix. For example, if you type a prefix of "@PGR:", select the Pager-Address check box, and specify no suffix, the To Line will look like:

@PGR:pageremailaddress


CC Line

Creates the CC Line template of a pager e-mail message. Specify the prefix, whether to include the pager address, and the suffix. For example, if you type a prefix of "MISPager" and do not select the Pager-Address check box or specify a suffix, the CC Line will look like:

MISPager


Subject

Creates a template for the Subject Line of a pager e-mail message. Specify the subject prefix and suffix. For example, if you type a prefix of SQL Server Alert and a suffix of "Fix It Now", the Subject line will look like:

SQL Server AlertAlertSubjectTextFix It Now


Include Body of Email in Notification Page

Specifies that the text of the e-mail message will be sent to the pager. A notification consists of lines of text. For pager notifications where hardware character buffers are at a premium, limit the amount of text to send. To send only the subject line, clear this check box.


Server Manager Window

Use this window to navigate through your servers and the objects on those servers. For more information, choose one of the following:

 Expanding and Collapsing Lists

 Navigating Through a List of Servers

 Accessing Menu and Toolbar Items

 Shortcut Menus

 Display Refresh

 Server Status Information

 Display Legend

See Also

Registering a Server

Creating a Server Group

Modifying Server Information


Expanding and Collapsing Lists

To expand and collapse lists in the Server Manager window, click the plus (+) or minus (-) sign that is beside the selected item. For example:

To view servers in a group, click the plus sign (+) that is beside that group name.

To view a list of objects and services on a specified server, click the plus sign (+) that is beside that server name.

To view a list of objects and services in a folder, click the plus (+) sign that is beside that folder.


Navigating Through a List of Servers

To quickly navigate to a particular server, expand the Server box and select the server name.


Accessing Menu and Toolbar Items

Certain menu and toolbar items are available only if the corresponding object is selected in the Server Manager window. For example, you cannot manage a server until you select it in the Server Manager window. You cannot manage any database objects until you select a database in the Server Manager window.


Shortcut Menus

In addition to using the menus or toolbar buttons in SQL Enterprise Manager, you can choose a task for a selected object by clicking the object with the right mouse button. A menu appears adjacent to the object and lists the tasks you can perform for that object.


Display Refresh

To update the information that is displayed in the Server Manager window, click the right mouse button on a folder and then select Refresh from the shortcut menu.


Server Status Information

The status of each server is displayed in the Server Manager window. The traffic light beside each server indicates whether SQL Server is started, paused, or stopped for that server. A red zigzag next to the traffic light indicates the server that you are currently connected to. You cannot see the status of servers if you are running SQL Enterprise Manager on a Windows 95-based computer.


 Display Legend

Displays a legend for the icons that appear in the Server Manager window.


Server Error Log Window

Displays the current error log for the selected SQL Server. The current log is labeled Current. A new log is created each time SQL Server is started. The previous six logs are maintained, and are labeled Archive followed by a number. The lowest number is the most recently archived log.

For more information about an error message, double-click the error message.


Manage SQL Server Messages Dialog Box

Use this dialog box to search for SQL Server error messages by message text, severity, and/or error number, and by messages that are always written to the Windows NT application event log. You can create or edit user-defined messages. Only the system administrator can view SQL Server messages, and only for SQL Server version 6.0 or later. For more information, choose one of the following:

 Message Text Contains

 Error Number

 Severity

 Only Include Logged Messages

 Only Include User-Defined Messages

 Find

 New

 Edit

 Delete

 Select

See Also

New/Edit Message Dialog Box


Message Text Contains

Specifies to search for messages that contain the text typed in this box.


Severity

Specifies to search for messages of the selected severity level in this box.


Error Number

Specifies the error number to search for.


Only Include Logged Messages

Restricts the list to SQL Server messages that are always written to the Windows NT application event log. If the Only Include User-Defined Messages option is also selected, the list includes all user-defined messages that are configured to be written to the log. If the Only Include User-Defined Messages option is cleared, the list includes system messages with severity levels 19 through 25, and all user-defined messages configured to be written to the log.


Only Include User-Defined Messages

Restricts the search to user-defined messages. If this option is cleared, the search returns user-defined and system messages.


Find

Searches for the defined message. Messages that fit the definition are displayed. To sort the messages by a column attribute, click the heading for that column. Sorting is not available if the list contains more than 250 rows. The default sort is by error number.


New

Displays the New Message dialog box, which you can use to create user-defined messages.


Edit

Displays the Edit Message dialog box, which you can use to edit messages. All information for user-defined messages, except error number, can be changed. For other messages, only the option to always write the message to the Windows NT application event log can be changed, and only for messages with severity levels less than 19.


Delete

Deletes a selected message. Only user-defined messages can be deleted.


Select

Copies the selected message to the New Alert or Edit Alert dialog box. This button is displayed only if you have accessed the Manage SQL Server Messages dialog box from the New/Edit Alert dialog box.


New/Edit Message Dialog Box

Use this dialog box to create or edit a user-defined message. You can also specify whether the message is to be logged to the Windows NT application event log. For more information, choose one of the following:

 Error Number

 Severity

 Message Text

 Language

 Always Write to Windows NT Eventlog

See Also

Managing SQL Server Messages


Error Number

Specifies an error number for a selected user-defined message. If you are creating a message, type a number in this box. User-defined messages begin at 50001. If you are editing a message, the message error number is displayed in this box and cannot be changed.


Severity

Specifies the severity level of the message. You can change the severity level of a user-defined message. You cannot change the severity level of a system message.


Message Text

Specifies text for a user-defined message. If you are creating a message, type the text for the message in this box. If you are editing a user-defined message, modify the information as necessary. You cannot modify the text of system messages.


Language

Specifies the language of the user-defined message. You cannot specify a language for system messages.


Always Write to Windows NT Eventlog

Specifies whether to write the message to the Windows NT application event log. You can use this option for system messages of severity levels less than 19.


Rename Index Dialog Box

Use this dialog box to rename an index. In the New Index Name box, type a name for the index.


Index Distribution Statistics Dialog Box

Use this dialog box to view distribution information for an index in a table. For more information, choose one of the following:

 Table Name

 Index Name

 Rows in Table

 Number of Steps

 Sampling Step Interval

 Average Row Hits

 Date of Last Update

 Distribution Steps (column 'column_name' only)

 Update


Table Name

Displays the name of the selected table.


Index Name

Displays the name of the selected index for the selected table.


Rows in Table

Displays the number of rows in the selected table.


Number of Steps

Displays the number of steps in the index for the selected table.


Sampling Step Interval

Displays the number of rows that are between key value sampling steps.


Average Row Hits

Displays the average number of rows that would be returned by an equality qualified query on the first column of the index (for example, SELECT * FROM AUTHORS WHERE AU_ID = '172-32-1176'). The smaller the number of rows returned the better, with 1 row being ideal. For indexes on tables that contain more than 200 rows, one of the following subjective ratings will also be displayed:

Very Good (more than 1 row but less than 0.5 percent of the rows)

Good (more than 0.5 percent of the rows but less than 1 percent of the rows)

Fair (more than 1 percent of the rows but less than 2.5 percent of the rows)

Poor (more than 2.5 percent of the rows but less than 5 percent of the rows)

Very Poor (more than 5 percent of the rows)

These ratings are provided as rough guidelines to assist in determining the effectiveness of the index and may not apply to all indexes.


Date of Last Update

Displays the last date distribution statistics for the index were updated.


Distribution Steps (column 'column_name' only)

Displays the key value at each step of the distribution statistics.


Update

Updates the statistics information for the index. You can execute this option immediately, but it could take time. You can schedule this option and choose to apply to all indexes for a selected table.


Specify Table Name Dialog Box

Use this dialog box to specify the name of a new table. In the New Table Name box, type the name for the table.


Object Scripting Preview Dialog Box

Use this dialog box to preview the text of the object script you are generating. Choose Save As to change and then save the script to disk.


Delete Non-Empty Device Dialog Box

Use this dialog box to confirm deleting a database device. For more information, choose the following:

 Delete Device


Delete Device

Drops the database device and the databases and/or logs stored on the device.


alerts

Are an automatic response by SQL Enterprise Manager to specified SQL Server events. A response can include running a task that you have defined or sending an e-mail and/or a pager message to a specified operator.


alias

Is a database username that is shared by several login IDs. With an alias, more than one person can be granted the same permissions for a database. Aliases are commonly used to allow several users to assume the role of database owner.


ANSI to OEM conversion

When you connect to a server, the ANSI to OEM option controls the default conversion behavior. If ANSI to OEM is set to on, conversion is automatically turned on in the following cases:

ANSI clients to OEM servers (Windows and Windows NT)

OEM clients to ANSI servers (Windows NT)

The ANSI to OEM option enables DB-Library to convert characters from OEM to ANSI when communicating with SQL Server, and from ANSI to OEM when communicating from SQL Server to the client. By default, this option is set to on.

For Windows-based clients, the SQL Client Configuration Utility includes the automatic ANSI to OEM option. By default, the setting for the ANSI to OEM option is set to OFF.


application log

Is a Windows NT application file that records new events. The application log can be viewed only by using the Windows NT Event Viewer. When SQL Server is configured to use the Windows NT application log, each SQL Server session writes new events to that application log. Note that unlike the SQL Server error log, a new application log is not created each time you start SQL Server.


article

Is the basic unit of replication. An article contains data that originates from a table that has been marked for replication. One or more articles are grouped within a publication.


attribute

Describes the character, quantity, quality, degree, or extent of an entity or relation. For example, column headings are usually considered to be attributes.


auto-start options

Specifies that SQL Server and SQL Executive will run automatically when Windows NT is started. By default, the setup program installs SQL Server and SQL Executive to run as manually started services of Windows NT.


automatic synchronization

Specifies that synchronization is accomplished automatically by SQL Server. A snapshot is taken of the table data, and along with the table schemas, that snapshot is written to files for transfer. The job to copy the table schema and the data is transferred, as is any other replication job, via the distribution database. No operator intervention is required.


backup device

Is a file that stores backups of databases.


base datatype

Is one of the system datatypes and includes the length for char, varchar, binary, and varbinary.


base object

Is an object (a table or another view) from which a view is derived. A view can have one or more underlying objects.


base table

Is a table from which a view is derived. A view can have one or more underlying tables. A view can also have underlying views. Base table is also called underlying table.


batch

Is a set of SQL statements that are submitted together and executed as a group. A script is often a series of batches that are submitted one after the other. A batch is compiled only once as a whole and is terminated by an end-of-batch signal (GO).


binding

Associates a default or rule with a column or datatype. The sp_bindefault system stored procedure binds a default to a column or to a user-defined datatype.

The sp_bindrule system stored procedure binds a rule to a column or to a user-defined datatype.


bulk copy program (bcp)

Is a command-line utility that copies SQL Server data to or from an operating-system file in a user-specified format.


bulk data copy

Specifies to break up large transactions when bulk copying data into a database. If you use bcp without specifying a batch size, the entire operation is performed as a single logical transaction.

If another user process executes a DUMP TRANSACTION statement, the log records associated with the bulk copy operation remain in the log until the entire operation completes or another DUMP TRANSACTION statement is executed. This is one of the most common causes of error 1105. You can avoid the problem by splitting the bulk copy operation into batches.


business rules

Is an organizational standard operating procedure for databases that requires certain policies (rules) be followed. Examples of business rules include: no debit without corresponding credit, no active customers to be deleted, or no additional credit for those whose payments are past due. Business rules ensure that the database maintains its accuracy and integrity in a business sense.


cascading delete

Removes all related database rows or columns.


cascading update

Refreshes all related database rows or columns.


CHECK constraints

Specify data values that are acceptable in a column. You can apply CHECK constraints to multiple columns or to a single column.

When a table is dropped, all CHECK constraints are also dropped.


checkpoint

Is the point at which all data pages that have been changed are guaranteed to have been written to the disk.


clustered index

Is an index in which the logical (indexed) order of the key values matches the physical order in which the corresponding rows (that contain the key values) exist in the table.


column

Is the set of all rows in a table that have a common attribute (for example, the firstname column in the authors table of the pubs database). Contains an individual data within a row or a record.


column-level constraints

Is a restriction that is used to enforce data integrity on a column (column-level constraints) or on a table (table-level constraints, which are usually multicolumn constraints). You can define constraints by using SQL Enterprise Manager or by specifying related options in the CREATE TABLE statement. SQL Server provides the following types of constraints: CHECK, DEFAULT, FOREIGN KEY, PRIMARY KEY, and UNIQUE.


common key

Is a key that is created to make explicit a logical relationship between two tables in a database. See also primary key; foreign key.


composite index

Is an index that uses from 2 to 16 columns.


composite key

Is a key that is composed of two or more columns. Composite keys result in more complex join processing.


connections

Is the number of logins or attempted logins to a SQL Server.


constraint

Is a restriction that is placed on the value that can be entered into a column or row. An example of a constraint is: age cannot be < 0 or > 110. SQL Server provides the following constraints: CHECK, DEFAULT, FOREIGN KEY, PRIMARY KEY, and UNIQUE.


creation script

Is an option that adds object-creation statements to the script. Creation_script is the path and the name of an article schema script that is used to create target tables.


data definition

Is the process of setting up databases and creating database objects, such as tables, indexes, constraints, defaults, rules, procedures, triggers, and views.


data definition language (DDL)

Is a language that is used to model the structure (not the contents) of a database. With DDL, you can create, modify, and remove databases and database objects.


data integrity

Is the accuracy and the reliability of data. Data integrity is important in single-user and multiuser environments. In multiuser environments, where data is shared, the potential for and the cost of data corruption is high. In large-scale DBMS environments, data integrity is a primary concern.


data modification

Is the activity of adding, deleting, or changing information in the database (using INSERT, DELETE, and UPDATE statements).


data synchronization

Is the process that matches schema and data in the publication and destination tables. Before a subscriber can receive replicated transactions from a publisher, the destination tables must be synchronized to those publication tables.


data transfer

Is the process of copying data to or from a SQL Server.


database

Is a collection of information comprising data tables and other objects. Tables and objects in a database are organized and presented to aid in accessing information, such as searching, sorting, and recombining data. Databases are stored on devices.


database consistency checker (DBCC)

Is a statement that is used to check the logical and physical consistency of a database. The DBCC statement can be used to check memory usage, decrease the size of a database, and check performance statistics. The DBCC statement helps to make a database physically and logically consistent, but it is not corrective.


database device

Is a file that databases are stored in. One database can be stored in several devices.


database name

Specifies a name for a database and must correspond to the rules for identifiers. The database name can have as many as 30 characters.


database object

Is one of the components of a database: table, index, trigger, view, key, constraint, default, rule, user-defined datatype, or stored procedure. Anything that has a name and consumes space in a database is an object.


database object owner

Is the designated owner of a database object (tables, indexes, views, defaults, constraints, triggers, rules, and procedures). A database object owner is the user who creates a database object. The database object owner owns that database object and is automatically granted all permissions on it. The owner can grant permission to other users to use that object. Ownership cannot be transferred.


database owner (DBO)

Is the creator of a database. The DBO has full privileges on that database and determines the access and capabilities that are provided to other users for that database. When in other databases, the DBO is known by his or her database username. DBO status can be reassigned to a different user; however, only one DBO can exist. Only one login ID can be the DBO login ID, although other login IDs can be aliased to the DBO.


database scripts

Is a collection of statements that are used to create database objects. Transact-SQL scripts are saved as files and usually end with the .SQL filename extension.


datatype

Is an identifier that specifies what type of information a column holds and how the data is stored. System-supplied datatypes are provided by SQL Server; user-defined datatypes can be created.


deadlock

Is a situation that arises when two users who each have a lock on one piece of data attempt to acquire a lock on the other's piece. Each user waits for the other to release his or her lock. SQL Server detects deadlocks and terminates one user's process.


declarative referential integrity (DRI)

Is a built-in capacity in SQL Server that checks the data integrity of a specific related table.


default

Is the database object that SQL Server uses to insert a value into a column when the user has not entered a value. In a relational database management system, each data element (a particular column in a particular row) must contain some value, even if that value is NULL. Because some columns do not accept null values, some other value must be entered, either by the user or by SQL Server. For example, you can create a default that has the value "???" or the value "fill in later", and then instruct SQL Server to enter that default if a user does not make an entry.


default database

Is the database a user is connected to when first logging on to SQL Server.


default device

Is the device on which a user's database is automatically stored (unless another device is specified).


default language

Is the language (for example, French, German, or English) that is used to communicate with the server. Once the default language is set, the user is automatically logged on as using that language.


delimiter

Is the character that is used to separate elements in a list.


dependencies

Are the views and procedures that depend on a specified table or view, and the tables and views that are depended on by the specified view or procedure.


destination database

Is the subscribing database in replication. The destination database receives tables and data that are copied from a publication database.


destination table

Is the subscribing table in replication. The destination table is replicated as a duplicate of a published table. A destination table in a destination database is synchronized with and contains data derived from the published table in a publication database.


device

Is one of two types of files in which databases are stored: database devices, which store databases, and backup devices, which store backups of a database. One database can be stored on several devices.


disk mirroring

Is the process that protects against media failure by maintaining a fully redundant copy of a partition on another disk.


distribute

Moves transactions from the distribution database to the subscription database in replication. Applies the transactions to the destination tables in the destination database.


distribution database

Holds transactions that are waiting to be distributed to subscription servers in replication. The distribution database receives transactions from the publication server by the log reader process and holds the transaction until the distribution process moves them to the subscription servers.


distribution process

Moves transactions from the distribution database tables to subscription servers in replication. The transactions are applied to the destination tables in the destination databases. The distribution process is a subsystem of the scheduling engine in SQL Executive.


distributor

Is the server that contains the distribution database in replication. The distributor receives all changes to published data, stores the changes in its distribution database, and when appropriate (depending on scheduling and other variables), transmits the changes to subscription servers. The distributor can be the same computer that is acting as the publisher or can be a different computer. Is also referred to as a distribution server.


domain

Is a collection of computers that are grouped for viewing and administrative purposes, and that share a common security database in Windows NT.


domain integrity

Enforces valid entries for a given column. Domain integrity is enforced by restricting the type (through datatypes), the format (through CHECK constraints and rules), or the range of possible values (through REFERENCE and CHECK constraints, and rules).


backups

Backs up a database. Creates a copy of a database's tables, data, and user-defined objects.


dynamic backup

Is a backup of a database or a transaction log that is made while the database is active. The dynamic backup makes backups convenient and continuous. However, the dynamic backup slows SQL Server and should be executed when the database is not being heavily updated.


dynamic recovery

Is the process that detects and/or attempts to correct software failures and losses of data integrity within a database management system.


entity integrity

Defines a row as a unique entity for a particular table. Usually enforces the primary key of a table (through indexes, UNIQUE constraints, or PRIMARY KEY constraints).


error log

Is a file that records error information from SQL Server. The error log can be viewed using SQL Enterprise Manager or any text editor. When SQL Server is configured to use its error log, each SQL Server session creates a new log. SQL Server retains the last six logs created.


event log

Is a file that contains SQL Server error messages, and messages for all activities on the computer.


exclusive lock

Is a lock that prevents any other transaction from acquiring a lock until the original lock is released at the end of a transaction. An exclusive lock is always applied during an update operation (INSERT, UPDATE, or DELETE).


field

Is a single item of information that is contained within a row or a record. A field is the logical equivalent of a column.


fill factor

Specifies how full SQL Server should make each index page. The amount of empty space on an index page is important because when an index page fills up, the system must take the time to split the page to make room for additional rows.


filtering

Is the method by which only selected rows or columns of a table are designated for replication. Filtering is the method by which partitioning is accomplished.


foreign key (FK)

Is the column or combination of columns whose values match the primary key (PK) of another table. A foreign key does not have to be unique; in fact, foreign keys are often in a many-to-one relationship to a primary key. Foreign key values should be copies of the primary key values; no value in the foreign key except NULL should ever exist unless the same value exists in the primary key. If any part of a composite foreign key is NULL, the entire foreign key must be NULL.


group

Is a set of database users. By placing users in groups, you can grant or revoke permissions to more than one user at the same time. All users belong to the public group by default and can belong to only one additional group.


group name

Is the name of a group of database users. A group name can have as many as 30 characters and must be unique within the database. The characters can be alphanumeric, but the first character must be a letter or the symbols number sign (#) or underscore (_) (for example, DATAOPS or #OPERS8).


guest

Is a name assigned to specified database users. Creating a user named guest in a database enables any user with a login ID for SQL Server to access the database as a guest user. If a user attempts to access the database but does not have a username (the username is not found in the database's sysusers table), SQL Server looks for a user named guest. If the username guest exists, the user can use the database under the permissions assigned to guest.


horizontal partitioning

Is the process of creating an article that replicates only selected rows from the base table. Subscription servers receive only that subset of data.


identifier

Is the name of a database object. An identifier can contain 1 to 30 characters. The first character must be a letter or the symbols underscore (_), at sign (@), or number sign (#). An identifier that begins with # denotes a temporary table. An identifier that begins with @ denotes a variable. Embedded spaces are not allowed.


IDENTITY property

Enables columns to contain system-generated values that uniquely identify each row within a table. When inserting values into a table that has an identity column, SQL Server automatically generates the next identifier based on the last used identity value and the increment value specified when the column was created.


index

Is a database object that provides access to data in the rows of a table and is based on key values. Specifically, an index is a set of pointers that are logically ordered by the values of a key. Indexes provide quick access to data and can enforce uniqueness on the rows in a table. SQL Server supports clustered and nonclustered indexes. In a clustered index, data is stored in the same order as the index; in a nonclustered index, data is stored differently from the index.


installation path

Is the drive and the directory into which the SQL Server files will be copied. The default is C:\MSSQL, and it can be set at installation time. After installation, the installation path is often referred to as the SQL Server root directory.


integrated security

Enables a SQL Server to use Windows NT authentication mechanisms to validate logins for all connections. Only trusted (multiprotocol or named pipes) connections are allowed.


ISQL/w

Is a SQL Server utility that you can use to enter Transact-SQL statements and system procedures in a graphical query interface. ISQL/w also provides the capability for graphically analyzing queries.


key

Is a field that is used to identify a record. A key is often used as the index field for a table.


keyword

Are words reserved by the server to be used to define, manipulate, and access database objects.


leaf level

Is the bottom level of a clustered or nonclustered index. In a clustered index, the leaf level contains the actual data pages of the table. In a nonclustered index, the leaf level points to data pages and does not contain the data.


livelock

Is a request for an exclusive lock that is repeatedly denied because of interference from a series of overlapping shared locks. SQL Server detects the situation after four denials and refuses further shared locks. Livelock creates a situation in which read transactions can monopolize a table or page, forcing a write transaction to wait indefinitely.


local distribution server

Refers to a server acting as a publication and distribution server. The publication database and the distribution database reside on the same computer.


local login identification

Is the login identification (login ID) a user must use to log on to a local server. A login ID can have as many as 30 characters. The characters can be alphanumeric, but the first character must be a letter (for example, CHRIS or TELLER8).


local server

Is the server(s) the user is logged on to. If remote servers are set up for the local server, users can access remote servers from their local servers.


lock

Restricts access to a resource in a multiuser environment. SQL Server automatically locks users out of a specific record, field, or file to maintain security or prevent problems that stem from concurrent data manipulation.


log device

Is a file that contains a database transaction log.


log reader process

Is the process of moving transactions from the transaction log of the publication server into the distribution database. The log reader process is a subsystem of the scheduling engine in SQL Executive.


logical name

Is the name used by SQL Server to identify a device. A logical name for a device must correspond to the rules for identifiers and can have as many as 30 characters.


login identification

Is the login ID, which is the unique name a user uses to log on to SQL Server. A login ID can have as many as 30 characters and must be unique for that server. The characters can be alphanumeric, but the first character must be a letter or the symbols number sign (#) or underscore (_). With integrated security for Windows NT, a separate login ID for SQL Server is not needed.


login security mode

Determines how SQL Server validates a login request. The three types of login security are integrated, standard, and mixed.


loose consistency

Is a replication model that allows a time lag between the moment original data is altered and the replicated copies of that data are updated. Loose consistency does not guarantee that all copies will be constantly identical to the original. An advantage of loose consistency is that it supports LANs, WANs, fast and slow communication links, and intermittently connected databases. It also provides better database availability and scales much better when implemented than does tight consistency. SQL Server replication is based on a loose consistency model.


manual synchronization

Is synchronization that is accomplished by a user. As with automatic synchronization, the publication server produces files containing the schema and a snapshot of the data from the published table. But with manual synchronization, the files are applied to the subscriber manually by using tape or another medium.


MAPI

Is an application programming interface (API) for e-mail.


master database

Is the database that controls the user databases and the operation of SQL Server as a whole. The master database is automatically installed with SQL Server and tracks such things as user accounts, remote user accounts, remote servers, ongoing processes, the configurable environment variables, system error messages, the databases on SQL Server, the storage space allocated to each database, the tapes and disks available on the system, and the active locks.


MASTER device

Is the device that is automatically installed with SQL Server and used to store the master, model, and tempdb system databases and transaction logs, and the pubs sample database and transaction log.


message number

Is the number that uniquely identifies an error message.


mirror name

Is the name specified for a mirrored device. Must correspond to the rules for identifiers and can have as many as 30 characters.


mirroring

Is the continuous duplication of information in one SQL Server device to another. Mirroring can provide continuous recovery in case of media failure.


mixed security

Enables SQL Server to validate login requests using either integrated or standard security. Trusted connections (as used by integrated security) and nontrusted connections (as used by standard security) can be established.


model database

Is the database that is supplied by SQL Server to provide a template or prototype for new user databases. Each time a database is created, SQL Server makes a copy of the model database and then sizes it as requested. A new database can never be smaller than the model database.

The model database contains the system tables that are required for each user database. The model database can be modified to customize the structure of newly created databases, so that every change you make to model is in each new database.


multiuser

Is the ability of a computer to support many users who are operating at the same time, while providing to each user the full capabilities of the computer system.


named pipe

Is an interprocess communication (IPC) mechanism that SQL Server and Open Data Services use to provide communication between clients and servers. Named pipes permit access to shared network resources.


nonclustered index

Is an index in which the logical order of the index does not match the physical order of the rows on disk. Clustered indexes usually provide faster access to data than do nonclustered indexes.


NULL

Is an entry that is used in Transact-SQL that has no explicitly assigned value. NULL is not equivalent to zero or blank. A value of NULL is not considered to be greater than, less than, or equivalent to any other value, including another value of NULL.


nullability

Is the capability of a column to allow null values (NULLs) for data in that column.


object

Is one of the components of a database: table, index, trigger, view, key, constraint, default, rule, user-defined datatype, or stored procedure. Is also called a database object.


object dependencies

Are the views and procedures that depend on a table or view, and the tables and views that are depended on by a view or procedure.


object owner

Is the user who owns the object, and is usually the creator of the object. Is also called database object owner (DBO).


object permissions

Are the permissions that regulate the use of certain statements (data modification statements) on certain database objects. Permissions can be granted or revoked by the owner of the object.


ownership chain

Are the dependencies of views on other views and/or tables and of procedures on other procedures, views, and/or tables.


partitioning

Is the process of creating an article that replicates only selected information from the base table in replication. Subscription servers receive only that subset of data from the source table. Partitioning is sometimes referred to as filtering. See also horizontal partitioning, vertical partitioning.


permissions

Are authorizations to enforce database security. The SQL Server permissions system specifies which users are authorized to use which Transact-SQL statements, views, and stored procedures. The ability to assign permissions is determined by each user's status. The two types of permissions are object permissions and statement permissions.


physical name

Is the path where a device or a mirrored device is located.

The default for a device is the path of the MASTER.DAT file followed by the first eight characters of the device's logical name. For example, if ACCOUNTING is the logical name and the MASTER.DAT file is located in MSSQL\DATA, the default physical name is MSSQL\DATA\ACCOUNTI.DAT.

The default for a mirrored device is the path of the MASTER.MIR file followed by the first eight characters of the mirror device's logical name. For example, if MACCOUNT is the name of the mirror device and the MASTER.MIR file is located in MSSQL\DATA, the default physical name of the mirror device is MSSQL\DATA\MACCOUNT.MIR.


polling interval

Is the option that sets how often the state of the service (SQL Server or SQL Executive) is checked.


primary domain controller (PDC)

Is a server in a Windows NT domain that maintains the domain's security database and authenticates user login IDs. The PDC also provides a copy of the domain's security database to back up domain controllers (BDCs), which share the user login authentication load.


primary key (PK)

Is the column or combination of columns that uniquely identifies a table. The primary key must always be non-null and must always have a unique index. A primary key is used for joins with foreign keys in other tables.


publication

Is a group of tables that are available for replication as a unit. A publication can contain one or more published articles from one user database. Each user database can have one or more publications.


publication database

Is a database that is the source of replicated data, or is a database that contains tables that are available for replication.


publish

Is to make data available for replication.


publisher

Is a server with data that is available for replication. A publisher maintains publication databases, makes published data from those databases available for replication, and sends copies of all changes to the published data to the distribution server. Is also referred to as a publication server.


pull subscription

Is a subscription that is performed while administrative focus is set on the subscription server. A subscription is created by pulling in a publication or an article from a publisher.


push subscription

Is a subscription that is performed while administrative focus is set on the publication server. A subscription is created by pushing out an article to one or more subscribers.


query

Is a specific request to retrieve, modify, or delete data.


query optimizer

Is a SQL Server component that generates the optimum execution plan for a query.


record

Is a group of related fields (columns) of information that is treated as a unit. A record is the logical equivalent of a row.


referential integrity (RI)

Is an integrity mechanism that ensures that vital data in a database—such as the unique identifier for a given piece of data—remains accurate and usable as the database changes. Referential integrity involves managing corresponding data values between tables when the foreign key of a table contains the same values as the primary key of another table.


remote distributor

Is a server that distributes replication data and does not reside on the same computer as the publisher. Compare with local distribution server.


remote login identification

Is the login identification (login ID) that is assigned to a user for accessing procedures on a remote server. The remote login ID can be the same as the user's local login ID. A remote login ID can have as many as 30 characters. The characters can be alphanumeric, but the first character must be a letter (for example, CHRIS or TELLER8).


remote server

Is a SQL server on the network that can be accessed through a user's local server. The setup program can install, upgrade, or configure remote servers.


remote stored procedure

Is a collection of SQL statements and optional control-of-flow statements that are stored under a name on a remote server. Remote stored procedures can be called by clients or by SQL Server.


replication

Is the process of duplicating table schema and data from a source database to a destination database, usually (but not necessarily) on separate servers.


restricted

Allows replication to only selected servers. A publication marked Unrestricted is visible to and can be subscribed to by any subscriber. A publication marked Restricted is visible only to those subscribers that have been marked for access.


restricted publication

Is a publication that is displayed to and can be subscribed to by servers that have been granted access. See also unrestricted publication.


restriction clause

Is the process of partitioning an article horizontally in replication.


retention

Is the period of time that a transaction is maintained in the distribution database after it has been successfully delivered to the destination database on the subscriber.


row

Is a set of related fields of information (columns) in a table that are treated as a unit and that describe a specific entity. A row is the logical equivalent of a record.


rule

Is a database object that is bound to a column or to a user-defined datatype. A rule specifies which data can be entered in a column. Each time a user enters or modifies a value (with an INSERT or UPDATE statement), SQL Server checks the entry against the current rule that is bound to the specified column. No table lookups are possible, but limit checking and list checking are. Data that is entered before creating and binding a rule is not checked.


scheduled backup

Is a backup operation that is automatically accomplished by SQL Executive as defined and scheduled by an administrator.


scheduled table refresh

Specifies that at scheduled intervals all articles in a specified publication will be refreshed. Each time refresh occurs, all data (and optionally, the table schemas) will be applied to all destination tables. No data changes are sent between the scheduled refresh intervals. Transaction-based replication does not occur.


schema

Is a description of a database that the database management system generated by using the data definition language.


script

Is a collection of statements that is used to create database objects. Transact-SQL scripts are saved as files that usually end with the .SQL filename extension.


server name

Is the name of the SQL Server and is taken from the computer's name. Must be a valid SQL identifier. The first character must be a letter or an underscore (_). The characters that follow can include letters, numbers, or the symbols number sign (#), dollar sign ($), or underscore (_). Embedded spaces are not allowed.


server state polling

Specifies the polling interval, which determines how often the state of the service (SQL Server or SQL Performance Monitor) is checked.


severity level number

Represents the severity level of an error. Valid levels are 1 through 25. Only the system administrator can add a message with a severity level of 19 through 25.


shared lock

Is a lock that is created by nonupdate (read) operations. Other users can read the data concurrently, but no transaction can acquire an exclusive lock on the data until all the shared locks have been released.


Showplan

Is an option of ISQL/w and SQL Enterprise Manager. Shows the execution plan for a query.


single-user mode

Is a startup mode that restricts connections. Only a single user can connect, and the CHECKPOINT mechanism, which guarantees that completed transactions are regularly written from the disk cache to the database device, is not started.


SQL Executive

Is a component of SQL Enterprise Manager. SQL Executive provides powerful scheduling capabilities that enable replication. With SQL Executive, you can schedule other SQL Server events, including backups, DBCC operations, and administrative maintenance tasks. SQL Executive replaces SQL Monitor, which was included in earlier releases of SQL Server.


SQL Mail

Is a component of Microsoft SQL Server. SQL Mail includes extended stored procedures that enable SQL Server to send and receive mail messages through the built-in mail application programming interface (MAPI) client interface in Windows NT. A mail message can consist of short text strings, the output from a query, or an attached file.


SQL Performance Monitor Integration

Is the integration of Windows NT Performance Monitor with SQL Server to provide up-to-the-minute activity and performance statistics.


SQL Security Manager

Is a SQL Server utility that provides a way to manage integrated and mixed security. This functionality is available in the SQL Enterprise Manager.


SQL Service Manager

Is a utility that is provided with SQL Server. The SQL Service Manager provides a graphical way to start, pause, and stop MSSQL Server, MS DTC, and SQL Executive. SQL Server is also integrated with the service control management of Windows NT, so you can also start, pause, and stop MSSQL Server, MS DTC, and SQL Executive from the Services application in Control Panel or from the Server Manager window in SQL Enterprise Manager.


SQL Transfer Manager

Is a utility that is provided in SQL Server. SQL Transfer Manager provides a graphical way to transfer objects and data from one SQL Server to another. You can transfer from a Microsoft-based SQL Server or other SQL Server to a Windows NT−based SQL Server. For example, you can transfer data from a Microsoft SQL Server running on an Intel-based architecture to a different processor architecture.


standalone installation

Is an installation of SQL Server on a computer that is not connected to a network. A standalone installation may be used to install SQL Server on a computer that will soon be but is not yet connected to a network (for example, it does not yet have a network adapter card installed.) Or, a standalone installation might be performed on a computer that is intended as a development system and will have no need for a network connection.


standard security

Is the security mode that uses SQL Server's own login validation process for all connections. To log on to a SQL Server with standard security, each user must provide a valid login ID and password.


statement permissions

Are the authorizations that provide privileges to issue certain Transact-SQL statements. Statement permissions are not object-specific. They can be granted only by the system administrator or the database owner. Statement permissions are also called command permissions.


stored procedure

Is a precompiled collection of Transact-SQL statements and optional control-of-flow statements that is stored under a name and processed as a unit. Stored procedures are kept within a database, can be executed with one call from an application, and allow user-declared variables, conditional execution, and other powerful programming features. Stored procedures that are supplied by SQL Server are called system stored procedures.


subscribe

Is an agreement to receive a publication or an article. A destination database on a subscriber subscribes to replicated data from a publication database on a publisher.


subscriber

Is the server that maintains destination databases, which receive and maintain copies of published data. Is also referred to as a subscription server.


synchronization

Is the process of matching schema and data on a publication and destination tables. Synchronization must be done before a subscriber can receive replicated transactions from an article or publication.


synchronization process

Is the process that creates files that contain data from published tables and applies these files, along with table schema files, to destination database tables. The synchronization process is a subsystem of the scheduling engine in SQL Executive.


system administrator (SA)

Is the person who is responsible for the administrative and operational functions that are independent of any particular application. The SA is likely to be a person with a comprehensive overview of SQL Server and all its applications. The SA advises application designers about data that already exists on SQL Server, makes recommendations about standardizing data definitions across applications, and so on.

The SA operates outside the protection system (SQL Server does not check permissions for the SA). The SA is also treated as the owner of whatever database he or she is using. Anyone who knows the SA's password can log on and act as the SA.


table

Is a collection of rows (or records) that have associated columns (or fields). A table is the logical equivalent of a database file.


table data file

Is a file that contains a snapshot of the data of a published table. A table data file is used during synchronization as the source of data that is inserted into the destination table. The data snapshot is written to a file that ends with the .TMP filename extension.


table schema script

Is a script that contains the schema of a published table. The table schema script is used during synchronization to create the destination table. The schema script is written to a file that ends with the .SCH filename extension. See also table data file.


table-level constraint

Defines data integrity for an individual column (column-level constraint) or a combination of columns (table-level constraints) when the table is defined or altered. Constraints support domain integrity, entity integrity, and referential integrity, as well as user-defined integrity.


tape backup

Is the process of backing up a database to any tape device that is supported by Windows NT. If you are creating a tape backup device, you must first install the tape device using Windows NT. The tape device must be physically attached to the SQL Server you are backing up.


tempdb database

Is the database that provides a storage area for temporary tables and other temporary working storage needs. No special permissions are required to use tempdb (that is, to create temporary tables or to execute commands that might require storage space in the tempdb database). All temporary tables are stored in tempdb, no matter what database the user who creates them is using.


thread

Is a mechanism that allows one or more paths of execution through the same instance of an application. Each device requires one thread and each remote site requires two threads. SQL Server takes advantage of the native thread services of Windows NT.

There are separate threads for each network, a separate thread for database checkpoints, and a pool of threads for all users.


tight consistency

Is a replication model that guarantees all copies will be identical to the original. Tight consistency is usually implemented using two-phase commit, and it requires a high-speed LAN. Tight consistency also reduces database availability and is less scalable in its implementation as compared to loose consistency.


Transact-SQL (T-SQL)

Is the standard language for communication between applications and SQL Server. The Transact-SQL language is an enhancement to the Structured Query Language (SQL), which is the ANSI-standard relational database language. Transact-SQL provides a comprehensive language for defining tables; for inserting, updating, or deleting information stored in tables; and for controlling access to data in those tables. Transact-SQL includes statements, commands, control-of-flow language, stored procedures, triggers, rules, and defaults. Extensions such as stored procedures make Transact-SQL a full programming language.


transaction log

Is a reserved area of the database in which all changes to the database are recorded. A transaction log is stored in the syslogs system table and is used by SQL Server during automatic recovery.


transaction processing

Is a method by which transactions are executed immediately after they are received by the system.


trigger

Is a special type of stored procedure that is activated when data in a specified table is modified. Triggers are often created to enforce referential integrity or consistency among logically related data in different tables.


trusted connection

Is an authenticated connection between a client and a server. The multiprotocol and named pipe protocols provide trusted connections. Integrated security requires network protocols that support trusted connections.


underlying object

Is an object (a table or another view) from which a view is derived. A view can have one or more underlying objects.


underlying table

Is a table from which a view is derived. A view can have one or more underlying tables. A view can also have underlying views. An underlying table is also called a base table.


unhandled event-forwarding server

Is a remote server to which any unhandled SQL Server events on the local server (events for which there are no locally defined alerts) will be sent.


UNIQUE constraints

Are constraints that enforce entity integrity on a non-primary key. UNIQUE constraints ensure that no duplicate values are entered, that null values are not allowed, and that an index is created to enhance performance.


unique index

Is an index in which no two rows can have the same index value, thus prohibiting duplicate index or key values. The system checks for duplicate key values when the index is created and checks each time data is added with an INSERT or UPDATE statement.


universal naming convention (UNC)

Is a naming convention that consists of the following format:

\\servername\sharename\path\filename


unrestricted publication

Is a publication that is displayed to and can be subscribed to by any registered subscriber. Unrestricted is the default.


update statistics

Are statistics that update information about the distribution of key values in specified indexes. If a table has no data when the index on the table is created, then update the index statistics after data is added.


user databases

Are databases defined by the user. Information is recorded in the master database about user databases. User-defined databases are automatically created with a subset of system tables.


username

Is the name that is assigned to a login ID for the purpose of allowing that user to access a specified database. The abilities a user has within a database depend on the permissions that are granted to the username and to any groups the username is a member of. A username can have as many as 30 characters and must be unique within the database. The characters can be alphanumeric, but the first character must be a letter or the symbols number sign (#) or underscore (_) (for example, CHRIS or #USER8).


user-defined datatype

Is a definition of the type of data a column can contain. A user-defined datatype is created by the user and defined in terms of existing system datatypes. Rules and defaults can be bound to user-defined datatypes (but not to system datatypes).


variables

Are entities that are assigned values. A local variable is defined with a DECLARE statement, and it is assigned an initial value within the statement batch where it is declared with a SELECT statement. Global variables are predefined and maintained by the system.


vertical partitioning

Is the process of creating an article that replicates only selected columns from the base table. Subscribers receive only the subset of data that was vertically partitioned. Note that the replicated columns must include the primary key column(s).


view

Is another way of looking at data from one or more tables in the database. A view is usually created as a subset of columns from one or more tables. The tables from which views are derived are called base tables. A view can also be derived from another view.

The definition of a view (the base tables from which the view is derived) is stored in the database. All views are stored in the base tables. No separate copies of data are associated with views. A view looks almost exactly like any other database table. You can display it and manipulate it almost as you can on any other table.


Windows NT Event Viewer

Is the Windows NT application that you can use to view events, filter events, and retain event logs.


Windows NT Performance Monitor

Is a utility that is supplied by Windows NT that provides system administrators a way to monitor the performance of SQL Server. SQL Server produces statistics on locks, the current sizes of transaction logs, user connections, and server performance. You can even set alerts to take any action you specify if a specified threshold is reached.


write-ahead log

Is a method in which the transaction log is always written before the data is written.