![]() | ![]() |
Home |
|
|
What's New in SYBASE SQL Server Release 10.0? |
|
| Chapter 1: New Features in SQL Server Release 10.0 |
|
| Enhancements to Permissions |
Object and command permissions in SQL Server have been enhanced with the following new options.
A new clause for the grant command, with grant option , allows a permission holder to pass grant capability, along with the specific permission, to other users, though not to groups, roles, or public . A corresponding clause, cascade , for the revoke command, allows the privilege holder to revoke permissions from all users who obtained it via with grant option . See "grant" and "revoke" in Volume 1, Chapter 1 of the SQL Server Reference Manual for syntax information. Chapter 5, "Managing User Permissions" , of the System Administration Guide provides a full discussion and examples of this new option.
You can grant and revoke object and command permissions to all users who have been granted a specific role. The roles are sa_role , sso_role , and oper_role . Permissions granted to roles override permissions granted to individuals or groups.
New sp_configure options allow System Administrators to reset the network packet size used by SQL Server. Larger packet sizes can yield performance improvements when transferring large amounts of data in or out of SQL Server. See Chapter 12, "Fine-Tuning Performance and Operations" of the System Administration Guide for full information.
New command line options for isql and bcp allow you to set the packet size for an individual session. See the SQL Server Utility Programs manual for your operating system for information about using these options. Open Clientä Client-Library documentation includes information on using variable packet sizes.
Chargeback accounting provides a mechanism for tracking CPU and I/O usage for each server user. This feature was previously available only on VMS.
See "sp_clearstats" and "sp_reportstats" in Volume 2, Chapter 1 of the SQL Server Reference Manual for information on getting reports and restarting the accounting interval. See "sp_configure" for information on the cpu flush and i/o flush configuration variables that affect chargeback accounting.
These changes have been made to dbcc , the database consistency checker:
The kill command, used to terminate SQL Server sessions, can now terminate more kinds of sessions. In previous releases, some of these sessions could not be terminated (except by rebooting SQL Server), or would only actually terminate when the processes stopped sleeping. Now, these sessions can be terminated immediately. The sp_who system procedure now displays different status values for these sessions. For more information, see "kill" in Volume 1, Chapter 1 of the SQL Server Reference Manual or Chapter 11, "Diagnosing System Problems" of the System Administration Guide.
The shutdown command, used to shutdown a SQL Server, can now be used to shut down a Backup Server. The Backup Server must be listed in your sysservers table and in the interfaces file for the SQL Server from which you execute the shutdown command.
Unless you use the nowait option, shutdown waits for active dumps and loads to complete. Once you issue a shutdown command to a Backup Server, no new dumps or loads to the Backup Server can start.
By default, all users now have create table permission in tempdb . See "Temporary Tables" in Volume 1, Chapter 3 of the SQL Server Reference Manual for more information.
System procedures now display additional information about space available in databases:
|
|