Sybase

System Administration Guide: Volume 1 Adaptive Server Enterprise
15.0
DOCUMENT ID: DC31654-01-1500-02 LAST REVISED: October 2005 Copyright 1987-2005 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S. and Canadian customers should call Customer Fulfillment at (800) 685-8225, fax (617) 229-9845. Customers in other countries with a U.S. license agreement may contact Customer Fulfillment via the above fax number. All other international customers should contact their Sybase subsidiary or local distributor. Upgrades are provided only at regularly scheduled software release dates. No part of this publication may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Sybase, Inc. Sybase, the Sybase logo, ADA Workbench, Adaptable Windowing Environment, Adaptive Component Architecture, Adaptive Server, Adaptive Server Anywhere, Adaptive Server Enterprise, Adaptive Server Enterprise Monitor, Adaptive Server Enterprise Replication, Adaptive Server Everywhere, Adaptive Warehouse, Afaria, Answers Anywhere, Anywhere Studio, Application Manager, AppModeler, APT Workbench, APT-Build, APT-Edit, APT-Execute, APT-Translator, APT-Library, AvantGo Mobile Delivery, AvantGo Mobile Inspection, AvantGo Mobile Marketing Channel, AvantGo Mobile Pharma, AvantGo Mobile Sales, AvantGo Pylon, AvantGo Pylon Application Server, AvantGo Pylon Conduit, AvantGo Pylon PIM Server, AvantGo Pylon Pro, Backup Server, BizTracker, ClearConnect, Client-Library, Client Services, Convoy/DM, Copernicus, Data Pipeline, Data Workbench, DataArchitect, Database Analyzer, DataExpress, DataServer, DataWindow, DataWindow .NET, DB-Library, dbQueue, Developers Workbench, DirectConnect, DirectConnect Anywhere, Distribution Director, e-ADK, E-Anywhere, e-Biz Impact, e-Biz Integrator, E-Whatever, EC Gateway, ECMAP, ECRTP, eFulfillment Accelerator, Embedded SQL, EMS, Enterprise Application Studio, Enterprise Client/Server, Enterprise Connect, Enterprise Data Studio, Enterprise Manager, Enterprise SQL Server Manager, Enterprise Work Architecture, Enterprise Work Designer, Enterprise Work Modeler, eProcurement Accelerator, EWA, Financial Fusion, Financial Fusion Server, Gateway Manager, GlobalFIX, iAnywhere, iAnywhere Solutions, ImpactNow, Industry Warehouse Studio, InfoMaker, Information Anywhere, Information Everywhere, InformationConnect, InternetBuilder, iScript, Jaguar CTS, jConnect for JDBC, M2M Anywhere, Mach Desktop, Mail Anywhere Studio, Mainframe Connect, Maintenance Express, Manage Anywhere Studio, M-Business Channel, M-Business Network, M-Business Server, MDI Access Server, MDI Database Gateway, media.splash, MetaWorks, mFolio, Mirror Activator, MySupport, NetGateway, Net-Library, New Era of Networks, ObjectConnect, ObjectCycle, OmniConnect, OmniSQL Access Module, OmniSQL Toolkit, Open Biz, Open Client, Open ClientConnect, Open Client/Server, Open Client/Server Interfaces, Open Gateway, Open Server, Open ServerConnect, Open Solutions, Optima++, PB-Gen, PC APT Execute, PC DB-Net, PC Net Library, PocketBuilder, Pocket PowerBuilder, Power++, power.stop, PowerAMC, PowerBuilder, PowerBuilder Foundation Class Library, PowerDesigner, PowerDimensions, PowerDynamo, PowerScript, PowerSite, PowerSocket, Powersoft, PowerStage, PowerStudio, PowerTips, Powersoft Portfolio, Powersoft Professional, PowerWare Desktop, PowerWare Enterprise, ProcessAnalyst, QAnywhere, Rapport, RemoteWare, RepConnector, Replication Agent, Replication Driver, Replication Server, Replication Server Manager, Replication Toolkit, ReportExecute, Report Workbench, Resource Manager, RFID Anywhere, RW-DisplayLib, RW-Library, S-Designor, SDF, Search Anywhere, Secure SQL Server, Secure SQL Toolset, Security Guardian, SKILS, smart.partners, smart.parts, smart.script, SOA Anywhere, SQL Advantage, SQL Anywhere, SQL Anywhere Studio, SQL Code Checker, SQL Debug, SQL Edit, SQL Edit/TPU, SQL Everywhere, SQL Modeler, SQL Remote, SQL Server, SQL Server Manager, SQL SMART, SQL Toolset, SQL Server/CFT, SQL Server/DBM, SQL Server SNMP SubAgent, SQL Station, SQLJ, STEP, SupportNow, S.W.I.F.T. Message Format Libraries, Sybase Central, Sybase Client/ Server Interfaces, Sybase Financial Server, Sybase Gateways, Sybase IQ, Sybase MPP, Sybase SQL Desktop, Sybase SQL Lifecycle, Sybase SQL Workgroup, Sybase User Workbench, SybaseWare, Syber Financial, SyberAssist, SybFlex, SyBooks, System 10, System 11, System XI (logo), SystemTools, Tabular Data Stream, TradeForce, Transact-SQL, Translation Toolkit, UltraLite, UltraLite.NET, UNIBOM, Unilib, Uninull, Unisep, Unistring, URK Runtime Kit for UniCode, VisualWriter, VQL, WarehouseArchitect, Warehouse Control Center, Warehouse Studio, Warehouse WORKS, Watcom, Watcom SQL, Watcom SQL Server, Web Deployment Kit, Web.PB, Web.SQL, WebSights, WebViewer, WorkGroup SQL Server, XA-Library, XA-Server, XcelleNet, and XP Server are trademarks of Sybase, Inc. 06/05 Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. All other company and product names used herein may be trademarks or registered trademarks of their respective companies. Use, duplication, or disclosure by the government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of DFARS 52.227-7013 for the DOD and as set forth in FAR 52.227-19(a)-(d) for civilian agencies. Sybase, Inc., One Sybase Drive, Dublin, CA 94568.
Contents
About This Book .......................................................................................................................... xv
PART 1 CHAPTER 1
BASICS OF SYSTEM ADMINISTRATION Overview of System Administration.............................................. 3 Adaptive Server administration tasks ............................................... 3 Roles required for system administration tasks......................... 4 Using isql to perform system administration tasks .................... 7 Using Sybase Central for system administration tasks ............. 8 System tables................................................................................... 9 Querying the system tables ..................................................... 10 Keys in system tables.............................................................. 11 Updating system tables ........................................................... 11 System procedures ........................................................................ 12 Using system procedures ........................................................ 13 System procedure tables......................................................... 13 Creating system procedures ................................................... 14 System extended stored procedures ............................................. 15 Creating system ESPs ............................................................ 15 Logging error messages ................................................................ 15 Connecting to Adaptive Server ...................................................... 16 The interfaces file .................................................................... 16 Directory services .................................................................... 17 LDAP as a directory service .................................................... 18 Security features available in Adaptive Server............................... 20 System and Optional Databases ................................................. Overview of system databases ...................................................... master database ............................................................................ Controlling object creation in master ....................................... Backing up master and keeping copies of system tables........ model database.............................................................................. sybsystemprocs database.............................................................. 23
23 25 27 27 28 29
CHAPTER 2
System Administration Guide: Volume 1
iii
tempdb database............................................................................ 29 Creating temporary tables ....................................................... 30 sybsecurity database...................................................................... 31 sybsystemdb database................................................................... 31 sybmgmtdb database ..................................................................... 32 pubs2 and pubs3 sample databases.............................................. 32 Maintaining the sample databases .......................................... 32 pubs2 image data .................................................................... 33 dbccdb database ............................................................................ 33 sybdiag database ........................................................................... 33 Determining the version of the installation scripts .......................... 33
CHAPTER 3
System Administration for Beginners......................................... 35 Logical page sizes .......................................................................... 35 Using test servers ........................................................................ 36 Understanding new procedures and features.......................... 36 Planning resources .................................................................. 36 Achieving performance goals .................................................. 37 Installing Sybase products.............................................................. 37 Check product compatibility..................................................... 38 Install or upgrade Adaptive Server .......................................... 38 Install additional third-party software ....................................... 38 Configure and test client connections...................................... 39 Allocating physical resources ......................................................... 39 Dedicated versus shared servers ............................................ 40 Decision support and OLTP applications................................. 40 Advance resource planning ..................................................... 40 Operating system configuration ............................................... 41 Backup and recovery...................................................................... 42 Keep up-to-date backups of master......................................... 42 Automate backup procedures.................................................. 43 Verify data consistency before backing up a database ........... 44 Monitor the log size.................................................................. 45 Ongoing maintenance and troubleshooting.................................... 45 Starting and stopping Adaptive Server .................................... 45 Viewing and pruning the error log............................................ 46 Keeping records ............................................................................. 46 Contact information.................................................................. 46 Configuration information......................................................... 47 Maintenance schedules ........................................................... 47 System information .................................................................. 48 Disaster recovery plan ............................................................. 48 Getting more help ........................................................................... 48
iv
Adaptive Server Enterprise
CHAPTER 4
Introduction to the Adaptive Server Plug-in for Sybase Central 49 Overview for Adaptive Server Sybase Central Plug-in ................... 49 Using the Adaptive Server Plug-in.................................................. 50 Starting and stopping Sybase Central ............................................ 51 Registering Adaptive Server Plug-in............................................... 52 Performing common tasks.............................................................. 52 Using Interactive SQL..................................................................... 59 Starting Interactive SQL........................................................... 60 Setting Configuration Parameters ............................................... 61 What are configuration parameters? .............................................. 61 The Adaptive Server configuration file..................................... 62 How to modify configuration parameters ................................. 62 Who can modify configuration parameters? ............................ 62 Unit specification using sp_configure ...................................... 64 Getting help information on configuration parameters............. 64 Using sp_configure......................................................................... 65 Syntax elements ...................................................................... 66 Using sp_configure with a configuration file ............................ 67 The parameter hierarchy ......................................................... 71 User-defined subsets of the parameter hierarchy: display levels . 74 The reconfigure command....................................................... 75 Performance tuning with sp_configure and sp_sysmon .......... 75 Output from sp_configure ............................................................... 76 The sysconfigures and syscurconfigs tables .................................. 78 Querying syscurconfigs and sysconfigures: an example......... 78 Configuration parameters ............................................................... 79 Alphabetical listing of configuration parameters ...................... 79 Overview of Disk Resource Issues ............................................ 237 Device allocation and object placement ....................................... 237 Commands for managing disk resources ..................................... 238 Considerations in storage management decisions....................... 239 Recovery................................................................................ 240 Performance .......................................................................... 240 Status and defaults at installation time ......................................... 241 System tables that manage storage ............................................. 242 The sysdevices table ............................................................. 243 The sysusages table.............................................................. 243 The syssegments table.......................................................... 244 The sysindexes table ............................................................. 244 The syspartitions table........................................................... 244
CHAPTER 5
CHAPTER 6
CHAPTER 7
Initializing Database Devices ..................................................... 245 What are database devices? ........................................................ 245 Using the disk init command......................................................... 246 disk init syntax .............................................................................. 246 disk init examples .................................................................. 247 Specifying a logical device name with disk init ...................... 247 Specifying a physical device name with disk init ................... 247 Choosing a device number for disk init.................................. 247 Specifying the device size with disk init ................................. 248 Specifying the dsync setting with disk init (optional).............. 250 Using directio to bypass operating system buffer .................. 252 Other optional parameters for disk init................................... 253 Getting information about devices ................................................ 253 Dropping devices.......................................................................... 255 Designating default devices.......................................................... 256 Choosing default and nondefault devices.............................. 256 Increasing the size of devices with disk resize ............................. 257 Insufficient disk space............................................................ 258 disk resize syntax .................................................................. 258 Setting Database Options .......................................................... 261 What are database options?......................................................... 261 Using the sp_dboption procedure................................................. 261 Database option descriptions ....................................................... 262 abort tran on log full ............................................................... 263 allow nulls by default.............................................................. 263 asynch log service ................................................................. 263 auto identity ........................................................................... 264 dbo use only .......................................................................... 264 ddl in tran ............................................................................... 264 delayed commit...................................................................... 266 identity in nonunique index .................................................... 266 no chkpt on recovery ............................................................. 266 no free space acctg ............................................................... 267 read only ................................................................................ 267 select into/bulkcopy/pllsort..................................................... 267 single user ............................................................................. 268 trunc log on chkpt .................................................................. 268 unique auto_identity index ..................................................... 269 Changing database options.......................................................... 270 Viewing the options on a database............................................... 271 Configuring Character Sets, Sort Orders, and Languages ..... 273
CHAPTER 8
CHAPTER 9
vi
Understanding internationalization and localization ..................... 273 Advantages of internationalized systems ..................................... 274 A sample internationalized system ............................................... 275 Elements of an internationalized system ...................................... 277 Selecting the character set for your server................................... 277 Unicode.................................................................................. 280 Selecting the server default character set ............................. 284 Selecting the sort order ................................................................ 287 Using sort orders ................................................................... 288 Different types of sort orders ................................................. 288 Selecting the default sort order.............................................. 289 Selecting a language for system messages ................................. 294 Setting up your server: examples ................................................. 296 A Spanish-version server....................................................... 296 A U.S.-based company in Japan ........................................... 296 A Japan-based company with multinational clients ............... 297 Changing the character set, sort order, or message language .... 298 Changing the default character set........................................ 298 Changing the sort order with a resources file ........................ 299 Changing the default sort order ............................................. 300 Reconfiguring the character set, sort order, or message language 300 Unicode examples ................................................................. 301 Preliminary steps ................................................................... 303 Setting the users default language ....................................... 304 Recovery after reconfiguration............................................... 304 Installing date strings for unsupported languages ........................ 308 Server versus client date interpretation ................................. 308 Internationalization and localization files ...................................... 309 Types of internationalization files........................................... 309 Character sets directory structure.......................................... 310 Types of localization files....................................................... 311 Software messages directory structure ................................. 311 Message languages and global variables.............................. 312
CHAPTER 10
Configuring Client/Server Character Set Conversions............ 313 Character set conversion in Adaptive Server ............................... 313 Supported character set conversions ........................................... 314 Conversion for native character sets ..................................... 314 Conversion in a Unicode system ........................................... 315 Types of character set conversion................................................ 316 Adaptive Server direct conversions ....................................... 316 Unicode conversions ............................................................. 316 Which type of conversion do I use?.............................................. 317
vii
Non-Unicode client/server systems ....................................... 317 Unicode client/server systems ............................................... 318 Configuring the server ........................................................... 318 Enabling and disabling character set conversion ......................... 319 Characters that cannot be converted..................................... 320 Error handling in character set conversion ................................... 320 Conversions and changes to data lengths ................................... 321 Configuring your system and application............................... 322 Specifying the character set for utility programs........................... 322 Display and file character set command line options ................... 323 Setting the display character set............................................ 324 Setting the file character set .................................................. 324
CHAPTER 11
Diagnosing System Problems ................................................... 325 How Adaptive Server uses error messages ................................. 325 Error messages and message numbers................................ 327 Variables in error message text ............................................. 327 Adaptive Server error logging....................................................... 328 Error log format...................................................................... 329 Severity levels........................................................................ 330 Security levels 1018............................................................. 331 Severity levels 1926............................................................. 334 Reporting errors..................................................................... 336 Backup Server error logging......................................................... 337 Killing processes........................................................................... 338 Using kill with status only....................................................... 341 Using sp_lock to examine blocking processes ...................... 342 Housekeeper functionality ............................................................ 342 Three housekeepers.............................................................. 343 Housekeeper wash ................................................................ 343 Housekeeper chores.............................................................. 343 Housekeeper garbage collection ........................................... 343 Configuring enable housekeeper GC .................................... 344 Configuring Adaptive Server to save SQL batch text ................... 346 Allocating memory for batch text ........................................... 346 SQL commands not represented by text ............................... 348 Viewing the query plan of a SQL statement .......................... 349 Viewing a nested procedure .................................................. 350 Shutting down servers .................................................................. 351 Shutting down Adaptive Server ............................................. 351 Shutting down a Backup Server ............................................ 352 Learning about known problems .................................................. 353
viii
PART 2 CHAPTER 12
SECURITY ADMINISTRATION Introduction to Security .............................................................. 357 Introduction to security ................................................................. 357 What is information security? ..................................................... 358 Information security standards ..................................................... 359 Adaptive Server version 12.5.2 available for common criteria configuration ................................................................... 359 C2 security evaluation for Adaptive Server release 11.0.6.... 360 FIPS 140-2 Validated cryptographic module ......................... 361 Getting Started With Security Administration in Adaptive Server. 363 General process of security administration .................................. 363 Recommendations for setting up security .................................... 364 Using the sa login................................................................ 365 Changing the sa login password ......................................... 365 When to enable auditing ........................................................ 365 Assigning login names........................................................... 365 An example of setting up security................................................. 366 Introduction to Security Features in Adaptive Server ................... 367 Identification and authentication ................................................... 368 External authentication ................................................................. 368 Managing remote servers............................................................. 369 Discretionary access controls....................................................... 369 Policy-Based Access Control................................................. 370 Division of roles ............................................................................ 371 Role hierarchy........................................................................ 371 Mutual exclusivity................................................................... 371 Auditing for accountability............................................................. 372 Confidentiality of data ................................................................... 372 Password-Protected Database Backup ................................. 373 Managing Adaptive Server Logins, Database Users, and Client Connections .......................................................................... 375 Overview....................................................................................... 376 Choosing and creating a password .............................................. 377 Adding logins to Adaptive Server ................................................. 377 Login failure to Adaptive Server ................................................... 380 Creating groups ............................................................................ 380 Adding users to databases ........................................................... 381 Adding a guest user to a database...................................... 382
CHAPTER 13
CHAPTER 14
ix
Adding a guest user to the server.......................................... 384 Adding remote users.............................................................. 384 Number of user and login IDs....................................................... 385 Limits and ranges of ID numbers........................................... 385 Login connection limitations................................................... 385 Viewing server limits for logins, users, and groups................ 386 Creating and assigning roles to users .......................................... 387 System-defined roles ............................................................. 387 System Administrator privileges ............................................ 388 System Security Officer privileges ......................................... 389 Operator privileges ................................................................ 390 Sybase technical support....................................................... 390 Replication role ...................................................................... 390 Distributed Transaction Manager role.................................... 391 High availability role............................................................... 391 Monitoring and diagnosis....................................................... 391 Job Scheduler roles ............................................................... 391 Real-Time Messaging role..................................................... 392 Web Services role.................................................................. 392 User-defined roles ................................................................. 392 Adding and removing passwords from a role ........................ 393 Role hierarchies and mutual exclusivity................................. 394 Role heirarchies and mutual exclusivity................................. 394 Setting up default activation at login ...................................... 398 Activating and deactivating roles ........................................... 399 Dropping users, groups, and user-defined roles .......................... 399 Dropping users ...................................................................... 400 Dropping groups .................................................................... 400 Dropping user-defined roles .................................................. 400 Locking or dropping Adaptive Server login accounts ................... 401 Locking and unlocking login accounts ................................... 402 Dropping login accounts ........................................................ 402 Locking logins that own thresholds........................................ 402 Changing user information ........................................................... 403 Changing passwords ............................................................. 404 Changing user defaults.......................................................... 405 Changing a users group membership................................... 406 Changing the user process information ................................. 407 Using aliases in databases........................................................... 408 Adding aliases ....................................................................... 409 Dropping aliases .................................................................... 410 Getting information about aliases .......................................... 410 Getting information about users ................................................... 411 Getting reports on users and processes................................ 411
Getting information about login accounts .............................. 412 Getting information about database users............................. 412 Finding user names and IDs.................................................. 413 Displaying information about roles......................................... 414 Establishing a password and login policy ..................................... 417 Setting and changing the maximum login attempts ............... 418 Logging in after lost password ............................................... 420 Locking and unlocking logins and roles ................................. 421 Displaying password information ........................................... 422 Checking passwords for at least one digit ............................. 423 Setting and changing minimum password length .................. 423 Setting the expiration interval for a password........................ 425 Monitoring license use.................................................................. 428 How licenses are counted...................................................... 429 Configuring the License Use Manager to monitor user licenses .. 429 Monitoring license use with the housekeeper task ................ 430 Logging the number of user licenses..................................... 430 Getting information about usage: chargeback accounting ........... 431 Reporting current usage statistics ......................................... 432 Specifying the interval for adding accounting statistics ......... 432
CHAPTER 15
Managing Remote Servers ......................................................... 435 Overview....................................................................................... 435 Managing remote servers............................................................. 436 Adding a remote server ......................................................... 437 Managing remote server names ............................................ 438 Setting server connection options.......................................... 439 Getting information about servers.......................................... 441 Dropping remote servers ....................................................... 441 Adding remote logins.................................................................... 442 Mapping users server IDs ..................................................... 442 Mapping remote logins to particular local names .................. 443 Mapping all remote logins to one local name ........................ 443 Keeping remote login names for local servers....................... 444 Example of remote user login mapping ................................. 444 Password checking for remote users ........................................... 446 Effects of using the untrusted mode ...................................... 446 Getting information about remote logins....................................... 447 Configuration parameters for remote logins ................................. 447 Allowing remote access ......................................................... 448 Controlling the number of active user connections................ 448 Controlling the number of remote sites.................................. 449 Controlling the number of active remote connections............ 449
xi
Controlling number of preread packets.................................. 449
CHAPTER 16
External Authentication.............................................................. 451 Overview....................................................................................... 451 Configuring Adaptive Server for Network-Based Security............ 452 How applications use security services ................................. 452 Security services and Adaptive Server .................................. 453 Administering network-based security ................................... 454 Setting up configuration files for security ............................... 455 Identifying users and servers to the security mechanism ...... 461 Configuring Adaptive Server for security ............................... 462 Restarting the server to activate security services ................ 466 Adding logins to support unified login .................................... 467 Establishing security for remote procedures.......................... 468 Connecting to the server and using the security services ..... 475 Getting information about available security services............ 478 Using Kerberos ...................................................................... 480 Configuring Adaptive Server for LDAP User Authenticaiton......... 486 Composed DN algorithm ....................................................... 487 Searched DN algorithm ......................................................... 487 Configuring LDAP .................................................................. 488 LDAP administration .............................................................. 489 Adaptive Server logins and LDAP user accounts .................. 492 Configuring Adaptive Server for authentication using PAM.......... 493 Enabling PAM in Adaptive Server.......................................... 494 Enhanced login controls ............................................................... 497 Forcing authentication ........................................................... 497 Mapping logins using sp_maplogin........................................ 498 Managing User Permissions ...................................................... 501 Overview....................................................................................... 501 Permissions for creating databases ............................................. 503 Changing database ownership .............................................. 503 Database Owner privileges .......................................................... 504 Permissions on system procedures....................................... 505 Database object owner privileges................................................. 506 Other database user privileges..................................................... 506 Granting and revoking permissions .............................................. 507 Object access permissions .................................................... 507 Granting permissions on functions ........................................ 516 Granting and revoking permissions to execute commands ... 517 Granting permissions on dbcc commands............................. 520 Permissions on system tables ............................................... 521
CHAPTER 17
xii
Combining grant and revoke statements ............................... 523 Understanding permission order and hierarchy..................... 524 Grant dbcc and set proxy issue warning for fipsflagger......... 525 Granting and revoking roles ......................................................... 525 Granting roles ........................................................................ 526 Understanding grant and roles .............................................. 526 Revoking roles ....................................................................... 527 Using row-level access control ..................................................... 528 Access rules .......................................................................... 528 Using the Application Context Facility ................................... 538 Creating and using application contexts ................................ 540 SYS_SESSION system application context .......................... 544 Solving a problem using an access rule and ACF ................. 545 Using login triggers ................................................................ 547 Acquiring the permissions of another user ................................... 555 Using setuser......................................................................... 555 Using proxy authorization ...................................................... 556 Reporting on permissions............................................................. 560 Querying the sysprotects table for proxy authorization.......... 561 Displaying information about users and processes ............... 561 Reporting permissions on database objects or users............ 562 Reporting permissions on specific tables .............................. 563 Reporting permissions on specific columns........................... 564 Using views and stored procedures as security mechanisms ...... 565 Using views as security mechanisms .................................... 565 Using stored procedures as security mechanisms ................ 567 Understanding ownership chains........................................... 568 Permissions on triggers ......................................................... 572
CHAPTER 18
Auditing ........................................................................................ 573 Introduction to auditing in Adaptive Server................................... 573 Correlating Adaptive Server and operating system audit records 574 The audit system ................................................................... 574 Installing and setting up auditing .................................................. 578 Installing the audit system ..................................................... 578 Setting up audit trail management ......................................... 582 Setting up transaction log management ................................ 588 Enabling and disabling auditing ............................................. 589 Single-table auditing .............................................................. 590 Restarting auditing................................................................. 593 Setting global auditing options...................................................... 594 Auditing options: types and requirements.............................. 594 Determining current auditing settings .................................... 601
xiii
Adding user-specified records to the audit trail...................... 601 Querying the audit trail ................................................................. 603 Understanding the audit tables..................................................... 603 Reading the extrainfo column ................................................ 604 Auditing login failures............................................................. 612
CHAPTER 19
Confidentiality of Data ................................................................ 615 Secure Sockets Layer (SSL) in Adaptive Server.......................... 615 Internet communications overview ........................................ 616 SSL in Adaptive Server.......................................................... 618 Enabling SSL ......................................................................... 622 Performance .......................................................................... 628 Cipher Suites ......................................................................... 628 Setting SSL cipher suite preferences .................................... 629 Kerberos confidentiality ................................................................ 635 Dumping and loading databases with password protection ......... 635 Passwords and earlier versions of Adaptive Server .............. 636 Passwords and character sets............................................... 636
Index............................................................................................................................................ 637
xiv
About This Book
This manual, the Sybase Adaptive Server System Administration Guide, describes how to administer and control Sybase Adaptive Server Enterprise databases independent of any specific database application.
Audience How to use this book
This manual is for Sybase System Administrators and Database Owners. This guide (System Administration Guide Volume 1) is comprised of two parts: Part One describes the concepts of system administration, Part Two discusses security administration issues. Part One includes the following chapters: Chapter 1, Overview of System Administration, describes the structure of the Sybase system. Chapter 2, System and Optional Databases, discusses the contents and function of the Adaptive Server system databases. Chapter 3, System Administration for Beginners, summarizes important tasks that new System Administrators must perform. Chapter 4, Introduction to the Adaptive Server Plug-in for Sybase Central, describes how to start and use Sybase Central, a graphical user interface for managing Adaptive Server. Chapter 5, Setting Configuration Parameters, summarizes the configuration parameters that you set with sp_configure, which control many aspects of Adaptive Server behavior. Chapter 6, Overview of Disk Resource Issues, discusses Adaptive Server and Backup Server error handling and how to shut down servers and kill user processes. Chapter 7, Initializing Database Devices, describes how to initialize database devices and assign devices to the default pool of devices. Chapter 8, Setting Database Options, describes how to set database options.
xv
Chapter 9, Configuring Character Sets, Sort Orders, and Languages, discusses international issues, such as the files included in the Language Modules and how to configure an Adaptive Server language, sort order, and character set. Chapter 10, Configuring Client/Server Character Set Conversions, discusses character set conversion between Adaptive Server and clients in a heterogeneous environment. Chapter 11, Diagnosing System Problems, discusses Adaptive Server and Backup Server error handling and shows how to shut down servers and kill user processes.
Part Two includes these chapters: Chapter 12, Introduction to Security, introduces you to security concepts. Chapter 13, Getting Started With Security Administration in Adaptive Server, provides an overview of the security features available in Adaptive Server. Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections, describes methods for managing Adaptive Server login accounts and database users. Chapter 15, Managing Remote Servers, discusses the steps the System Administrator and System Security Officer of each Adaptive Server must execute to enable remote procedure calls (RPCs). Chapter 16, External Authentication, describes the network-based security services that enable you to authenticate users and protect data transmitted among machines on a network. Chapter 17, Managing User Permissions, describes the use and implementation of user permissions. Chapter 18, Auditing, describes how to set up auditing for your installation. Chapter 19, Confidentiality of Data, describes how to configure Adaptive Server to ensure that all data is secure and confidential.
Volume 2 of the System Administration Guide contains these chapters Chapter 1, Limiting Access to Server Resources, explains how to create and manage resource limits with Adaptive Server.
xvi
About This Book
Chapter 2, Mirroring Database Devices, describes how to mirror database devices for nonstop recovery from media failures. Chapter 3, Configuring Memory, explains how to configure Adaptive Server to use the available memory on your system. Chapter 4, Configuring Data Caches, discusses how to create named caches in memory and bind objects to those caches. Chapter 5, Managing Multiprocessor Servers, explains how to use multiple CPUs with Adaptive Server and discusses system administration issues that are unique to symmetric multiprocessing (SMP) environments. Chapter 6, Creating and Managing User Databases, discusses the physical placement of databases, tables, and indexes, and the allocation of space to them. Chapter 7, Database Mount and Unmount, describes how to transport databases from a source Adaptive Server to a destination Adaptive Server. Chapter 8, Creating and Using Segments, describes how to use segments, which are named collections of database devices, in databases. Chapter 9, Using the reorg Command, describes how to use the reorg command. Chapter 10, Checking Database Consistency, describes how to use the database consistency checker, dbcc, to detect and fix database problems. Chapter 11, Developing a Backup and Recovery Plan, discusses the capabilities of the Backup Server and how to develop your backup strategy. Chapter 12, Backing Up and Restoring User Databases, discusses how to recover user databases. Chapter 13, Restoring the System Databases, discusses how to recover system databases. Chapter 14, Automatic Database Expansion, describes how to configure databases to expand automatically when they run out of space. Chapter 15, Managing Free Space with Thresholds, discusses managing space with thresholds.

Related documents
The Sybase Adaptive Server Enterprise documentation set consists of the following: The release bulletin for your platform contains last-minute information that was too late to be included in the books.
xvii
A more recent version of the release bulletin may be available on the World Wide Web. To check for critical product or document information that was added after the release of the product CD, use the Sybase Technical Library. The Installation Guide for your platform describes installation, upgrade, and configuration procedures for all Adaptive Server and related Sybase products. Whats New in Adaptive Server Enterprise? describes the new features in Adaptive Server version 15.0, the system changes added to support those features, and changes that may affect your existing applications. ASE Replicator Users Guide describes how to use the Adaptive Server Replicator feature of Adaptive Server to implement basic replication from a primary server to one or more remote Adaptive Servers. Component Integration Services Users Guide explains how to use the Adaptive Server Component Integration Services feature to connect remote Sybase and non-Sybase databases. The Configuration Guide for your platform provides instructions for performing specific configuration tasks for Adaptive Server. Full-Text Search Specialty Data Store Users Guide describes how to use the Full-Text Search feature with Verity to search Adaptive Server Enterprise data. Glossary defines technical terms used in the Adaptive Server documentation. Historical Server Users Guide describes how to use Historical Server to obtain performance information for SQL Server and Adaptive Server. Java in Adaptive Server Enterprise describes how to install and use Java classes as data types, functions, and stored procedures in the Adaptive Server database. Job Scheduler User's Guide provides instructions on how to install and configure, and create and schedule jobs on a local or remote Adaptive Server using the command line or a graphical user interface (GUI). Messaging Service Users Guide describes how to useReal Time Messaging Services to integrate TIBCO Java Message Service and IBM WebSphere MQ messaging services with all Adaptive Server database applications.
xviii
About This Book
Monitor Client Library Programmers Guide describes how to write Monitor Client Library applications that access Adaptive Server performance data. Monitor Server Users Guide describes how to use Monitor Server to obtain performance statistics from SQL Server and Adaptive Server. Performance and Tuning Guide is a series of four books for Adaptive Server version 12.5.x that explains how to tune Adaptive Server for maximum performance: Basics the basics for understanding and investigating performance questions in Adaptive Server. Locking describes how the various locking schemas can be used for improving performance in Adaptive Server. Optimizer and Abstract Plans describes how the optimizer processes queries and how abstract plans can be used to change some of the optimizer plans. Monitoring and Analyzing explains how statistics are obtained and used for monitoring and optimizing performance.
Quick Reference Guide provides a comprehensive listing of the names and syntax for commands, functions, system procedures, extended system procedures, datatypes, and utilities in a pocket-sized book. Reference Manual is a series of four books that contains the following detailed Transact-SQL information: Building Blocks Transact-SQL datatypes, functions, global variables, expressions, identifiers and wildcards, and reserved words. Commands Transact-SQL commands. Procedures Transact-SQL system procedures, catalog stored procedures, system extended stored procedures, and dbcc stored procedures. Tables Transact-SQL system tables and dbcc tables.
System Administration Guide provides in-depth information about administering servers and databases. This manual includes instructions and guidelines for managing physical resources, security, user and system databases, and specifying character conversion, international language, and sort order settings.
xix
System Tables Diagram illustrates system tables and their entity relationships in a poster format. Available only in print version. Transact-SQL Users Guide documents Transact-SQL, Sybases enhanced version of the relational database language. This manual serves as a textbook for beginning users of the database management system. This manual also contains descriptions of the pubs2 and pubs3 sample databases. Using Adaptive Server Distributed Transaction Management Features explains how to configure, use, and troubleshoot Adaptive Server DTM features in distributed transaction processing environments. Using Sybase Failover in a High Availability System provides instructions for using Sybases Failover to configure an Adaptive Server as a companion server in a high availability system. Unified Agent and Agent Management Console Describes the Unified Agent, which provides runtime services to manage, monitor and control distributed Sybase resources. Utility Guide documents the Adaptive Server utility programs, such as isql and bcp, which are executed at the operating system level. Web Services Users Guide explains how to configure, use, and troubleshoot Web Services for Adaptive Server. XA Interface Integration Guide for CICS, Encina, and TUXEDO provides instructions for using the Sybase DTM XA interface with X/Open XA transaction managers. XML Services in Adaptive Server Enterprise describes the Sybase native XML processor and the Sybase Java-based XML support, introduces XML in the database, and documents the query and mapping functions that comprise XML Services.
Other sources of information
Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product: The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.
xx
About This Book
The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format. Some documentation may be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the PDF files, you need Adobe Acrobat Reader. Refer to the SyBooks Installation Guide on the Getting Started CD, or the README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.
The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network. To access the Sybase Product Manuals Web site, go to Product Manuals at
http://www.sybase.com/support/manuals/.
Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications
1 2 3 4 5
Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/. Select Products from the navigation bar on the left. Select a product name from the product list and click Go. Select the Certification Report filter, specify a time frame, and click Go. Click a Certification Report title to display the report.
Finding the latest information on component certifications
1 2 3
Point your Web browser to Availability and Certification Reports at http://certification.sybase.com/. Either select the product family and product under Search by Product; or select the platform and product under Search by Platform. Select Search to display the availability and certification report for the selection.
xxi
Conventions
Creating a personalized view of the Sybase Web site (including support pages)
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages. 1 2
Sybase EBFs and software maintenance Finding the latest information on EBFs and software maintenance
Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/. Click MySybase and create a MySybase profile.
1 2 3 4
Point your Web browser to the Sybase Support Page at http://www.sybase.com/support. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password. Select a product. Specify a time frame and click Go. A list of EBFs/Maintenance releases is displayed. Padlock icons indicate that you do not have download authorization for certain EBFs/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the Technical Support Contact role to your MySybase profile.
Click the Info icon to display the EBFs/Maintenance report, or click the product description to download the software.
Conventions
This section describes the style conventions used in this manual.
xxii
About This Book
Formatting SQL statements

SQL is a free-form language: there are no rules about the number of words you can put on a line or where you must break a line. However, for readability, all examples and syntax statements in this manual are formatted so that each clause of a statement begins on a new line. Clauses that have more than one part extend to additional lines, which are indented.
SQL syntax conventions

Table 1 lists the conventions for syntax statements in this manual:
Table 1: Syntax statement conventions Key
command
Definition Command names, command option names, utility names, utility flags, and other keywords are in
Courier
variable
{ } [ ]
( ) | ,
in syntax statements, and in bold Helvetica in paragraph text. Variables, or words that stand for values that you fill in, are in italics. Curly braces indicate that you choose at least one of the enclosed options. Do not include braces in your option. Square brackets indicate that choosing one or more of the enclosed options is optional. Do not include brackets in your option. Type parentheses as part of the command. The vertical bar means you may select only one of the options shown. The comma means you may choose as many of the options shown as you like, separating your choices with commas.
Syntax statements (displaying the syntax and all options for a command) are printed like this:
sp_dropdevice [device_name]
or, for a command with more options:

select column_name from table_name where search_conditions
xxiii
Conventions
In syntax statements, keywords (commands) are in normal font and identifiers are in lowercase: normal font for keywords, italics for usersupplied words. Examples showing the use of Transact-SQL commands are printed like this:
select * from publishers
pub_id ------0736 0877 1389
Examples of output from the computer are printed like this:

city ----------Boston Washington Berkeley state ----MA DC CA
pub_name ------------------New Age Books Binnet & Hardley Algodata Infosystems
(3 rows affected)
Case
You can disregard case when you type keywords:
SELECT is the same as Select is the same as select.
Obligatory options {you must choose at least one}

Curly braces and vertical bars: Choose only one option.
{die_on_your_feet | live_on_your_knees | live_on_your_feet}
Curly braces and commas: Choose one or more options. If you choose more than one, separate your choices with commas.
{cash, check, credit}
Optional options
One item in square brackets: You do not have to choose it.
[anchovies]
Square brackets and vertical bars: Choose none or only one.

[beans | rice | sweet_potatoes]
Square brackets and commas: Choose none, one, or more than one option. If you choose more than one, separate your choices with commas.
xxiv
About This Book
[extra_cheese, avocados, sour_cream]
Ellipsis
An ellipsis (. . .) means that you can repeat the last unit as many times as you like. In this syntax statement, buy is a required keyword:
buy thing = price [cash | check | credit] [, thing = price [cash | check | credit] ]...
You must buy at least one thing and give its price. You may choose a method of payment: one of the items enclosed in square brackets. You may also choose to buy additional things: as many of them as you like. For each thing you buy, give its name, its price, and (optionally) a method of payment. An ellipsis may also be used inline to signify portions of a command that are omitted from a text example. The following syntax statement represents the complete create database command, even though required keywords and other options are missing:
create database...for load
Expressions
Several different types of expressions are used in Adaptive Server syntax statements.
Table 2: Types of expressions used in syntax statements Usage expression logical_expression constant_expression float_expr integer_expr numeric_expr char_expr binary_expression Accessibility features Definition Can include constants, literals, functions, column identifiers, variables, or parameters An expression that returns TRUE, FALSE, or UNKNOWN An expression that always returns the same value, such as 5+3 or ABCDE Any floating-point expression or expression that implicitly converts to a floating value Any integer expression or an expression that implicitly converts to an integer value Any numeric expression that returns a single value An expression that returns a single character-type value An expression that returns a single binary or varbinary value
This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.
xxv
Conventions
Adaptive Server documentation has been tested for compliance with U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.
Note You might need to configure your accessibility tool for optimal use.
Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool. For information about how Sybase supports accessibility, see Sybase Accessibility at http://www.sybase.com/accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.
xxvi
PA RT
Basics of System Administration
The following chapters introduce the concepts of system administration in Adaptive Server: Chapter 1, Overview of System Administration, describes the structure of the Sybase system. Chapter 2, System and Optional Databases, discusses the contents and function of the Adaptive Server system databases. Chapter 3, System Administration for Beginners, summarizes important tasks that new System Administrators must perform. Chapter 4, Introduction to the Adaptive Server Plug-in for Sybase Central, describes how to start and use Sybase Central, a graphical user interface for managing Adaptive Server. Chapter 5, Setting Configuration Parameters, summarizes the configuration parameters that you set with sp_configure, which control many aspects of Adaptive Server behavior. Chapter 6, Overview of Disk Resource Issues, provides an overview of Adaptive Server disk resource issues. Chapter 7, Initializing Database Devices, describes how to initialize database devices and assign devices to the default pool of devices. Chapter 8, Setting Database Options, describes how to set database options.
Chapter 9, Configuring Character Sets, Sort Orders, and Languages, discusses international issues, such as the files included in the Language Modules and how to configure an Adaptive Server language, sort order, and character set. Chapter 10, Configuring Client/Server Character Set Conversions, discusses character set conversion between Adaptive Server and clients in a heterogeneous environment. Chapter 11, Diagnosing System Problems, discusses Adaptive Server and Backup Server error handling and how to shut down servers and kill user processes.
CH A PTE R
Overview of System Administration
This chapter introduces the basic topics of Adaptive Server system administration.
Topic Adaptive Server administration tasks System tables System procedures System extended stored procedures Logging error messages Connecting to Adaptive Server Security features available in Adaptive Server Page 3 9 12 15 15 16 20
Adaptive Server administration tasks

Administering Adaptive Server includes tasks such as: Installing Adaptive Server and Backup Server Creating and managing Adaptive Server login accounts Granting roles and permissions to Adaptive Server users Managing and monitoring the use of disk space, memory, and connections Backing up and restoring databases Diagnosing system problems Configuring Adaptive Server to achieve the best performance
In addition, System Administrators may assist with certain database design tasks that overlap with the work of application designers, such as enforcing integrity standards.
Although a System Administrator concentrates on tasks that are independent of the applications running on Adaptive Server, he or she is likely to be the person with the best overview of all the applications. For this reason, a System Administrator can advise application designers about the data that already exists on Adaptive Server, make recommendations about standardizing data definitions across applications, and so on. However, the distinction between what is specific to an application is sometimes unclear. Owners of user databases may consult certain sections of this book. Similarly, System Administrators and Database Owners will use the Transact-SQL Users Guide (especially the chapters on data definition, stored procedures, and triggers). Both System Administrators and application designers will use the Performance and Tuning Guide.
Roles required for system administration tasks

Many of the commands and procedures discussed in this manual require the System Administrator or System Security Officer role. Other sections in this manual are relevant to Database Owners. Various security-related, administrative, and operational tasks are grouped into the following system roles: System Administrator by default the system administrator (sa) has the following roles: sa_role sso_role oper_role sybase_ts_role
The system administrators tasks include: Managing disk storage Monitoring Adaptive Servers automatic recovery procedure Fine-tuning Adaptive Server by changing configurable system parameters Diagnosing and reporting system problems Backing up and loading databases Modifying and dropping server login accounts
CHAPTER 1
Granting and revoking the System Administrator role Granting permissions to Adaptive Server users Creating user databases and granting ownership of them Setting up groups, which can be used for granting and revoking permissions
System Security Officer performs security-related tasks such as: Creating server login accounts, which includes assigning initial passwords Changing the password of any account Granting and revoking the System Security Officer and Operator roles Creating, granting, and revoking user-defined roles Granting the capability to impersonate another user throughout the server Setting the password expiration interval Setting up Adaptive Server to use network-based security services Managing the audit system
Operator a user who can back up and load databases on a server-wide basis. The Operator role allows a single user to use the dump database, dump transaction, load database, and load transaction commands to back up and restore all databases on a server without having to be the owner of each one. These operations can be performed for an individual database by the database owner or by a System Administrator. However, an Operator can perform them for any database.
These roles provide individual accountability for users performing operational and administrative tasks. Their actions can be audited and attributed to them. A System Administrator operates outside the discretionary access control (DAC) protection system; that is, when a System Administrator accesses objects, Adaptive Server does not check the DAC permissions. In addition, two kinds of object owners have special status because of the objects they own. These ownership types are: Database Owner Database object owner
Database Owner
The Database Owner is the creator of a database or someone to whom database ownership has been transferred. A System Administrator grants users the authority to create databases with the grant command. A Database Owner logs in to Adaptive Server using his or her assigned login name and password. In other databases, that owner is known by his or her regular user name. In the database, Adaptive Server recognizes the user as having the dbo account. A Database Owner can: Run the system procedure sp_adduser to allow other Adaptive Server users access to the database Use the grant command to give other users permission to create objects and execute commands within the database
Adding users to databases is discussed in Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections. Granting permissions to users is discussed in Chapter 17, Managing User Permissions. The Database Owner does not automatically receive permissions on objects owned by other users. However, a Database Owner can temporarily assume the permissions of other users in the database at any time by using the setuser command. Using a combination of the setuser and grant commands, the Database Owner can acquire permissions on any object in the database.
Note Because the Database Owner role is so powerful, the System
Administrator should plan carefully who should own databases in the server. The System Security Officer should consider auditing the database activity of all Database Owners.
Database object owner

A Database object owner is a user who creates a database object. Database objects are tables, indexes, views, defaults, triggers, rules, constraints, and procedures. Before a user can create a database object, the Database Owner must grant the user permission to create objects of a particular type. There is no special login name or password for a database object owner. The database object owner creates an object using the appropriate create statement, and then grants permission to other users.
CHAPTER 1
The creator of a database object is automatically granted all permissions on that object. The System Administrator also has all permissions on the object. The owner of an object must explicitly grant permissions to other users before they can access the object. Even the Database Owner cannot use an object directly unless the object owner grants him or her the appropriate permission. However, the Database Owner can always use the setuser command to impersonate any other user in the database, including the object owner.
Note When a database object is owned by someone other than the Database
Owner, the user (including a System Administrator) must qualify the name of that object with the object owners nameownername.objectnameto access the object. If an object or a procedure must be accessed by a large number of users, particularly in ad hoc queries, having these objects owned by dbo greatly simplifies access.
Using isql to perform system administration tasks

This book assumes that the system administration tasks described in this guide are performed using the command line utility isql. This section provides some basic information about using isql. For complete information, see the Utility Guide. You can also use the graphic tool Sybase Central to perform many of the tasks described in this book, as described in Using Sybase Central for system administration tasks on page 8.
Starting isql
To start isql on most platforms, type this command at an operating system prompt, where username is the user name of the System Administrator:
isql -Uusername
Adaptive Server prompts you for your password.

Note Do not use the -P option of isql to specify your password; another user
might then see your password. You can use isql in command line mode to enter many of the Transact-SQL examples in this manual.
Entering statements
The statements that you enter in isql can span several lines. isql does not process statements until you type go on a separate line. For example:
1> 2> 3> 4> select * from sysobjects where type = "TR" go
The examples in this manual do not include the go command between statements. If you are typing the examples, you must enter the go command to see the sample output.
Saving and reusing statements

This manual frequently suggests that you save the Transact-SQL statements you use to create or modify user databases and database objects. The easiest way to do this is to create or copy the statements to an ASCII-formatted file. You can then use the file to supply statements to isql to re-create databases or database objects later. The syntax for using isql with an ASCII-formatted file is the following, where filename is the full path and file name of the file that contains Transact-SQL statements:
isql -Uusername -ifilename
On UNIX and other platforms, use the less than symbol (<) to redirect the file. The Transact-SQL statements in the ASCII file must use valid syntax and the go command. When reading commands from a file, you must: Supply the -Ppassword option at the command line, or, Include the named user's password on the first line of the input file.
Using Sybase Central for system administration tasks

You can accomplish many of the system administration tasks detailed in this book with Sybase Central, a graphic tool that comes with Adaptive Server. Here are some of the tasks you can use Sybase Central for:
CHAPTER 1
Initializing database devices Setting configuration parameters Viewing the amount of free log space in a database Generating data definition language (DDL) Creating logins Adding remote servers Creating databases Creating stored procedures Defining roles Adding data caches Setting database options Backing up and restoring databases
You can also use the Monitor Viewer feature of Sybase Central to access Adaptive Server Monitor. Sybase Central also comes with extensive online help. You can use the Sybase Central DDL-generation feature to record your work to Transact-SQL scripts. The DDL-generation feature lets you save to a script the actions you performed in an entire server or within a specific database.
System tables
The master database contains system tables that keep track of information about Adaptive Server. In addition, each database (including the master database) contains system tables that keep track of information specific to that database. All the Adaptive Server-supplied tables in the master database (Adaptive Servers controlling database) are considered system tables. Each user database is created with a subset of these system tables. The system tables may also be referred to as the data dictionary or the system catalogs.
System tables
A master database and its tables are created automatically when Adaptive Server is installed. The system tables in a user database are created when the create database command is issued. The names of all system tables start with sys. You cannot create tables in user databases that have the same names as system tables. An explanation of the system tables and their columns is in the Reference Manual.
Querying the system tables

You can query system tables in the same manner as any other tables. For example, the following statement returns the names of all the triggers in the database:
select name from sysobjects where type = "TR"
In addition, Adaptive Server supplies stored procedures (called system procedures), many of which provide shortcuts for querying the system tables. Here are the system procedures that provide information from the system tables:
sp_commonkey sp_configure sp_countmedatada sp_dboption sp_estspace sp_help sp_helpartition sp_helpcache sp_helpconfig sp_helpconstraint sp_helpdb sp_helpdevice sp_helpgroup sp_helpindex sp_helpjava sp_helpjoins sp_helpkey sp_helplanguage sp_helpremotelogin sp_help_resource_limit sp_helprotect sp_helpsegment sp_helpserver sp_helpsort sp_helptext sp_helpthreshold sp_helpuser sp_lock sp_monitor sp_monitorconfig sp_showcontrolinfo sp_showexeclass sp_showplan sp_spaceused sp_who sp_help_resource_limit
10
CHAPTER 1
sp_helplog
For complete information about the system procedures, see the Reference Manual.
Keys in system tables

Primary, foreign, and common keys for the system tables are defined in the master and model databases. You can generate a report on defined keys by executing sp_helpkey. For a report on columns in two system tables that are likely join candidates, execute sp_helpjoins. The Adaptive Server System Tables Diagram included with Adaptive Server shows the relationships between columns in the system tables.
Updating system tables

The Adaptive Server system tables contain information that is critical to the operation of your databases. Under ordinary circumstances, you need not perform direct data modifications to system tables. Update system tables only when you are instructed to do so by Sybase Technical Support or by an instruction in the Error Messaging and Troubleshooting Guide or in this manual. When you update system tables, you must issue an sp_configure command that enables system table updates. While this command is in effect, any user with appropriate permission can modify a system table. Other requirements for direct changes to system tables are: Modify system tables only inside a transaction. Issue a begin transaction command before you issue the data modification command. Verify that only the rows you wanted changed were affected by the command and that the data was changed correctly.
11
System procedures
If the command was incorrect, issue a rollback transaction command. If the command was correct, issue a commit transaction command.
Warning! Some system tables should not be altered by any user under any circumstances. Some system tables are built dynamically by system processes, contain encoded information, or display only a portion of their data when queried. Imprudent, ad hoc updates to certain system tables can make Adaptive Server unable to run, make database objects inaccessible, scramble permissions on objects, or terminate a user session. Moreover, you should never attempt to alter the definition of the system tables in any way. For example, do not alter system tables to include constraints. Triggers, defaults, and rules are not allowed in system tables. If you try to create a trigger or bind a rule or default to a system table, you will get an error message.
System procedures
The names of all system procedures begin with sp_. They are located in the sybsystemprocs database, but you can run many of them in any database by issuing the stored procedure from the database or by qualifying the procedure name with the database name. Sybase-supplied system procedures (such as sp_who) are created using the installmaster installation script. You can use sp_version to determine which version of installmaster was run last. See the Reference Manual: System Procedures for more information about sp_version. If you execute a system procedure in a database other than sybsystemprocs, it operates on the system tables in the database from which it was executed. For example, if the Database Owner of pubs2 runs sp_adduser from pubs2 or issues the command pubs2..sp_adduser, the new user is added to pubs2..sysusers. However, this does not apply to system procedures that update only tables in the master database. Permissions on system procedures are discussed in the Reference Manual.
12
CHAPTER 1
Using system procedures

A parameter is an argument to a stored or system procedure. If a parameter value for a system procedure contains reserved words, punctuation, or embedded blanks, it must be enclosed in single or double quotes. If the parameter is an object name, and the object name is qualified by a database name or owner name, the entire name must be enclosed in single or double quotes. System procedures can be invoked by sessions using either chained or unchained transaction mode. However, you cannot execute the system procedures that modify data in system tables in the master database from within a transaction, since this may compromise recovery. You cannot run the system procedures that create temporary worktables from transactions. If no transaction is active when you execute a system procedure, Adaptive Server turns off chained mode and sets transaction isolation level 1 for the duration of the procedure. Before returning, the sessions chained mode and isolation level are reset to their original settings. For more information about transaction modes and isolation levels, see the Reference Manual. All system procedures report a return status. For example, the following means that the procedure executed successfully:
return status = 0
System procedure tables

The system procedures use several system procedure tables in the master and sybsystemdb databases to convert internal system values (for example, status bits) into human-readable format. One of these tables, spt_values, is used by a variety of system procedures, including:
sp_configure sp_dboption sp_depends sp_help sp_helpdb sp_helpdevice sp_helpindex sp_helpkey sp_helprotect sp_lock
The spt_values table can be updated only by an upgrade; it cannot be modified otherwise. To see how it is used, execute sp_helptext and look at the text for one of the system procedures that references it.
13
System procedures
The other system procedure tables are spt_monitor, spt_committab, and tables needed by the catalog stored procedures. (The spt_committab table is located in the sybsystemdb database.) In addition, several of the system procedures create and then drop temporary tables. For example, sp_helpdb creates #spdbdesc, sp_helpdevice creates #spdevtab, and sp_helpindex creates #spindtab.
Creating system procedures

Many of the system procedures are explained in this manual, in the sections where they are relevant. For complete information about system procedures, see the Reference Manual: System Procedures. System Administrators can write system procedures that can be executed in any database. Simply create a stored procedure in sybsystemprocs and give it a name that begins with sp_. The uid of the stored procedure must be 1, the uid of the Database Owner. Most of the system procedures that you create query the system tables. You can also create stored procedures that modify the system tables, although this is not recommended. To create a stored procedure that modifies system tables, a System Security Officer must first turn on the allow updates to system tables configuration parameter. Any stored procedure created while this parameter is set to on will always be able to update system tables, even when allow updates to system tables is set to off. To create a stored procedure that updates the system tables: 1 2 3 Use sp_configure to set allow updates to system tables to on. Create the stored procedure with the create procedure command. Use sp_configure to set allow updates to system tables to off.
Warning! Use extreme caution when you modify system tables. Always test the procedures that modify system tables in development or test databases, not in your production database.
14
CHAPTER 1
System extended stored procedures

An extended stored procedure (ESP) provides a way to call external language functions from within Adaptive Server. Adaptive Server provides a set of ESPs; users can also create their own. The names of all system extended stored procedures begin with xp_, and are located in the sybsystemprocs database. One very useful system ESP is xp_cmdshell, which executes an operating system command on the system that is running Adaptive Server. You can invoke a system ESP just like a system procedure. The difference is that a system ESP executes procedural language code rather than TransactSQL statements. All ESPs are implemented by an Open Server application called XP Server, which runs on the same machine as Adaptive Server. XP Server starts automatically on the first ESP invocation. For information about the system ESPs provided with Adaptive Server, see the Reference Manual.
Creating system ESPs

Create a system ESP in the sybsystemprocs database using the create procedure command. System procedures are automatically included in the sybsystemprocs database. The name of the ESP, and its procedural language function, should begin with xp_. The uid of the stored procedure must be 1, the uid of the Database Owner. For general information about creating ESPs, see Chapter 17, Using Extended Stored Procedures, in the Transact-SQL Users Guide.
Logging error messages

Adaptive Server writes start-up information to a local error log file each time it starts. The installation program automatically sets the error log location when you configure a new Adaptive Server. See the Configuration Guide for your platform to learn the default location and file name of the error log. Many error messages from Adaptive Server go to the users terminal only. However, fatal error messages (severity levels 19 and above), kernel error messages, and informational messages from Adaptive Server are recorded in the error log file.
15
Connecting to Adaptive Server
Adaptive Server keeps the error log file open until you stop the server process. To reduce the size of the error log by deleting old messages, stop the Adaptive Server process before you do so.
Note On some platforms, such as Windows NT, Adaptive Server also records
error messages in the operating system event log. See the installation and configuration guide for your platform for additional information about error logs.

Adaptive Server can communicate with other Adaptive Servers, Open Server applications, and client software on the network. Clients can talk to one or more servers, and servers can communicate with other servers via remote procedure calls. For products to interact with one another, each needs to know where the others reside on the network. This network service information is stored in the interfaces file.
The interfaces file

The interfaces file is usually named interfaces, interface, or sql.ini, depending on the operating system. The interfaces file is like an address book. It lists the name and address of every known server. When you use a client program to connect to a server, the program looks up the server name in the interfaces file and then connects to the server using the address, as shown in Figure 1-1.
16
CHAPTER 1
Figure 1-1: Connecting to Adaptive Server
Connect me to the TEST Adaptive Server.
interfaces interfaces file

TEST
TEST Adaptive Server
The name, location, and contents of the interfaces file differ between operating systems. Also, the format of the Adaptive Server addresses in the interfaces file differs between network protocols. When you install Adaptive Server, the installation program creates a simple interfaces file that you can use for local connections to Adaptive Server over one or more network protocols. As a System Administrator, it is your responsibility to modify the interfaces file and distribute it to users so that they can connect to Adaptive Server over the network. See the Configuration Guide for your platform for information about the interfaces file.
Directory services
A directory service manages the creation, modification, and retrieval of network service information. Directory services are provided by platform or third-party vendors and must be purchased and installed separately from Adaptive Server. Two examples of directory services are NT Registry and Distributed Computing Environment (DCE). The $SYBASE/$SYBASE_OCS/config/libtcl.cfg file is a Sybase-supplied configuration file used by servers and clients to determine: Which directory service to use, and The location of the specified directory service driver.
17
If no directory services are installed or listed in the libtcl.cfg file, Adaptive Server defaults to the interfaces file for obtaining network service information. The System Administrator must modify the libtcl.cfg file as appropriate for the operating environment. Some directory services are specific to a given platform; others can be used on several different platforms. Because of the platform-specific nature of directory services, refer to the configuration documentation for your platform for detailed information on configuring for directory services.
LDAP as a directory service

Lightweight Directory Access Protocol (LDAP) is an industry standard for accessing directory services. Directory services allow components to look up information by a distinguished name (DN) from an LDAP server that stores and manages server, user, and software information that is used throughout the enterprise or over a network. The LDAP server can be located on a different platform from the one on which Adaptive Server or the clients are running. LDAP defines the communication protocol and the contents of messages exchanged between clients and servers. Messages are operators, such as client requests for read, write and query, and server responses, including data-format information. The LDAP server can store and retrieve information about: Adaptive Server, such as IP address, port number, and network protocol Security mechanisms and filters High availability companion server name Authentication information for user access to Adaptive Server You can authenticate users logging in to Adaptive Server through information stored in the syslogins directory or through a centralized LDAP server that enables a single login and password throughout the enterprise. See Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections, for more information. The LDAP server can be configured with these access restrictions: Anonymous authentication all data is visible to any user. User name and password authentication Adaptive Server uses the default user name and password from the file:
18
CHAPTER 1
UNIX, 32-bit $SYBASE/$SYBASE_OCS/config/libtcl.cfg UNIX, 64-bit $SYBASE/$SYBASE_OCS/config/libtcl64.cfg NT %SYBASE%\%SYBASE_OCS%\ini\libtcl.cfg User name and password authentication properties establish and end a session connection to an LDAP server.
Note The default user name and password stored in libtcl.cfg and passed to the
LDAP server for authentication purposes are distinct and different from those used to access Adaptive Server. The default user name and password allow access to the LDAP server for administrative tasks. When an LDAP server is specified in the libtcl.cfg or libtcl64.cfg file (collectively called libtcl*.cfg file), the server information is accessible only from the LDAP server. Adaptive Server ignores the interfaces file. If multiple directory services are supported in a server, then the order in which they are searched is specified in libtcl*.cfg. You cannot specify the search order with the dataserver command line option.
Multiple directory services

Any type of LDAP service, whether it is an actual server or a gateway to other LDAP services, is called an LDAP server. You can specify multiple directory services for high-availability failover protection in libtcl*.cfg. Not every directory service in the list must be an LDAP server. In the following example, if the connection to test:389 fails, the connection fails over to the DCE driver with the specified DIT base. If this also fails, a connection to the LDAP server on huey:11389 is attempted. Different vendors employ different DIT base formats.
[DIRECTORY] ldap=libdldap.so ldap://test:389/dc=sybase,dc=com dce=libddce.so ditbase=/.:/subsys/sybase/dataservers ldap=libdldap.so ldap://huey:11389/dc=sybase,dc=com Note For more information, see the Open Client Client-Library/C
Programmers Guide and the Open Client Client-Library/C Reference Manual.
19
Security features available in Adaptive Server
LDAP directory services versus the Sybase interfaces file

The LDAP driver implements directory services for use with an LDAP server. LDAP directories are an infrastructure that provide: A network-based alternative to the traditional Sybase interfaces file A single, hierarchical view of information, including users, software, resources, networks, files, and so on
Table 1-1 highlights the differences between the Sybase interfaces file and an LDAP server.
Table 1-1: interfaces file versus LDAP directory services interfaces file Platform-specific Specific to each Sybase installation Contains separate master and query entries Cannot store metadata about the server Performance Directory services Platform-independent Centralized and hierarchical One entry for each server that is accessed by both clients and servers Stores metadata about the server
Performance when using an LDAP server may be slower than when using an interfaces file because the LDAP server requires time to make a network connection and retrieve data. Since this connection is made when Adaptive Server is started, changes in performance are seen at login time, if at all. During normal system load, the delay should not be noticeable. During high system load with many connections, especially repeated connections with short duration, the overall performance difference of using an LDAP server versus the traditional interfaces file might be noticeable.

Table 1-2 summarizes the major security features available for Adaptive Server. For information about configuring Adapative Server for security, see Part Two of this manual.
Table 1-2: Major security features Security feature Identification and authentication controls Description Ensures that only authorized users can log into the system. In addition to password based login authentication, Adaptive Server supports external authentication using Kerberos, LDAP, or PAM.
20
CHAPTER 1
Security feature Discretionary Access Controls (DAC) Division of roles
Description Provides access controls that give object owners the ability to restrict access to objects, usually with the grant and revoke commands. This type of control is dependent upon an object owners discretion. Allows an administrator to grant privileged roles to specified users so only designated users can perform certain tasks. Adaptive Server has predefined roles, called system roles, such as System Administrator and System Security Officer. In addition, Adaptive Server allows System Security Officers to define additional roles, called user-defined roles. Provides the ability to audit events such as logins, logouts, server start operations, remote procedure calls, accesses to database objects, and all actions performed by a specific user or with a particular role active. Adaptive Server also provides a single option to audit a set of server-wide security-relevant events. Maintains a confidentiality of data using encrytion for Client-Server communications, available with Kerberos or SSL. Data that is not active is kept confidential with password-protected database backup.
Accountability
Confidentiality of data
21
22
CH A PTE R
System and Optional Databases
This chapter describes the system databases that reside on all Adaptive Server systems. It also describes optional Sybase-supplied databases that you can install, and a database that Sybase Technical Support may install for diagnostic purposes.
Topic Overview of system databases master database model database sybsystemprocs database tempdb database sybsecurity database sybsystemdb database Chapter , sybmgmtdb database, pubs2 and pubs3 sample databases dbccdb database sybdiag database Page 23 25 28 29 29 31 31 32 32 33 33
Overview of system databases

When you install Adaptive Server, it includes these system databases: The master database The model database The system procedure database, sybsystemprocs The two-phase commit transaction database, sybsystemdb The temporary database, tempdb
Optionally, you can install: The auditing database, sybsecurity
23
Overview of system databases
The sample databases, pubs2 and pubs3 The dbcc database, dbccdb The Job Scheduler database, sybmgmtdb
For information about installing the master, model, sybsystemprocs, tempdb, and sybmgmtdb databases, see the installation documentation for your platform. For information on installing dbccdb, see Chapter 10, Checking Database Consistency. For information about using Job Scheduler, see the Job Scheduler Users Guide. The master, model, sybsystemdb, and temporary databases reside on the device named during installation, which is known as the master device. The master database is contained entirely on the master device and cannot be expanded onto any other device. All other databases and user objects should be created on other devices.
Warning! Do not store user databases on the master device. Storing user databases on the master device makes it difficult to recover the system databases if they become damaged. Also, you cannot recover user databases stored on the master device.
You should install the sybsecurity and sybmgmtdb databases on their own devices and segment. For more information, see the installation documentation for your platform. You can install the sybsystemprocs database on a device of your choice. You may want to modify the installation scripts for pubs2 and pubs3 to share the device you create for sybsystemprocs. You install the sybmgmtdb database with the installjsdb script (located in $SYBASE/ASE-15_0/scripts). installjsdb looks for a device named sybmgmtdev on which to create the sybmgmtdb database and its accompanying tables and stored procedures. If the sybmgmtdb database already exists, installjsdb creates the Job Scheduler tables and stored procedures in the existing database. If installjsdb cannot find either a sybmgmtdev device or a sybmgmtdb database, it creates sybmgmtdb on the master device. However, Sybase strongly recommends that you remove the sybmgmtdb database from the master device.
24
CHAPTER 2
The installpubs2 and the installpubs3 scripts do not specify a device in their create database statement, so they are created on the default device. At installation time, the master device is the default device. To change this, you can either edit the scripts or follow the instructions in Chapter 7, Initializing Database Devices, for information about adding more database devices and designating default devices.
master database
The master database controls the operation of Adaptive Server and stores information about all user databases and their associated database devices. Table 2-1 describes the information that the master database tracks.
25
master database
Table 2-1: Information the master database tracks Information User accounts Remote user accounts Remote servers that this server can interact with Ongoing processes Configurable environment variables System error messages Databases on Adaptive Server Storage space allocated to each database Tapes and disks mounted on the system Active locks Character sets Languages Users who hold server-wide roles Server roles Adaptive Server engines that are online System table
syslogins sysremotelogins sysservers sysprocesses sysconfigures sysmessages sysdatabases sysusages sysdevices syslocks syscharsets syslanguages sysloginroles syssrvroles sysengines
Because the master database stores information about user databases and devices, you must be in the master database to issue the create database, alter database, disk init, disk refit, disk reinit, and disk mirroring commands.
Note The minimum size of your master database depends on your server's logical page size. The master database must contain at least 6656 logical pages,
so its minimum physical size for each logical page size is: 2K page 13MB 4K page 26MB 8K page 52MB 16K page 104MB
26
CHAPTER 2
Controlling object creation in master

When you initially install Adaptive Server, only a System Administrator can create objects in the master database, because the System Administrator implicitly becomes dbo of any database he or she uses. Any objects created on the master database should be used for the administration of the system as a whole. Permissions in master should remain set so that most users cannot create objects there.
Warning! Never place user objects in master. Storing user objects in master can cause the transaction log to fill quickly. If the transaction log runs out of space completely, you cannot use dump transaction commands to free space in master.
Another way to discourage users from creating objects in master is to change the default database for users (the database to which a user is connected when he or she logs in) with sp_modifylogin. See Adding users to databases on page 381 for more information. If you create your own system procedures, create them in the sybsystemprocs database rather than in master.
Backing up master and keeping copies of system tables

To be prepared for hardware or software failure on Adaptive Server: Perform frequent backups of the master database and all user databases. See Keep up-to-date backups of master on page 42 for more information. See also Chapter 13, Restoring the System Databases, for an overview of the process for recovering the master database. Keep a copy (preferably offline) of these system tables: sysusages, sysdatabases, sysdevices, sysloginroles, and syslogins. See Keep offline copies of system tables on page 43 for more information. If you have copies of these scripts, and a hard disk crash or other disaster makes your database unusable, you can use the recovery procedures described in Chapter 13, Restoring the System Databases. If you do not have current copies of your scripts, it is much more difficult to recover Adaptive Server when the master database is damaged.
27
model database
model database
Adaptive Server includes the model database, which provides a template, or prototype, for new user databases. Each time a user enters the create database command, Adaptive Server makes a copy of the model database and extends the new database to the size specified by the create database command.
Note A new database cannot be smaller than the model database.
The model database contains the required system tables for each user database. You can modify model to customize the structure of newly created databases everything you do to model is reflected in each new database. Some of the changes that System Administrators commonly make to model are: Adding user-defined datatypes, rules, or defaults. Adding users who should have access to all databases on Adaptive Server. Granting default privileges, particularly for guest accounts. Setting database options such as select into/bulkcopy/pllsort. The settings are reflected in all new databases. Their original value in model is off. For more information about the database options, see Chapter 8, Setting Database Options.
Typically, most users do not have permission to modify the model database. There is not much point in granting read permission either, since Adaptive Server copies its entire contents into each new user database. The size of model cannot be larger than the size of tempdb. By default, the size of the model database is six allocation units (an allocation unit is 256 logical pages.). Adaptive Server displays an error message if you try to increase the size of model without making tempdb at least as large.
Note Keep a backup copy of the model database, and back up model with dump database each time you change it. In case of media failure, restore model as you
would a user database.
28
CHAPTER 2
sybsystemprocs database
Sybase system procedures are stored in the database sybsystemprocs. When a user in any database executes a system stored procedure (that is, a procedure whose name begins with sp_), Adaptive Server first looks for that procedure in the users current database. If there is no procedure there with that name, Adaptive Server looks for it in sybsystemprocs. If there is no procedure in sybsystemprocs by that name, Adaptive Server looks for the procedure in master. If the procedure modifies system tables (for example, sp_adduser modifies the sysusers table), the changes are made in the database from which the procedure was executed. To change the default permissions on system procedures, you must modify those permissions in sybsystemprocs.
Note Any time you make changes to sybsystemprocs, you should back up the
database.
tempdb database
Adaptive Server has a temporary database, tempdb, provides a storage area for temporary tables and other temporary working storage needs. The space in tempdb is shared among all users of all databases on the server. The default size of tempdb depends on the logical page size for your server, 2, 4, 8, or 16K. Certain activities may make it necessary for you to increase the size of tempdb. The most common of these are: Large temporary tables. A lot of activity on temporary tables, which fills up the tempdb logs. Large sorts or many simultaneous sorts. Subqueries and aggregates with
group by also cause some activity in tempdb.
You can increase the size of tempdb with alter database. tempdb is initially created on the master device. Space can be added from the master device or from any other database device.
29
tempdb database
Adaptive Server allows you to create and manage multiple temporary databases in addition to the system temporary database, tempdb. Multiple temporary databases reduce contention on system catalogs and logs in tempdb.
Creating temporary tables

No special permissions are required to use tempdb, that is, to create temporary tables or to execute commands that may require storage space in the temporary database. Create temporary tables either by preceding the table name in a create table statement with a pound sign (#) or by specifying the name prefix tempdb... Temporary tables created with a pound sign are accessible only by the current Adaptive Server session: users on other sessions cannot access them. These nonsharable, temporary tables are destroyed at the end of each session. The first 13 bytes of the tables name, including the pound sign (#), must be unique. Adaptive Server assigns the names of such tables a 17-byte number suffix. (You can see the suffix when you query tempdb..sysobjects.) Temporary tables created with the tempdb.. prefix are stored in tempdb and can be shared among Adaptive Server sessions. Adaptive Server does not change the names of temporary tables created this way. The table exists either until you restart Adaptive Server or until its owner drops it using drop table. System procedures work on temporary tables, but only if you use them from tempdb. If a stored procedure creates temporary tables, the tables are dropped when the procedure exits. Temporary tables can also be dropped explicitly before a session ends.
Warning! Do not create temporary tables with the tempdb.. prefix from inside a stored procedure unless you intend to share those tables among other users and sessions.
Each time you restart Adaptive Server, it copies model to tempdb, which clears the database. Temporary tables are not recoverable.
30
CHAPTER 2
sybsecurity database
The sybsecurity database contains the audit system for Adaptive Server. It consists of: The system tables, sysaudits_01, sysaudits_02, ... sysaudits_08, which contain the audit trail The sysauditoptions table, which contains rows describing the global audit options All other default system tables that are derived from model
The audit system is discussed in more detail in Chapter 18, Auditing.
sybsystemdb database
The sybsystemdb database stores information about distributed transactions. Adaptive Server versions 12.0 and later can provide transaction coordination services for transactions that are propagated to remote servers using remote procedure calls (RPCs) or Component Integration System (CIS). Information about remote servers participating in distributed transactions is stored in the syscoordinations table.
Note Distributed transaction management (DTM) services are available in
Adaptive Server version 12.0 and later as a separately-licensed feature. You must purchase and install a valid license for Distributed Transaction Management before you can use it. See Using Adaptive Server Distributed Transaction Management Features and the installation guide for more information. The sybsystemdb database also stores information about SYB2PC transactions that use the Sybase two-phase commit protocol. The spt_committab table, which stores information about and tracks the completion status of each twophase commit transaction, is stored in the sybsystemdb database. Two-phase commit transactions and how to create the sybsystemdb database is discussed in detail in the configuration documentation for your platform.
31
sybmgmtdb database
sybmgmtdb database
The sybmgmtdb database stores jobs, schedules, scheduled jobs information, and data the internal Job Scheduler task needs for processing. sybmgmtdb also maintains the output and results from these executed tasks. For more information on the Job Scheduler and sybmgmtdb, refer to the Job Scheduler User's Guide.
pubs2 and pubs3 sample databases

Installing the pubs2 and pubs3 sample databases is optional. These databases are provided as a learning tool for Adaptive Server. The pubs2 sample database is used for most of the examples in the Adaptive Server documentation, except for examples, where noted, that use the pubs3 database. For information about installing pubs2 and pubs3, see the installation documentation for your platform. For information about the contents of these sample databases, see the Transact-SQL Users Guide.
Maintaining the sample databases

The sample databases contain a guest user login that allows access to the database by any authorized Adaptive Server user. The guest login has been given a wide range of privileges in pubs2 and pubs3, including permissions to select, insert, update, and delete user tables. For more information about the guest login and a list of the guest permissions in pubs2 and pubs3, see Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections. The size of the pubs2 and pubs3 databases are determined by the size of the logical page size for your server; 2, 4, 8, and 16K. If possible, give each new user a clean copy of pubs2 and pubs3 so that she or he is not confused by other users changes. To place pubs2 or pubs3 on a specific database device, edit the installation script before installing the database. If space is a problem, instruct users to issue the begin transaction command before updating a sample database. After the user has finished updating one of the sample databases, he or she can issue the rollback transaction command to undo the changes.
32
CHAPTER 2
pubs2 image data

Adaptive Server includes a script for installing image data in the pubs2 database (pubs3 does not use the image data). The image data consists of six pictures, two each in PICT, TIF, and Sun raster file formats. Sybase does not provide any tools for displaying image data. You must use the appropriate screen graphics tools to display the images after you extract them from the database. See the the installation documentation for your platform for information about installing the image data in pubs2.
dbccdb database
dbcc checkstorage records configuration information for the target database, operation activity, and the results of the operation in the dbccdb database. Stored in the database are dbcc stored procedures for creating and maintaining dbccdb and for generating reports on the results of dbcc checkstorage operations. For more information, see Chapter 10, Checking Database Consistency.
sybdiag database
Sybase Technical Support may create the sybdiag database on your system for debugging purposes. This database holds diagnostic configuration data, and should not be used by customers.
Determining the version of the installation scripts

sp_version allows you to determine the current version of the scripts
(installmaster, installdbccdb, and so on) installed on Adaptive Server, whether they ran successfully or not, and the time they took to complete. The syntax for sp_version is:
sp_version [script_file [, all]]
33
Determining the version of the installation scripts
where: script_file is the name of the installation script (the default value is NULL).
all reports details about the installation scripts, such as the date it was run and the time it took to run.
For example, the following reports the latest version of installmaster that was run:
1> sp_version installmaster Script Version Status -------------------------------------------------------------------------------installmaster 15.0/EBF XXXXX/B/Sun_svr4/OS 5.8/asemain/1/32-bit/OPT/Thu Sep 23 22:12:12 2004 Complete
This example describes what installation scripts were run, what time they were run, and what time they finished:
sp_version null, all Script Version Status -------------------------------------------------------------------------------installmaster 15.0/EBF XXXXX/B/Sun_svr4/OS 5.8/asemain/1/32-bit/OPT/Thu Sep 23 22:12:12 2004 Complete [Started=Sep 24 2004 3:39PM]-[Completed=Sep 24 2004 3:45PM
34
CH A PTE R
System Administration for Beginners
This chapter: Introduces new System Administrators to important topics Helps System Administrators find information in the Sybase documentation
Experienced administrators may also find this chapter useful for organizing their ongoing maintenance activities.
Topic Logical page sizes Using test servers Installing Sybase products Allocating physical resources Backup and recovery Ongoing maintenance and troubleshooting Keeping records Getting more help Page 35 36 37 39 42 45 46 48
Logical page sizes

The logical page size is a server-wide setting. You cannot have databases with different-sized logical pages within the same server. Adaptive Server allows you to create master devices and databases with logical page sizes of 2K, 4K, 8K, or 16K, but a given server installation can use only one of these four logical page sizes. All databases in a serverand all objects in every databaseuse the same logical page size. You select the page size when you create the master device with dataserver -z. All the logical pages of a server must be the same size. For instance, all the pages on a server with a logical page size of 4K must be 4K, even though you may not use some pages beyond the initial 2K.
35
Using test servers
For more information about the dataserver, command see the Utility Guide. For more information about logical page sizes, see Chapter 3, Configuring Memory.
Using test servers

Sybase suggests that you install and use a test and/or development Adaptive Server, then remove it before you create the production server. Using a test server makes it easier to plan and test different configurations and less stressful to recover from mistakes. It is much easier to learn how to install and administer new features when there is no risk of having to restart a production server or re-create a production database. If you use a test server, Sybase suggests that you do so from the point of installing or upgrading Adaptive Server through the process of configuring the server. It is in these steps that you make some of the most important decisions about your final production system. The following sections describe how using a test server can help System Administrators.
Understanding new procedures and features

Using a test server allows you to practice basic administration procedures before performing them in a production environment. If you are a new Adaptive Server administrator, many of the procedures discussed in this book may be unfamiliar to you, and it may take several attempts to complete a task successfully. However, even experienced administrators may benefit from practicing techniques that are introduced by new features in Adaptive Server.
Planning resources
Working with a test server helps you plan the final resource requirements for your system and helps you discover resource deficiencies that you might not have anticipated.
36
CHAPTER 3
In particular, disk resources can have a dramatic effect on the final design of the production system. For example, you may decide that a particular database requires nonstop recovery in the event of a media failure. This necessitates configuring one or more additional database devices to mirror the critical database. Discovering these resource requirements in a test server allows you to change the physical layout of databases and tables without affecting database users. You can also use a test server to benchmark both Adaptive Server and your applications using different hardware configurations. This allows you to determine the optimal setup for physical resources at both the Adaptive Server level and the operating system level before bringing the entire system online for general use.
Achieving performance goals

Most performance objectives can be met only by carefully planning a databases design and configuration. For example, you may discover that the insert and I/O performance of a particular table causes a bottleneck. In this case, the best course of action may be to re-create the table on a dedicated segment and partition the table. Changes of this nature are disruptive to a production system; even changing a configuration parameter may require you to restart Adaptive Server.
Installing Sybase products

The responsibility for installing Adaptive Server and other Sybase products is sometimes placed with the System Administrator. If installation is one of your responsibilities, use the following pointers to help you in the process.
37
Installing Sybase products
Check product compatibility

Before installing new products or upgrading existing products, always read the release bulletin included with the products to understand any compatibility issues that might affect your system. Compatibility problems can occur between hardware and software and between different release levels of the same software. Reading the release bulletin in advance can save the time and guesswork of troubleshooting known compatibility problems. Also, refer to the lists of known problems that are installed with Adaptive Server. See the release bulletin for more information.
Install or upgrade Adaptive Server

Read through the installation documentation for your platform before you begin a new installation or upgrade. You must plan parts of the installation and configure the operating system before installing Adaptive Server. You may also want to consult with the operating system administrator to discuss operating system requirements for Adaptive Server. These requirements can include the configuration of memory, raw devices, asynchronous I/O, and other features, depending on the platform you use. Many of these tasks must be completed before you have begun the installation. If you are upgrading a server, back up all data (including the master database, user databases, triggers, and system procedures) offline before you begin. After upgrading, immediately create a separate, full backup of your data, especially if there are incompatibilities between older dump files and the newer versions.
Install additional third-party software

Network protocols
Adaptive Server generally includes support for the network protocols that are common to your hardware platform. If your network supports additional protocols, install the required protocol support. As an alternative to the Sybase interfaces file, you can use a directory service to obtain a servers address and other network information. Directory services are provided by platform or third-party vendors and must be purchased and installed separately from the installation of Adaptive Server. For more information on directory services currently supported by Adaptive Server, see the configuration documentation for your platform. See also Directory services on page 17.
Directory services
38
CHAPTER 3
Configure and test client connections

A successful client connection depends on the coordination of Adaptive Server, the client software, and network products. If you are using one of the network protocols installed with Adaptive Server, see the configuration documentation for your platform for information about testing network connections. If you are using a different network protocol, follow the instructions that are included with the network product. You can also use ping utilities that are included with Sybase connectivity products to test client connections with Adaptive Server. For a general description of how clients connect to Adaptive Server, see Connecting to Adaptive Server on page 16. See also the configuration documentation for your platform for details about the name and contents of the interfaces file.
Allocating physical resources

Allocating physical resources is the process of providing Adaptive Server the memory, disk space, worker processes, and CPU power required to achieve your performance and recovery goals. When installing a new server, every System Administrator must make decisions about resource utilization. You must also reallocate Adaptive Servers resources if you upgrade your platform by adding new memory, disk controllers, or CPUs, or if the design of your database system changes. Early benchmarking of Adaptive Server and your applications can help you spot deficiencies in hardware resources that create performance bottlenecks. See Chapter 16, Overview of Disk Resources in Volume 2 of the System Administration Guide to understand the kinds of disk resources required by Adaptive Server. See also Chapter 3, Configuring Memory, and Chapter 5, Managing Multiprocessor Servers, for information about memory and CPU resources. The following sections provide helpful pointers in determining physical resource requirements.
39
Allocating physical resources
Dedicated versus shared servers

The first step in planning Adaptive Server resources is understanding the resources required by other applications running on the same machine. In most cases, System Administrators dedicate an entire machine for Adaptive Server use. This means that only the operating system and network software consume resources that otherwise might be reserved for Adaptive Server. On a shared system, other applications, such as Adaptive Server client programs or print servers, run on the same machine as Adaptive Server. It can be difficult to calculate the resources available to Adaptive Server on a shared system, because the types of programs and their pattern of use may change over time. In either case, it is the System Administrators responsibility to take into account the resources used by operating systems, client programs, windowing systems, and so forth when configuring resources for Adaptive Server. Configure Adaptive Server to use only the resources that are available to it. Otherwise, the server may perform poorly or fail to start.
Decision support and OLTP applications

Adaptive Server contains many features that optimize performance for OLTP, decision-support, and mixed workload environments. However, you must determine in advance the requirements of your systems applications to make optimal use of these features. For mixed workload systems, list the individual tables that you anticipate will be most heavily used for each type of application; this can help you achieve maximum performance for applications.
Advance resource planning

It is extremely important that you understand and plan resource usage in advance. In the case of disk resources, for example, after you initialize and allocate a device to Adaptive Server, that device cannot be used for any other purpose (even if Adaptive Server never fills the device with data). Likewise, Adaptive Server automatically reserves the memory for which it is configured, and this memory cannot be used by any other application. The following suggestions can help you plan resource usage:
40
CHAPTER 3
For recovery purposes, it is always best to place a databases transaction log on a separate physical device from its data. See Chapter 6, Creating and Managing User Databases. Consider mirroring devices that store mission-critical data. See Chapter 2, Mirroring Database Devices. You may also consider using disk arrays and disk mirroring for Adaptive Server data if your operating system supports these features. If you are working with a test Adaptive Server, it is sometimes easier to initialize database devices as operating system files, rather than raw devices, for convenience. Adaptive Server supports either raw partitions or certified file systems for its devices. Keep in mind that changing configuration options can affect the way Adaptive Server consumes physical resources. This is especially true of memory resources. See Chapter 5, Setting Configuration Parameters, for details about the amount of memory used by individual parameters.
Operating system configuration

Once you have determined the resources that are available to Adaptive Server and the resources you require, configure these physical resources at the operating system level: If you are using raw partitions, initialize the raw devices to the sizes required by Adaptive Server. If you initialize a raw device for Adaptive Server, that device cannot be used for any other purpose (for example, to store operating system files). Ask your operating system administrator for assistance in initializing and configuring raw devices to the required sizes. Configure the number of network connections. Make sure that the machine on which Adaptive Server runs can actually support the number of connections you configure. See your operating system documentation. Additional configuration may be required for your operating system and the applications that you use. Read the installation documentation for your platform. Also read your client software documentation or consult with your engineers to understand the operating system requirements for your applications.
41
Backup and recovery
Backup and recovery

Making regular backups of your databases is crucial to the integrity of your database system. Although Adaptive Server automatically recovers from system crashes (for example, power outages) or server crashes, only you can recover from data loss caused by media failure. Follow the basic guidelines below for backing up your system. The following chapters describe how to develop and implement a backup and recovery plan: Chapter 11, Developing a Backup and Recovery Plan Chapter 12, Backing Up and Restoring User Databases Chapter 13, Restoring the System Databases Chapter 15, Managing Free Space with Thresholds
Keep up-to-date backups of master

Backing up the master database is the cornerstone of any backup and recovery plan. The master database contains details about the structure of your entire database system. Its keeps track of the Adaptive Server databases, devices, and device fragments that make up those databases. Because Adaptive Server needs this information during recovery, it is crucial that you maintain an up-todate backup copy of the master database at all times. To ensure that your backup of master is always up to date, back up the database after each command that affects disks, storage, databases, or segments. This means you should back up master after performing any of the following procedures: Creating or deleting databases Initializing new database devices Adding new dump devices Using any device mirroring command Creating or dropping system stored procedures, if they are stored in master Creating, dropping, or modifying a segment Adding new Adaptive Server logins
42
CHAPTER 3
To back up master to a tape device, start isql and enter the command, where tape_device is the name of the tape device (for example, /dev/rmt0):
dump database master to "tape_device"
Keep offline copies of system tables

In addition to backing up master regularly, keep offline copies of the contents of the following system tables: sysdatabases, sysdevices, sysusages, sysloginroles, and syslogins. Do this by using the bcp utility described in the Utility Guide, and by storing a printed copy of the contents of each system table. You can create a printed copy by printing the output of the following queries:
select select select select select * * * * * from from from from from sysusages order by vstart sysdatabases sysdevices sysloginroles syslogins
If you have copies of these tables, and a hard disk crash or some other disaster makes your database unusable, you can use the recovery procedures described in Chapter 13, Restoring the System Databases. You should also keep copies of all data definition language (DDL) scripts for user objects, as described under Keeping records on page 46.
Automate backup procedures

Creating an automated backup procedure takes the guesswork out of performing backups and makes the procedure easier and quicker to perform. Automating backups can be as simple as using an operating system script or a utility (for example, the UNIX cron utility) to perform the necessary backup commands. Or you can automate the procedure further by using thresholds, which are discussed in Chapter 15, Managing Free Space with Thresholds.
Creating an automated backup procedure
Although the commands required to create an automated script vary, depending on the operating system you use, all scripts should accomplish the same basic steps: 1 Start isql and dump the transaction log to a holding area (for example, a temporary file).
43
Backup and recovery
2 3 4 5
Rename the dump file to a name that contains the dump date, time, and database name. Make a note about the new backup in a history file. In a separate file, record any errors that occurred during the dump. Automatically send mail to the System Administrator for any error conditions.
Verify data consistency before backing up a database

Having backups of a database sometimes is not enoughyou must have consistent, accurate backups (especially for master). If you back up a database that contains internal errors, the database has the same errors when you restore it. Using the dbcc commands, you can check a database for errors before backing it up. Always use dbcc commands to verify the integrity of a database before dumping it. If dbcc detects errors, correct them before dumping the database. Over time, you can begin to think of running dbcc as insurance for your databases. If you discovered few or no errors while running dbcc in the past, you may decide that the risk of database corruption is small and that you need to run dbcc occasionally. If the consequences of losing data are too high, continue to run dbcc commands each time you back up a database.
Note For performance considerations, many sites choose to run dbcc checks
outside of peak hours or on separate servers. See Chapter 10, Checking Database Consistency, for information about the dbcc command.
44
CHAPTER 3
Monitor the log size

When the transaction log becomes nearly full, it may be impossible to use standard procedures to dump transactions and reclaim space. The System Administrator should monitor the log size and perform regular transaction log dumps (in addition to regular database dumps) to make sure this situation never occurs. Use the preferred method of setting up a threshold stored procedure that notifies you (or dumps the log) when the log reaches a certain capacity. See Chapter 15, Managing Free Space with Thresholds, for information about using threshold procedures. Sybase also suggests that you dump the transaction log just prior to doing a full database dump to shorten the time required to dump and load the database. You can also monitor the space used in the log segment manually using sp_helpsegment, as described under Creating and Using Segments on page 175.
Ongoing maintenance and troubleshooting

In addition to making regularly scheduled backups, the System Administrator performs the following maintenance activities throughout the life of a server.
Starting and stopping Adaptive Server

Most System Administrators automate the procedure for starting Adaptive Server to coincide with the start-up of the server machine. This can be accomplished by editing operating system start-up scripts or through other operating system procedures. See the configuration documentation for your platform to determine how to start and stop Adaptive Server.
45
Keeping records
Viewing and pruning the error log

Examine the contents of the error log on a regular basis to determine if any serious errors have occurred. You can also use operating system scripts to scan the error log for particular messages and to notify the System Administrator when specific errors occur. Checking the error log regularly helps you determine whether there are continuing problems of the same nature or whether a particular database device is going bad. See Chapter 11, Diagnosing System Problems, for more information about error messages and their severity. The error log file can grow large over time, since Adaptive Server appends informational and status messages to it each time it starts up. You can periodically prune the log file by opening the file and deleting old records. Keeping the log file to a manageable size saves disk space and makes it easier to locate current errors.
Keeping records
Keeping records about your Adaptive Server system is an important part of your job as a System Administrator. Accurate records of changes and problems that you have encountered can be a valuable reference when you are contacting Sybase Technical Support or recovering databases. They can also provide vital information for administrators who manage the Adaptive Server system in your absence. The following sections describe the kinds of records that are most valuable to maintain.
Contact information
Maintain a list of contact information for yourself as well as the System Security Officer, Operator, and Database Owners on your system. Also, record secondary contacts for each role. Make this information available to all Adaptive Server users so that the appropriate contacts receive enhancement requests and problem reports.
46
CHAPTER 3
Configuration information
Ideally, create databases and database objects, and configure Adaptive Server using script files that you later store in a safe place. Storing the script files use makes it possible to re-create your entire system in the event of a disaster. It also allows you to re-create database systems quickly on new hardware platforms for evaluation purposes. If you use a third-party tool to perform system administration, remember to generate equivalent scripts after performing administration tasks. Consider recording the following kinds of information: Commands used to create databases and database objects (DDL scripts) Commands that add new Adaptive Server logins and database users The current Adaptive Server configuration file, as described in Using sp_configure with a configuration file on page 67 The names, locations, and sizes of all files and raw devices initialized as database devices
Maintain a dated log of all changes to the Adaptive Server configuration. Mark each change with a brief description of when and why you made the change, as well a summary of the end result.
Maintenance schedules
Keep a calendar of regularly scheduled maintenance activities; list any of the procedures you perform at your site: Using dbcc to check database consistency Backing up user and system databases Monitoring the space left in transaction logs (if this is not done automatically) Dumping the transaction log Examining the error log contents for Adaptive Server, Backup Server, and Adaptive Server Monitor Running the update statistics command (see Chapter 4, Using the set statistics Commands, in Performance and Tuning: Monitoring and Analyzing) Examining auditing information, if the auditing option is installed
47
Getting more help
Recompiling stored procedures Monitoring the resource utilization of the server machine
System information
Record information about the hardware and operating system on which you run Adaptive Server. This can include: Copies of operating system configuration files or start-up files Copies of network configuration files (for example, the hosts and services files) Names and permissions for the Adaptive Server executable files and database devices Names and locations of the tape devices used for backups Copies of operating system scripts or programs for automated backups, starting Adaptive Server, or performing other administration activities
Disaster recovery plan

Consolidate the basic backup and recovery procedures, the hints provided in Backup and recovery on page 42, and your personal experiences in recovering data into a concise list of recovery steps tailored to your system. This can be useful to both yourself and to other System Administrators who may need to recover a production system in the event of an emergency.
Getting more help

The amount of new information that System Administrators must learn may seem overwhelming. There are several software tools that can help you learn and facilitate basic administration tasks. These include Adaptive Server Monitor, used for monitoring server performance and other activities, and Sybase Central, which simplifies many administration tasks. There are also many third-party software packages available designed to help System Administrators manage daily maintenance activities.
48
CH A PTE R
Introduction to the Adaptive Server Plug-in for Sybase Central
This chapter describes how to use Sybase Central to manage Adaptive Server. This chapter is meant as an overview to introduce you to Sybase Central. For a complete description of the Adaptive Server Plug-in features, see the Sybase Central online help.
Topic Overview for Adaptive Server Sybase Central Plug-in Using the Adaptive Server Plug-in Starting and stopping Sybase Central Registering Adaptive Server Plug-in Performing common tasks Using Interactive SQL Page 49 50 51 52 52 59
Overview for Adaptive Server Sybase Central Plug-in

Sybase Central is a graphical user interface (GUI) management tool. Sybase Central accepts a variety of Plug-ins that allow you to manage specific Sybase products. The Adaptive Server Plug-in allows you to manage Adaptive Server and helps you perform complex administration tasks without the need to remember the syntax of Transact-SQL commands or system stored procedures. You can use the Adaptive Server Plug-in to: Manage multiple servers from one console You can manage all the Adaptive Server installations from the Sybase Central main window. Generate database definition language (DDL) You can generate DDL for the objects in Adaptive Server.
49
Using the Adaptive Server Plug-in
Visually represent objects You can see the databases and logins in each Adaptive Server and the objects in each database, and windows expand and contract to display information about databases and logins. The Adaptive Server Plug-in expands to display information about many items, including: Databases and tables Disk devices Active processes and locks Logins and users Data caches ASE Replicator, Job Scheduler, and Messaging Services Access to other utilities such as Interactive SQL (for sending queries and displaying query results).
Navigate between related objects To get more information about a database object related to the one whose property sheet you are displaying, navigate directly through the displayed objects dialog box to the related object.
Using the Adaptive Server Plug-in

The Adaptive Server Plug-in for Sybase Central provides you with an intuitive and easy way to administer Adaptive Server Enterprise. Sybase Central displays the Adaptive Server plug-in in its left-hand pane. Included in this pane is a hierarchical list of folders that represent different objects the Plug-in can manage, including: Viewing and changing the characteristics of the object Creating another object: Generating the SQL text for creating an object (which allows you to reverse engineer Adaptive Server objects) Deleting an object Configuring Adaptive Server Managing:
50
CHAPTER 4
Database devices Proxy and temporary databases Indexes Partitions Segments Triggers Logins and roles Views ASE Replicator
Configuring Adaptive Server jobs with Job Scheduler Starting and stopping Adaptive Server Executing queries Logging SQL statements generated by the Plug-in, based on a users actions.
Starting and stopping Sybase Central

To start Sybase Central: On UNIX, move to the $SYBASE/shared/sybcentral43 directory and run the scjview.sh script. On Windows, choose Programs | Sybase | Sybase Central v4.3 from the Start menu, or On Windows, move to the %SYBASE%\Shared\Sybase Central 4.3\ directory and run the scjview.bat script. To stop Sybase Central, select File | Exit
51
Registering Adaptive Server Plug-in
Registering Adaptive Server Plug-in

The Adaptive Server Plug-in is registered in Sybase Central as part of the server installation. However, if Adaptive Server Plug-in is not correctly registered, you can manually register the Adaptive Server Plug-in: On Unix, run $SYBASE/ASEP/bin/registerASEP. On Windows, run %SYBASE%\ASEP\bin\registerASEP.bat You can register the Adaptive Server Plug-in manually by: a b c d e Select Register from Tools | Plug-ins. A registration wizard appears. Select Register Select Register a plug-in by specifying a plug-in registration file. Click Browse. Navigate to $SYBASE/ASEP/bin (%SYBASE%\ASEP\bin on Windows) and select ASEPlugin.jpr. Follow the wizard to register the Adaptive Server Plug-in.
Performing common tasks

The following are some common tasks users perform with the Adaptive Server Plug-in. For more information about all the following tasks, see the Adaptive Server Plug-in online help.
Starting and stopping Adaptive Server
If the Unified Agent is monitoring Adaptive Server, you can start, stop, and restart the server by right-clicking on the server and selecting Shutdown, Start, or Restart. If the Unified Agent is not monitoring Adaptive Server, you can shutdown the server by selecting Shutdown.
You can connect to an Adaptive Server by any of these methods: Select the Connect icon from the tool bar. Right click on Adaptive Server Enterprise and select Connect from the menu. Right click on any server group and select Connect from the menu.
52
CHAPTER 4
The connected server is displayed in the Default server group if the connection is initiated from the Adaptive Server Enterprise folder or the connect icon. The Plug-in displays Connected to server in the corresponding server group if the connection is initiated from the server group. You can also specify a server to which you want to connect by any of the following: Specifying the servers hostname and port number in the Connect dialog box. Selecting a pre-defined Adaptive Server from the server name dropdown list. This drop down list is derived from the servers listed in the interfaces file (UNIX) and sql.ini files (Windows) and LDAP servers. Discover which Adaptive Servers are available by clicking on Find in the Connect dialog. Before you can use this method, you must first define the discovery servers in Server Discovery tab located in the Adaptive Server Enterprise property page.
Creating a database
Before creating a database, make sure enough space is available on the database devices you plan to use. To create a database: 1 2 Right-click on the Add Database icon in the right-hand panel, or, Select the Databases folder. Choose File | New | Database or click on the Add Database option in the Databases folder. The Create a New Database wizard opens. The Create a New Database wizard asks for the following information:
53
Table 4-1: Inputs to create a new database wizard Input Database name Database device Database device size Data or log With override For load Description Enter a name for the database Specify the database device or devices on which to allocate the new database Specify a size for each database device Specify whether the database device will store data or the transaction log. Specify with override if you want to store data and log on the same device. If you are creating the database so you can restore it from a backup, check the For Load check box. This is the case only if you are recovering from media failure or if you are moving a database from one location to another. Specify whether to create a guest user in the database.
Guest account
If you do not enter a size, Adaptive Server allocates either the value of the database size configuration variable or the size of the model database, whichever is larger. If you have limited storage and must put the transaction log and the data on the same logical device, specifying With Override allows Adaptive Server to maintain the log on separate device fragments from the data. You cannot remove or change a database device after creating the database unless you first delete the database.
Warning! Deleting a database also deletes all its objects. Deleting a database
Only the owner of a database can delete it. To delete a database: 1 2 3 Select the database icon. Choose Edit | Delete. Confirm the deletion in the confirmation dialog box.
Note Sybase recommends that you back up the master database after you
delete a user database.

Adding a user
Database owners can add and delete users in the databases they own.
54
CHAPTER 4
To create a user: 1 2 Expand the databases folder (select the + icon) and select the Users folder. Choose File | New | User. The Add a New User wizard opens and asks for this information:
Table 4-2: Inputs to Add a New User wizard Input Name Login name Group Description A name for the user. The name does not have to be the same as the login. Login to which this user is assigned. Optionally, assign a group to the user. Default: public
Note A user can be a member of one assigned group or the default public
group. You can also select the Users folder. In the right pane, double-click the Add User icon.
Deleting a user
You cannot delete a user who owns objects. Since there is no command to transfer ownership of objects, you must delete objects owned by a user before you can delete the user. Also, you cannot delete a user who has granted permissions to other users without first revoking the permissions with cascade. If appropriate, re-grant the permissions to the other users. Locking a login is a simple alternative to deleting a user. To delete a user: 1 2 3 Select the user icon. Choose Edit | Delete. Confirm the deletion in the confirmation dialog box.
You can also select the user folder by right-clicking on the user icon and select Delete. Before you delete a user: 1 2 3 Revoke the users command and object permissions with cascade. Re-grant the permissions to the other users, if appropriate. Delete the users objects.
55
Creating a table
Only a database owner or a user with create table permission can create a table. To create a table: 1 2 In a database you are working in, select the User Tables folder. Choose File | New | Table or click on the Add Table icon in the User Tables folder. The Table Editor opens. 3 4 In the Name box, enter a name. From the Owner list, choose an owner. The default is dbo.
You can also select the User Tables folder. In the right pane, double-click the Add Table icon.
Deleting a table
Before you delete a table, be sure that no other objects reference it. If any objects reference it, you must edit those objects to avoid errors. To find out if other objects reference a table, check its dependencies.
Note When you delete a table, Adaptive Server deletes the indexes and triggers
associated with the table and unbinds the rules or defaults that are bound to its columns. Only table owners can delete tables. To delete a table: Follow these steps:
Creating a server group
Select the table icon. Choose Edit | Delete. Confirm the deletion in the confirmation dialog box, or,
You can also select the table by right-clicking on the table icon and selecting Delete.
To create a server group: 1 2 3 Select Adaptive Server Enterprise Choose File | New | Server Group Follow the steps provided by the Create New Server Group wizard.
You can also add a server group by double-clicking on the Add Server Group from the right-hand pane.
56
CHAPTER 4
Getting server status
If the Unified Agent is monitoring Adaptive Server, check the server status by any of the following: Click on the server group to which the server belongs. Check the Status column in the Details pane of the server group. Click on the Adaptive Server Enterprise listed under Sybase Central, and then click on Servers tab on the right hand side panel. The server status is printed in the Status column. A green triangle on the lower right-hand side of the server icon indicates that Adaptive Server is running. A red square indicates that Adaptive Server is stopped.
Note By default, the Adaptive Server Plug-in does not have Check Server
Status enabled. To enable Unified Agent to monitor Adaptive Server: Right click on Adaptive Server Enterprise and select Properties. Select Preferences and check Enable Unified Agent (UA) related features.
Getting the server log
If the Unified Agent is monitoring Adaptive Server, retrieve the server log by selecting the server and clicking on the Server Log tab in the right-hand pane. The server log is retrieved based on how you have configured the filter for the the server log. To configure the server log filtering, right-click on the server and select Server Log Filter. By default, the Adaptive Server Plug-in retrieves the last 1000 lines from the server log. You can configure the server filter to retrieve: The entire log file. The last n number of lines. The log from the last n number of days. The lines that match the regular expression
Logging SQL statements
To log all SQL statements executed through the Adaptive Server Plug-in: Right click on a server and select Log SQL Statement. Select whether you want SQL statements logged directly to a window or to a file.
Executing SQL statements
You can execute SQL statements from within the Adaptive Server Plug-in by using the Interactive SQL query tool. To start the Interactive SQL tool, you can either:
57
1 2
Right-click the server on which you want to execute the SQL statements and select Open Interactive SQL from the menu, or Click on Adaptive Server Enterprise. Click the Utilities tab on the right-hand pane and select Interactive SQL
You can execute SQL statements simultaneously on a set of servers belonging to a server group: 1 2 3 Right -click the server group and choose Execute SQL. Select the servers on which you want to execute the SQL statements Click Execute.
The result set for each server is listed in the Result Set pane of the SQL Execution dialog.
Viewing SQL execution plan and cost information
You can use the Adaptive Server Plug-in to view a GUI version of the SQL execution plan for individual queries (much like a GUI version of showplan) and execution plans for all queries in a stored procedure. This GUI display includes nodes for each of the operators of the execution plan. To get the GUI plan: 1 2 3 4 5 6 7 Start Interactive SQL. Execute the query or stored procedure Click on the plan tab in the Results pane of Interactive SQL Select a query from the queries drop down list. Click the Details tab to see the GUI plan of the selected query. Click on an operator node to see the detailed statistics for that node. Click on the XML tab to see an XML representation of the execution plan for the selected query Click on the Text tab to see the execution plan in a text format for the submitted queries For more information about Interactive SQL, see Starting Interactive SQL on page 60.
Viewing and updating object properties
You can view and modify the configuration of any object represented in the Adaptive Server Plug-in using the Property dialog. To bring up the Property dialog: 1 Click on the object you want to view or modify.
58
CHAPTER 4
2 3 4 5
Generate the SQL text for creating an object
Right-click on the object and select Properties. Select the appropriate tab to perform your task. Make any modification in the Property dialog. Click on Apply, OK, or Cancel.
You can generate the SQL text required for creating an object, which allows you to reverse engineer the object. To generate SQL text, right-click on the object and select Generate DDL. You can view and update the Adaptive Server configuration parameters using the Server Properties dialog. To view and update configuration parameters: 1 2 3 4 5 Right click on the server and select Configuration in the menu Select the functional group from the drop down list in the Show Configuration Parameters Find and select the parameter you want to view or update Enter new valuing the value column if update is necessary Click on Apply/OK/Cancel accordingly
Viewing and updating Adaptive Server configuration parameters
Using Interactive SQL

Interactive SQL allows you to execute SQL statements, build scripts, and display database data to the server. You can use it to: Browse the information in a database. Test SQL statements that you plan to include in an application. Save query results to a file. Edit data in result sets. Load data into a database and carry out administrative tasks.
In addition, Interactive SQL can run command files or script files. For example, you can build repeatable scripts to run against a database and then use Interactive SQL to execute these scripts as batches.
59
Using Interactive SQL
Starting Interactive SQL

To start Interactive SQL from Sybase Central
To start Interactive SQL, either: Select a database in Sybase Central and select File | Open Interactive SQL. Interactive SQL connects to the database. You can also right-click on the database and select Open Interactive SQL. The menu item Open Interactive SQL opens a connection to a server. However, when you select the menu item for a server, Interactive SQL opens a connection to the default database for that server. When you select a specific database from the Open Interactive SQL menu, Interactive SQL opens to the selected database. To start Interactive SQL without a connection to a server, select Tools | Adaptive Server Enterprise | Open Interactive SQL. The Connect dialog appears.
To start Interactive SQL from the command line
How you start Interactive SQL from the command line depends on your operating system. If you start Interactive SQL independently, the Connect dialog appears, which lets you connect to a database just as you would in Sybase Central. For UNIX, change to the $SYBROOT/DBISQL/bin directory and enter:
dbisql
On Windows, change to the %SYBROOT%\DBISQL\bin directory and enter:

dbisql.bat
In the Connection dialog, enter the information to connect to a database in the Connect dialog box and click OK.
To open a new Interactive SQL window: 1 2 Choose Window | New Window. The Connect dialog appears. In the Connect dialog, enter connection options, and click OK to connect. The connection information (including the database name, your user ID, and the database server) appears on the title bar above the SQL Statements pane. You can also connect to or disconnect from a database with the Connect and Disconnect commands in the SQL menu, or by executing a connect or disconnect statement in the SQL Statements pane.
60
CH A PTE R
Setting Configuration Parameters
This chapter describes the Adaptive Server configuration parameters. The parameters are listed alphabetically. A configuration parameter is a user-definable setting that you set, using the system procedure sp_configure. Configuration parameters are used for a wide range of services, from basic to specific server operations, and for performance tuning.
Topic What are configuration parameters? Using sp_configure Output from sp_configure The sysconfigures and syscurconfigs tables Configuration parameters Page 61 65 76 78 79
What are configuration parameters?

Configuration parameters are user-definable settings that control various aspects of Adaptive Servers behavior. Adaptive Server supplies default values for all configuration parameters. You can use configuration parameters to tailor Adaptive Server for an installations particular needs. Read this chapter carefully to determine which configuration parameters you should reset to optimize server performance. Also, see the Performance and Tuning Guide for more information on using sp_configure to tune Adaptive Server.
Warning! Change configuration parameters with caution. Arbitrary changes in parameter values can adversely affect Adaptive Server performance and other aspects of server operation.
61
The Adaptive Server configuration file

Adaptive Server stores the values of configuration parameters in a configuration file, which is an ASCII text file. When you install a new Adaptive Server, your parameters are set to the default configuration; the default name of the file is server_name.cfg, and the default location of the file is the Sybase installation directory ($SYBASE). When you change a configuration parameter, Adaptive Server saves a copy of the old configuration file as server_name.001, server_name.002, and so on. Adaptive Server writes the new values to the file server_name.cfg or to a file name you specify at startup.
How to modify configuration parameters

Set or change configuration parameters in one of the following ways: By executing sp_configure with the appropriate parameters and values, By editing your configuration file and then invoking sp_configure with the configuration file option, or By specifying the name of a configuration file at start-up.
Configuration parameters are either dynamic or static. Dynamic parameters take effect as soon as you execute sp_configure. Static parameters require Adaptive Server to reallocate memory, so they take effect only after you have restarted. The description of each parameter in this chapter indicates whether it is static or dynamic. Adaptive Server writes the new value to the system table sysconfigures and to the configuration file when you change the value. The current configuration file and sysconfigures reflect configured values, not run values. The system table syscurconfigs reflects current run values of configuration parameters.
Who can modify configuration parameters?

The roles required for using sp_configure are as follows: Any user can execute sp_configure to display information about parameters and their current values. Only a System Administrator or a System Security Officer can execute sp_configure to modify configuration parameters.
62
CHAPTER 5
Only a System Security Officer can execute sp_configure to modify values for:
allow procedure grouping allow remote access allow sendmsg allow updates to system tables auditing audit queue size check password for digit current audit table enable ldap user auth enable pam user auth enable ssl log audit logon failure log audit logon success maximum failed logins minimum password length msg confidentiality reqd msg integrity reqd secure default login select on syscomments.text SQL Perfmon Integration syb_sendmsg port number suspended audit when device full systemwide password expiration unified login required use security services
63
Unit specification using sp_configure

sp_configure allows you to specify the value for configuration parameters in unit specifiers. The unit specifiers are p or P for pages, m or M for megabytes, and g or G for gigabytes. If you do not specify a unit, and you are configuring a parameter that controls memory, Adaptive Server uses the logical page size for the basic unit.
The syntax to indicate a particular unit specification is:

sp_configure "parameter name", 0, "p|P|k|K|m|M|g|G"
You must include the 0 as a placeholder. You can use this unit specification to configure any parameter. For example, when setting number of locks to 1024 you can enter:
sp_configure "number of locks", 1024
or:
sp_configure "number of locks", 0, 1K
This functionality does not change the way in which Adaptive Server reports sp_configure output.
Note When you are configuring memory-related parameters, use only the P (pagesize) parameter for your unit specification. If you use any other parameter to configure memory related parameters, Adaptive Server may issue an arithmetic overflow error message.
Getting help information on configuration parameters

Use either sp_helpconfig or sp_configure to display information on a particular configuration parameter. For example:
sp_helpconfig "number of open" Configuration option is not unique. option_name config_value run_value ------------------------------ ------------ ----------number of open databases 12 12 number of open indexes 500 500 number of open objects 500 500 sp_helpconfig "number of open indexes"
64
CHAPTER 5
number of open indexes sets one time on SQL Server. The Minimum Value Maximum Value ------------- ------------100 2147483647
the maximum number of indexes that can be open at default value is 500. Default Value Current Value Memory Used ------------- ------------- ----------500 500 208
sp_configure "number of open indexes" Parameter Name ----------------------number of open indexes Default ------500 Memory Used ----------208 Config Value -----------500 Run Value --------500
For more information, see Using sp_helpconfig on page 60.
Using sp_configure
sp_configure displays and resets configuration parameters. You can restrict the number of parameters displayed by sp_configure using sp_displaylevel to set your display level to one of three values:
Basic Intermediate Comprehensive
For information about display levels, see User-defined subsets of the parameter hierarchy: display levels on page 74. For information about sp_displaylevel, see the Reference Manual: Stored Procedures. Table 5-1 describes the syntax for sp_configure. The information in the Effect column assumes that your display level is set to comprehensive.
Table 5-1: sp_configure syntax Command
sp_configure
sp_configure parameter sp_configure parameter, value sp_configure parameter, 0, default
Effect Displays all configuration parameters by group, their current values, their default values, the value to which they have most recently been set, and the amount of memory used by this particular setting. Displays current value, default value, most recently changed value, and amount of memory used by setting for all parameters matching parameter. Resets parameter to value. Resets parameter to its default value.
65
Using sp_configure
Command
sp_configure group_name
Effect Displays all configuration parameters in group_name, their current values, their default values, the values to which they were recently set, and the amount of memory used by each setting. Sets configuration parameters from the configuration file. See Using sp_configure with a configuration file on page 67 for descriptions of the parameters.
sp_configure configuration file, 0,
sub_command, file_name
Syntax elements
The commands in Table 5-1 use the following variables: parameter is any valid Adaptive Server configuration parameter or parameter substring. value is any integer within the valid range for that parameter. (See the descriptions of the individual parameters for valid range information.) Parameters that work as toggles have only two valid values: 1 (on) and 0 (off). group_name is the name of any group in the parameter hierarchy.
Parameter parsing
sp_configure parses each parameter (and parameter name fragment) as
%parameter%. A string that does not uniquely identify a particular parameter returns values for all parameters matching the string. The following example returns values for all configuration parameters that include lock, such as lock shared memory, number of locks, lock promotion HWM, server clock tick length, print deadlock information, and deadlock retries:
sp_configure "lock" Note If you attempt to set a parameter value with a nonunique parameter name fragment, sp_configure returns the current values for all parameters matching the fragment and asks for a unique parameter name.
66
CHAPTER 5
Using sp_configure with a configuration file

You can configure Adaptive Server either interactively, by using sp_configure as described above, or noninteractively, by instructing Adaptive Server to read values from an edited or restored version of the configuration file. The benefits of using configuration files include: You can replicate a specific configuration across multiple servers by using the same configuration file. You can use a configuration file as a baseline for testing configuration values on your server. You can use a configuration file to perform validation checking on parameter values before actually setting the values. You can create multiple configuration files and switch between them as your resource needs change.
You can make a copy of the configuration file using sp_configure with the parameter configuration file and then edit the file at the operating system level. Then, you can use sp_configure with the parameter configuration file to instruct Adaptive Server to read values from the edited file. Or you can specify the name of the configuration file at start-up. For information on editing the file, see Editing the configuration file on page 69. For information on specifying the name of the configuration file at start-up, see Starting Adaptive Server with a configuration file on page 71.
Naming tips for the configuration file

Each time you modify a configuration parameter with sp_configure, Adaptive Server creates a copy of the outdated configuration file, using the naming convention server_name.001, server_name.002, server_name.003...server_name.999. To work with a configuration file with a name other than the default name, keeping the server_name part of the file name, include at least one alphabetic character in the extension. Alternatively, you can change the server_name to part of the file name. Doing this avoids confusion with the backup configuration files generated by Adaptive Server when you modify a parameter.
67
Using sp_configure
Using sp_configure to read or write the configuration file

The syntax for using the configuration file option with sp_configure is:
sp_configure "configuration file", 0, "subcommand", "file_name"
where:
configuration file including quotes, specifies the configuration file
parameter.
0 must be included as the second parameter to sp_configure for backward compatibility. subcommand is one of the commands described below. file_name specifies the configuration file to use in conjunction with any
subcommand. If you do not specify a directory as part of the file name, the directory where Adaptive Server was started is used.
Parameters for using configuration files

You can use the four parameters described below with configuration files.
write creates file_name from the current configuration. If file_name
already exists, a message is written to the error log; the existing file is renamed using the convention file_name.001, file_name.002, and so on. If you have changed a static parameter, but you have not restarted your server, write displays the currently running value for that parameter. If you do not specify a directory with file_name, the file is written to the directory from which Adaptive Server was started.
read performs validation checking on values contained in file_name and reads those values that pass validation into the server. If any parameters are missing from file_name, the current values for those parameters are used.
If the value of a static parameter in file_name is different from its current running value, read fails and a message is printed. However, validation is still performed on the values in file_name.
verify performs validation checking on the values in file_name. This is
useful if you have edited the configuration file, as it prevents you from attempting to configure your server with invalid configuration values.
68
CHAPTER 5
restore creates file_name with the most recently configured values. If you have configured static parameters to new values, this subcommand writes the configured, not the currently running, values to the file. This is useful if all copies of the configuration file have been lost and you must generate a new copy. If you do not specify a directory with file_name, the file is written to the directory from which Adaptive Server was started.
Examples
Example 1 Performs validation checking on the values in the file srv.config and reads the parameters that pass validation into the server. Current run values are substituted for values that do not pass validation checking:
sp_configure "configuration file", 0, "read", "srv.config" Example 2 Creates the file my_server.config and writes the current configuration values the server is using to that file: sp_configure "configuration file", 0, "write", "my_server.config" Example 3
Runs validation checking on the values in the file generic.config:
sp_configure "configuration file", 0, "verify", "generic.config" Example 4
Writes configured values to the file restore.config:
sp_configure "configuration file", 0, "restore", "restore.config"
Editing the configuration file

The configuration file is an operating system ASCII file that you can edit with any text editor that can save files in ASCII format. The syntax for each parameter is:
parameter_name={value | DEFAULT}
where:
Examples
parameter_name is the name of the parameter you want to specify. value is the numeric value for set parameter_name. DEFAULT specifies that you want to use the default value for parameter_name.
Example 1 The following example specifies that the transaction can retry to acquire a lock one time when deadlocking occurs during an index page split or shrink: cpu accounting flush interval=DEFAULT Example 2 The following example specifies that the default value for the parameter cpu accounting flush interval should be used:
69
Using sp_configure
deadlock retries = 1
When you edit a configuration file, your edits are not validated until you check the file using the verify option, read the file with the read option, or restart Adaptive Server with that configuration file. If all your configuration files are lost or corrupted, you can re-create one from a running server by using the restore subcommand and specifying a name for the new file. The parameters in the new file are set to the values with which your server is currently running.
Permissions for configuration files
Configuration files are nonencrypted ASCII text files. By default, they are created with read and write permissions set for the file owner and read permission set for all other users. If you created the configuration file at the operating system level, you are the file owner; if you created the configuration file from Adaptive Server, using the write or restore parameter, the file owner is the user who started Adaptive Server. Usually, this is the user sybase. To restrict access to configuration files, use your operating systems file permission command to set read, write, and execute permissions as appropriate.
Note You must set permissions accordingly on each configuration file created.
Backing up configuration files
Configuration files are not automatically backed up when you back up the master database. They are operating system files, and you should back them up in the same way you back up your other operating system files.
Checking the name of the configuration file currently in use
The output from sp_configure truncates the name of the configuration file due to space limitations. To see the full name of the configuration file, use:
select s1.value2 from syscurconfigs s1, sysconfigures s2 where s1.config = s2.config and s2.name = "configuration file"
70
CHAPTER 5
Starting Adaptive Server with a configuration file

By default, Adaptive Server reads the configuration file server_name.cfg in the start-up directory when it starts. If this file does not exist, it creates a new file and uses Adaptive Server defaults for all values. You can start Adaptive Server with a specified configuration file. For more information, see the Utility Guide. If the configuration file you specify does not exist, Adaptive Server prints an error message and does not start. If the command is successful, the file server_name.bak is created. This file contains the configuration values stored in sysconfigures prior to the time sysconfigures was updated with the values read in from the configuration file you specified. This file is overwritten with each subsequent start-up.
Configuration file errors
When there are errors in the configuration file, Adaptive Server may not start or may use default values. Adaptive Server uses default values if: There are illegal values. For example, if a parameter requires a numeric value, and the configuration file contains a character string, Adaptive Server uses the default value. Values are below the minimum allowable value.
The parameter hierarchy

Configuration parameters are grouped according to the area of Adaptive Server behavior they affect. This makes it easier to identify all parameters that you might need to tune to improve a particular area of Adaptive Server performance. Although each parameter has a primary group to which it belongs, many have secondary groups to which they also belong. For example, number of remote connections belongs primarily to the network communication group, but it also belongs secondarily to the memory use group. This reflects the fact that some parameters have implications for a number of areas of Adaptive Server behavior. sp_configure displays parameters in all groups to which they belong. Table 5-2 lists the configuration parameter groups.
71
Using sp_configure
Table 5-2: Configuration groups Parameter group Backup/Recovery Cache manager Component Integration Services administration DTM administration Diagnostics Disk I/O Error log Extended stored procedures General information Java services Configures Adaptive Server for:
Backing up and recovering data The data and procedure caches Component Integration Services Distributed transaction management (DTM) facilities
Diagnostic principles
Disk I/O Error log and the logging of Adaptive Server events to the Windows Event Log Affecting the behavior of extended stored procedures (ESPs).
Basic system administration Memory for Java in Adaptive Server See the Java in Adaptive Server Enterprise manual for complete information about Java in the database. If you use method calls to JDBC, you may need to increase the size of the execution stack available to the user. See stack size on page 218 for information about setting the stack size parameter.
Languages Lock manager Memory use Meta-data caches
Languages, sort orders, and character sets

Locks Memory consumption Setting the metadata cache size for frequently used system catalog information. The metadata cache is a reserved area of memory used for tracking information on databases, indexes, or objects. The greater the number of open databases, indexes, or objects, the larger the metadata cache size. For a discussion of metadata caches in a memory-usage context, see Configuring Memory on page 41. Collecting monitoring information. By default, Adaptive Server does not collect monitoring information required by the monitoring tables. For more information about the monitoring tables see Chapter 2, Monitoring Tables, in the Perfomance and Tuning Guide: Monitorig and Analyzing.
Monitoring
Network communication O/S resources Physical memory Processors Query Tuning RepAgent thread administration
Communication between Adaptive Server and remote servers, and between Adaptive Server and client programs Use of operating system resources Your machines physical memory resources Processors in an SMP environment
Query optimization
Replication via Replication Server
72
CHAPTER 5
Parameter group SQL Server administration Security related Unicode User environment
Configures Adaptive Server for: General Adaptive Server administration.
Security-related features Unicode-related features User environments The syntax for displaying all groups and their associated parameters, and the current values for the parameters, is:
sp_configure Note The number of parameters sp_configure returns depends on the value to which you have your display level set. See User-defined subsets of the parameter hierarchy: display levels on page 74 for further information about display levels.
The following is the syntax for displaying a particular group and its associated parameter, where group_name is the name of the group you are interested in:
sp_configure "group_name"
For example, to display the disk I/O group, enter:

sp_configure "Disk I/O" Group: Disk I/O Parameter Name Default Memory Used Config Value Run Value unit type -------------------- ----------- ------------ -------------------------allow sql server async i/o 1 0 1 1 switch static diable disk mirroring 1 0 1 1 switch static disk i/o structures 256 0 256 256 number dynamic number of devices 10 0 10 10 number dynamic number of large I/O buffers 6 12352 6 6 number dynamic page utilization percent 95 0 95 95 percent dynamic
73
Using sp_configure
Note If the server uses a case-insensitive sort order, sp_configure with no parameters returns a list of all configuration parameters and groups in alphabetical order with no grouping displayed.
User-defined subsets of the parameter hierarchy: display levels

Depending on your use of Adaptive Server, you may need to adjust some parameters more frequently than others. You may find it is easier to work with a subset of parameters than having to see the entire group when you are working with only a few. You can set your display level to one of three values to give you the subset of parameters that best suits your working style. The default display level is comprehensive. When you set your display level, the setting persists across multiple sessions. However, you can reset it at any time to see more or fewer configuration parameters. Basic shows only the most basic parameters, and is appropriate for very general server tuning. Intermediate includes parameters that are somewhat more complex, in addition to the basic parameters. This level is appropriate for a moderately complex level of server tuning. Comprehensive includes all the parameters, including the most complex ones. This level is appropriate for users doing highly detailed server tuning.
The syntax for showing your current display level is:

sp_displaylevel
The following is the syntax for setting your display level, where user_name is your Adaptive Server login name:
sp_displaylevel user_name [, basic | intermediate | comprehensive]
74
CHAPTER 5
The effect of the display level on sp_configure output

If your display level is set to either basic or intermediate, sp_configure returns only a subset of the parameters that are returned when your display level is set to comprehensive. For instance, if your display level is set to intermediate, and you want to see the parameters in the languages group, enter:
sp_configure "Languages"
The output looks like this:

sp_configure Group: Languages Parameter Name --------------default character set default language id . . . Default Memory Used Config Value Run Value ------- ----------- ------------ --------1 0 1 1 0 0 0 0 Unit ---id id Type ---static dyna
However, this is only a subset of the parameters in the languages group, because some parameters in that group are displayed only at the comprehensive level.
The reconfigure command

Pre-11.0 SQL Server versions required you to execute reconfigure after executing sp_configure. Beginning with SQL Server version 11.0, this was no longer required. The reconfigure command still exists, but it does not have any effect. It is included in this version of Adaptive Server so you can run pre-11.0 SQL scripts without modification. Scripts using reconfigure still run in the current version, but change them at your earliest convenience because reconfigure will not be supported in future versions of Adaptive Server.
Performance tuning with sp_configure and sp_sysmon

sp_sysmon monitors Adaptive Server performance and generates statistical information that describes the behavior of your Adaptive Server system. See the Performance and Tuning Guide for more information.
75
Output from sp_configure
You can run sp_sysmon before and after using sp_configure to adjust configuration parameters. The output gives you a basis for performance tuning and allows you to observe the results of configuration changes. This chapter includes cross-references to the Performance and Tuning Guide for the sp_configure parameters that can affect Adaptive Server performance.
Output from sp_configure

The sample output below shows the type of information sp_configure prints if you have your display level set to comprehensive and you execute it with no parameters. The values it prints vary, depending on your platform and on what values you have already changed.
sp_configure Group: Configuration Options Group: Backup/Recovery Parameter Name Default Memory Used Config Value Run Value -------------------- ----------- ------------ --------allow remote access 1 0 1 1 print recovery info 0 0 0 0 recovery interval in m 5 0 5 5 ... Unit Type ---- ---switch dyn switch dyn minutes dyn
Note All configuration groups and parameters appears in output if your
display level is set to comprehensive. Where: The Default column displays the value Adaptive Server is shipped with. If you do not explicitly reconfigure a parameter, it retains its default value. The Memory Used column displays the amount of memory used (in kilobytes) by the parameter at its current value. Some related parameters draw from the same memory pool. For instance, the memory used for stack size and stack guard size is already accounted for in the memory used for number of user connections. If you added the memory used by each of these parameters separately, it would total more than the amount actually used. In the Memory Used column, parameters that share memory with other parameters are marked with a hash mark (#).
76
CHAPTER 5
The Config Value column displays the most recent value to which the configuration parameter has been set. When you execute sp_configure to modify a dynamic parameter: The configuration and run values are updated. The configuration file is updated. The change takes effect immediately.
When you modify a static parameter: The configuration value is updated. The configuration file is updated. The change takes effect only when you restart Adaptive Server.
The Run Value column displays the value Adaptive Server is currently using. It changes when you modify a dynamic parameters value and, for static parameters, after you restart Adaptive Server. The Unit column displays the unit value in which the configuration parameter is displayed. Adaptive Server displays information in the following units:
Name of unit number clock ticks microseconds milliseconds seconds minutes hours bytes days kilobytes megabytes memory pages (2K) virtual pages (2K) logical pages percent ratio switch
Unit description Displays the number of items for which a parameter is configured. Number of clock ticks for which a parameter is set. Number of microseconds for which a parameter is set. Number of milliseconds for which a parameter is set. Number of seconds for which a parameter is set. Number of minutes for which a parameter is set. Number of hours for which a parameter is set. Number of bytes for which a parameter is set. Number of days for which a parameter is set. Number of kilobytes for which a parameter is set. Number of megabytes for which a parameter is set. Number of 2K memory pages for which the parameter is set. Number of 2K virtual pages for which the parameter is set. Number of logical pages for which the parameter is configured. This value depends on which logical page size your server is using; 2, 4, 8, or 16K. Displays the value of the configured parameter as a percentage. Displays the value of the configured parameter as a ratio. Value of the parameter is either TRUE (the parameter is turned on, or FALSE
77
The sysconfigures and syscurconfigs tables
Name of unit id name
Unit description ID of the configured parameter you are investigating. Character string name assigned to the run or configure value of the parameter. For example, the string binary appears under the the run or configure value column for the output of sp_configure "lock scheme". Number of rows for which the specified parameter is configured.
row
The Type column displays whether the configuration option is static or dynamic. Changes to static parameters require that you restart Adaptive Server for the changes to take effect. Changes to dynamic parameters take effect immediately without having to restart Adaptive Server.
The sysconfigures and syscurconfigs tables

The report displayed by sp_configure is constructed mainly from the master..sysconfigures and master..syscurconfigs system tables, with additional information provided from sysattributes, sysdevices, and other system tables. The value column in the sysconfigures table records the last value set from sp_configure or the configuration file; the value column in syscurconfigs stores the value currently in use. For dynamic parameters, the two values match; for static parameters, which require a restart of the server to take effect, the two values are different if the values have been changed since Adaptive Server was last started. The values may also be different when the default values are used. In this case, sysconfigures stores 0, and syscurconfigs stores the value that Adaptive Server computes and uses.
sp_configure performs a join on sysconfigures and syscurconfigs to display the values reported by sp_configure.
Querying syscurconfigs and sysconfigures: an example

You might want to query sysconfigures and syscurconfigs to get information organized the way you want. For example, sp_configure without any arguments lists the memory used for configuration parameters, but does not list minimum and maximum values. You can query these system tables to get a complete list of current memory usage, as well as minimum, maximum, and default values, with the following query:
78
CHAPTER 5
select b.name, memory_used, minimum_value, maximum_value, defvalue from master.dbo.sysconfigures b, master.dbo.syscurconfigs c where b.config *= c.config and parent != 19 and b.config > 100
Configuration parameters
In many cases, the maximum allowable values for configuration parameters are extremely high. The maximum value for your server is usually limited by available memory, rather than by sp_configure limitations.
Note To find the maximum supported values for your platform and version of
Adaptive Server, see the table Adaptive Server Specifications in the Installation Guide for your platform.
Alphabetical listing of configuration parameters

The following sections include both summary and detailed information about each configuration parameter.
abstract plan cache

Summary information Default value Range of values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Query Tuning
79
abstract plan cache enables caching of abstract plan hash keys. By default,
caching is not enabled. For more information, see Chapter 16, Creating and Using Abstract Plans in the Performance and Tuning Guide: Optimizer and Abstract Plans. abstract plan load must be enabled in order for plan caching to take effect.
abstract plan dump

abstract plan dump enables the saving of abstract plans to the ap_stdout abstract
plans group. For more information, see Chapter 16, Creating and Using Abstract Plans in the Performance and Tuning Guide: Optimizer and Abstract Plans.
abstract plan load

Summary information Default value Range of values Status Display level Required role Configuration group
1 (on) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Query Tuning
abstract plan load enables association of queries with abstract plans in the ap_stdin abstract plans group. For more information, see Chapter 16, Creating
and Using Abstract Plans in the Performance and Tuning Guide: Optimizer and Abstract Plans.
80
CHAPTER 5
abstract plan replace

abstract plan replace enables plan replacement for abstract plans in the ap_stdout abstract plans group. For more information, see Chapter 16,
Creating and Using Abstract Plans in the Performance and Tuning Guide: Optimizer and Abstract Plans. abstract plan load must be enabled in order for replace mode to take effect.
additional network memory

Summary information Default value Range of values Status Display level Required role Configuration groups 0 02147483647 Dynamic Intermediate System Administrator Memory Use, Network Communication, Physical Memory
additional network memory sets the maximum size of additional memory that
can be used for network packets that are larger than the default packet size. Adaptive Server rounds down the value you enter to the nearest 2K value. The default value indicates that no extra space is allocated for large packets.
81
When a login requests a large packet size, Adaptive Server verifies it has sufficient memory available to satisfy the request. If it does, the login continues. If it does not, Adaptive Server finds the largest available block of memory and tries the appropriate size (which is a multiple of default network packet size) less than the largest memory block. If that fails, Adaptive Server decreases the value of the request by the numbe of bytes equal to default network packet size, if this is available. Adaptive Server continues for 10 iterations or until the size equals the value of default network packet size, whichever comes first. On the tenth iteration, Adaptive Server uses the value of the default network packet size for the packet size. If you increase max network packet size but do not increase additional network memory, clients cannot use packet sizes that are larger than the default size, because all allocated network memory is reserved for users at the default size. Adaptive Server guarantees that every user connection can log in at the default packet size. In this situation, users who request a large packet size when they log in receive a warning message telling them that their application will use the default size. If you request a large packet size, Adaptive Server checks if the memory is available to satisfy the request. If the memory is available, the login continues If the memory is not available, Adaptive Server finds the largest available block of memory and tries again with a packet size equal to the largest block less the default network packet size. If that fails, Adaptive Server retries, but reduces the size of the request by the value of default network packet size. It repeats this process for 10 attempts until the packet size is equal to the configured default network packet size. At the tenth attempt, Adaptive Server drops the packet size to the configured default network packet size, since this size is always available. The "additional network memory" parameter is used to guarantee memory is available for these larger packet size allocations
Increasing additional network memory may improve performance for applications that transfer large amounts of data. To determine the value for additional network memory when your applications use larger packet sizes: Estimate the number of simultaneous users who will request the large packet sizes, and the sizes their applications will request, Multiply this sum by three, since each connection needs three buffers, Add two percent for overhead for 32-bit servers or four percent for 64-bit servers, and
82
CHAPTER 5
Round the value to the next highest multiple of 2048.
For example, if you estimate these simultaneous needs for larger packet sizes:
Application
bcp
Packet size 8192 8192 4096 4096 24576 * 3=73728
Overhead
Client-Library Client-Library Client-Library Total Multiply by 3 buffers/user Compute 2% overhead Add overhead Additional network memory Round up to multiple of 2048
* .02=1474 + 1474 75202 75776
You should set additional network memory to 75,776 bytes.
allocate max shared memory

Summary information Default value Range of values Status Display level Required role Configuration groups
0 0,1 Dynamic Basic System Administrator Memory Use, Physical Memory
allocate max shared memory determines whether Adaptive Server allocates all the memory specified by max memory at start-up or only the amount of memory
the configuration parameter requires. By setting allocate max shared memory to 0, you ensure that Adaptive Server uses only the amount of shared memory required by the current configuration, and allocates only the amount of memory required by the configuration parameters at start-up, which is a smaller value than max memory.
83
If you set allocate max shared memory to 1, Adaptive Server allocates all the memory specified by max memory at start-up. If allocate max shared memory is 1, and if you increase max memory, Adaptive Server immediately uses additional shared memory segments. This means that Adaptive Server always has the memory required for any memory configuration changes you make and there is no performance degradation while the server readjusts for additional memory. However, if you do not predict memory growth accurately, and max memory is set to a large value, you may waste total physical memory.
allow backward scans

Summary information Default value Valid values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Dynamic Intermediate System Administrator Query Tuning
allow backward scans controls how the optimizer performs select queries that contain the order by...desc command:
When the value is set to 1, the optimizer can access the index or table rows by following the page chain in descending index order. When the value is set to 0, the optimizer selects the rows into a worktable by following the index page pointers in ascending order and then sorts the worktable in descending order.
The first methodperforming backward scanscan speed access to tables that need results ordered by descending column values. Some applications, however, may experience deadlocks due to backward scans. In particular, look for increased deadlocking if you have delete or update queries that scan forward using the same index. There may also be deadlocks due to page splits in the index. You can use print deadlock information to send messages about deadlocks to the error log. See print deadlock information on page 199. Alternatively, you can use sp_sysmon to check for deadlocking. See the Performance and Tuning Guide for more information on deadlocks.
84
CHAPTER 5
allow nested triggers

Summary information Default value Valid values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Static Intermediate System Administrator SQL Server Administration
allow nested triggers controls the use of nested triggers. When the value is set to 1, data modifications made by triggers can fire other triggers. Set allow nested triggers to 0 to disable nested triggers. A set option, self_recursion,
controls whether the modifications made by a trigger can cause that trigger to fire again.
allow procedure grouping

Summary information Default value Range of values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Dynamic Comprehensive System Security Officer Security Related
allow procedure grouping controls the ability to group stored procedures of the same name so that they can be dropped with a single drop procedure statement.
allow remote access

Summary information Default value Valid values Status Display level Required role Configuration groups
1 (on) 0 (off), 1 (on) Dynamic Intermediate System Security Officer Backup/Recovery, Network Communication
85
allow remote access controls logins from remote Adaptive Servers. The default
value of 1 allows Adaptive Server to communicate with Backup Server. Only a System Security Officer can set allow remote access. Setting the value to 0 disables server-to-server RPCs. Since Adaptive Server communicates with Backup Server via RPCs, setting this parameter to 0 makes it impossible to back up a database. Since other system administration actions are required to enable remote servers other than Backup Server to execute RPCs, leaving this option set to 1 does not constitute a security risk.
allow resource limits

0 (off) 0 (off), 1 (on) Static Comprehensive System Administrator Memory Use, SQL Server Administration
allow resource limits controls the use of resource limits. When the value is set to 1, the server allocates internal memory for time ranges, resource limits, and internal server alarms. The server also internally assigns applicable ranges and limits to user sessions. The output of showplan and statistics io displays the optimizers cost estimate for a query. Set allow resource limits to 0 to disable resource limits.
allow sendmsg
Summary information Default value Valid values Status Display level Required role Configuration group
0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Security Officer Network Communication
86
CHAPTER 5
The allow sendmsg parameter enables or disables sending messages from Adaptive Server to a UDP (User Datagram Protocol) port. When allow sendmsg is set to 1, any user can send messages using sp_sendmsg or syb_sendmsg. To set the port number used by Adaptive Server, see syb_sendmsg port number on page 224.
Note Sending messages to UDP ports is not supported on Windows.
allow sql server async i/o

Summary information Default value Valid values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Static Comprehensive System Administrator Disk I/O
The allow sql server async i/o parameter enables Adaptive Server to run with asynchronous disk I/O. To use asynchronous disk I/O, you must enable it on both Adaptive Server and your operating system. See your operating system documentation for information on enabling asynchronous I/O at the operating system level. In all circumstances, disk I/O runs faster asynchronously than synchronously. This is because when Adaptive Server issues an asynchronous I/O, it does not have to wait for a response before issuing further I/Os.
allow updates to system tables

0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator SQL Server Administration
87
allow updates to system tables enables users with the System Administrator role
to make changes to the system tables and to create stored procedures that can modify system tables. A database administrator can update system tables in any tables that he or she owns if allow updates to system tables is enabled. System tables include: All Sybase-supplied tables in the master database All tables in user databases that begin with sys and that have an ID value in the sysobjects table of less than or equal to 100
Warning! Incorrect alteration of a system table can result in database corruption and loss of data. Always use begin transaction when modifying a system table to protect against errors that might corrupt your databases. Immediately after finishing your modifications, disable allow updates to system tables.
Stored procedures and triggers you create while allow updates to system tables is set on can update the system tables, even after the parameter has been set off. When you set allow updates to system tables to on, you create a window of vulnerability, a period of time during which users can alter system tables or create a stored procedure with which the system tables can be altered in the future. Because the system tables are so critical, Sybase suggests that you set this parameter to on only in highly controlled situations. To guarantee that no other users can access Adaptive Server while the system tables can be directly updated, restart Adaptive Server in single-user mode. For details, see startserver and dataserver in the Utility Guide.
audit queue size

Summary information Default value Range of values Status Display level Required role Configuration groups 100 165535 Dynamic Intermediate System Security Officer Memory Use, Security Related
88
CHAPTER 5
The in-memory audit queue holds audit records generated by user processes until the records can be processed and written to the audit trail. A System Security Officer can change the size of the audit queue using audit queue size. There is a trade-off between performance and risk that must be considered when you configure the queue size. If the queue is too large, records can remain in it for some time. As long as records are in the queue, they are at risk of being lost if the system crashes. However, if the queue is too small, it can become full repeatedly, which affects overall system performance; user processes that generate audit records sleep if the audit queue is full. Following are some guidelines for determining how big your audit queue should be. You must also take into account the amount of auditing to be performed at your site. The memory requirement for a single audit record is 424 bytes; however a record can be as small as 22 bytes when it is written to a data page. The maximum number of audit records that can be lost in a system crash is the size of the audit queue (in records), plus 20. After records leave the audit queue they remain on a buffer page until they are written to the current audit table on the disk. The pages are flushed to disk every 20 records at the most (less if the audit process is not constantly busy). In the system audit tables, the extrainfo field and fields containing names are of variable length, so audit records that contain complete name information are generally larger.
The number of audit records that can fit on a page varies from 4 to as many as 80 or more. The memory requirement for the default audit queue size of 100 is approximately 42K.
auditing
0 (off) 0 (off), 1 (on) Dynamic Intermediate System Security Officer Security Related
auditing enables or disables auditing for Adaptive Server.
89
check password for digit

Summary information Default value Range of values Status Display level Required role Configuration group 0 1, 0 Dynamic 10 System Security Officer Security Related
The System Security Officer can tell the server to check for at least one character or digit in a password using the server-wide configuration parameter check password for digit. If set, this parameter does not affect existing passwords. By default, checking for digits is off. To activate check password for digit functionality, enter:
sp_configure "check password for digit", 1
To deactivate check password for digit functionality, enter:

cis bulk insert array size

50 02147483647 Dynamic Comprehensive System Administrator Component Integration Services
When performing a bulk transfer of data from one Adaptive Server to another Adaptive Server, CIS buffers rows internally, and asks the Open Client bulk library to transfer them as a block. The size of the array is controlled by cis bulk insert array size. The default is 50 rows, and the property is dynamic, allowing it to be changed without restartign the server.
90
CHAPTER 5
cis bulk insert batch size

Summary information Default value Range of values Status Display level Required role Configuration group 0 02147483647 Dynamic Comprehensive System Administrator Component Integration Services
The cis bulk insert batch size parameter determines how many rows from the source tables are to be bulk copied into the target table as a single batch using select into. If the parameter is left at zero (the default), all rows are copied as a single batch. Otherwise, after the count of rows specified by this parameter has been copied to the target table, the server issues a bulk commit to the target server, causing the batch to be committed. If a normal client-generated bulk copy operation (such as that produced by the bcp utility) is received, then the client is expected to control the size of the bulk batch, and the server ignores the value of this configuration parameter.
cis connect timeout

Summary information Default value Range of values Status Display level Required role Configuration group 0 032767 Dynamic Comprehensive System Administrator Component Integration Services
The cis connect timeout parameter determines the wait time in seconds for a successful Client-Library connection. By default, no timeout is provided.
cis cursor rows

Summary information Default value
50
91
Summary information Range of values Status Display level Required role Configuration group 12147483647 Dynamic Comprehensive System Administrator Component Integration Services
The cis cursor rows parameter specifies the cursor row count for cursor open and cursor fetch operations. Increasing this value means more rows are fetched in one operation. This increases speed but requires more memory.
cis packet size

512 51232768 Dynamic Comprehensive System Administrator Component Integration Services
The cis packet size parameter specifies the size of Tabular Data Stream (TDS) packets that are exchanged between the server and a remote server when a connection is initiated. The default packet size on most systems is 512 bytes, and this may be adequate for most applications. However, larger packet sizes may result in significantly improved query performance, especially when text, unitext, and image or bulk data is involved. If you specify a packet size larger than the default, and the requested server is a version 10 or later Adaptive Server, then the target server must be configured to allow variable-length packet sizes. Adaptive Server configuration parameters of interest in this case are:
additional netmem maximum network packet size
92
CHAPTER 5
cis rpc handling

Summary information Default value Valid values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Component Integration Services
The cis rpc handling parameter specifies the default method for remote procedural call (RPC) handling. Setting cis rpc handling to 0 sets the Adaptive Server site handler as the default RPC handling mechanism. Setting the parameter to 1 forces RPC handling to use Component Integration Service access methods. For more information, see set cis rpc handling in the Component Integration Services Users Guide.
configuration file
Summary information Default value Range of values Status Display level Required role Configuration group 0 N/A Dynamic Comprehensive System Administrator General Information
The configuration file parameter specifies the location of the configuration file currently in use. See Using sp_configure with a configuration file on page 67 for a complete description of configuration files. In sp_configure output, the Run Value column displays only 10 characters. For this reason, the output may not display the entire path and name of your configuration file.
cpu accounting flush interval

Summary information Default value Range of values
200 12147483647
93
Summary information Status Display level Required role Configuration group Dynamic Comprehensive System Administrator SQL Server Administration
cpu accounting flush interval specifies the amount of time, in machine clock ticks, that Adaptive Server waits before flushing CPU usage statistics for each user from sysprocesses to syslogins, a procedure used in chargeback accounting. (This is measured in machine clock ticks, not Adaptive Server clock ticks.)
When a user logs in to Adaptive Server, the server begins accumulating figures for CPU usage for that user process in sysprocesses. When a user logs off Adaptive Server, or when the value of cpu accounting flush interval is exceeded, the accumulated CPU usage statistics are flushed from sysprocesses to syslogins. These statistics continue accumulating in syslogins until you clear the totals using sp_clearstats. You can display the current totals from syslogins using sp_reportstats. The value to which you set cpu accounting flush interval depends on the type of reporting you intend to do. If you run reports on a monthly basis, set cpu accounting flush interval to a relatively high value. With infrequent reporting, it is less critical that the data in syslogins be updated as often. On the other hand, if you perform periodic ad hoc selects on the totcpu column in syslogins to determine CPU usage by process, set cpu accounting flush interval to a lower value. Doing so increases the likelihood of the data in syslogins being up-to-date when you execute your selects. Setting cpu accounting flush interval to a low value may cause processes to be mistakenly identified as potential deadlock victims by the lock manager. When the lock manager detects a deadlock, it checks the amount of CPU time accumulated by each competing processes. The process with the lesser amount is chosen as the deadlock victim and is terminated by the lock manager. Additionally, when cpu accounting flush interval is set to a low value, the task handlers that store CPU usage information for processes are initialized more frequently, thus making processes appear as if they have accumulated less CPU time than they actually have. Because of this, the lock manager may select a process as the deadlock victim when, in fact, that process has more accumulated CPU time than the competing process.
94
CHAPTER 5
If you do not intend to report on CPU usage at all, set cpu accounting flush interval to its maximum value. This reduces the number of times syslogins is updated, and reduces the number of times its pages need to be written to disk.
cpu grace time

Summary information Default value Range of values Status Display level Required role Configuration group 500 02147483647 Dynamic Comprehensive System Administrator SQL Server Administration
cpu grace time, together with time slice, specifies the maximum amount of time that a user process can run without yielding the CPU before Adaptive Server preempts it and terminates it with a timeslice error. The units for cpu grace time are time ticks, as defined by sql server clock tick length. See sql server clock tick length on page 214 for more information.
When a process exceeds cpu grace time Adaptive Server infects it by removing the process from the internal queues. The process is killed, but Adaptive Server is not affected. This prevents runaway processes from monopolizing the CPU. If any of your user processes become infected, you may be able to temporarily fix the problem by increasing the value of cpu grace time. However, be sure that the problem really is a process that takes more than the current value of cpu grace time to complete, rather than a runaway process. Temporarily increasing the cpu grace time value is a workaround, not a permanent fix, since it may cause other complications; see time slice on page 227. Also, see Chapter 4, Using Engines and CPUs in the Performance and Tuning Guide: Basics for a more detailed discussion of task scheduling.
current audit table

Summary information Default value Range of values Status Display level
1 08 Dynamic Intermediate
95
Summary information Required role Configuration group System Security Officer Security Related
current audit table establishes the table where Adaptive Server writes audit
rows. A System Security Officer can change the current audit table, using:
sp_configure "current audit table", n [, "with truncate"]
where n is an integer that determines the new current audit table, as follows: 1 means sysaudits_01, 2 means sysaudits_02, and so forth, up to 8. 0 tells Adaptive Server to set the current audit table to the next table. For example, if your installation has three audit tables, sysaudits_01, sysaudits_02, and sysaudits_03, Adaptive Server sets the current audit table to: 2 if the current audit table is sysaudits_01 3 if the current audit table is sysaudits_02 1 if the current audit table is sysaudits_03
"with truncate" specifies that Adaptive Server should truncate the new table if it is not already empty. sp_configure fails if this option is not specified and the
table is not empty.

Note If Adaptive Server truncates the current audit table, and you have not
archived the data, the tables audit records are lost. Be sure that the audit data is archived before using the with truncate option. To execute sp_configure to change the current audit table, you must have the sso_role active. You can write a threshold procedure to change the current audit table automatically.
deadlock checking period

Summary information Default value Range of values Status Display level 500 02147483 Dynamic Comprehensive
96
CHAPTER 5
Summary information Required role Configuration group System Administrator Lock Manager
deadlock checking period specifies the minimum amount of time (in
milliseconds) before Adaptive Server initiates a deadlock check for a process that is waiting on a lock to be released. Deadlock checking is time-consuming overhead for applications that experience no deadlocks or very few, and the overhead grows as the percentage of lock requests that must wait for a lock also increases. If you set deadlock checking period to a nonzero value (n), Adaptive Server initiates a deadlock check after a process waits at least n milliseconds. For example, you can make a process wait at least 700 milliseconds for a lock before each deadlock check by entering:
sp_configure "deadlock checking period", 700
If you set deadlock checking period to 0, Adaptive Server initiates deadlock checking when each process begins to wait for a lock. Any value less than the number of milliseconds in a clock tick is treated as 0. See sql server clock tick length on page 214 for more information. Configuring deadlock checking period to a higher value produces longer delays before deadlocks are detected. However, since Adaptive Server grants most lock requests before this time elapses, the deadlock checking overhead is avoided for those lock requests. If your applications deadlock infrequently, set deadlock checking period to a higher value to avoid the overhead of deadlock checking for most processes. Otherwise, the default value of 500 should suffice. Use sp_sysmon to determine the frequency of deadlocks in your system and the best setting for deadlock checking period. See the Performance and Tuning Guide for more information.
deadlock pipe active

Summary information Default value Range of values Status Display level Required role
0 01 Dynamic Comprehensive System Administrator
97
Summary information Configuration groups Memory Use, Monitoring
deadlock pipe active controls whether Adaptive Server collects deadlock messages. If both deadlock pipe active and deadlock pipe max messages are
enabled, Adaptive Server collects the text for each deadlock. You can retrieve these deadlock messages using monDeadLock.
deadlock pipe max messages

Summary information Default value Range of values Status Display level Required role Configuration group 0 02147483647 Dynamic Comprehensive System Administrator Monitoring
deadlock pipe max messages determines the number of deadlock messages
Adaptive Server stores per engine. The total number of messages in the
monSQLText table will be the value of sql text pipe max messages times the
number of engines running.
deadlock retries
5 02147483647 Dynamic Intermediate System Administrator Lock Manager, SQL Server Administration
deadlock retries specifies the number of times a transaction can attempt to acquire a lock when deadlocking occurs during an index page split or shrink.
For example, Figure 5-1 illustrates the following scenario: Transaction A locks page 1007 and needs to acquire a lock on page 1009 to update the page pointers for a page split.
98
CHAPTER 5
Transaction B is also inserting an index row that causes a page split, holds a lock on page 1009, and needs to acquire a lock on page 1007.
In this situation, rather than immediately choosing a process as a deadlock victim, Adaptive Server relinquishes the index locks for one of the transactions. This often allows the other transaction to complete and release its locks. For the transaction that surrendered its locking attempt, the index is rescanned from the root page, and the page split operation is attempted again, up to the number of times specified by deadlock retries.
Figure 5-1: Deadlocks during page splitting in a clustered index Page 1001 Bennet 1007 Karsen 1009 Smith 1062
Transaction A: Splitting index page 1007; holds lock on 1007; needs to acquire a lock on 1009 to update its previous-page pointer
Page 1007 Bennet 1132 Greane 1133 Hunter 1127 Irons 1218
Page 1009 Karsen 1315 Lemmon 1220 Perkins 1257 Quigley 1254
Transaction B: Splitting index page 1009; holds lock on 1009; needs to acquire a lock on 1007 to update its next-page pointer
Page 1007 Bennet 1132 Greane 1133 Grizley 1127
Page 1033 Hunter 1127 Irons 1218
Page 1009 Karsen 1315 Lemmon 1220 Mouton 1244
Page 1044 Perkins 1257 Quigley 1254
sp_sysmon reports on deadlocks and retries. See the Performance and Tuning
Guide for more information.
99
default character set id

Summary information Default value Range of values Status Display level Required role Configuration group 1 0255 Static Intermediate System Administrator Languages
The default character set id parameter specifies the number of the default character set used by the server. The default is set at installation time, and can be changed later with the Sybase installation utilities. See Chapter 9, Configuring Character Sets, Sort Orders, and Languages, for a discussion of how to change character sets and sort orders.
default database size

Summary information Default value Range of values Status Display level Required role Configuration group 3MB 2a 10000
a. Minimum determined by servers logical page size.
Dynamic Intermediate System Administrator SQL Server Administration
default database size sets the default number of megabytes allocated to a new user database if the create database statement is issued without any size parameters. A database size given in a create database statement takes precedence over the value set by this configuration parameter.
If most of the new databases on your Adaptive Server require more than one logical page size, you may want to increase the default.
Note If you alter the model database, you must also increase the default database size, because the create database command copies model to create a
new user database.
100
CHAPTER 5
default exp_row_size percent

Summary information Default value Range of values Status Display level Required role Configuration group 5 0100 Dynamic Intermediate System Administrator SQL Server Administration
default exp_row_size percent reserves space for expanding updates in data-
only-locked tables, to reduce row forwarding. An expanding update is any update to a data row that increases the length of the row. Data rows that allow null values or that have variable-length columns may be subject to expanding updates. In data-only-locked tables, expanding updates can require row forwarding if the data row increases in size so that it no longer fits on the page. The default value, 5, sets aside 5 percent of the available data page size for use by expanding updates. Since 2002 bytes are available for data storage on pages in data-only-locked tables, this leaves 100 bytes for expansion. This value is applied only to pages for tables that have variable-length columns. Valid values are 0100. Setting default exp_row_size percent to 0 means that all pages are completely filled and no space is left for expanding updates.
default exp_row_size percent is applied to data-only-locked tables with variable-length columns when exp_row_size is not explicitly provided with create table or set with sp_chgattribute. If a value is provided with create table,
that value takes precedence over the configuration parameter setting. See the Performance and Tuning Guide for more information.
default fill factor percent

101
default fill factor percent determines how full Adaptive Server makes each index page when it is creating a new index on existing data, unless the fill factor is specified in the create index statement. The fillfactor percentage is relevant only at the time the index is created. As data changes, pages are not maintained at any particular level of fullness. default fill factor percent affects:
The amount of storage space used by your data Adaptive Server redistributes the data as it creates the clustered index. Performance splitting up pages uses Adaptive Server resources.
There is seldom a reason to change default fill factor percent, especially since you can override it in the create index command. For more information about the fill factor percentage, see create index in the Reference Manual.
default language id
0 032767 Dynamic Intermediate System Administrator Languages
The default language id parameter is the number of the language that is used to display system messages unless a user has chosen another language from those available on the server. us_english always has an ID of NULL. Additional languages are assigned unique numbers as they are added.
default network packet size

512 512 65535 Static Intermediate System Administrator
102
CHAPTER 5
Summary information Configuration groups Memory Use, Network Communication, User Environment
default network packet size configures the default packet size for all Adaptive Server users. You can set default network packet size to any multiple of 512
bytes; values that are not even multiples of 512 are rounded down. Memory for all users who log in with the default packet size is allocated from Adaptive Servers memory pool, as set with total logical memory. This memory is allocated for network packets when Adaptive Server is started. Each Adaptive Server user connection uses: One read buffer One buffer for messages One write buffer
Each of these buffers requires default network packet size bytes. The total amount of memory allocated for network packets is:
(number of user connections + number of worker processes) * 3 * default network packet size
For example, if you set the default network packet size to 1024 bytes, and you have 50 user connections and 20 worker processes, the amount of network memory required is: (50 + 20) * 3 * 1024 = 215040 bytes If you increase the default network packet size, you must also increase the max network packet size to at least the same size. If the value of max network packet size is greater than the value of default network packet size, increase the value of additional network memory. See additional network memory on page 81 for further information. Use sp_sysmon to see how changing the default network packet size parameter affects network I/O management and task switching. For example, try increasing default network packet size and then checking sp_sysmon output to see how this affects bcp for large batches. See the Performance and Tuning Guide for more information.
103
Requesting a larger packet size at login
The default packet size for most client programs like bcp and isql is set to 512 bytes. If you change the default packet size, clients must request the larger packet size when they connect. Use the -A flag to Adaptive Server client programs to request a large packet size. For example:
isql -A2048
default sortorder id
Summary information Default value Range of values Status Display level Required role Configuration group 50 0255 Static Comprehensive System Administrator Languages
The default sortorder id parameter is the number of the sort order that is installed as the default on the server. To change the default sort order, see Chapter 9, Configuring Character Sets, Sort Orders, and Languages.
default unicode sortorder

Summary information Default value Range of values Status Display level Required role Configuration group binary (not currently used) Static Comprehensive System Administrator Unicode
The default unicode sortorder parameter is a string parameter that defines the default Unicode sort order installed on the server. A string parameter is used rather than a numeric parameter to guarantee a unique ID. To change the Unicode default sort order, see Chapter 9, Configuring Character Sets, Sort Orders, and Languages.
104
CHAPTER 5
default XML sortorder

Summary information Default value Range of values Status Display level Required role Configuration group binary (not currently used) Static Comprehensive System Administrator Unicode
The default XML sortorder parameter is a string parameter that defines the sort order used by the XML engine. A string parameter is used rather than a numeric parameter to guarantee a unique ID. For more information, see Chapter 6, XML Support for I18N in XML Services in Adaptive Server Enterprise.
disable character set conversions

Summary information Default value Valid values Status Display level Required role Configuration group 0 (enabled) 0 (enabled), 1 (disabled) Static Comprehensive System Administrator Languages
Changing disable character set conversions to 1 turns off character set conversion for data moving between clients and Adaptive Server. By default, Adaptive Server performs conversion on data moving to and from clients that use character sets that are different than the servers. For example, if some clients use Latin-1 (iso_1) and Adaptive Server uses Roman-8 (roman8) as its default character set, data from the clients is converted to Roman-8 when being loaded into Adaptive Server. For clients using Latin-1, the data is reconverted when it is sent to the client; for clients using the same character set as Adaptive Server, the data is not converted. By setting disable character set conversions, you can request that no conversion take place. For example, if all clients are using a given character set, and you want Adaptive Server to store all data in that character set, you can set disable character set conversions to 1, and no conversion takes place.
105
disable disk mirroring

Summary information Default value Valid values Status Display level Required role Configuration group 1 0 (off), 1 (on) Static Comprehensive System Administrator Disk I/O
disable disk mirroring enables or disables disk mirroring for Adaptive Server. This is a global variable; Adaptive Server does not perform any disk mirroring after this configuration parameter is set to 1 and Adaptive Server is restarted. Setting disable disk mirroring to 0 enables disk mirroring.
Note Disk mirroring must be disabled if you configure Adaptive Server for
Failover in a high availability system.
disk i/o structures

Summary information Default value Range of values Status Display level Required role Configuration group 256 02147483647 Dynamic Comprehensive System Administrator Disk I/O, Memory Use
The disk i/o structures parameter specifies the initial number of disk I/O control blocks Adaptive Server allocates at start-up. User processes require a disk I/O control block before Adaptive Server can initiate an I/O request for the process. The memory for disk I/O control blocks is preallocated when Adaptive Server starts. You should configure disk i/o structures to as high a value as your operating system allows, to minimize the chance of running out of disk I/O structures. See your operating system documentation for information on concurrent disk I/Os.
106
CHAPTER 5
Use sp_sysmon to determine whether to allocate more disk I/O structures. See the Performance and Tuning Guide. You can set the max asynch i/os per server configuration parameter to the same value as disk i/o structures. See max async i/os per server on page 143 for more information.
dtm detach timeout period

Summary information Default value Valid values Status Display level Required role Configuration group 0 (minutes) 0 2147483647 (minutes) Dynamic 10 System Administrator DTM Administration
dtm detach timeout period sets the amount of time, in minutes, that a distributed
transaction branch can remain in the detached state. In some X/Open XA environments, a transaction may become detached from its thread of control (usually to become attached to a different thread of control). Adaptive Server permits transactions to remain in a detached state for the length of time specified by dtm detach timeout period. After this time has passed, Adaptive Server rolls back the detached transaction.
dtm lock timeout period

300 (seconds) 1 2147483647 (seconds) Dynamic 10 System Administrator DTM Administration
dtm lock timeout period sets the maximum amount of time, in seconds, that a distributed transaction branch waits for lock resources to become available. After this time has passed, Adaptive Server considers the transaction to be in a deadlock situation, and rolls back the transaction branch that triggered the deadlock. This ultimately rolls back the entire distributed transaction.
107
Distributed transactions may potentially deadlock themselves if they propagate a transaction to a remote server, and in turn, the remote server propagates a transaction back to the originating server. This situation is shown in Figure 52 the work of distributed transaction dxact1 is propagated to Adaptive Server 2 via rpc1. Adaptive Server 2 then propagates the transaction back to the coordinating server via rpc2. rpc2 and dxact1 share the same gtrid but have different branch qualifiers, so they cannot share the same transaction resources. If rpc2 is awaiting a lock held by dxact1, a deadlock situation exists.
Figure 5-2: Distributed transaction deadlock
dxact1 ASE1 ASTC rpc1 rpc2
ASE2 ASTC
Adaptive Server does not attempt to detect interserver deadlocks. Instead, it relies on dtm lock timeout period. In Figure 5-2, after dtm lock timeout period has expired, the transaction created for rpc2 is aborted. This causes Adaptive Server 2 to report a failure in its work, and dxact1 is ultimately aborted as well. The value of dtm lock timeout period applies only to distributed transactions. Local transactions may use a lock timeout period with the server-wide lock wait period parameter.
Note Adaptive Server does not use dtm lock timeout period to detect deadlocks
on system tables.
dump on conditions
0 (off) 0 (off), 1 (on)
108
CHAPTER 5
Summary information Status Display level Required role Configuration group Dynamic Intermediate System Administrator Group Diagnostics
dump on conditions determines whether Adaptive Server generates a dump of data in shared memory when it encounters the conditions specified in maximum dump conditions.
Note The dump on conditions parameter is included for use only by Sybase
Technical Support. Do not modify it unless you are instructed to do so by Sybase Technical Support.
dynamic allocation on demand

1 0, 1 Dynamic Basic System Administrator Memory Use, Physical Memory
Determines when memory is allocated for changes to dynamic memory configuration parameters. If you set dynamic allocation on demand to 1, memory is allocated only as it is needed. That is, if you change the configuration for number of user connections from 100 to 200, the memory for each user is added only when the user connects to the server. Adaptive Server continues to add memory until it reaches the new maximum for user connections. If dynamic allocation on demand is set to 0, all the memory required for any dynamic configuration changes is allocated immediately. That is, when you change the number of user connections from 100 to 200, the memory required for the extra 100 user connections is immediately allocated.
109
enable cis
Summary information Default value Valid values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Static Comprehensive System Administrator Component Integration Services
The enable cis parameter enables or disables Component Integration Service.
enable DTM
Summary information Default value Valid values Status Display level Required role Configuration groups 0 (off) 0 (off), 1(on) Static 10 System Administrator DTM Administration, SQL Server Administration
enable DTM enables or disables the Adaptive Server Distributed Transaction
Management (DTM) feature. When the DTM feature is enabled, you can use Adaptive Server as a resource manager in X/Open XA and MSDTC systems. You must reboot the server for this parameter to take effect. See the XA Interface Integration Guide for CICS, Encina, and TUXEDO for more information about using Adaptive Server in an X/Open XA environment. See Using Adaptive Server Distributed Transaction Management Features for information about transactions in MSDTC environments, and for information about Adaptive Server native transaction coordination services.
Note The license information and the run value for enable DTM are
independent of each other. Whether or not you have a license for DTM, the Run value and the configuration value are set to 1 after you reboot Adaptive Server. Until you have a license, you cannot run DTM. If you have not installed a valid license, Adaptive Server logs an error message and does not activate the feature. See the installation guide for your platform for information about installing license keys.
110
CHAPTER 5
enable enterprise java beans

Summary information Default value Range of values Status Display level Required role Configuration group 0 (disabled) 0 (disabled), 1 (enabled) Static Comprehensive System Administrator Java Services
The enable enterprise java beans parameter enables and disables EJB Server in the Adaptive Server database. You cannot use EJB Server until the Adaptive Server is enabled for EJB Server.
Note The license information and the Run value for enable java beans are independent of each other. Whether or not you have a license for java, the Run
value and the Config value are set to 1 after you restart Adaptive Server. You cannot run EJB Server until you have a license. If you have not installed a valid license, Adaptive Server logs an error message and does not activate the feature. See the installation guide for your platform for information about installing license keys.
enable file access

Summary information Default value Valid values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Static Comprehensive System Administrator Component Integration Services
Enables access through proxy tables to the External File System. Requires a license for ASE_XFS.
111
enable full-text search

Summary information Default value Valid values Status Display level Required role Configuration group 1 0 (off), 1 (on) Static Comprehensive System Administrator Component Integration Services
Enables Enhanced Full-Text Search services. Requires a license for ASE_EFTS.
enable HA
Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 02 Static Comprehensive System Administrator SQL Server Administration
Setting enable HA is set to 1 allows you to configure Adaptive Server as a companion server in an active-active high availability subsystem. Setting enable HA is set to 2 allows you to configure Adaptive Server as a companion server in an active-passive high availability subsystem.
112
CHAPTER 5
Adaptive Server uses Sybase Failover to interact with the high availability subsystem. You must set enable HA to 1 before you run the installhasvss script (insthasv on Windows), which installs the system procedures for Sybase Failover.
Note The license information and the Run value for enable HA are independent of each other. Whether or not you have a license for Sybase Failover, the Run value and the Config value are set to 1 after you reboot Adaptive Server. And until you have a license, you cannot run Sybase Failover. If you have not installed a valid license, Adaptive Server logs an error message and does not activate the feature. See the Installation Guide for your platform for information about installing license keys.
Setting enble HA to 1 or 2 does not mean that Adaptive Server is configured to work in a high availability system. You must perform the steps described in Using Sybase Failover in A High Availability System to configure Adaptive Server to be a companion server in a high availability system. When enable HA is set to 0, you cannot configure for Sybase Failover, and you cannot run installhasvss (insthasv on Windows).
enable housekeeper GC
Summary information Default value Range of values Status Display level Required role Configuration group 1 (on) 04 Dynamic Intermediate System Administrator SQL Server Administration
The housekeeper garbage collection task performs space reclamation on dataonly-locked tables. When a user task deletes a row from a data-only-locked table, a task is queued to the housekeeper to check the data and index pages for committed deletes. The housekeeper garbage collection task is controlled by enable housekeeper GC. For more information on the housekeeper garbage collection task see Chapter 4, Using Engines and CPUs in the Performance and Tuning Guide: Basics. These are valid values for enable housekeeper GC:
113
0 disables the housekeeper garbage collection task, but enables the delete commands lazy garbage collection. You must use reorg reclaim_space to deallocate empty pages. This is the cheapest option with the lowest performance impact, but it may cause performance problems if many empty pages accumulate. Sybase does not recommend using this value. 1 enables lazy garbage collection for the housekeeper garbage collection task and the delete command. If more empty pages accumulate than your application allows, consider options 4 or 5. You can use the optdiag utility to obtain statistics of empty pages. 2 reserved for future. 3 reserved for future. 4 enables aggressive garbage collection for the housekeeper garbage collection task and the delete command. This option is the most effective, but the delete command is expensive. This option is ideal if the deletes on your DOL tables are in a batch. 5 enables aggressive garbage collection for the housekeeper, and lazy garbage collection for the delete command. This option is less expensive for deletes than option 4. This option is suitable when deletes are caused by concurrent transactions
sp_sysmon reports on how often the housekeeper garbage collection task
performed space reclamation and how many pages were reclaimed. See the Performance and Tuning Guide for more information.
enable java
0 (disabled) 0 (disabled), 1 (enabled) Static Comprehensive System Administrator Java Services
114
CHAPTER 5
The enable java parameter enables and disables Java in the Adaptive Server database. You cannot install Java classes or perform any Java operations until the server is enabled for Java.
Note The license information and the Run value for enable java are independent of each other. Whether or not you have a license for java, the Run value and the Config value are set to 1 after you restart Adaptive Server. You cannot run Java until you have a license. If you have not installed a valid license, Adaptive Server logs an error message and does not activate the feature. See the installation guide for your platform for information about installing license keys.
enable job scheduler

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator SQL Server Administration
Determines whether Job Scheduler starts when Adaptive Server starts.
enable ldap user auth

Summary information Default value Valid values
0 (off) 0 (off) allows only syslogins authentication, 1 (on) allows both LDAP and syslogins authentication, 2 (on) allows only LDAP authentication Dynamic Comprehensive System Security Officer Security Related
Status Display level Required role Configuration group
115
When enable ldap user auth is 1, Adaptive Server searches the LDAP server to authenticate each user. If the LDAP authentication fails, Adaptive Server searches syslogins to authenticate the user. Use this level when migrating users from Adaptive Server authentication to LDAP authentication.
enable metrics capture

Summary information Default value Range of values Status Display level Required role Configuration group 0 1 (disabled), 0 (enabled) Dynamic Intermediate System Administrator SQL Server Administration
enable metrics capture enables Adaptive Server to capture metrics at the server
level. Metrics for ad hoc statements are captured in the system catalogs; metrics for statements in a stored procedure are saved in the procedure cache.
enable monitoring
0 01 Dynamic Comprehensive System Administrator Monitoring
enable monitoring controls whether Adaptive Server collects the monitoring table data. Data is not collected if enable monitoring is set to 0. enable monitoring acts as a master switch that determines whether any of the following configuration parameters are enabled.
enable pam user auth

0 (off)
116
CHAPTER 5
Summary information Range of values 0 (off) allows only syslogins authentication 1 (on) allows both PAM and syslogins authentication 2 (on) allows only PAM authentication Dynamic Intermediate System Security Officer Security Related
enable pam user auth controls the ability to authenticate users using pluggable authentication modules (PAM).
When enable pam user auth is set to 1, Adaptive Server uses the PAM provider to authenticate each user. If the PAM authentication fails, Adaptive Server searches syslogins to authenticate the user. Use this level when migrating users from Adaptive Server authentication to PAM authentication.
enable real time messaging

1 (on) 0 (off), 1 (on) Dynamic Comprehensive System Administrator SQL Server Administration
Use enables the real time messaging services.
enable rep agent threads

1 (on) 0 (off), 1 (on) Dynamic Basic System Administrator Memory Use, Rep Agent Thread Administration
117
enable rep agent threads enables the RepAgent thread within Adaptive Server.
Through version 11.0.3 of Replication Server, the Log Transfer Manager (LTM), a replication system component, transfers replication data to the Replication Server. Beginning with Replication Server versions later than 11.0.3, transfer of replication data is handled by RepAgent, which runs as a thread under Adaptive Server. Setting enable rep agent threads enables this feature. Other steps are also required to enable replication. For more information, see the Replication Server documentation.
enable row level access control

0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Security Officer Security Related
Enables row level access control. You must have the security services license key enabled before you can configure enable row level access control.
enable ssl
0 (off) 0 (off), 1 (on) Static Comprehensive System Security Officer Security Related
The enable ssl parameter enables or disables Secure Sockets Layer sessionbased security.
118
CHAPTER 5
enable semantic partitioning

Summary information Default value Range of values Status Display level Required role Configuration group 0 1 (enabled), 0 (disabled) Dynamic Comprehensive System Administrator SQL Server Administration
Enables partitioning other than round-robin (for example list, hash, and range partitioning) in Adaptive Server. Before you use any of these partitioning schemes, you must first have the appropriate license.
enable surrogate processing

Summary information Default value Range of values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Unicode
Activates the processing and maintains the integrity of surrogate pairs in Unicode data. Set enable surrogate processing to 1 to enable surrogate processing. If this is disabled, the server ignores the presence of surrogate pairs in the Unicode data, and all code that maintains the integrity of surrogate pairs is skipped. This enhances performance, but restricts the range of Unicode characters that can appear in the data.
enable unicode conversion

1 02 Dynamic Comprehensive System Administrator
119
Summary information Configuration groups Languages, Unicode
Activates character conversion using Unilib for the char, varchar, and text datatypes. Set enable unicode conversion to 1 to use the built-in conversion. If it cannot find a built-in conversion, Adaptive Server uses the Unilib character conversion. Set enable unicode conversion to 2 to use the appropriate Unilib conversion. Set the parameter to 0 to use only the built-in character-set conversion.
enable unicode normalization

Summary information Default value Range of values Status Display level Required role Configuration group 1 (on) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Unicode
Activates Unilib character normalization. The normalization process modifies the data so there is only a single representation in the database for a given sequence of abstract characters. Often, characters followed by combined diacritics are replaced by precombined forms. Set enable unicode normalization to 1 to use the built-in process that enforces normalization on all incoming Unicode data. If this parameter is disabled (set to 0), the normalization step is bypassed and the client code is responsible for normalization rather than the server. If normalization is disabled, performance is improvedbut only if all clients present Unicode data to the server using the same representation.
Note Once disabled, normalization cannot be turned on again. This one-way
change prevents non-normalized data from entering the data base.
enable webservices
120
CHAPTER 5
Summary information Range of values Status Display level Required role Configuration group 1 (disabled), 0 (enabled) Dynamic Intermediate System Administrator SQL Server Administration
Enables the webservices. A value of one enables webservices, and a value of 0 disables webservices.
enable xact coordination

1 (on) 0 (off), 1(on) Static 10 System Administrator DTM Administration
enable xact coordination enables or disables Adaptive Server transaction coordination services. When this parameter is set to 1 (on), coordination services are enabled, and the server can propagate transactions to other Adaptive Servers. This may occur when a transaction executes a remote procedure call (RPC) to update data in another server, or updates data in another server using Component Integration Services (CIS). Transaction coordination services ensure that updates to remote Adaptive Server data commit or roll back with the original transaction.
If this parameter is set to 0 (off), Adaptive Server does not coordinate the work of remote servers. Transactions can still execute RPCs and update data using CIS, but Adaptive Server cannot ensure that remote transactions are rolled back with the original transaction or that remote work is committed along with an original transaction, if remote servers experience a system failure. This corresponds to the behavior of Adaptive Server versions earlier than version 12.x.
121
enable xml
Summary information Default value Range of values Status Display level Required role Configuration group 0 1 (disabled), 0 (enabled) Dynamic Intermediate System Administrator SQL Server Administration
Enables the XML services. A value of one enables XML services, and a value of 0 disables XML services.
errorlog pipe active

errorlog pipe active controls whether Adaptive Server collects error log messages. If both errorlog pipe active and errorlog pipe max messages are enabled, Adaptive Server collects all the messages sent to the error log. You can retrieve these error log messages using monErrorLog.
errorlog pipe max messages

0 02147483647 Dynamic Comprehensive System Administrator Memory Use, Monitoring
122
CHAPTER 5
errorlog pipe max messages determines the number of error log messages Adaptive Server stores per engine. The total number of messages in the monSQLText table will be the value of sql text pipe max messages times the number of engines running.
esp execution priority

Summary information Default value Range of values Status Display level Required role Configuration group 8 015 Dynamic Comprehensive System Administrator Extended Stored Procedure
The esp execution priority parameter sets the priority of the XP Server thread for ESP execution. ESPs can be CPU-intensive over long periods of time. Also, since XP Server resides on the same machine as Adaptive Server, XP Server can impact Adaptive Servers performance. Use esp execution priority to set the priority of the XP Server thread for ESP execution. See the Open Server Server-Library/C Reference Manual for information about scheduling Open Server threads.
esp execution stacksize

34816 34816214 Static Comprehensive System Administrator Extended Stored Procedure
The esp execution stacksize parameter sets the size of the stack, in bytes, to be allocated for ESP execution. Use this parameter if you have your own ESP functions that require a larger stack size than the default, 34816.
123
esp unload dll

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Extended Stored Procedure
The esp unload dll parameter specifies whether DLLs that support ESPs should be automatically unloaded from XP Server memory after the ESP call has completed. If esp unload dll is set to 0, DLLs are not automatically unloaded. If it is set to 1, they are automatically unloaded. If esp unload dll is set to 0, you can still unload individual DLLs explicitly at runtime, using sp_freedll.
event buffers per engine

Summary information Default value Range of values Status Display level Required role Configuration groups 100 12147483647 Static Comprehensive System Administrator Memory Use, SQL Server Administration
The event buffers per engine parameter specifies the number of events per Adaptive Server engine that can be monitored simultaneously by Adaptive Server Monitor. Events are used by Adaptive Server Monitor for observing Adaptive Server performance; if you are not using Adaptive Server Monitor, set this parameter to 1. The value to which you set event buffers per engine depends on the number of engines in your configuration, the level of activity on your Adaptive Server, and the types of applications you are running.
124
CHAPTER 5
Setting event buffers per engine to a low value may result in the loss of event information. The default value is likely to be too low for most sites. Values of 2000 and above may be more reasonable for general monitoring. However, you should experiment to determine the appropriate value for your site. In general, setting event buffers per engine to a high value may reduce the amount of performance degradation that Adaptive Server Monitor causes Adaptive Server. Each event buffer uses 100 bytes of memory. To determine the total amount of memory used by a particular value for event buffers per engine, multiply the value by the number of Adaptive Server engines in your configuration.
event log computer name (Windows only)

Summary information Default value Valid values
LocalSystem Name of an Windows machine on the network configured to record Adaptive Server messages LocalSystem NULL
Dynamic Comprehensive System Administrator Error Log
The event log computer name parameter specifies the name of the Windows PC that logs Adaptive Server messages in its Windows Event Log. You can use this parameter logs Adaptive Server messages logged to a remote machine. This feature is available on Windows servers only. A value of LocalSystem or NULL specifies the default local system. You can also use the Server Config utility to set the event log computer name parameter by specifying the Event Log Computer Name under Event Logging. See the configuration guide for information about the Server Config utility. Setting the event log computer name parameter with sp_configure or specifying the Event Log Computer Name under Event Logging overwrites the effects of the command line -G option, if it was specified. If Adaptive Server was started with the -G option, you can change the destination remote machine by setting the event log computer name parameter.
125
For more information about logging Adaptive Server messages to a remote site, see the Configuration Guide for Windows.
event logging (Windows only)

Summary information Default value Valid values Status Display level Required role Configuration group 1 0 (off), 1 (on) Dynamic Comprehensive System Administrator Error Log
The event logging parameter enables and disables the logging of Adaptive Server messages in the Windows Event Log. This feature is available on Windows servers only. The default value of 1 enables Adaptive Server message logging in the Windows Event Log; a value of 0 disables it. You use the Server Config utility to set the event logging parameter by selecting Use Windows Event Logging under Event Logging. See the configuration guide for information about the Server Config utility. Setting the event logging parameter or selecting Use Windows Event Logging overwrites the effects of the command line -g option, if it was specified.
executable codesize + overhead

0 0 2147483647 Calculated Basic System Administrator Memory Use
executable codesize + overhead reports the combined size (in kilobytes) of the
Adaptive Server executable and overhead. It is a calculated value and is not user-configurable.
126
CHAPTER 5
extended cache size

Summary information Default value Range of values Status Display level Required role Configuration group 0 Static Intermediate System Administrator Cache Manager
extended cache size specify the size of the secondary cache.
global async prefetch limit

Summary information Default value Range of values Status Display level Required role Configuration group 10 0100 Dynamic Intermediate System Administrator Cache Manager
The global async prefetch limit parameter specifies the percentage of a buffer pool that can hold the pages brought in by asynchronous prefetch that have not yet been read. This parameter sets the limit for all pools in all caches for which the limit has not been set explicitly with sp_poolconfig. If the limit for a pool is exceeded, asynchronous prefetch is temporarily disabled until the percentage of unread pages falls below the limit. For more information, see Tuning Asynchronous Prefetch in the Performance and Tuning Guide: Optimizer and Abstract Plans.
global cache partition number

1 1-64, as powers of 2 Static Intermediate
127
Summary information Required role Configuration group System Administrator Cache Manager
global cache partition number sets the default number of cache partitions for all
data caches. The number of partitions for a particular cache can be set using
sp_cacheconfig; the local value takes precedence over the global value.
Use cache partitioning to reduce cache spinlock contention; in general, if spinlock contention exceeds 10 percent, partitioning the cache should improve performance. Doubling the number of partitions cuts spinlock contention by about one-half. See Adding cache partitions on page 113 for information on configuring cache partitions. See Tuning Asynchronous Prefetch in the Performance and Tuning Guide: Optimizer and Abstract Plans for information.
heap memory per user

Summary information Default value Valid values Status Display level Required role Configuration groups 4K 0 2147483647 bytes Dynamic Comprehensive System Administrator Memory Use, Physical Memory
heap memory per user configures the amount of heap memory per user. A heap memory pool is an internal memory created at start-up that tasks use to dynamically allocate memory as needed. This memory pool is important if you are running tasks that use wide columns, which require a lot of memory from the stack. The heap memory allocates a temporary buffer that enables these wide column tasks to finish. The heap memory the task uses is returned to the heap memory pool when the task is finished.
The size of the memory pool depends on the number of user connections. Sybase recommends that you set heap memory per user to three times the size of your logical page.
128
CHAPTER 5
histogram tuning factor

Summary information Default value Range of values Status Display level Required role Configuration group 1 (off) 1 100 Dynamic Intermediate System Administrator SQL Server Administration
histogram tuning factor controls the number of steps Adaptive Server analyzes per histogram for update statistics, update index statistics, update all statistics, and create index.
In the following example, Adaptive Server generates an intermediate 20-step histogram with 30 values:
sp_configure 'histogram tuning factor',20 update statistics tab using 30 values
Adaptive Server analyzes the histogram and compresses it into the resulting histogram according to the following parameters: The first step is copied unchanged. The high-frequency steps are copied unchanged. The consecutive range steps are collapsed into the resulting step, so the total weight of the collapsed step would not be bigger than one-thirtieth of the value.
The final histogram in sysstatistics: Has range steps generated in a way similar for a 30-step update statistics, and high frequency ranges are isolated as if the histogram were created with 600 steps. The total number of steps in the resulting histogram may differ between 30 and 600 values. For equally distributed data, the value should be very close to 30. More frequent values in the table means more steps in the histogram. If a column has few different values, all those values may appear as highfrequency cells.
129
You could achieve the same result by increasing the number of steps to 600 as using histogram tuning factor, but this would use more resources in the buffer and procedure cache
histogram tuning factor minimizes the resources histograms consume, and only
increases resource usage when it is in the best interest for optimization. For example, when there is non-uniform distribution of data in a column, or highly duplicated values within a column. In this situation, up to 600 histogram steps are used. However, in most cases, it uses the default value (30 in the example above).
housekeeper free write percent

1 0100 Dynamic Intermediate System Administrator SQL Server Administration
housekeeper free write percent specifies the maximum percentage by which the
housekeeper wash task can increase database writes. For example, to stop the housekeeper task from working when the frequency of database writes reaches 5 percent above normal, set housekeeper free write percent to 5:
sp_configure "housekeeper free write percent", 5
When Adaptive Server has no user tasks to process, the housekeeper wash task automatically begins writing changed pages from cache to disk. These writes result in improved CPU utilization, decreased need for buffer washing during transaction processing, and shorter checkpoints. In applications that repeatedly update the same database page, the housekeeper wash may initiate some unnecessary database writes. Although these writes occur only during the servers idle cycles, they may be unacceptable on systems with overloaded disks.
130
CHAPTER 5
The table and index statistics that are used to optimize queries are maintained in memory structures during query processing. When these statistics change, the changes are not written to the systabstats table immediately, to reduce I/O contention and improve performance. Instead, the housekeeper chores task periodically flushes statistics to disk. The default value allows the housekeeper wash task to increase disk I/O by a maximum of 1 percent. This results in improved performance and recovery speed on most systems. To disable the housekeeper wash task, set the value of housekeeper free write
percent to 0:
Set this value to 0 only if disk contention on your system is high, and it cannot tolerate the extra I/O generated by the housekeeper wash task. If you disable the housekeeper tasks, keep statistics current. Commands that write statistics to disk are:
update statistics dbcc checkdb (for all tables in a database) or dbcc checktable (for a single
table)
sp_flushstats
Run one of these commands on any tables that have been updated since the last time statistics were written to disk, at the following times: Before dumping a database Before an orderly shutdown After rebooting, following a failure or orderly shutdown; in these cases, you cannot use sp_flushstatsyou must use update statistics or dbcc commands After any significant changes to a table, such as a large bulk copy operation, altering the locking scheme, deleting or inserting large numbers of rows, or performing a truncate table command
To allow the housekeeper wash task to work continuously, regardless of the percentage of additional database writes, set housekeeper free write percent to 100:
Use sp_sysmon to monitor housekeeper performance. See the Performance and Tuning Guide for more information.
131
You might also want to look at the number of free checkpoints initiated by the housekeeper task. The Performance and Tuning Guide describes this output.
i/o accounting flush interval

i/o accounting flush interval specifies the amount of time, in machine clock ticks,
that Adaptive Server waits before flushing I/O statistics for each user from
sysprocesses to syslogins. This is used for chargeback accounting.
When a user logs in to Adaptive Server, the server begins accumulating I/O statistics for that user process in sysprocesses. When the value of i/o accounting statistics interval is exceeded, or a user logs off Adaptive Server, the accumulated I/O statistics for that user are flushed from sysprocesses to syslogins. These statistics continue accumulating in syslogins until you clear the totals by using sp_clearstats. You can display the current totals from syslogins by using sp_reportstats. The value to which you set i/o accounting flush interval depends on the type of reporting you intend to do. If you run reports on a monthly basis, set i/o accounting flush interval to a relatively high value. With infrequent reporting, it is less critical that the data in syslogins be updated frequently. If you perform periodic ad hoc selects on the totio column syslogins to determine I/O volume by process, set i/o accounting flush interval to a lower value. Doing so increases the likelihood of the data in syslogins being up to date when you execute your selects. If you do not report on I/O statistics at all, set i/o accounting flush interval to its maximum value. This reduces the number of times syslogins is updated and the number of times its pages must be written to disk.
132
CHAPTER 5
i/o batch size

i/o batch size sets the number of writes issued in a batch before the task goes to
sleep. Once this batch is completed, the task is woken up, and the next batch of writes are issued, ensuring that the I/O subsystem is not flooded with many simultaneous writes. Setting i/o batch size to the appropriate value can improve the performance of operations like checkpoint, dump database, select into, and so on.
i/o polling process count

i/o polling process count specifies the maximum number of processes that Adaptive Server can run before the scheduler checks for disk and/or network I/O completions. Tuning i/o polling process count affects both the response time and throughput of Adaptive Server.
Adaptive Server checks for disk or network I/O completions: If the number of tasks run since the last time Adaptive Server checked for I/O completions equals the value for i/o polling process count, and At every Adaptive Server clock tick.
133
As a general rule, increasing the value of i/o polling process count increases throughput for applications that generate a lot of disk and network I/O. Conversely, decreasing the value improves process response time in these applications, possibly at the risk of lowering throughput. If your applications create both I/O and CPU-bound tasks, tuning i/o polling process count to a low value (12) ensures that I/O-bound tasks get access to CPU cycles. For OLTP applications (or any I/O-bound application with user connections and short transactions), tuning i/o polling process count to a value in the range of 2030 may increase throughput, but may also increase response time. When tuning i/o polling process count, consider three other parameters: sql server clock tick length, which specifies the duration of Adaptive Servers clock tick in microseconds. See sql server clock tick length on page 214. time slice, which specifies the number of clock ticks the Adaptive Servers scheduler allows a user process to run. See time slice on page 227. cpu grace time, which specifies the maximum amount of time (in clock ticks) a user process can run without yielding the CPU before Adaptive Server preempts it and terminates it with a timeslice error. See cpu grace time on page 95.
Use sp_sysmon to determine the effect of changing the i/o polling process count parameter. See the Performance and Tuning Guide for more information.
identity burning set factor

5000 19999999 Static Intermediate System Administrator SQL Server Administration
IDENTITY columns are of type numeric and scale zero whose values are generated by Adaptive Server. Column values can range from a low of 1 to a high determined by the column precision.
134
CHAPTER 5
For each table with an IDENTITY column, Adaptive Server divides the set of possible column values into blocks of consecutive numbers, and makes one block at a time available in memory. Each time you insert a row into a table, Adaptive Server assigns the IDENTITY column the next available value from the block. When all the numbers in a block have been used, the next block becomes available. This method of choosing IDENTITY column values improves server performance. When Adaptive Server assigns a new column value, it reads the current maximum value from memory and adds 1. Disk access becomes necessary only after all values within the block have been used. Because all remaining numbers in a block are discarded in the event of server failure (or shutdown with nowait), this method can lead to gaps in IDENTITY column values. Use identity burning set factor to change the percentage of potential column values that is made available in each block. This number should be high enough for good performance, but not so high that gaps in column values are unacceptably large. The default value, 5000, releases .05 percent of the potential IDENTITY column values for use at one time. To get the correct value for sp_configure, express the percentage in decimal form, and then multiply it by 10 7 (10,000,000). For example, to release 15 percent (.15) of the potential IDENTITY column values at a time, specify a value of .15 times 107 (or 1,500,000) in sp_configure:
sp_configure "identity burning set factor", 1500000
identity grab size

identity grab size allows each Adaptive Server process to reserve a block of
IDENTITY column values for inserts into tables that have an IDENTITY column.
135
This is useful if you are performing inserts, and you want all the inserted data to have contiguous IDENTITY numbers. For instance, if you are entering payroll data, and you want all records associated with a particular department to be located within the same block of rows, set identity grab size to the number of records for that department.
identity grab size applies to all users on Adaptive Server. Large identity grab size values result in large gaps in the IDENTITY column when many users insert data into tables with IDENTITY columns.
Sybase recommends that you set identity grab size to a value large enough to accommodate the largest group of records you want to insert into contiguous rows.
job scheduler interval

1 (in minutes) 1 600 Dynamic Comprehensive System Administrator SQL Server Administration
Sets the interval when the Job Scheduler checks which scheduled job are due to be executed
job scheduler tasks

32 1 640 Dynamic Comprehensive System Administrator SQL Server Administration
Maximum number of jobs that can run at the same time through Job Scheduler.
136
CHAPTER 5
license information
Summary information Default value Valid values Status Display level Required role Configuration group 25 0231 Dynamic Comprehensive System Administrator SQL Server Administration
license information allows Sybase System Administrators to monitor the number of user licenses used in Adaptive Server. Enabling this parameter only monitors the number of licenses issued; it does not enforce the license agreement.
If license information is set to 0, Adaptive Server does not monitor license use. If license information is set to a number greater than 0, the housekeeper chores task monitors the number of licenses used during the idle cycles in Adaptive Server. Set license information to the number of licenses specified in your license agreement.
license information is set to 25, by default. To disable license information, issue:
sp_configure "license information", 0
If the number of licenses used is greater than the number to which license information is set, Adaptive Server writes the following error message to the error log:
WARNING: Exceeded configured number of user licenses
At the end of each 24-hour period, the maximum number of licenses used during that time is added to the syblicenseslog table. The 24-hour period restarts if Adaptive Server is restarted. See Monitoring license use on page 428 for more information.
lock address spinlock ratio

100 12147483647 Static Comprehensive
137
Summary information Required role Configuration group System Administrator Lock Manager
For Adaptive Servers running with multiple engines, the address lock spinlock ratio sets the number of rows in the internal address locks hash table that are protected by one spinlock. Adaptive Server manages the acquiring and releasing of address locks using an internal hash table with 1031 rows (known as hash buckets). This table can use one or more spinlocks to serialize access between processes running on different engines. Adaptive Servers default value for address lock spinlock ratio is 100, which defines 11 spinlocks for the address locks hash table. The first 10 spinlocks protect 100 rows each, and the eleventh spinlock protects the remaining 31 rows. If you specify a value of 1031 or greater for address lock spinlock ratio, Adaptive Server uses only 1 spinlock for the entire table.
lock hashtable size

Summary information Default value Range of values Status Display level Required role Configuration groups 2048 12147483647 Static Comprehensive System Administrator Lock Manager, Memory Use
lock hashtable size specifies the number of hash buckets in the lock hash table.
This table manages all row, page, and table locks, and all lock requests. Each time a task acquires a lock, the lock is assigned to a hash bucket, and each lock request for that lock checks the same hash bucket. Setting this value too low results in large numbers of locks in each hash bucket and slows the searches. On Adaptive Servers with multiple engines, setting this value too low can also lead to increased spinlock contention. Do not set the value to less than the default value, 2048.
lock hashtable size must be a power of 2. If the value you specify is not a power of 2, sp_configure rounds the value to the next highest power of 2 and prints an informational message.
138
CHAPTER 5
The optimal hash table size is a function of the number of distinct objects (pages, tables, and rows) that will be locked concurrently. The optimal hash table size is at least 20 percent of the number of distinct objects that need to be locked concurrently. See the Performance and Tuning Guide for more information on configuring the lock hash table size.
lock scheme
Summary information Default value Range of values Status Display level Required role Configuration group allpages allpages, datapages, datarows Dynamic Comprehensive System Administrator Lock Manager
lock scheme sets the default locking scheme to be used by create table and select into commands when a lock scheme is not specified in the command.
The values for lock scheme are character data, so you must use 0 as a placeholder for the second parameter, which must be numeric, and specify allpages, datapages, or datarows as the third parameter:
sp_configure "lock scheme", 0, datapages
lock shared memory

Summary information Default value Valid values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Static Comprehensive System Administrator Physical Memory
lock shared memory disallows swapping of Adaptive Server pages to disk and allows the operating system kernel to avoid the servers internal page locking code. This can reduce disk reads, which are expensive.
139
Not all platforms support shared memory locking. Even if your platform does, lock shared memory may fail due to incorrectly set permissions, insufficient physical memory, or for other reasons. See the configuration documentation for your platform for information on shared memory locking.
lock spinlock ratio

Summary information Default value Range of values Status Display level Required role Configuration groups 85 12147483647 Static Comprehensive System Administrator Lock Manager, Memory Use
Adaptive Server manages the acquiring and releasing of locks using an internal hash table with a configurable number of hash buckets. On SMP systems, this hash table can use one or more spinlocks to serialize access between processes running on different engines. To set the number of hash buckets, use lock hashtable size. For Adaptive Servers running with multiple engines, lock spinlock ratio sets a ratio that determines the number of lock hash buckets that are protected by one spinlock. If you increase lock hashtable size, the number of spinlocks increases, so the number of hash buckets protected by one spinlock remains the same. The Adaptive Server default value for lock spinlock ratio is 85. With lock hashtable size set to the default value of 2048, the default spinlock ratio defines 26 spinlocks for the lock hash table. For more information about configuring spinlock ratios, see Configuring spinlock ratio parameters on page 132.
sp_sysmon reports on the average length of the hash chains in the lock hash
table. See the Performance and Tuning Guide for more information.
lock table spinlock ratio

Summary information Default value Range of values Status
20 12147483647 Static
140
CHAPTER 5
Summary information Display level Required role Configuration group Comprehensive System Administrator Lock Manager
For Adaptive Servers running with multiple engines, the table lock spinlock ratio configuration parameter sets the number of rows in the internal table locks hash table that are protected by one spinlock. Adaptive Server manages the acquiring and releasing of table locks using an internal hash table with 101 rows (known as hash buckets). This table can use one or more spinlocks to serialize access between processes running on different engines. The Adaptive Server default value for table lock spinlock ratio is 20, which defines 6 spinlocks for the table locks hash table. The first 5 spinlocks protect 20 rows each; the sixth spinlock protects the last row. If you specify a value of 101 or greater for table lock spinlock ratio, Adaptive Server uses only 1 spinlock for the entire table.
lock wait period

2147483647 02147483647 Dynamic Comprehensive System Administrator Lock Manager
lock wait period limits the number of seconds that tasks wait to acquire a lock on a table, data page, or data row. If the task does not acquire the lock within the specified time period, Adaptive Server returns error message 12205 to the user and rolls back the transaction.
The lock wait option of the set command sets a session-level number of seconds that a task waits for a lock. It overrides the server-level setting for the session.
lock wait period, used with the session-level setting set lock wait nnn, is applicable only to user-defined tables. These settings have no influence on system tables.
141
At the default value, all processes wait indefinitely for locks. To restore the default value, reset the value to 2147483647 or enter:
sp_configure "lock wait period", 0, "default"
log audit logon failure

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Error Log
The log audit logon failure parameter specifies whether to log unsuccessful Adaptive Server logins to the Adaptive Server error log and, on Windows servers, to the Windows Event Log, if event logging is enabled. A value of 1 requests logging of unsuccessful logins; a value of 0 specifies no logging.
log audit logon success

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Error Log
The log audit logon success parameter specifies whether to log successful Adaptive Server logins to the Adaptive Server error log and, on Windows servers, to the Windows Event Log, if event logging is enabled. A value of 1 requests logging of successful logins; a value of 0 specifies no logging.
142
CHAPTER 5
max async i/os per engine

Summary information Default value Range of values Status Display level Required role Configuration group 2147483647 12147483647 Static Comprehensive System Administrator O/S Resources
max async i/os per engine specifies the maximum number of outstanding asynchronous disk I/O requests for a single engine at one time. See max async i/os per server on page 143 for more information.
max async i/os per server

Summary information Default value Range of values Status Display level Required role Configuration group 2147483647 12147483647 Static Comprehensive System Administrator O/S Resources
The max async i/os per server parameter specifies the maximum number of asynchronous disk I/O requests that can be outstanding for Adaptive Server at one time. This limit is not affected by the number of online engines per Adaptive Server; max async i/os per server limits the total number of asynchronous I/Os a server can issue at one time, regardless of how many online engines it has. max async i/os per engine limits the number of outstanding I/Os per engine. Most operating systems limit the number of asynchronous disk I/Os that can be processed at any one time; some operating systems limit the number per operating system process, some limit the number per system, and some do both. If an application exceeds these limits, the operating system returns an error message. Because operating system calls are relatively expensive, it is inefficient for Adaptive Server to attempt to perform asynchronous I/Os that get rejected by the operating system.
143
To avoid this, Adaptive Server maintains a count of the outstanding asynchronous I/Os per engine and per server; if an engine issues an asynchronous I/O that would exceed either max async i/os per engine or max async i/os per server, Adaptive Server delays the I/O until enough outstanding I/Os have completed to fall below the exceeded limit. For example, assume an operating system limit of 200 asynchronous I/Os per system and 75 per process and an Adaptive Server with three online engines. The engines currently have a total of 200 asynchronous I/Os pending, distributed according to the following table:
Engine 0 1 2 Number of I/Os pending 60 75 65 Outcome Engine 0 delays any further asynchronous I/Os until the total for the server is under the operating system per-system limit and then continues issuing asynchronous I/Os. Engine 1 delays any further asynchronous I/Os until the per-engine total is under the operating system per-process limit and then continues issuing asynchronous I/Os. Engine 2 delays any further asynchronous I/Os until the total for server is under the operating system per-system limit and then continues issuing asynchronous I/Os.
All I/Os (both asynchronous and synchronous) require a disk I/O structure, so the total number of outstanding disk I/Os is limited by the value of disk i/o structures. It is slightly more efficient for Adaptive Server to delay the I/O because it cannot get a disk I/O structure than because the I/O request exceeds max i/os per server. Set max async i/os per server equal to the value of disk i/o structures. See disk i/o structures on page 106. If the limits for asynchronous I/O can be tuned on your operating system, make sure they are set high enough for Adaptive Server. There is no penalty for setting them as high as needed. Use sp_sysmon to see if the per server or per engine limits are delaying I/O on your system. If sp_sysmon shows that Adaptive Server exceeded the limit for outstanding requests per engine or per server, raise the value of the corresponding parameter. See the Performance and Tuning Guide for more information.
max cis remote connections

0 02147483647 Dynamic
144
CHAPTER 5
Summary information Display level Required role Configuration group Basic System Administrator Component Integration Services
The max cis remote connections parameter specifies the maximum number of concurrent Client-Library connections that can be made to remote servers by Component Integration Services. By default, Component Integration Services allows up to four connections per user to be made simultaneously to remote servers. If you set the maximum number of users to 25, as many as 100 simultaneous Client-Library connections are allowed by Component Integration Services. If this number does not meet the needs of your installation, you can override the setting by specifying exactly how many outgoing Client-Library connections you want the server to be able to make at one time.
max concurrently recovered db

0 1 number of engines at startup minus 1 Dynamic Comprehensive System Administrator Backup/Recovery
max concurrently recovered db determines the degree of parallelism. The minimum value is 1, but you can also use the default value of 0, directing Adaptive Server to use a self-tuning apparoach. The maximum value is the number of engines at startup minus 1. max concurrently recovered db is also limited by the value of the configuration parameter number of open databases.
The default value is 0, which indicates automatic self-tuning by the server to determine the appropriate number of recovery tasks. A value of 1 indicates serial recovery.
145
max memory
Summary information Default value Range of values Status Display level Required role Configuration groups Platform-dependent Platform-dependent minimum 2147483647 Dynamic Basic System Administrator Memory Use, Physical Memory
Specifies the maximum amount of total physical memory that you can configure Adaptive Server to allocate. max memory must be greater than the total logical memory consumed by the current configuration of Adaptive Server. There is no performance penalty for configuring Adaptive Server to use the maximum memory available to it on your computer. However, assess the other memory needs on your system, or Adaptive Server may not be able to acquire enough memory to start. See Chapter 3, Configuring Memory, for instructions on how to maximize the amount of max memory for Adaptive Server.
If Adaptive Server cannot start
When allocate max shared memory is set to 1, Adaptive Server must have the amount of memory available that is specified by max memory. If the memory is not available, Adaptive Server does not start. If this occurs, reduce the memory requirements for Adaptive Server by manually changing the value of max memory in the servers configuration file. You can also change the value of allocate max shared memory to 0 so that not all memory required by max memory is required at start-up. You may also want to reduce the values for other configuration parameters that require large amounts of memory. Then restart Adaptive Server to use the memory specified by the new values. If Adaptive Server fails to start because the total of other configuration parameter values is higher than the max memory value, see Chapter 3, Configuring Memory, for information about configuration parameters that use memory.
146
CHAPTER 5
max native threads per engine

Summary information Default value Maximum values Status Display level Required role Configuration group 50 1000 Dynamic Intermediate System Administrator O/S Resources
Use to define the maximum number of native threads the server spawns per engine. When the limit for the native threads is reached, Adaptive Server sessions that require a native thread, sleep until another session releases a native thread.
max network packet size

Summary information Default value Range of values Status Display level Required role Configuration group 512 51265024 Static Intermediate System Administrator Network Communication
max network packet size specifies the maximum network packet size that can
be requested by clients communicating with Adaptive Server. If some of your applications send or receive large amounts of data across the network, these applications can achieve significant performance improvement by using larger packet sizes. Two examples are large bulk copy operations and applications that read or write large text, unitext, and image values. Generally, you want: The value of default network packet size to be small for users who perform short queries
max network packet size to be large enough to allow users who send or
receive large volumes of data to request larger packet sizes
147
max network packet size must always be as large as, or larger than, the default network packet size. Values that are not even multiples of 512 are rounded
down. For client applications that explicitly request a larger network packet size to receive it, you must also configure additional network memory. See additional network memory on page 81 for more information. Open Client Server cannot accept a network packet size greater than 64K. See bcp and isql in the Utility Guide for information on using larger packet sizes from these programs. Open Client Client-Library documentation includes information on using variable packet sizes.
Choosing packet sizes
For best performance, choose a server packet size that works efficiently with the underlying packet size on your network. The goals are: Reducing the number of server reads and writes to the network Reducing unused space in network packets (increasing network throughput)
For example, if your network packet size carries 1500 bytes of data, setting Adaptive Servers packet size to 1024 (512*2) will probably achieve better performance than setting it to 1536 (512*3). Figure 5-3 shows how four different packet size configurations would perform in such a scenario.
148
CHAPTER 5
Figure 5-3: Factors in determining packet size
Underlying network packets: 1500 bytes after overhead Packet size 512 Used 1024 bytes Unused 476 bytes % Used: 68% 2 server reads Packet size 1024 Used 1024 bytes Unused 476 bytes % Used: 68% 1 server read Packet size 2560 Used 2560 bytes Unused 440 bytes % Used 85% 2 server reads Possibly the best option of illustrated choices Packet size 1536 Used 1536 bytes Unused 1464 bytes % Used 51% 2 server reads Probably the worst option of illustrated choices Key: Overhead Data Unused
Depending on amount of data, network packets may have 1 or 2 packets
Should yield improved performance over default of 512
After you determine the available data space of the underlying packets on your network, perform your own benchmark tests to determine the optimum size for your configuration. Use sp_sysmon to see how changing max network packet size affects network I/O management and task switching. For example, try increasing max network packet size and then checking sp_sysmon output to see how this affects bcp for large batches. See the Performance and Tuning Guide for more information.
149
max number network listeners

Summary information Default value Range of values Status Display level Required role Configuration groups 5 02147483647 Static Comprehensive System Administrator Memory Use, Network Communication
max number network listeners specifies the maximum number of network listeners allowed by Adaptive Server at one time.
Each master port has one network listener. Generally, there is no need to have multiple master ports, unless your Adaptive Server must communicate over more than one network type. Some platforms support both socket and TLI (Transport Layer Interface) network interfaces. See the configuration documentation for your platform for information on supported network types.
max online engines

Summary information Default value Range of values Status Display level Required role Configuration groups 1 1128 Static Intermediate System Administrator Memory Use, Processors
The role of max online engines is to set a high value of engines to be taken online at any one time in an SMP environment. It does not take the number of CPUs available at start-up into account, and allows users to add CPUs at a later date.
max engines online specifies the maximum number of Adaptive Server engines that can be online at any one time in an SMP environment. See Chapter 5, Managing Multiprocessor Servers, for a detailed discussion of how to set this parameter for your SMP environment.
150
CHAPTER 5
At start-up, Adaptive Server starts with a single engine and completes its initialization, including recovery of all databases. Its final task is to allocate additional server engines. Each engine accesses common data structures in shared memory. When tuning the max engines online parameter: Never have more online engines than there are CPUs. Depending on overall system load (including applications other than Adaptive Server), you may achieve optimal throughput by leaving some CPUs free to run non-Adaptive Server processes. You can achieve better throughput by running fewer engines with high CPU use, rather than by running more engines with low CPU use. Scalability is application-dependent. Conduct extensive benchmarks on your application to determine the best configuration of online engines. You can use sp_engine to take engines offline or to bring them online. You can take all engines offline except engine zero.
See Chapter 4, Using Engines and CPUs in the Performance and Tuning Guide: Basics for more information on performance and engine tuning.
max parallel degree

1 1255 Dynamic Basic System Administrator Query Tuning
max parallel degree specifies the server-wide maximum number of worker
processes allowed per query. This is called the maximum degree of parallelism. If this number is too low, the performance gain for a given query may not be as significant as it could be; if the number is too high, the server may compile plans that require more processes than are actually available at execution time, or the system may become saturated, resulting in decreased throughput. To enable parallel partition scans, set this parameter to be equal to or greater than the number of partitions in the table you are querying.
151
The value of this parameter must be less than or equal to the current value of number of worker processes. If you set max parallel degree to 1, Adaptive Server scans all tables or indexes serially. Changing max parallel degree causes all query plans in the procedure cache to be invalidated, and new plans are compiled the next time you execute a stored procedure or trigger. For more information on parallel sorting, see Chapter 9, Parallel Sorting in the Performance and Tuning Guide: Optimizer and Abstract Plans.
max repartition degree

1 1 value of max parallel degree Dynamic Comprehensive System Administrator Query Tuning
max repartition degree configures the amount of dynamic repartitioning Adaptive Server requires, which enables Adaptive Server to use horizontal parallelism. However, if the number of partitions is too large, the system is flooded with worker processes that compete for resources, which degrades performance. The value for max repartition degree enforces the maximum number of partitions created for these resources. If all of the tables and indices are unpartitioned, Adaptive Server uses the value for max repartition degree to provide the number of partitions to create as a result of re-partitioning the data.
max resource granularity

10 1 100 Dynamic Comprehensive System Administrator Query Tuning
152
CHAPTER 5
max resource granularity indicates the maximum percentage of the systems resources a query can use. It is set to 10 percent by default. However, this parameter is not enforced at execution time but is only a guide for the query optimizer, and does not prevent the query processor from running queries in parallel. The query engine can avoid some memory intensive strategies by using max resource granularity as a guide.
max scan parallel degree

Summary information Default value Range of values Status Display level Required role Configuration group 1 1255 Dynamic Basic System Administrator Query Tuning
max scan parallel degree specifies the server-wide maximum degree of parallelism for hash-based scans. Hash-based scans may be used for the following access methods:
Parallel index scans for partitioned and nonpartitioned tables Parallel table scans for nonpartitioned tables
max scan parallel degree applies per table or index; that is, if max scan parallel degree is 3, and one table in a join query is scanned using a hash-based table
scan and the second can best be accessed by a hash-based index scan, the query can use 9 worker processes (as long as max scan parallel degree is set to 9 or higher.) The optimizer uses this parameter as a guideline when it selects the number of processes to use for parallel, nonpartition-based scan operations. It does not apply to parallel sort. Because there is no partitioning to spread the data across devices, parallel processes can be accessing the same device during the scan. This can cause additional disk contention and head movement, which can degrade performance. To prevent multiple disk accesses from becoming a problem, use this parameter to reduce the maximum number of processes that can access the table in parallel.
153
If this number is too low, the performance gain for a given query is not as significant as it could be; if the number is too large, the server may compile plans that use enough processes to make disk access less efficient. A general rule of thumb is to set this parameter to no more than 2 or 3, because it takes only 2 to 3 worker processes to fully utilize the I/O of a given physical device. Set the value of this parameter to less than or equal to the current value of max parallel degree. Adaptive Server returns an error if you specify a number larger than the max parallel degree value. If you set max scan parallel degree to 1, Adaptive Server does not perform hashbased scans. Changing max scan parallel degree causes all query plans in the procedure cache to be invalidated, and new plans are compiled the next time you execute a stored procedure or trigger.
max SQL text monitored

0 02147483647 Static Comprehensive System Administrator Memory Use, Monitoring
max SQL text monitored specifies the amount of memory allocated per user
connection for saving SQL text to memory shared by Adaptive Server Monitor. Initially, the amount of memory allocated for saving text is 0, and since this parameter is static, you must restart Adaptive Server before you can start saving SQL text. If you do not allocate enough memory for the batch statements, the text you want to view may be in the section of the batch that is truncated. Sybase recommends an initial value of 1024 bytes of memory per user connection. The total memory allocated from shared memory for the SQL text is the product of max SQL text monitored multiplied by the currently configured number of user connections. For more information on max SQL text monitored, see Configuring Adaptive Server to save SQL batch text on page 346.
154
CHAPTER 5
maximum dump conditions

Summary information Default value Range of values Status Display level Required role Configuration group 10 10100 Static Intermediate System Administrator Group Diagnostics
The maximum dump conditions parameter sets the maximum number of conditions you can specify under which Adaptive Server generates a dump of data in shared memory.
Note This parameter is included for use only by Sybase Technical Support. Do
not modify it unless you are instructed to do so by Sybase Technical Support.
maximum failed logins

Summary information Default value Range of values Status Display level Required role Configuration group 0 0 32767 Dynamic 10 System Security Officer Security Related
maximum failed logins allows you to set the server-wide maximum number of failed login attempts for logins and roles. For example, to set the system-wide maximum failed logins to 5, enter:
sp_configure "maximum failed logins", 5
Use create role to set maximum failed logins for a specific role or creation. To create the intern_role role with the password temp244, and set maximum failed logins for intern_role to 20, enter:
create role intern_role with passwd "temp244", maximum failed logins 20
155
Use sp_modifylogin to set or change maximum failed logins for an existing login. To change maximum failed logins for the login joe to 40, enter:
sp_modifylogin "joe", @option="maximum failed logins", @value="40" Note The value parameter is a character datatype; therefore, quotes are
required for numeric values. To change the overrides for maximum failed logins for all logins to 3, enter:
sp_modifylogin "all overrides", "maximum failed logins", "3"
To remove the overrides for maximum failed logins option for all logins, enter:
sp_modifylogin "all overrides", @option="maximum failed logins", @value="-1"
Use alter role to set or change the maximum failed logins for an existing role. For example, to change the maximum failed logins allowed for physician_role to 5, enter:
alter role physician_role set maximum failed logins 5
To remove the overrides for maximum failed logins for all roles, enter:
alter role "all overrides" set maximum failed logins -1
maximum job output

32768 02147483647 Dynamic Comprehensive System Administrator SQL Server Administration
Sets limit, in bytes, on the maximum output a single job can produce. If a job produces more output than specified in this parameter, all the data returned above this vale is discarded.
156
CHAPTER 5
memory alignment boundary

Summary information Default value Range of values Status Display level Required role Configuration group Logical page size 2048a 16384
a. Minimum determined by servers logical page size
Static Comprehensive System Administrator Cache Manager
The memory alignment boundary parameter determines the memory address boundary on which data caches are aligned. Some machines perform I/O more efficiently when structures are aligned on a particular memory address boundary. To preserve this alignment, values for memory alignment boundary should always be powers of two between the logical page size and 2048K.
Note The memory alignment boundary parameter is included for support of
certain hardware platforms. Do not modify it unless you are instructed to do so by Sybase Technical Support.
memory per worker process

1024 10242147483647 Dynamic Basic System Administrator Memory Use
157
memory per worker process specifies the amount of memory (in bytes) used by
worker processes. Each worker process requires memory for messaging during query processing. This memory is allocated from a shared memory pool; the size of this pool is memory per worker process multiplied by number of worker processes. For most query processing, the default size is more than adequate. If you use dbcc checkstorage, and have set number of worker processes to 1, you may need to increase memory per worker process to 1792 bytes. See Chapter 9, Parallel Sorting of the Performance and Tuning Guide: Optimizer and Abstract Plans for information on setting this parameter. For more information on Adaptive Servers memory allocation, see Chapter 3, Configuring Memory.
messaging memory
400 60 2147483647 Dynamic Intermediate System Administrator Memory Use, Physical Memory
Configures the memory for messaging.
minimum password length

6 0 30 Dynamic 10 System Security Officer Security Related
158
CHAPTER 5
minimum password length allows you to customize the length of server-wide
password values or per-login or per-role password values to fit your personal needs. The per-login or per-role minimum password length value overrides the server-wide value. Setting minimum password length affects only the passwords you create after you have set the value; existing password lengths are not changed. Use minimum password length to specify a server-wide value for minimum password length for both logins and roles. For example, to set the minimum password length for all logins and roles to 4 characters, enter:
sp_configure "minimum password length", 4
To set minimum password length for a specific login at creation, use sp_addlogin. For example, to create the new login joe with the password Djdiek3, and set minimum password length for joe to 4, enter:
sp_addlogin joe, "Djdiek3", minimum password length=4
To set minimum password length for a specific role at creation, use create role. To create the new role intern_role with the password temp244 and set the minimum password length for intern_role to 0, enter:
create role intern_role with passwd "temp244", minimum password length 0
The original password is seven characters, but the password can be changed to one of any length because the minimum password length is set to 0. Use sp_modifylogin to set or change minimum password length for an existing login. sp_modifylogin only effects user roles, not system roles. For example, to change minimum password length for the login joe to 8 characters, enter:
sp_modifylogin "joe", @option="minimum password length", @value="8" Note The value parameter is a character datatype; therefore, quotes are
required for numeric values. To change the value of the overrides for minimum password length for all logins to 2 characters, enter:
sp_modifylogin "all overrides", "minimum password length", @value="2"
To remove the overrides for minimum password length for all logins, enter:
sp_modifylogin "all overrides", @option="minimum password length", @value="-1"
159
Use alter role to set or change the minimum password length for an existing role. For example, to set the minimum password length for physician_role, an existing role, to 5 characters, enter:
alter role physician_role set minimum password length 5
To override the minimum password length for all roles, enter:

alter role "all overrides" set minimum password length -1
msg confidentiality reqd

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Intermediate System Security Officer Security Related
The msg confidentiality reqd parameter requires that all messages into and out of Adaptive Server be encrypted. The use security services parameter must be 1 for messages to be encrypted.
msg integrity reqd

0 (off) 0 (off), 1 (on) Dynamic Intermediate System Security Officer Security Related
msg integrity reqd requires that all messages be checked for data integrity. use security services must be 1 for message integrity checks to occur. If msg integrity reqd is set to 1, Adaptive Server allows the client connection to
succeed unless the client is using one of the following security services:
message integrity, replay detection, origin checks, or out-of-seq checks.
160
CHAPTER 5
number of alarms
Summary information Default value Range of values Status Display level Required role Configuration groups 40 402147483647 Dynamic Comprehensive System Administrator Memory Use, SQL Server Administration
number of alarms specifies the number of alarm structures allocated by
Adaptive Server. The Transact-SQL command waitfor defines a specific time, time interval, or event for the execution of a statement block, stored procedure, or transaction. Adaptive Server uses alarms to execute waitfor commands correctly. Other internal processes require alarms. When Adaptive Server needs more alarms than are currently allocated, this message is written to the error log:
uasetalarm: no more alarms available
The number of bytes of memory required for each is small. If you raise the number of alarms value significantly, you should adjust max memory accordingly.
number of aux scan descriptors

number of aux scan descriptors sets the number of auxiliary scan descriptors
available in a pool shared by all users on a server.
161
Each user connection and each worker process has 48 scan descriptors exclusively allocated to it. Of these, 16 are reserved for user tables, 12 are reserved for worktables, and 20 are reserved for system tables (with 4 of these set aside for rollback conditions). A descriptor is needed for each table referenced, directly or indirectly, by a query. For user tables, a table reference includes the following: All tables referenced in the from clause of the query All tables referenced in a view named in the query (the view itself is not counted) All tables referenced in a subquery All tables that need to be checked for referential integrity (these are used only for inserts, updates, and deletes) A table created with select...into All worktables created for the query
If a table is referenced more than once (for example, in a self-join, in more than one view, or in more than one subquery) the table is counted each time. If the query includes a union, each select statement in the union query is a separate scan. If a query runs in parallel, the coordinating process and each worker process needs a scan descriptor for each table reference. When the number of user tables referenced by a query scan exceeds 16, or the number of worktables exceeds 12, scan descriptors from the shared pool are allocated. Data-only-locked tables also require a system table descriptor for each data-only-locked table accessed via a table scan (but not those accessed via an index scan). If more than 16 data-only-locked tables are scanned using table scans in a query, auxiliary scan descriptors are allocated for them. If a scan needs auxiliary scan descriptors after it has used its allotted number, and there are no descriptors available in the shared pool, Adaptive Server displays an error message and rolls back the user transaction. If none of your queries need additional scan descriptors, you may still want to leave number of aux scan descriptors set to the default value in case your system requirements grow. Set it to 0 only if you are sure that users on your system will not run queries on more than 16 tables and that your tables have few or no referential integrity constraints. See Monitoring scan descriptor usage on page 163 for more information. If your queries need more scan descriptors, use one of the following methods to remedy the problem:
162
CHAPTER 5
Rewrite the query, or break it into steps using temporary tables. For dataonly-locked tables, consider adding indexes if there are many table scans. Redesign the tables schema so that it uses fewer scan descriptors, if it uses a large number of referential integrity constraints. You can find how many scan descriptors a query would use by enabling set showplan, noexec on before running the query. Increase the number of aux scan descriptors setting.
The following sections describe how to monitor the current and high-watermark usage with sp_monitorconfig to avoid running out of descriptors and how to estimate the number of scan descriptors you need.
Monitoring scan descriptor usage
sp_monitorconfig reports the number of unused (free) scan descriptors, the number of auxiliary scan descriptors currently being used, the percentage that is active, and the maximum number of scan descriptors used since the server was last started. Run it periodically, at peak periods, to monitor scan descriptor use.
This example output shows scan descriptor use with 500 descriptors configured:
sp_monitorconfig "aux scan descriptors" Usage information at date and time: Apr 22 2002 2:49PM. Name num_free num_active pct_act Max_Used Reused --------------------- --------- --------------- -----number of aux 260 240 48.00 427 NA
Only 240 auxiliary scan descriptors are being used, leaving 260 free. However, the maximum number of scan descriptors used at any one time since the last time Adaptive Server was started is 427, leaving about 20 percent for growth in use and exceptionally heavy use periods. Re-used does not apply to scan descriptors.
Estimating and configuring auxiliary scan descriptors
To get an estimate of scan descriptor use:
163
Determine the number of table references for any query referencing more than 16 user tables or those that have a large number of referential constraints, by running the query with set showplan and set noexec enabled. If auxiliary scan descriptors are required, showplan reports the number needed:
Auxiliary scan descriptors required: 17
The reported number includes all auxiliary scan descriptors required for the query, including those for all worker processes. If your queries involve only referential constraints, you can also use sp_helpconstraint, which displays a count of the number of referential constraints per table. 2 For each query that uses auxiliary scan descriptors, estimate the number of users who would run the query simultaneously and multiply. If 10 users are expected to run a query that requires 8 auxiliary descriptors, a total of 80 will be needed at any one time. Add the per-query results to calculate the number of needed auxiliary scan descriptors.
number of checkpoint tasks

Summary information Default value Valid values Status Display level Required role Configuration group 1 1 8 Dynamic Comprehensive System Administrator Backup/Recovery
number of checkpoint tasks configures parallel checkpoints. The value of number of checkpoint tasks must be less than or equal to the value of number of engines at startup. The maximum value is limited by the value of the configuration parameters number of engines online at startup and number of open databases, with an absolute ceiling of 8.
The default value is 1, which implies serial checkpoints is the default behavior.
164
CHAPTER 5
number of devices
Summary information Default value Range of values Status Display level Required role Configuration groups 10 12,147,483,647 Dynamic Basic System Administrator Disk I/O, Memory Use
The number of devices parameter controls the number of database devices Adaptive Server can use. It does not include devices used for database or transaction log dumps. When you execute disk init, you can also assign the virtual device number (the vdevno). although this value is optional. If you do not assign the vdevno, Adaptive Server assigns the next available virtual device number. If you do assign the virtual device number, each device number must be unique among the device numbers used by Adaptive Server. The number 0 is reserved for the master device. Otherwise, valid numbers are 12,147,483,647. You can enter any unused device number. To determine which numbers are currently in use, enter:
select vdevno from master..sysdevices where status & 2 = 2
Here, status 2 specifies physical disk.

Note On UNIX platforms: If you are using a large number of devices, Sybase recommends that you set the appropriate number of devices and user connections in the configuration file and then restart Adaptive Server. Attempting to configure a large number of devices dynamically using sp_configure may fail.
number of dtx participants

Summary information Default value Valid values Status
500 100 2147483647 Dynamic
165
Summary information Display level Required role Configuration groups 10 System Administrator DTM Administration, Memory Use
number of dtx participants sets the total number of remote transactions that the
Adaptive Server transaction coordination service can propagate and coordinate at one time. A DTX participant is an internal memory structure that the coordination service uses to manage a remote transaction branch. As transactions are propagated to remote servers, the coordination service must obtain new DTX participants to manage those branches. By default, Adaptive Server can coordinate 500 remote transactions. Setting number of dtx participants to a smaller number reduces the number of remote transactions that the server can manage. If no DTX participants are available, new distributed transactions cannot start. In-progress distributed transactions may abort if no DTX participants are available to propagate a new remote transaction. Setting number of dtx participants to a larger number increases the number of remote transaction branches that Adaptive Server can handle, but also consumes more memory.
Optimizing the number of dtx participants for your system
During a peak period, use sp_monitorconfig to examine the use of DTX participants:
sp_monitorconfig "number of dtx participants" Usage information at date and time: Apr 22 2002 Name num_free num_active pct_act --------------------- ---------- --------number of dtx 80 20 4.00 2:49PM. Max_Used -------210 Reused -----NA
If the num_free value is zero or very low, new distributed transactions may be unable to start due to a lack of DTX participants. Consider increasing the number of dtx participants value. If the Max_used value is too low, unused DTX participants may be consuming memory that could be used by other server functions. Consider reducing the value of number of dtx participants.
166
CHAPTER 5
number of dump threads

Summary information Default value Range of values Status Display level Required role Configuration group Disabled 1 (disabled, no parallelism) 8 (fully parallel) Dynamic Intermediate System Administrator Group Diagnostics
number of dump threads controls the number of threads that Adaptive Server spawns to perform a memory dump. Using the appropriate value for number of dump threads can reduce the amount of time the engines are halted during the memory dump.
Consider the following when you are determining the number of threads for memory: Use a value of 8 if the machine has enough free memory for the file system cache to hold the entire memory dump. If you do not know whether the machine has enough free memory, the value for number of dump threads depends on many factors, including the speed of the I/O system, the speed of the disks, the controllers cache, whether the dump file lives in a logical volume manager created on several disks, and so on. Use a value of 1 (no parallel processing) if you do not halt the engines when performing memory dumps, described below. When Adaptive Server performs a memory dump, the number of files it creates is the sum of the number of memory segments that it has allocated multiplied by the number of threads configured. Adaptive Server uses separate threads to write on separate files. When this job completes, the engines are restarted, and the files are merged into the target dump file. Because of this, the time to dump the shared memory in parallel is greater than doing it serially. If you halt the engines during the memory dump, a value other than 1 may reduce the amount of time the engines spend stopped while dumping the memory.
167
number of engines at startup

Summary information Default value Range of values Status Display level Required role Configuration groups 1 1 number of CPUs on machine Static Basic System Administrator Java Services, Memory Use, Processors
Adaptive Server allows users to take all engines offline, except engine zero.
number of engines at startup is used exclusively during start-up to set the number of engines brought online. It is designed to allow users the greatest flexibility in the number of engines brought online, subject to the restriction that you cannot set the value of number of engines at startup to a value greater than the number of CPUs on your machine, or to a value greater than the configuration of max online engines. Users who do not intend to bring engines online after start-up should set max online engines and number of engines at startup to the same value. A difference between number of engines at startup and max online engines wastes approximately 1.8 MB of memory per engine.
number of histogram steps

Summary information Default value Range of values Status Display level Required role Configuration group 20 3 2147483647 Dynamic Comprehensive System Administrator Query Tuning
number of histogram steps specifies the number of steps in a histogram.
number of index trips

0 065535
168
CHAPTER 5
Summary information Status Display level Required role Configuration group Dynamic Comprehensive System Administrator Cache Manager
The number of index trips parameter specifies the number of times an aged index page traverses the most recently used/least recently used (MRU/LRU) chain before it is considered for swapping out. As you increase the value of number of index trips, index pages stay in cache for longer periods of time. A data cache is implemented as an MRU/LRU chain. As the user threads access data and index pages, these pages are placed on the MRU end of the caches MRU/LRU chain. In some high transaction environments (and in some benchmarks), it is desirable to keep index pages in cache, since they will probably be needed again soon. Setting number of index trips higher keeps index pages in cache longer; setting it lower allows index pages to be swapped out of cache sooner. You do need not set the number of index pages parameter for relaxed LRU pages. For more information, see Chapter 4, Configuring Data Caches.
Note If the cache used by an index is relatively small (especially if it shares
space with other objects) and you have a high transaction volume, do not set
number of index trips too high. The cache can flood with pages that do not age
out, and this may lead to the timing out of processes that are waiting for cache space.
number of java sockets

0 0 32767) Dynamic Comprehensive System Administrator Java Services, Memory Use
169
The new number of java sockets parameter is necessary to enable the Java VM and the java.net classes Sybase supports. To open 10 sockets, for example, enter:
sp_configure "number of java sockets", 10
number of large i/o buffers

Summary information Default value Valid values Status Display level Required role Configuration groups 6 1256 Dynamic Comprehensive System Administrator Disk I/O, Memory Use, SQL Server Administration
The number of large i/o buffers parameter sets the number of allocation unitsized buffers reserved for performing large I/O for certain Adaptive Server utilities. These large I/O buffers are used primarily by the load database command, which uses one buffer to load the database, regardless of the number of stripes it specifies. load database then uses up to 32 buffers to clear the pages for the database it is loading. These buffers are not used by load transaction. To perform more than six load database commands concurrently, configure one large I/O buffer for each load database command.
create database and alter database use these buffers for large I/O while clearing database pages. Each instance of create database or load database can use up
to 32 large I/O buffers. These buffers are also used by disk mirroring and by some dbcc commands.
Note In Adaptive Server version 12.5.0.3 and later, the size of the large I/O
buffers is one allocation (256 pages), not one extent (8 pages). The server thus requires more memory allocation for large buffers. For example, a disk buffer that required memory for 8 pages in earlier versions now requires memory for 256 pages.
170
CHAPTER 5
number of locks
Summary information Default value Range of values Status Display level Required role Configuration groups 5000 10002147483647 Dynamic Basic System Administrator Lock Manager, Memory Use
The number of locks parameter sets the total number of available locks for all users on Adaptive Server. The total number of locks needed by Adaptive Server depends on the number and nature of the queries that are running. The number of locks required by a query can vary widely, depending on the number of concurrent and parallel processes and the types of actions performed by the transactions. To see how many locks are in use at a particular time, use sp_lock. For serial operation, we suggest that you can start with an arbitrary number of 20 locks for each active, concurrent connection. Parallel execution requires more locks than serial execution. For example, if you find that queries use an average of five worker processes, try increasing, by one-third, the number of locks configured for serial operation. If the system runs out of locks, Adaptive Server displays a server-level error message. If users report lock errors, it typically indicates that you need to increase number of locks; but remember that locks use memory. See Number of locks on page 68 for information.
Note Datarows locking may require that you change the value for number of locks. See the Performance and Tuning Guide for more information.
number of mailboxes
Summary information Default value Range of values Status Display level 30 302147483647 Dynamic Comprehensive
171
Summary information Required role Configuration groups System Administrator Memory Use, SQL Server Administration
number of mailboxes specifies the number of mailbox structures allocated by Adaptive Server. Mailboxes, which are used in conjunction with messages, are used internally by Adaptive Server for communication and synchronization between kernel service processes. Mailboxes are not used by user processes. Do not modify this parameter unless instructed to do so by Sybase Technical Support.
number of messages
number of messages specifies the number of message structures allocated by
Adaptive Server. Messages, which are used in conjunction with mailboxes, are used internally by Adaptive Server for communication and synchronization between kernel service processes. Messages are also used for coordination between a family of processes in parallel processing. Do not modify this parameter unless instructed to do so by Sybase Technical Support.
number of oam trips

Summary information Default value Range of values Status Display level Required role 0 065535 Dynamic Comprehensive System Administrator
172
CHAPTER 5
The number of oam trips parameter specifies the number of times an object allocation map (OAM) page traverses the MRU/LRU chain before it is considered for swapping out. The higher the value of number of oam trips, the longer aged OAM pages stay in cache. Each table, and each index on a table, has an OAM page, which holds information on pages allocated to the table or index and is checked when a new page is needed for the index or table. (See page utilization percent on page 192 for further information.) A single OAM page can hold allocation mapping for between 2,000 and 63,750 data or index pages. The OAM pages point to the allocation page for each allocation unit where the object uses space. The allocation pages, in turn, track the information about extent and page usage within the allocation unit. In some environments and benchmarks that involve significant allocations of space (that is, massive bulk copy operations), keeping OAM pages in cache longer improves performance. Setting number of oam trips higher keeps OAM pages in cache.
Note If the cache is relatively small and used by a large number of objects, do not set number of oam trips too high. This may result in the cache being flooded with OAM pages that do not age out, and user threads may begin to time out.
number of open databases

Summary information Default value Range of values Status Display level Required role Configuration groups 12 52147483647 Dynamic Basic System Administrator Memory Use, Meta-Data Caches, SQL Server Administration
number of open databases sets the maximum number of databases that can be
open simultaneously on Adaptive Server. When you calculate a value, include the system databases master, model, sybsystemprocs, and tempdb. If you have installed auditing, include the sybsecurity database. Also, count the sample databases pubs2 and pubs3, the syntax database sybsyntax, and the dbcc database dbccdb if they are installed.
173
If you are planning to make a substantial change, such as loading a large database from another server, you can calculate an estimated metadata cache size by using sp_helpconfig. sp_helpconfig displays the amount of memory required for a given number of metadata descriptors, as well as the number of descriptors that can be accommodated by a given amount of memory. A database metadata descriptor represents the state of the database while it is in use or cached between uses.
Optimizing the number of open databases parameter for your system
If Adaptive Server displays a message saying that you have exceeded the allowable number of open databases, adjust the value. To set the number of open databases parameter optimally: Step 1: Determine the total number of databases (database metadata descriptors). Step 2: Reset number of open databases to that number. Step 3: Find the number of active databases (active metadata descriptors) during a peak period. Step 4: Reset number of open databases to that number, plus 10 percent.
The following section details the basic steps listed above. 1 Use sp_countmetadata to find the total number of database metadata descriptors. For example:
sp_countmetadata "open databases"
The best time to run sp_countmetadata is when there is little activity on the server. Running sp_countmetadata during a peak time can cause contention with other processes. Suppose Adaptive Server reports the following information:
There are 50 databases, requiring 1719 Kbytes of memory. The 'open databases' configuration parameter is currently set to 500.
Configure number of open databases with the value of 50:

sp_configure "number of open databases", 50
This new configuration number is only a start; the ideal size should be based on the number of active metadata database cache descriptors, not the total number of databases. 3 During a peak period, find the number of active metadata descriptors. For example:
174
CHAPTER 5
sp_monitorconfig "open databases" Usage information Name -------------number of open at date and time: Apr 22 2002 2:49PM. num_free num_active pct_act Max_Used -----------------------------50 20 40.00 26 Reused -----No
At this peak period, 20 metadata database descriptors are active; the maximum number of descriptors that have been active since the server was last started is 26. Use sp_monitorconfig in the Reference Manual: Procedures for more information. 4 Configure number of open databases to 26, plus additional space for 10 percent more (about 3), for a total of 29:
sp_configure "number of open databases", 29
If there is a lot of activity on the server, for example, if databases are being added or dropped, run sp_monitorconfig periodically. You must reset the cache size as the number of active descriptors changes.
number of open indexes

Summary information Default value Range of values Status Display level Required role Configuration groups 500 1002147483647 Dynamic Basic System Administrator Memory Use, Meta-Data Caches
number of open indexes sets the maximum number of indexes that can be used simultaneously on Adaptive Server.
If you are planning to make a substantial change, such as loading databases with a large number of indexes from another server, you can calculate an estimated metadata cache size by using sp_helpconfig. sp_helpconfig displays the amount of memory required for a given number of metadata descriptors, as well as the number of descriptors that can be accommodated by a given amount of memory. An index metadata descriptor represents the state of an index while it is in use or cached between uses.
175
Optimizing the number of open indexes parameter for your system
The default run value is 500. If this number is insufficient, Adaptive Server displays a message after trying to reuse active index descriptors, and you must adjust this value. To configure the number of open indexes parameter optimally, perform the following steps: 1 Use sp_countmetadata to find the total number of index metadata descriptors. For example:
sp_countmetadata "open indexes"
The best time to run sp_countmetadata is when there is little activity in the server. Running sp_countmetadata during a peak time can cause contention with other processes. Suppose Adaptive Server reports the following information:
There are 698 user indexes in all database(s), requiring 286.289 Kbytes of memory. The 'open indexes' configuration parameter is currently set to 500.
Configure the number of open indexes parameter to 698 as follows:

sp_configure "number of open indexes", 698
This new configuration is only a start; the ideal size should be based on the number of active index metadata cache descriptors, not the total number of indexes. 3 During a peak period, find the number of active index metadata descriptors. For example:
sp_monitorconfig "open indexes" Usage information at date and time: Apr 22 2002 2:49PM. Name num_free num_active pct_act Max_Used ------------------------------------------number of open 182 516 73.92 590 Reused -----No
In this example, 590 is the maximum number of index descriptors that have been used since the server was last started. See sp_monitorconfig in the Reference Manual for more information. 4 Configure the number of open indexes configuration parameter to 590, plus additional space for 10 percent more (59), for a total of 649:
sp_configure "number of open indexes", 649
176
CHAPTER 5
If there is a lot of activity on the server, for example, if tables are being added or dropped, run sp_monitorconfig periodically. You must reset the cache size as the number of active descriptors changes.
number of open objects

Summary information Default value Range of values Status Display level Required role Configuration groups 500 1002147483647 Dynamic Basic System Administrator Memory Use, Meta-Data Caches, SQL Server Administration
number of open objects sets the maximum number of objects that can be open simultaneously on Adaptive Server.
If you are planning to make a substantial change, such as loading databases with a large number of objects from another server, you can calculate an estimated metadata cache size by using sp_helpconfig. sp_helpconfig displays the amount of memory required for a given number of metadata descriptors, as well as the number of descriptors that can be accommodated by a given amount of memory. An object metadata descriptor represents the state of an object while it is in use, or cached between uses.
Optimizing the number of open partitions parameter for your system
The default run value is 500. If this number is insufficient, Adaptive Server displays a message after trying to reuse active object descriptors. You must adjust this value. To set the number of open objects parameter optimally: 1 Use sp_countmetadata to find the total number of object metadata cache descriptors. For example:
sp_countmetadata "open objects"
There are 1042 user partitions in all database(s), requiring 1003 Kbytes of memory. The 'open
177
partitions' configuration parameter is currently set to 500.
Configure the number of open objects parameter to that value, as follows:

sp_configure "number of open partitions", 357
357 covers the 340 user objects, plus 5 percent to accommodate temporary tables. This new configuration is only a start; the ideal size should be based on the number of active object metadata cache descriptors, not the total number of objects. 3 During a peak period, find the number of active metadata cache descriptors, for example:
sp_monitorconfig "open partitions" Usage information at date and time: Apr 22 2002 2:49PM. Name num_free num_active pct_act Max_Used ------------------------------------------number of open 160 357 71.40 397 Reused -----No
In this example, 397 is the maximum number of object descriptors that have been used since the server was last started. 4 Configure the number of open objects to 397, plus 10 percent (40), for a total of 437:
sp_configure "number of open objects", 437
If there is a lot of activity on the server, for example, if tables are being added or dropped, run sp_monitorconfig periodically. You must reset the cache size as the number of active descriptors changes. See sp_monitorconfig in the Reference Manual for more information.
number of open partitions

500 100 2147483647 Dynamic Basic System Administrator Memory Use, Meta-Data Caches
178
CHAPTER 5
Specifies the number of partitions that Adaptive Server can access at one time. The default value is 500.
Optimizing the number of open objects parameter for your system
The default run value is 500. If this number is insufficient, Adaptive Server displays a message after trying to reuse active partition descriptors. You must adjust this value. To set the number of open partitions parameter optimally: 1 Use sp_countmetadata to find the total number of open partitions. For example:
sp_countmetadata "open partitions"
There are 42 user partitions in all database(s), requiring 109 Kbytes of memory. The 'open partitions' configuration parameter is currently set to 110.
Configure number of open partitions to that value, as follows:

During a peak period, find the number of active metadata cache descriptors, for example:
sp_monitorconfig "open partitions"
Usage information at date and time: Apr 22 2002 2:49PM. Name num_free num_active pct_act Max_Used ------------------------------------------number of open 160 357 71.40 397
Reused -----No
In this example, 397 is the maximum number of partition descriptors that have been used since the server was last started. 4 Configure the number of open partitions to 397, plus 10 percent (40), for a total of 437:
If there is a lot of activity on the server, for example, if tables are being added or dropped, run sp_monitorconfig periodically. You must reset the cache size as the number of active descriptors changes. See sp_monitorconfig in the Reference Manual for more information. 179
number of pre-allocated extents

number of pre-allocated extents specifies the number of extents (eight pages) allocated in a single trip to the page manager. Currently, this parameter is used only by bcp to improve performance when copying in large amounts of data. By default, bcp allocates two extents at a time and writes an allocation record to the log each time.
Setting number of pre-allocated extents means that bcp allocates the specified number of extents each time it requires more space, and writes a single log record for the event. An object may be allocated more pages than actually needed, so the value of number of pre-allocated extents should be low if you are using bcp for small batches. If you are using bcp for large batches, increase the value of number of pre-allocated extents to reduce the amount of overhead required to allocate pages and to reduce the number of log records.
number of remote connections

Summary information Default value Range of values Status Display level Required role Configuration groups 20 532767 Static Intermediate System Administrator Memory Use, Network Communication
number of remote connections specifies the number of logical connections that can be open to and from an Adaptive Server at one time. Each simultaneous connection to XP Server for ESP execution uses up to one remote connection each. For more information, see Chapter 15, Managing Remote Servers.
180
CHAPTER 5
number of remote logins

number of remote logins controls the number of active user connections from Adaptive Server to remote servers. Each simultaneous connection to XP Server for ESP execution uses up to one remote login each. Set this parameter to the same (or a lower) value as number of remote connections. For more information, see Chapter 15, Managing Remote Servers.
number of remote sites

number of remote sites determines the maximum number of remote sites that can access Adaptive Server simultaneously. Each Adaptive Server-to-XP Server connection uses one remote site connection.
Internally, number of remote sites determines the number of site handlers that can be active at any one time; all server accesses from a single site are managed with a single site handler. For more information, see Chapter 15, Managing Remote Servers.
number of sort buffers

500 032767
181
Summary information Status Display level Required role Configuration group Dynamic Comprehensive System Administrator SQL Server Administration
number of sort buffers specifies the number of 2K buffers used to hold pages read from input tables and perform index merges during sorts.
Sybase recommends that you leave this parameter set to the default except when you are creating indexes in parallel. Setting the value too high can rob non-sorting processes of access to the 2K buffer pool in caches being used to perform sorts. If you configure a high number of sort buffers, a sort on a large table may require more procedure cache. The effect is more pronounced with tables that have smaller row sizes, because the number of rows per page is higher. This equation estimates the amount of proc cache required: Number of sort buffers X rows per page X 100 If you do not configure enough procedure cache for the number of sort buffers, the sort may fail with error message 701. If this occurs, reconfigure Adaptive Server with a lower number of sort buffers and retry the sort. For more information on configuring this value for parallel create index statements, see Caches, sort buffers, and parallel sorts in the Performance and Tuning Guide: Optimizer and Abstract Plans.
number of user connections

Summary information Default value Range of values Status Display level Required role Configuration groups 25 52147483647 Dynamic Basic System Administrator Memory Use, User Environment
182
CHAPTER 5
number of user connections sets the maximum number of user connections that can be connected to Adaptive Server at the same time. It does not refer to the maximum number of processes; that number depends not only on the value of this parameter but also on other system activity.
Upper limit to the maximum number of user connections
The maximum allowable number of file descriptors per process is operatingsystem-dependent; see the configuration documentation for your platform. The number of file descriptors available for Adaptive Server connections is stored in the global variable @@max_connections. You can report the maximum number of file descriptors your system can use with:
select @@max_connections
The return value represents the maximum number of file descriptors allowed by the system for your processes, minus overhead. Overhead increases with the number of engines. For more information on how multiprocessing affects the number file descriptors available for Adaptive Server connections, see Managing user connections on page 130. In addition, you must reserve a number of connections for the following items, which you also set with configuration parameters: The database devices, including mirror devices Site handlers Network listeners
The following formula determines how high you can set number of user connections, number of devices, max online engines, number of remote sites, and max number network listeners: number of user connections + (number of devices * max online engines * 2) + number of remote sites + max number network listeners cannot be greater than the value of @@max_connections.
Reserved connections
One connection from the configured number of connections is reserved for temporary administrative tasks to make sure that database administrators can connect to Adaptive Server to increase the number of user connections and there are no free connections. A reserved connection is allocated only to a user who has the sa_role and has a total login time of 15 minutes. After this, Adaptive Server terminates the connection to ensure the availability of the reserved connection at an installation wth multiple database administrators. Adaptive Server uses this reserved connection automatically when a client uses the last resource for connecting to Adaptive Server.
183
If Adaptive Server is using a reserved connection, the following informational message is displayed when the user logs in to Adaptive Server:
There are not enough user connections available; you are being connected using a temporary administrative connection which will time out after '15' minutes. Increase the value of th 'number of user connections' parameter
Adaptive Server also prints a message similar to the following to the error log when the final connnection to Adaptive Server terminates due to a timeout:
00:00000:00008:2003/03/14 11:25:31.36 server Process '16' has been terminated as it exceeded the maximum login time allowed for such processes. This process used a connection reserved for system administrators and has a maximum login period of '15' minutes Optimizing the value of the max number of user connections parameter
There is no formula for determining how many connections to allow for each user. You must estimate this number, based on the system and user requirements described here. You must also take into account that on a system with many users, there is more likelihood that connections needed only occasionally or transiently can be shared among users. The following processes require user connections: One connection is needed for each user running isql. Application developers use one connection for each editing session. The number of connections required by users running an application depends on how the application has been programmed. Users executing Open Client programs need one connection for each open DB-Library dbprocess or Client-Library cs_connection.
Note Sybase suggests that you estimate the maximum number of connections used by Adaptive Server and update number of user connections as you add physical devices or users to the system. Use sp_who periodically to determine the number of active user connections on
your Adaptive Server. Certain other configuration parameters, including stack size and default network packet size, affect the amount of memory for each user connection.
User connections for shared memoryEJB Server
Adaptive Server uses the value of the number of user connections parameter to establish the number of shared-memory connections for EJB Server. Thus, if number of user connections is 30, Adaptive Server establishes 10 sharedmemory connections for EJB Server. Shared-memory connections are not a subset of user connections, and are not subtracted from the number of user connections.
184
CHAPTER 5
To increase the number of user connections for shared memory, you must: 1 2 Increase number of user connections to a number one-third of which is the number of desired shared-memory connections. Restart Adaptive Server.
Although number of user connections is a dynamic configuration parameter, you must restart the server to change the number of user connections for shared memory. See the EJB Server Users Guide for more information. With Adaptive Server version 12.5.3, ESD #2, no sockets are automatically reserved for EJB. However, you can enable traceflag 1642 to revert to the previous functionality, reserving one-third of the sockets for EJB. You must enable traceflag 1642 to setup the EJB server. For this release of Adaptive Server, if the message, "hbc_ninit: No sockets available for HBC",is in the errorlog, but the EJB server is not configured, the message can be ignored. In Adaptive Server version 12.5.3, if the EJB server is enabled and HBC sockets are not available, the message "hbc_ninit: No sockets available for HBC" is reported. If traceflag 1642 is not enabled, then Adaptive Server must be booted with the 1642 traceflag. If the EJB server is not enabled, then no message is reported and Adaptive Server automatically disables the sockets reserved for EJB server.
number of worker processes

0 02147483647 Dynamic Basic System Administrator Memory Use, Query Tuning
number of worker processes specifies the maximum number of worker processes that Adaptive Server can use at any one time for all simultaneously running parallel queries combined.
Adaptive Server issues a warning message at start-up if there is insufficient memory to create the specified number of worker processes. memory per worker process controls the memory allocated to each worker process.
185
o/s file descriptors

Summary information Default value Range of values Status Display level Required role Configuration group 0 Site-specific Read-only Comprehensive System Administrator O/S Resources
o/s file descriptors indicates the maximum per-process number of file
descriptors configured for your operating system. This parameter is read-only and cannot be configured through Adaptive Server. Many operating systems allow you to configure the number of file descriptors available per process. See your operating system documentation for further information on this. The number of file descriptors available for Adaptive Server connections, which is less than the value of o/s file descriptors, is stored in the variable @@max_connections. For more information on the number of file descriptors available for connections, see Upper limit to the maximum number of user connections on page 183.
object lockwait timing

object lockwait timing controls whether Adaptive Server collects timing
statistics for requests of locks on objects.
186
CHAPTER 5
open index hash spinlock ratio

Summary information Default value Range of values Status Display level Required role Configuration groups 100 12147483647 Dynamic Basic System Administrator Memory Use, Meta-Data Cache
open index hash spinlock ratio sets the number of index metadata descriptor hash tables that are protected by one spinlock. This parameter is used for multiprocessing systems only.
All the index descriptors belonging to the table are accessible through a hash table. When a query is run on the table, Adaptive Server uses hash tables to look up the necessary index information in its sysindexes rows. A hash table is an internal mechanism used by Adaptive Server to retrieve information quickly. Usually, you do not need to change this parameter. In rare instances, however, you may need to reset it if Adaptive Server demonstrates contention from hash spinlocks. You can get information about spinlock contention by using sp_sysmon. For more about sp_sysmon, see the Performance and Tuning Guide. For more information about configuring spinlock ratios, see Configuring spinlock ratio parameters on page 132.
open index spinlock ratio

Summary information Default value Range of values Status Display level Required role Configuration groups 100 1214748364 Dynamic Comprehensive System Administrator Memory Use, Meta-Data Cache
open index spinlock ratio specifies the number of index metadata descriptors that are protected by one spinlock.
187
Adaptive Server uses a spinlock to protect an index descriptor, since more than one process can access the contents of the index descriptor. This parameter is used for multiprocessing systems only. The value specified for this parameter defines the ratio of index descriptors per spinlock. If one spinlock is shared by too many index descriptors, it can cause spinlock contention. Use sp_sysmon to get a report on spinlock contention. See the Performance and Tuning Guide for more information. If sp_sysmon output indicates an index descriptor spinlock contention of more than 3 percent, try decreasing the value of open index spinlock ratio. For more information about configuring spinlock ratios, see see Configuring spinlock ratio parameters on page 132.
open object spinlock ratio

100 12147483647 Dynamic Comprehensive System Administrator Meta-Data Cache
open object spinlock ratio specifies the number of object descriptors that are
protected by one spinlock. Adaptive Server uses a spinlock to protect an object descriptor, since more than one process can access the contents of the object descriptor. This configuration parameter is used for multiprocessing systems only. The default value for this parameter is 100; 1 spinlock for each 100 object descriptors configured for your server. If your server is configured with only one engine, Adaptive Server sets only 1 object descriptor spinlock, regardless of the number of object descriptors. If one spinlock is shared by too many object descriptors, it causes spinlock contention. Use sp_sysmon to get a report on spinlock contention. See the Performance and Tuning Guide for more information on spinlock contention. If sp_sysmon output indicates an object descriptor spinlock contention of more than 3 percent, try decreasing the value of the open object spinlock ratio parameter.
188
CHAPTER 5
For more information about configuring spinlock ratios, see see Configuring spinlock ratio parameters on page 132.
optimization goal
allows_mix allrows_oltp, allrows_dss
Dynamic Comprehensive System Administrator Query Tuning
Optimization goals are a convenient way of matching the users query demands with the best optimization techniques, ensuring optimal use of the optimizer's time and resources. Adaptive Server allows users to configure for two optimization goals, which you can specify at three tiers: server level, session level, and query level. The server-level optimization goal is overridden at the session level, which is overridden at the query level. These optimization goals allow you to choose an optimization strategy that best fits your query environment:
allrows_oltp the most useful goal for purely OLTP queries. allrows_dss the most useful goal for operational DSS queries of medium-to-high complexity.
optimization timeout limit

10 1 1000 Dynamic Comprehensive System Administrator Query Tuning
189
The optimization timeout limit parameter specifies the amount of time Adaptive Server can spend optimizing a query as a fraction of the estimated execution time of the query.
page lock promotion HWM

Summary information Default value Range of values Status Display level Required role Configuration groups 200 22147483647 Dynamic Intermediate System Administrator Lock Manager, SQL Server Administration
page lock promotion HWM (high-water mark), together with the page lock promotion LWM (low-water mark) and page lock promotion PCT (percentage),
specifies the number of page locks permitted during a single scan session of a page-locked table or index before Adaptive Server attempts to escalate from page locks to a table lock.
page lock promotion HWM sets a maximum number of page locks allowed on a
table before Adaptive Server attempts to escalate to a table lock. When the number of page locks acquired during a scan session exceeds page lock promotion HWM, Adaptive Server attempts to acquire a table lock. The page lock promotion HWM value cannot be higher than number of locks value. For more detailed information on scan sessions and setting up page lock promotion limits, see Configuring locks and lock promotion thresholds in the Performance and Tuning Guide: Locking. The default value for page lock promotion HWM is appropriate for most applications. You may want to raise the value to avoid table locking. For example, if you know that there are regular updates to 500 pages of an allpageslocked or datapages-locked table containing thousands of pages, you can increase concurrency for the tables by setting page lock promotion HWM to 500 so that lock promotion does not occur at the default setting of 200. You can also configure lock promotion of page-locked tables and views at the per-object level. See sp_setrowlockpromote in the Reference Manual.
190
CHAPTER 5
Use sp_sysmon to see how changing page lock promotion HWM affects the number of lock promotions. sp_sysmon reports the ratio of exclusive page to exclusive table lock promotions and the ratio of shared page to shared table lock promotions. See Lock promotions in the Performance and Tuning Guide: Monitoring and Analyzing.
page lock promotion LWM

Summary information Default value Range of values Status Display level Required role Configuration groups 200 2value of page lock promotion HWM Dynamic Intermediate System Administrator Lock Manager, SQL Server Administration
The page lock promotion LWM low-water mark) parameter, together with the page lock promotion HWM (high-water mark) and the page lock promotion PCT, specify the number of page locks permitted during a single scan session of a page locked table or an index before Adaptive Server attempts to promote from page locks to a table lock. The page lock promotion LWM sets the number of page locks below which Adaptive Server does not attempt to issue a table lock on an object. The page lock promotion LWM must be less than or equal to page lock promotion HWM. For more information on scan sessions and setting up lock promotion limits, see Configuring locks and lock promotion thresholds in the Performance and Tuning Guide: Locking. The default value for page lock promotion LWM is sufficient for most applications. If Adaptive Server runs out of locks (except for an isolated incident), increase number of locks. See the Performance and Tuning Guide for more information. You can also configure page lock promotion at the per-object level. See sp_setpglockpromote in the Reference Manual: Procedures.
page lock promotion PCT

100
191
Summary information Range of values Status Display level Required role Configuration groups 1100 Dynamic Intermediate System Administrator Lock Manager, SQL Server Administration
If the number of locks held on an object is between page lock promotion LWM (low-water mark) and page lock promotion HWM (high-water mark). page lock promotion PCT sets the percentage of page locks (based on the table size) above which Adaptive Server attempts to acquire a table lock. For more detailed information on setting up page lock promotion limits, see Configuring locks and lock promotion thresholds in the Performance and Tuning Guide: Locking. The default value for page lock promotion PCT is appropriate for most applications. You can also configure lock promotion at the per-object level for page locked objects. See sp_setpglockpromote in the Reference Manual.
page utilization percent

95 1100 Dynamic Comprehensive System Administrator Disk I/O
The page utilization percent parameter is used during page allocations to control whether Adaptive Server scans a tables object allocation map (OAM) to find unused pages or simply allocates a new extent to the table. (See number of oam trips on page 172 for more information on the OAM.) The page utilization percent parameter is a performance optimization for servers with very large tables; it reduces the time needed to add new space.
192
CHAPTER 5
If you set page utilization percent to 100, Adaptive Server scans through all OAM pages to find unused pages allocated to the object before allocating a new extent. When this parameter is set lower than 100, Adaptive Server compares the page utilization percent setting to the ratio of used and unused pages allocated to the table, as follows:
100 * used pages/(used pages + unused pages)
If the page utilization percent setting is lower than the ratio, Adaptive Server allocates a new extent instead of searching for the unused pages. For example, when inserting data into a 10GB table that has 120 OAM pages and only 1 unused data page: A page utilization percent of 100 tells Adaptive Server to scan through all 120 OAM pages to locate an unused data page. A page utilization percent of 95 allows Adaptive Server to allocate a new extent to the object, because 95 is lower than the ratio of used pages to used and unused pages.
A low page utilization percent value results in more unused pages. A high page utilization percent value slows page allocations in very large tables, as Adaptive Server performs an OAM scan to locate each unused page before allocating a new extent. This increases logical and physical I/O. If page allocations (especially in the case of large inserts) seem to be slow, you can lower the value of page utilization percent, but reset it after inserting the data. A lower setting affects all tables on the server and results in unused pages in all tables. Fast bulk copy ignores the page utilization percent setting and always allocates new extents until there are no more extents available in the database.
partition groups
193
partition groups specifies the maximum number of partition groups that can be
allocated by Adaptive Server. Partition groups are internal structures used by Adaptive Server to control access to individual partitions of a table. Partition groups are used during upgrade or during a load database upgrade to unpartition Adaptive Server 12.5.x and earlier partitions. The default value allows a maximum 1024 open partition groups and a maximum of 16384 (1024 times 16) open partitions. The actual number of partitions may be slightly less, due to the grouping of partitions.
partition spinlock ratio

For Adaptive Servers running with multiple engines, partition spinlock ratio sets the number of rows in the partition descriptors that are protected by one spinlock. Adaptive Server manages access to table partitions using partition descriptors. Each partition descriptor stores information about a partition (for example, the last page of the partition) that processes must use when accessing that partition. Partition descriptors are configured using the configuration parameter number of open partitions. By default, Adaptive Server systems are configured with partition spinlock ratio set to 10, or 1 spinlock for every 10 partition caches. Decreasing the value of partition spinlock ratio may have little impact on the performance of Adaptive Server. The default setting is correct for most servers. For more information about configuring spinlock ratios, see Managing Multiprocessor Servers on page 123.
per object statistics active

194
CHAPTER 5
Summary information Range of values Status Display level Required role Configuration group 01 Dynamic Comprehensive System Administrator Monitoring
per object statistic active controls whether Adaptive Server collects statistics for
each object.
percent database for history

20 0 100 Dynamic Intermediate System Administrator SQL Server Administration
Specifies the amount of space reserved for the js_history table, as a percentage of the total space available in sybmgmtdb. Increase percent database for history if there are more jobs running, or if you need to store historical records about executed jobs for future queries.
percent database for output

195
This specifies the amount of space reserved for jobs' output in percentage of the total space available in sybmgmtdb. Legal values are between 0 and 100. Default value is 30. Increase this if there are more jobs running or jobs which produce lot of output information are running and that output needs to be stored for querying.
percent history free

Summary information Default value Valid values Status Display level Required role Configuration group 30 0 100 Dynamic Intermediate System Administrator SQL Server Administration
Specifies what percentage of reserved space in sybmgmtdb should be kept free For example, for the default value of 30 percent, when 70 percent of the space reserved for history in sybmgmtdb is occupied, Adaptive Server starts purging the oldest history records to make room for new records.
percent output free

Specifies the percentage of reserved space kept free in sybmgmtdb that is reserved for the Job Schedulers output. For example, for the default value of 30 percent, when 70 percent of the space reserved for history in sybmgmtdb is occupied, Adaptive Server starts purging the oldest history records to make room for new records. .
196
CHAPTER 5
performance monitoring option

performance monitoring option enables the license for the DBXray graphical
monitoring tool.
permission cache entries

Summary information Default value Range of values Status Display level Required role Configuration groups 15 12147483647 Dynamic Comprehensive System Administrator Memory Use, User Environment
permission cache entries determines the number of cache protectors per task. This parameter increases the amount of memory for each user connection and worker process.
Information about user permissions is held in the permission cache. When Adaptive Server checks permissions, it looks first in the permission cache; if it does not find what it needs, it looks in the sysprotects table. This process is significantly faster if Adaptive Server finds the information it needs in the permission cache and does not have to read sysprotects. However, Adaptive Server looks in the permission cache only when it is checking user permissions, not when permissions are being granted or revoked. When a permission is granted or revoked, the entire permission cache is flushed. This is because existing permissions have timestamps that become outdated when new permissions are granted or revoked.
197
If users on your Adaptive Server frequently perform operations that require their permissions to be checked, you may see a small performance gain by increasing the value of permission cache entries. This effect is not likely to be significant enough to warrant extensive tuning. If users on your Adaptive Server frequently grant or revoke permissions, avoid setting permission cache entries to a large value. The space used for the permission cache would be wasted, since the cache is flushed with each grant and revoke command.
plan text pipe active

plan text pipe active determines whether Adaptive Server collects query plan text. If both plan text pipe active and plan text pipe max messages are enabled,
Adaptive Server collects the plan text for each query. You can use monSysPlanText to retrieve the query plan text for all user tasks.
plan text pipe max messages

plan text pipe max messages determines the number of query plan text
messages Adaptive Server stores per engine. The total number of messages in the monSQLText table will be the value of sql text pipe max messages times the number of engines running.
198
CHAPTER 5
print deadlock information

Summary information Default value Valid values Status Display level Required role Configuration groups 0 (off) 0 (off), 1 (on) Dynamic Intermediate System Administrator Lock Manager, SQL Server Administration
print deadlock information enables the printing of deadlock information to the
error log. If you are experiencing recurring deadlocks, setting print deadlock information to 1 provides you with information that can be useful in tracing the cause of the deadlocks. However, setting print deadlock information to 1 can seriously degrade Adaptive Server performance. For this reason, you should use it only when you are trying to determine the cause of deadlocks. Use sp_sysmon output to determine whether deadlocks are occurring in your application. If they are, set print deadlock information to 1 to learn more about why they are occurring. See the Performance and Tuning Guide for more information.
print recovery information

Summary information Default value Valid values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Intermediate System Administrator Backup/Recovery
199
The print recovery information parameter determines what information Adaptive Server displays on the console during recovery. (Recovery is performed on each database at Adaptive Server start-up and when a database dump is loaded.) The default value is 0, which means that Adaptive Server displays only the database name and a message saying that recovery is in progress. The other value is 1, which means that Adaptive Server displays information about each individual transaction processed during recovery, including whether it was aborted or committed.
procedure cache size

Summary information Default value Range of values Status Display level Required role Configuration groups 3271 3271 2147483647 Dynamic Basic System Administrator Memory Use, SQL Server Administration
Specifies the size of the procedure cache in 2K pages. Adaptive Server uses the procedure cache while running stored procedures. If the server finds a copy of a procedure already in the cache, it does not need to read it from the disk. Adaptive Server also uses space in the procedure cache to compile queries while creating stored procedures. Since the optimum value for procedure cache size differs from application to application, resetting it may improve Adaptive Servers performance. For example, if you run many different procedures or ad hoc queries, your application uses the procedure cache more heavily, so you may want to increase this value.
Warning! If procedure cache size is too small, Adaptive Servers performance is greatly affected.
If you are upgrading
If you are upgrading, procedure cache size is set to the size of the original procedure cache at the time of upgrade. procedure cache size is dynamically configurable, subject to the amount of max memory currently configured.
200
CHAPTER 5
process wait events

Summary information Default value Range of values Status Display level Required role Configuration groups 0 01 Dynamic Comprehensive System Administrator Memory Use, Monitoring
process wait events controls whether Adaptive Server collect statistics for each wait event for every task. You can get wait information for a specific task using monProcessWaits.
read committed with lock

Summary information Default value Valid values Status Display level Required role Configuration group 0 (off) 0 (off), 1(on) Dynamic Comprehensive System Administrator Lock Manager
read committed with lock determines whether an Adaptive Server using
transaction isolation level 1 (read committed) holds shared locks on rows or pages of data-only-locked tables during select queries. For cursors, the option applies only to cursors declared as read-only. By default, this parameter is turned off to reduce lock contention and blocking. This parameter affects only queries on data-only locked tables. For transaction isolation level 1, select queries on allpages-locked tables continue to hold locks on the page at the current position. Any updatable cursor on a data-only-locked table also holds locks on the current page or row. See the Performance and Tuning Guide for more information.
recovery interval in minutes

201
Summary information Range of values Status Display level Required role Configuration group 132767 Dynamic Basic System Administrator Backup/Recovery
The recovery interval in minutes parameter sets the maximum number of minutes per database that Adaptive Server uses to complete its recovery procedures in case of a system failure. The recovery procedure rolls transactions backward or forward, starting from the transaction that the checkpoint process indicates as the oldest active transaction. The recovery process has more or less work to do, depending on the value of recovery interval in minutes. Adaptive Server estimates that 6000 rows in the transaction log require 1 minute of recovery time. However, different types of log records can take more or less time to recover. If you set recovery interval in minutes to 3, the checkpoint process writes changed pages to disk only when syslogs contains more than 18,000 rows since the last checkpoint.
Note The recovery interval has no effect on long-running, minimally logged transactions (such as create index) that are active at the time Adaptive Server
fails. It may take as much time to reverse these transactions as it took to run them. To avoid lengthy delays, dump each database after index maintenance operations. Adaptive Server uses the recovery interval in minutes setting and the amount of activity on each database to decide when to checkpoint each database. When Adaptive Server checkpoints a database, it writes all dirty pages (data pages in cache that have been modified) to disk. This may create a brief period of high I/O, called a checkpoint spike.The checkpoint also performs a other maintenance tasks, including truncating the transaction log for each database for which the truncate log on chkpt option has been set. About once per minute, the sleeping checkpoint process wakes up, checks the truncate log on chkpt setting, and checks the recovery interval to determine if a checkpoint is needed. Figure 5-4 shows the logic used by Adaptive Server during this process.
202
CHAPTER 5
Figure 5-4: The checkpoint process
Sleep
Checkpoint process wakes up and polls each database
Is truncate log on chkpt set? No No Time to checkpoint? Yes Checkpoint performed
Yes
Checkpoint performed
Logs truncated
You may want to change the recovery interval if your application and its use change. For example, you may want to shorten the recovery interval when there is an increase in update activity on Adaptive Server. Shortening the recovery interval causes more frequent checkpoints, with smaller, more frequent checkpoint spikes, and slows the system slightly. On the other hand, setting the recovery interval too high may cause the recovery time to be unacceptably long. The spikes caused by checkpointing can be reduced by reconfiguring the housekeeper free write percent parameter. See housekeeper free write percent on page 130 for further information. For more information on the performance implications of recovery interval in minutes, see Memory Use and Performance in the Performance and Tuning: Basics. Use sp_sysmon to determine how a particular recovery interval affects the system. See the Performance and Tuning Guide for more information.
203
remote server pre-read packets

remote server pre-read packets determines the number of packets that are preread by a site handler during connections with remote servers.
All communication between two servers is managed through a single site handler, to reduce the required number of connections. The site handler can pre-read and keep track of data packets for each user process before the receiving process is ready to accept them. The default value for remote server pre-read packets is appropriate for most servers. Increasing the value uses more memory; decreasing the value can slow network traffic between servers. For more information, see Chapter 15, Managing Remote Servers.
row lock promotion HWM

row lock promotion HWM (high-water mark), together with row lock promotion LWM (low-water mark) and row lock promotion PCT specifies the number of row
locks permitted during a single scan session of a table or an index before Adaptive Server attempts to escalate from row locks to a table lock.
204
CHAPTER 5
row lock promotion HWM sets a maximum number of row locks allowed on a
table before Adaptive Server attempts to escalate to a table lock. When the number of locks acquired during a scan session exceeds row lock promotion HWM, Adaptive Server attempts to acquire a table lock. The lock promotion HWM value cannot be higher than the number of locks value. For more information on scan sessions and setting up lock promotion limits, see Configuring locks and lock promotion thresholds in the Performance and Tuning Guide: Locking. The default value for row lock promotion HWM is appropriate for most applications. You may want to raise the value to avoid table locking. For example, if you know that there are regular updates to 500 rows on a table that has thousands of rows, you can increase concurrency for the tables by setting row lock promotion HWM to around 500. You can also configure row lock promotion at the per-object level. See sp_setpglockpromote in the Reference Manual.
row lock promotion LWM

200 2value of row lock promotion HWM Dynamic Intermediate System Administrator Lock Manager, SQL Server Administration
row lock promotion LWM (low-water mark), together with the row lock promotion HWM (high-water mark) and row lock promotion PCT specifies the number of
row locks permitted during a single scan session of a table or an index before Adaptive Server attempts to promote from row locks to a table lock.
row lock promotion LWM sets the number of locks below which Adaptive Server does not attempt to acquire a table lock on the object. The row lock promotion LWM must be less than or equal to row lock promotion HWM.
For more detailed information on scan sessions and setting up lock promotion limits, see Configuring locks and lock promotion thresholds in the Performance and Tuning Guide: Locking.
205
The default value for row lock promotion LWM is sufficient for most applications. If Adaptive Server runs out of locks (except for an isolated incident), increase number of locks. See the Performance and Tuning Guide for more information. You can also configure lock promotion at the per-object level. See sp_setpglockpromote in the Reference Manual.
row lock promotion PCT

If the number of locks held on an object is between row lock promotion LWM (low-water mark) and row lock promotion HWM (high-water mark), row lock promotion PCT sets the percentage of row locks (based on the number of rows in the table) above which Adaptive Server attempts to acquire a table lock. For more information on setting up lock promotion limits, see Configuring locks and lock promotion thresholds in the Performance and Tuning Guide: Locking. The default value for row lock promotion PCT is appropriate for most applications. You can also configure row lock promotion at the per-object level. See sp_sterowlockpromote in the Reference Manual.
rtm thread idle wait period

Summary information Default value 600 seconds Range of values Status Display level Required role 600 4026531839 seconds Dynamic Intermediate System Administrator
206
CHAPTER 5
Summary information Configuration group SQL Server Administration
Use to define the time a native thread used by Adaptive Server waits when it has no work to do. When the time set for a native thread is reached, the thread automatically fades out.
runnable process search count

runnable process search count specifies the number of times an engine loops while looking for a runnable task before relinquishing the CPU to the operating system.
Adaptive Server engines check the run queue for runnable tasks whenever a task completes or exceeds its allotted time on the engine. At times, there are not any tasks in the run queues. An engine can either relinquish the CPU to the operating system or continue to check for a task to run. Setting runnable process search count higher causes the engine to loop more times, thus holding the CPU for a longer time. Setting the runnable process search count lower causes the engine to release the CPU sooner. If your machine is a uniprocessor that depends on helper threads to perform I/O, you may see some performance benefit from setting runnable process search to perform network I/O, disk I/O, or other operating system tasks. If a client, such as a bulk copy operation, is running on the same machine as a single CPU server that uses helper threads, it can be especially important to allow both the server and the client access to the CPU.
Note If you are having performance problems, try setting runnable process search count to 3.
207
For Adaptive Servers running on uniprocessor machines that do not use helper threads, and for multiprocessor machines, the default value provides good performance. Use sp_sysmon to determine how the runnable process search count parameter affects the Adaptive Server use of CPU cycles, engine yields to the operating system, and blocking network checks. See the Performance and Tuning Guide for information.
sampling percent
Summary information Default value Range of values Status Display level Required role Configuration group 0 0 100 percent Dynamic Comprehensive System or database administrator Query Tuning
sampling percent is the numeric value of the sampling percentage, such as 05
for 5%, 10 for 10%, and so on. The sampling integer is between zero (0) and one hundred (100). To reduce I/O contention and resources, run update statistics using a sampling method, which can reduce the I/O and time when your maintenance window is small and the data set is large. If you are updating a large data set or table that is in constant use, being truncated and repopulated, you may want to perform a statistical sampling to reduce the time and the size of the I/O. You must use caution with sampling since the results are not fully accurate. Balance changes to histogram values against the savings in I/O. Although a sampling of the data set may not be completely accurate, usually the histograms and density values are reasonable within an acceptable range. When you are deciding whether or not to use sampling, consider the size of the data set, the time constraints you are working with, and if the histogram produced is as accurate as needed. The percentage to use when sampling depends on your needs. Test various percentages until you receive a result that reflects the most accurate information on a particular data set. Statistics are stored in the system tables systabstats and sysstatistics.
208
CHAPTER 5
secure default login

Summary information Default value Range of values Status Display level Required role Configuration group 0 0 (followed by another parameter naming the default login) Dynamic Intermediate System Security Officer Security Related
secure default login specifies a default login for all users who are preauthenticated but who do not have a login in master..syslogins.
Establish the secure default login with:

sp_configure "secure default login", 0, default_login_name
where:
secure default login is the name of the parameter. 0 is a required parameter because the second parameter of sp_configure must be a numeric value.
default_login_name is the name of the default login for a user who is unknown to Adaptive Server, but who has already been authenticated by a security mechanism. The login name must be a valid login in master..syslogins.
For example, to specify dlogin as the secure default login, type:

sp_configure "secure default login", 0, dlogin
select on syscomments.text column

Summary information Default value Range of values Status Display level Required role Configuration group 1 01 Dynamic Comprehensive System Security Officer Security Related
209
This parameter enables protection of the text of database objects through restriction of the select permission on the text column of the syscomments table. The default value of 1 allows select permission to public. Set the option to 0 to restrict select permission to the object owner and the System Administrator.
shared memory starting address

Summary information Default value Range of values Status Display level Required role Configuration group 0 Platform-specific Static Comprehensive System Administrator Physical Memory
shared memory starting address determines the virtual address where Adaptive
Server starts its shared memory region. It is unlikely that you will ever have to reconfigure shared memory starting address. You should do so only after consulting with Sybase Technical Support.
number of worker processes, max parallel degree, and max scan parallel degree control parallel query processing at the server level. Using the parallel_degree, process_limit_action, and scan_parallel_degree options to the set command can limit parallel optimization at the session level, and using the parallel keyword of the select command can limit parallel optimization of specific queries.
size of auto identity column

10 138 Dynamic Intermediate System Administrator SQL Server Administration
210
CHAPTER 5
size of auto identity column sets the precision of IDENTITY columns that are automatically created with the sp_dboption auto identity and unique auto_identity index options.
The maximum value that can be inserted into an IDENTITY column is 10precision -1. After an IDENTITY column reaches its maximum value, all further insert statements return an error that aborts the current transaction. If you reach the maximum value of an IDENTITY column, you can increase it with a modify operation in the alter table command. See Transact-SQL Users Guide for examples. You can also use the create table command to create a table that is identical to the old one, but with a larger precision for the IDENTITY column. After you have created the new table, use the insert command or bcp to copy data from the old table to the new one.
size of global fixed heap

Summary information Default values Minimum values Status Display level Required role Configuration groups
150 pages (32-bit version) 300 pages (64-bit version) 10 pages (32-bit version) 20 pages (64-bit version) Dynamic Comprehensive System Administrator Java Services, Memory Use
The size of global fixed heap parameter specifies the memory space for internal data structures and other needs. If you change the size of the global fixed heap, you must also change the total logical memory by the same amount.
size of process object heap

Summary information Default values 1500 pages (32-bit version) 3000 pages (64-bit version)
211
Summary information Minimum values Status Display level Required role Configuration groups 45 pages (32-bit version) 90 pages (64-bit version) Dynamic Basic System Administrator Java Services, Memory Use
The size of process object fixed heap parameter specifies the total memory space for all processes using the Java VM. If you change the size of process object fixed heap, you must change the total logical memory by that amount.
size of shared class heap

Summary information Default values Minimum values Status Display level Required role Configuration groups 1536 pages (32-bit version) 3072 pages (64-bit version) 650 pages (32-bit version) 1300 pages (64-bit version) Dynamic Basic System Administrator Java Services, Memory Use
The size of shared class heap parameter specifies the shared memory space for all Java classes called into the Java VM. Adaptive Server maintains the shared class heap server-wide for both user-defined and system-provided Java classes. If you change the size of shared class heap, you must change the total logical memory by the same amount.
size of unilib cache

0 02147483647 Dynamic
212
CHAPTER 5
Summary information Display level Required role Configuration groups Comprehensive System Administrator Memory Use, Unicode
Determines the size of the Unilib cache. size of unilib cache specifies the memory used in bytes rounded up to the nearest 1K in addition to the minimum overhead size, which provides enough memory to load a single copy of the largest Unilib conversion table plus the largest Unilib sort table. Asian clients may need to increase size of unilib cache by an extra 100K for every additional character set they want to support via Unicode-based conversion.
SQL batch capture

0 01 Dynamic Comprehensive System Administrator Monitoring
SQL batch capture controls whether Adaptive Server collects SQL text. If both SQL batch capture and max SQL text monitored are enabled, Adaptive Server
collects the SQL text for each batch for each user task.
SQL Perfmon Integration (Windows only)

1 (on) 0 (off), 1 (on) Static Intermediate System Administrator SQL Server Administration
SQL Perfmon Integration enables and disables the ability to monitor Adaptive
Server statistics from the Windows Performance Monitor.
213
Adaptive Server must be registered as an Windows Service to support monitor integration. This occurs automatically when: You start Adaptive Server using the Services Manager in the Sybase for the Windows program group. You use the Services option in the Control Panel. You have configured Windows to start Adaptive Server as an automatic service.
See Configuring Adaptive Server for Windows for a list of the Adaptive Server counters you can monitor.
sql server clock tick length

Platform-specific Platform-specific minimum1000000, in multiples of default value Static Comprehensive System Administrator SQL Server Administration
sql server clock tick length specifies the duration of the servers clock tick, in microseconds. Both the default value and the minimum value are platformspecific. Adaptive Server rounds values up to an even multiple of n, where n is the platform-specific clock-tick default value. You can find the current values for sql server clock tick length by using sp_helpconfig or sp_configure.
In mixed-use applications with some CPU-bound tasks, decreasing the value of sql server clock tick length helps I/O-bound tasks. A value of 20,000 is reasonable for this. Shortening the clock tick length means that CPU-bound tasks exceed the allotted time on the engine more frequently per unit of time, which allows other tasks greater access to the CPU. This may also marginally increase response times, because Adaptive Server runs its service tasks once per clock tick. Decreasing the clock tick length means that the service tasks are run more frequently per unit of time.
214
CHAPTER 5
Increasing sql server clock tick length favors CPU-bound tasks, because they execute longer between context switches. The maximum value of 1,000,000 may be appropriate for primarily CPU-bound applications. However, any I/Obound tasks may suffer as a result. This can be mitigated somewhat by tuning cpu grace time (see cpu grace time on page 95) and time slice (see time slice on page 227).
Note Changing the value of sql server clock tick length can have serious
effects on Adaptive Server performance. Consult with Sybase Technical Support before resetting this value.
sql text pipe active

sql text pipe active controls whether Adaptive Server collects SQL text. If this option is enabled and sql text pipe max messages is set, Adaptive Server
collects the SQL text for each query. You can use monSysSQLText to retrieve the SQL text for all user tasks.
sql text pipe max messages

215
sql text pipe max messages specifies the number of SQL text messages Adaptive Server stores per engine. The total number of messages in the monSQLText table will be the value of sql text pipe max messages times the number of engines running.
stack guard size

Summary information Default value Range of values Status Display level Required role Configuration groups 4096 02147483647 Static Comprehensive System Administrator Memory Use, User Environment
stack guard size sets the size (in bytes) of the stack guard area. The stack guard
area is an overflow stack of configurable size at the end of each stack. Adaptive Server allocates one stack for each user connection and worker process when it starts. These stacks are located contiguously in the same area of memory, with a guard area at the end of each stack. At the end of each stack guard area is a guardword, which is a 4-byte structure with a known pattern. Figure 5-5 illustrates how a process can corrupt a stack guardword.
216
CHAPTER 5
Figure 5-5: Process about to corrupt stack guardword
Stack 2 guard area
Stack guardwords Stack 2
Stack 1 guard area
Process overflowing stack area, about to corrupt stack guardword
Stack 1
Process begins executing Adaptive Server periodically checks to see whether the stack pointer for a user connection has entered the stack guard area associated with that user connections stack. If it has, Adaptive Server aborts the transaction, returns control to the application that generated the transaction, and generates Error 3626:
The transaction was aborted because it used too much stack space. Either use sp_configure to increase the stack size, or break the query into smaller pieces. spid: %d, suid: %d, hostname: %.*s, application name: %.*s
217
Adaptive Server also periodically checks the guardword pattern to see if it has changed, thus indicating that a process has overflowed the stack boundary. When this occurs, Adaptive Server prints these messages to the error log and shuts down:
kernel: *** Stack overflow detected: limit: 0x%lx sp: 0x%lx kernel: *** Stack Guardword corrupted kernel: *** Stack corrupted, server aborting
In the first message, limit is the address of the end of the stack guard area, and sp is the current value of the stack pointer. In addition, Adaptive Server periodically checks the stack pointer to see whether it is completely outside both the stack and the stack guard area for the pointers process. If it is, Adaptive Server shuts down, even if the guardword is not corrupted. When this happens, Adaptive Server prints the following messages to the error log:
kernel: *** Stack overflow detected: limit: 0x%lx sp: 0x%lx kernel: *** Stack corrupted, server aborting
The default value for stack guard size is appropriate for most applications. However, if you experience server shutdown from either stack guardword corruption or stack overflow, increase stack guard size by a 2K increment. Each configured user connection and worker process has a stack guard area; thus, when you increase stack guard size, you use up that amount of memory, multiplied by the number of user connections and worker processes you have configured. Rather than increasing stack guard size to avoid stack overflow problems, consider increasing stack size (see stack size on page 218). The stack guard area is intended as an overflow area, not as an extension to the regular stack. Adaptive Server allocates stack space for each task by adding the values of the stack size and stack guard size parameters. stack guard size must be configured in multiples of 2K. If the value you specify is not a multiple of 2K, sp_configure verification routines round the value up to the next highest multiple.
stack size
Summary information Default value Range of values platform-specific Platform-specific minimum2147483647
218
CHAPTER 5
Summary information Status Display level Required role Configuration group Static Basic System Administrator User Environment
stack size specifies the size (in bytes) of the execution stacks used by each user process on Adaptive Server. To find the stack size values for your platform, use sp_helpconfig or sp_configure. stack size must be configured in multiples of 2K. If the value you specify is not a multiple of 2K, sp_configure verification
routines round the value up to the next highest multiple. An execution stack is an area of Adaptive Server memory where user processes keep track of their process context and store local data. Certain queries can contribute to the probability of a stack overflow. Examples include queries with extremely long where clauses, long select lists, deeply nested stored procedures, and multiple selects and updates using holdlock. When a stack overflow occurs, Adaptive Server prints an error message and rolls back the transaction. See stack guard size on page 216 for more information on stack overflows. See the Troubleshooting and Error Messages Guide for more information on specific error messages. The two options for remedying stack overflows are to break the large queries into smaller queries and to increase stack size. Changing stack size affects the amount of memory required for each configured user connection and worker process. See total logical memory on page 229 for further information. If you have queries that exceed the size of the execution stack, you may want to rewrite them as a series of smaller queries. This is particularly true if there are only a small number of such queries or if you run them infrequently. There is no way to determine how much stack space a query requires without actually running the query. Stack space for each user connection and worker process is preallocated at start-up. Therefore, determining the appropriate value for stack size is an empirical process. Test your largest and most complex queries using the default value for stack size. If they run without generating error messages, the default is probably sufficient. If they generate error messages, begin by increasing stack size by a small amount (2K). Re-run your queries and see if the amount you have added is sufficient. If it is not, continue to increase stack size until queries run without generating error messages.
219
If you are using CIS, or if Java is enabled in the database and you want to use methods that call JDBC, Sybase recommends that you increase the default by 50 percent. If you are not using JDBC or CIS, the standard default value is usually sufficient.
start mail session (Windows only)

Summary information Default value Valid values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Comprehensive System Administrator Extended Stored Procedure
The start mail session parameter enables and disables the automatic initiation of an Adaptive Server mail session when you start Adaptive Server. This feature is available on Windows servers only. A value of 1 configures Adaptive Server to start a mail session the next time Adaptive Server is started. A value of 0 configures Adaptive Server not to start a mail session at the next restart. If start mail session is 0, you can start an Adaptive Server mail session explicitly, using the xp_startmail system ESP. Before setting the start mail session parameter, you must prepare your Windows system by creating a mailbox and mail profile for Adaptive Server. Then, you must create an Adaptive Server account for Sybmail. See the Configuration Guide for Windows for information about preparing your system for Sybmail.
statement cache size

0 Size of cache in 2K pages Dynamic Comprehensive System Administrator Memory Use, SQL Server Administration
220
CHAPTER 5
The statement cache size parameter increases the server allocation of procedure cache memory and limits the amount of memory from the procedure cache pool used for cached statements. The statement cache feature is enabled server-wide:
statement cache size size_of_cache Note You must configure set chained on/off in its own batch if you enable the
statement cache. Because cached statements are transformed into lightweight stored procedures, statement caching requires additional open object descriptors
statement pipe active

statement pipe active controls whether Adaptive Server collects statement-level statistics. If both statement pipe active and statement pipe max messages are enabled, Adaptive Server collects the statement statistics for each query. You can retrieve the statistics for all executed statements using monSysStatement.
statement pipe max messages

Summary information Default value Range of values Status Display level Required role Configuration groups 0 02147483647 Dynamic Comprehensive System Administrator Memory Use, Monitoring
221
statement pipe max messages determines the number of statement statistics
messages Adaptive Server stores per engine. The total number of messages in the monSQLText table will be the value of sql text pipe max messages times the number of engines running.
statement statistics active

statement statistic active controls whether Adaptive Server collects the
monitoring tables statement-level statistics. You can use monProcessStatement to get statement statistics for a specific task.
strict dtm enforcement

0 (off) 0 (off), 1(on) Static 10 System Administrator DTM Administration
strict dtm enforcement determines whether or not Adaptive Server transaction
coordination services strictly enforce the ACID properties of distributed transactions. In environments where Adaptive Server should propagate and coordinate transactions only to other Adaptive Servers that support transaction coordination, set strict dtm enforcement to 1 (on). This ensures that transactions are propagated only to servers that can participate in Adaptive Servercoordinated transactions, and transactions complete in a consistent manner. If a transaction attempts to update data in a server that does not support transaction coordination services, Adaptive Server aborts the transaction.
222
CHAPTER 5
In heterogeneous environments, you may want to make use of servers that do not support transaction coordination. This includes older versions of Adaptive Server and non-Sybase database stores configured using CIS. Under these circumstances, you can set strict dtm enforcement to 0 (off). This allows Adaptive Server to propagate transactions to legacy Adaptive Servers and other data stores, but does not ensure that the remote work of these servers is rolled back or committed with the original transaction.
suspend audit when device full

Summary information Default value Range of values Status Display level Required role Configuration group 1 01 Dynamic Intermediate System Security Officer Security Related
suspend audit when device full determines what Adaptive Server does when an audit device becomes completely full.
Note If you have two or more audit tables, each on a separate device other than
the master device, and you have a threshold procedure for each audit table segment, the audit devices should never become full. Only if a threshold procedure is not functioning properly would the full condition occur. Choose one of these values: 0 truncates the next audit table and starts using it as the current audit table when the current audit table becomes full. If you set the parameter to 0, you ensure that the audit process is never suspended. However, you incur the risk that older audit records are lost if they have not been archived. 1 suspends the audit process and all user processes that cause an auditable event. To resume normal operation, the System Security Officer must log in and set up an empty table as the current audit table. During this period, the System Security Officer is exempt from normal auditing. If the System Security Officers actions would generate audit records under normal operation, Adaptive Server sends an error message and information about the event to the error log.
223
syb_sendmsg port number

Summary information Default value Valid values Status Display level Required role Configuration group 0 0, or 102465535, or system limit Dynamic Comprehensive System Administrator Network Communication
The syb_sendmsg port number parameter specifies the port number that Adaptive Server uses to send messages to a UDP (User Datagram Protocol) port with sp_sendmsg or syb_sendmsg. If more than one engine is configured, a port is used for each engine, numbered consecutively from the port number specified. If the port number is set to the default value, 0 Adaptive Server assigns port numbers.
Note Sending messages to UDP ports is not supported on Windows.
A System Security Officer must set the allow sendmsg configuration parameter to 1 to enable sending messages to UDP ports. To enable UDP messaging, a System Administrator must set allow sendmsg to 1. See allow sendmsg on page 86. For more information on UDP messaging, see sp_sendmsg in the Reference Manual.
sysstatistics flush interval

Summary information Default value Valid values Status Display level Required role Configuration group 0 Between 0 and 32767 Dynamic Comprehensive System Administrator SQL Server Administration
The sysstatiscts flush interval parameter determines the length of the interval (in minutes) between flushes of sysstatistics.
224
CHAPTER 5
Adaptive Server dynamically maintains the statistics for the number of rows and columns modified in a table as part of any DML statement and flushes them according to the value of sysstatistics flush interval. Adaptive Server uses these statistics for query optimization since they are more accurate. The datachange function determines the amount of data that is changed at the table, column, or partition level since the last update statistics, and initiates updating statistics on the object. The in-memory statistics are always flushed to disk during a polite shutdown of the server. You can configure sysstatistics flush interval to flush these inmemory statistics to disk by the house keeper task at regular intervals. Set sysstatistics flush interval to 0 to disable this housekeeper task.
systemwide password expiration

0 032767 Dynamic Intermediate System Security Officer Security Related
systemwide password expiration, which can be set only by a System Security Officer, sets the number of days that passwords remain in effect after they are changed. If systemwide password expiration is set to 0, passwords do not expire. If it is set to a number greater than 0, all passwords expire after the specified number of days. An accounts password is considered expired if an interval greater than number_of_days has passed since the last time the password for that account was changed.
When the number of days remaining before expiration is less than 25 percent of the value of systemwide password expiration or 7 days, whichever is greater, each time the user logs in, a message displays, giving the number of days remaining before expiration. Users can change their passwords anytime before expiration. When an accounts password has expired, the user can still log in to Adaptive Server but cannot execute any commands until he or she has used sp_password to change his or her password. If the System Security Officer changes the users password while the account is in sp_password-only mode, the account returns to normal after the new password is assigned.
225
This restriction applies only to login sessions established after the password has expired. Users who are logged in at the time their passwords expire are not affected until the next time they log in.
tape retention in days

Summary information Default value Range of values Status Display level Required role Configuration group 0 0365 Dynamic Intermediate System Administrator Backup/Recovery
The tape retention in days parameter specifies the number of days you intend to retain each tape after it has been used for either a database or a transaction log dump. This parameter can keep you from accidentally overwriting a dump tape. For example, if you have set tape retention in days to 7 days, and you attempt to use the tape before 7 days have elapsed since the last time you dumped to that tape, Backup Server issues a warning message. You can override the warning using the with init option when executing the dump command. Doing this causes the tape to be overwritten and all data on the tape to be lost. Both the dump database and dump transaction commands provide a retaindays option, which overrides the tape retention in days value for a particular dump. See Protecting dump files from being overwritten on page 387 for more information.
tcp no delay
1 (on) 0 (off), 1 (on) Static Comprehensive System Administrator Network Communication, O/S Resources
226
CHAPTER 5
The tcp no delay parameter controls TCP (Transmission Control Protocol) packet batching. The default value is 1, which means that TCP packets are not batched. TCP normally batches small logical packets into single larger physical packets (by briefly delaying packets) fill physical network frames with as much data as possible. This is intended to improve network throughput in terminal emulation environments where there are mostly keystrokes being sent across the network. However, applications that use small TDS (Tabular Data Stream) packets may benefit from disabling TCP packet batching. To disable TCP packet batching, set tcp no delay to 1.
Note Disabling TCP packet batching means that packets are sent, regardless
of size; this increases the volume of network traffic.
text prefetch size

Summary information Default value Valid values Status Display level Required role 16 065535 Dynamic Comprehensive System Administrator
The text prefetch size parameter limits the number of pages of text, unitext, and image data that can be prefetched into an existing buffer pool. Adaptive Server prefetches only text, unitext, and image data that was created with Adaptive Server 12.x or was upgraded using dbcc rebuild_text.
time slice
Summary information Default value Range of values Status Display level Required role 100 501000 Dynamic Comprehensive System Administrator
227
Summary information Configuration group SQL Server Administration
time slice sets the number of milliseconds that the Adaptive Server scheduler allows a task to run. If time slice is set too low, Adaptive Server may spend too much time switching between tasks, which increases response time. If it is set too high, CPU-intensive tasks may monopolize engines, which also increases response time. The default value, 100 milliseconds, allows each task to run for 1/10 of a second before relinquishing the CPU to another task.
See cpu grace time and Chapter 4, Using Engines and CPUs in the Performance and Tuning: Basics for a more detailed discussion of task scheduling. Use sp_sysmon to determine how time slice affects voluntary yields by Adaptive Server engines. See the Performance and Tuning Guide for more information.
total data cache size

0 0 2147483647 Calculated Basic System Administrator Cache Manager, Memory Use
The total data cache size parameter reports the amount of memory, in kilobytes, that is currently available for data, index, and log pages. This parameter is a calculated value that is not directly user-configurable. The amount of memory available for the data cache can be affected by a number of factors, including: The amount of physical memory available on your machine The values to which the following parameters are set:
total logical memory number of user connections total procedure cache percent
228
CHAPTER 5
number of open databases number of open objects number of open indexes number of devices
A number of other parameters also affect the amount of available memory, but to a lesser extent. For information on how Adaptive Server allocates memory and for information on data caches, see Configuration parameters on page 79.
total logical memory

N/A N/A Read-only Intermediate System Administrator Memory Use, Physical Memory
total logical memory displays the total logical memory for the current
configuration of Adaptive Server. The total logical memory is the amount of memory that Adaptive Servers current configuration uses. total logical memory displays the memory that is required to be available, but which may or may not be in use at any given moment. For information about the amount of memory in use at a given moment, see the configuration parameter total physical memory. You cannot use total logical memory to set any of the memory configuration parameters.
total physical memory

N/A N/A Read-only Intermediate System Administrator Memory Use
229
total physical memory is a read-only configuration parameter that displays the
total physical memory for the current configuration of Adaptive Server. The total physical memory is the amount of memory that Adaptive Server is using at a given moment in time. Configure Adaptive Server so that the value for max memory is larger than the value for total logical memory, and the value for total logical memory is larger than the value for total physical memory.
txn to pss ratio

Summary information Default value Valid values Status Display level Required role Configuration groups 16 1 2147483647 Static 1 System Administrator DTM Administration, Memory Use
Adaptive Server manages transactions as configurable server resources. Each time a new transaction begins, Adaptive Server must obtain a free transaction descriptor from a global pool that is created when the server is started. Transaction descriptors are internal memory structures that Adaptive Server uses to represent active transactions. Adaptive Server requires one free transaction descriptor for: The outer block of each server transaction. The outer block of a transaction may be created explicitly when a client executes a new begin transaction command. Adaptive Server may also implicitly create an outer transaction block when clients use Transact-SQL to modify data without using begin transaction to define the transaction.
Note Subsequent, nested transaction blocks, created with additional begin transaction commands, do not require additional transaction descriptors.
Each database accessed in a multi-database transaction. Adaptive Server must obtain a new transaction descriptor each time a transaction uses or modifies data in a new database.
txn to pss ratio determines the total number of transaction descriptors available to the server. At start-up, this ratio is multiplied by the number of PSS structures to create the transaction descriptor pool:
# of transaction descriptors = PSS structures * txn to pss ratio
230
CHAPTER 5
The default value, 16, ensures compatibility with earlier versions of Adaptive Server. Prior to version 12.x, Adaptive Server allocated 16 transaction descriptors for each user connection. In version 12.x and later, the number of simultaneous transactions is limited only by the number of transaction descriptors available in the server.
Note You can have as many databases in a user transaction as there are in your Adaptive Server installation. For example, if your Adaptive Server has 25 databases, you can include 25 databases in your user transactions.
Optimizing the txn to pss ratio for your system
During a peak period, use sp_monitorconfig to examine the use of transaction descriptors:
sp_monitorconfig "txn to pss ratio" Usage information at date and time: Apr 22 2002 2:49PM. Name num_free num_active pct_act Max_Used --------------------- ---------- ---------------txn to pss ratio 784 80 10.20 523 Reused -----NA
If the num_used value is zero or very low, transactions may be delayed as Adaptive Server waits for transaction descriptors to become free in the server. In this case, consider increasing the value of txn to pss ratio. If the Max_used value is too low, unused transaction descriptors may be consuming memory that can be used by other server functions. Consider reducing the value of txn to pss ratio.
unified login required (Windows only)

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Dynamic Intermediate System Security Officer Security Related
231
unified login required requires that all users who log in to Adaptive Server be authenticated by the Windows LAN Manager. The use security services parameter must be 1 to use the unified login security service.
upgrade version
upgrade version reports the version of the upgrade utility that upgraded your
master device. The upgrade utility checks and modifies this parameter during an upgrade.
Warning! Although this parameter is configurable, do not reset it. Doing so may cause serious problems with Adaptive Server.
You can determine whether an upgrade has been done on your master device by using upgrade version without specifying a value:
sp_configure "upgrade version"
use security services (Windows only)

Summary information Default value Range of values Status Display level Required role Configuration group 0 (off) 0 (off), 1 (on) Static Intermediate System Security Officer Security Related
use security services specifies that Adaptive Server will use security services provided by Windows LAN Manager. If the parameter is set to 0, unified login services with the LAN Manager cannot be used.
232
CHAPTER 5
user log cache size

Summary information Default value Range of values Status Display level Required role Configuration groups Logical page size 2048a 2147483647
a. Minimum determined by servers logical page size
Static Intermediate System Administrator Memory Use, User Environment
user log cache size specifies the size (in bytes) for each users log cache. Its size is determined by the servers logical page size. There is one user log cache for each configured user connection and worker process. Adaptive Server uses these caches to buffer the user transaction log records, which reduces the contention at the end of the transaction log.
When a user log cache becomes full or another event occurs (such as when the transaction completes), Adaptive Server flushes all log records from the user log cache to the database transaction log. By first consolidating the log records in each users log cache, rather than immediately adding each record to the databases transaction log, Adaptive Server reduces contention of processes writing to the log, especially for SMP systems configured with more than one engine.
Note For transactions using a database with mixed data and log segments, the
user log cache is flushed to the transaction log after each log record. No buffering takes place. If your databases do not have dedicated log segments, do not increase the user log cache size. Do not configure user log cache size to be larger than the maximum amount of log information written by an applications transaction. Since Adaptive Server flushes the user log cache when the transaction completes, any additional memory allocated to the user log cache is wasted. If no transaction in your server generates more than 4000 bytes of transaction log records, set user log cache size no higher than that value. For example:
sp_configure "user log cache size", 4000
Setting user log cache size too high wastes memory. Setting it too low can cause the user log cache to fill up and flush more than once per transaction, increasing the contention for the transaction log. If the volume of transactions is low, the amount of contention for the transaction log may not be significant.
233
Use sp_sysmon to understand how this parameter affects cache behavior. See the Performance and Tuning Guide for more information.
user log cache spinlock ratio

Summary information Default value Range of values Status Display level Required role Configuration groups 20 12147483647 Dynamic Intermediate System Administrator Memory Use, User Environment
For Adaptive Servers running with multiple engines, the user log cache spinlock ratio parameter specifies the ratio of user log caches per user log cache spinlock. There is one user log cache for each configured user connection. The default value for this parameter is 20, or one spinlock for each 20 user connections configured for your server. Use sp_sysmon to understand how this parameter affects cache behavior. See the Performance and Tuning Guide for more information..
wait event timing

wait event timing controls whether Adaptive Server collects statistics for
individual wait events. A task may have to wait for a variety of reasons (for example, waiting for a buffer read to complete). The monSysWaits table contains the statistics for each wait event. The monWaitEventInfo table contains a complete list of wait events.
234
CHAPTER 5
xact coordination interval

Summary information Default value Valid values Status Display level Required role Configuration group 60 (seconds) 1 2147483647 (seconds) Dynamic 10 System Administrator DTM Administration
xact coordination interval defines the length of time between attempts to resolve
transaction branches that were propagated to remote servers. The coordinating Adaptive Server makes regular attempts to resolve the work of remote servers participating in a distributed transaction. The coordinating server contacts each remote server participating in the distributed transaction in a serial manner, as shown in Figure 5-6. The coordination service may be unable to resolve a transaction branch for a variety of reasons. For example, if the remote server is not reachable due to network problems, the coordinating server reattempts the connection after the time specified by xact coordination level.
Figure 5-6: Resolving remote transaction branches
Adaptive Server Coordination Service OK Adaptive Server 2 Network Problem Adaptive Server 4
OK Adaptive Server 3
With the default value of xact coordination interval, 60, Adaptive Server attempts to resolve remote transactions once every minute. Decreasing the value may speed the completion of distributed transactions, but only if the transactions are themselves resolved in less than a minute. Under normal circumstances, there is no performance penalty to decreasing the value of xact coordination interval.
235
Setting xact coordination interval to a higher number can slow the completion of distributed transactions, and cause transaction branches to hold resources longer than they normally would. Under normal circumstances, do not increase the value of xact coordination interval beyond its default.
xp_cmdshell context
Summary information Default value Valid values Status Display level Required role Configuration group 1 0, 1 Dynamic Comprehensive System Administrator Extended Stored Procedure
The xp_cmdshell context parameter sets the security context for the operating system command to be executed using the xp_cmdshell system ESP. Setting xp_cmdshell context to 1 restricts the xp_cmdshell security context to users who have accounts at the operating system level. Its behavior is platformspecific. If xp_cmdshell context is set to 1, to use an xp_cmdshell ESP, an operating system user account must exist for the Adaptive Server user name. For example, an Adaptive Server user named sa cannot use xp_cmdshell unless he or she has an operating-system-level user account named sa. On Windows , when xp_cmdshell context is set to 1, xp_cmdshell succeeds only if the user name of the user logging in to Adaptive Server is a valid Windows user name with Windows system administration privileges on the system on which Adaptive Server is running. On other platforms, when xp_cmdshell context is set to 1, xp_cmdshell succeeds only if Adaptive Server was started by a user with superuser privileges at the operating system level. When Adaptive Server gets a request to execute xp_cmdshell, it checks the uid of the user name of the ESP requestor and runs the operating system command with the permissions of that uid. If xp_cmdshell context is 0, the permissions of the operating system account under which Adaptive Server is running are the permissions used to execute an operating system command from xp_cmdshell. This allows users to execute operating commands that they would not ordinarily be able to execute under the security context of their own operating system accounts.
236
CH A PTE R
Overview of Disk Resource Issues
This chapter discusses some basic issues that determine how you allocate and use disk resources with Adaptive Server.
Topic Device allocation and object placement Commands for managing disk resources Considerations in storage management decisions Status and defaults at installation time System tables that manage storage Page 237 238 239 241 242
Many Adaptive Server defaults are set to reasonable values for aspects of storage management, such as where databases, tables, and indexes are placed and how much space is allocated for each one. Responsibility for storage allocation and management is often centralized, and usually, the System Administrator has ultimate control over the allocation of disk resources to Adaptive Server and the physical placement of databases, tables, and indexes on those resources.
Device allocation and object placement

When configuring a new system, the System Administrator must consider several issues that have a direct impact on the number and size of disk resources required. These device allocation issues refer to commands and procedures that add disk resources to Adaptive Server. Device allocation topics are described in the chapters shown in Table 6-1.
Table 6-1: Device allocation topics Task Chapter Initialize and allocate a default pool of database devices Chapter 7, Initializing Database Devices Mirror database devices for recovery Chapter 2, Mirroring Database Devices
237
Commands for managing disk resources
After the initial disk resources have been allocated to Adaptive Server, the System Administrator, Database Owner, and object owners should consider how to place databases and database objects on specific database devices. These object placement issues determine where database objects reside on your system and whether or not the objects share devices. Object placement tasks are discussed throughout this manual, including the chapters shown in Table 62.
Table 6-2: Object placement topics Task Place databases on specific database devices Chapter Chapter 6, Creating and Managing User Databases
Place tables and indexes on specific database devices Chapter 8, Creating and Using Segments
Do not consider allocating devices separately from object placement. For example, if you decide that a particular table must reside on a dedicated pair of devices, you must first allocate those devices to Adaptive Server. The remaining sections in this chapter provide an overview that spans both device allocation and object placement issues, providing pointers to chapters where appropriate.
Commands for managing disk resources

Table 6-3 lists the major commands a System Administrator uses to allocate disk resources to Adaptive Server and provides references to the chapters that discuss those commands.
Table 6-3: Commands for allocating disk resources Command
disk init name = "dev_name" physname = "phys_name"...
Task Makes a physical device available to a particular Adaptive Server. Assigns a database device name (dev_name) that is used to identify the device in other Adaptive Server commands. Changes the dsync setting of an existing database device file. Adds dev_name to the general pool of default database space. Dynamically increases the size of database devices.
See Chapter 7, Initializing Database Devices
sp_deviceattr logicalname, optname, optvalue sp_diskdefault "dev_name"... disk resize name = device_name, size = additional_space
Chapter 7, Initializing Database Devices Chapter 7, Initializing Database Devices Chapter 7, Initializing Database Devices
238
CHAPTER 6
Command
disk mirror name = "dev_name" mirror = "phys_name"...
Task Mirrors a database device on a specific physical device.
See Chapter 2, Mirroring Database Devices
Table 6-4 lists the commands used in object placement. For information about how object placement affects performance, see Chapter 6, Controlling Physical Data Placement, in the Performance and Tuning Guide: Basics.
Table 6-4: Commands for placing objects on disk resources Command
create database...on dev_name
Task Makes database devices available to a particular Adaptive Server database. The log on clause to create database places the databases logs on a particular database device. When used without the on dev_name clause, these commands allocate space on the default database devices. Creates a segment a named collection of space from the devices available to a particular database.
See Chapter 6, Creating and Managing User Databases Chapter 6, Creating and Managing User Databases Chapter 8, Creating and Using Segments
or
alter database...on dev_name create database...
or
alter database... sp_addsegment seg_name, dbname, devname
and
sp_extendsegment seg_name, dbname, devname create table...on seg_name
or
create index...on seg_name create table...
Creates database objects, placing them on a specific segment of the databases assigned disk space. When used without on seg_name, tables and indexes occupy the general pool of space allocated to the database (the default devices).
Chapter 8, Creating and Using Segments Chapter 8, Creating and Using Segments
or
create index...
Considerations in storage management decisions

The System Administrator must make many decisions regarding the physical allocation of space to Adaptive Server databases. The major considerations in these choices are: Recovery disk mirroring and maintaining logs on a separate physical device provide two mechanisms for full recovery in the event of physical disk crashes.
239
Considerations in storage management decisions
Performance for tables or databases where speed of disk reads and writes is crucial, properly placing database objects on physical devices yields performance improvements. Disk mirroring slows the speed of disk writes.
Recovery
Recovery is the key motivation for using several disk devices. Nonstop recovery can be accomplished by mirroring database devices. Full recovery can also be ensured by storing a databases log on a separate physical device.
Keeping logs on a separate device

Unless a database device is mirrored, full recovery requires that a databases transaction log be stored on a different device from the actual data (including indexes) of a database. In the event of a hard disk crash, you can create an upto-date database by loading a dump of the database and then applying the log records that were safely stored on another device. See Chapter 6, Creating and Managing User Databases, for information about the log on clause of create database.
Mirroring
Nonstop recovery in the event of a hard disk crash is guaranteed by mirroring all Adaptive Server devices to a separate physical disk. Chapter 2, Mirroring Database Devices, describes the process of mirroring devices.
Performance
You can improve system performance by placing logs and database objects on separate devices: Placing a table on one hard disk and nonclustered indexes on another ensures that physical reads and writes are faster, since the work is split between two disk drives. Splitting large tables across two disks can improve performance, particularly for multiuser applications. When log and data share devices, user log cache buffering of transaction log records is disabled.
240
CHAPTER 6
Partitioning provides multiple insertion points for a heap table, adds a degree of parallelism to systems configured to perform parallel query processing, and makes it possible to distribute a tables I/O across multiple database devices.
See Chapter 6, Controlling Physical Data Placement, in the Performance and Tuning Guide: Basics for a detailed discussion of how object placement affects performance.
Status and defaults at installation time

You can find instructions for installing Adaptive Server in the installation documentation for your platform. The installation program and scripts initialize the master device and set up the master, model, sybsystemprocs, sybsecurity, and temporary databases for you. When you install Adaptive Server, the system databases, system-defined segments, and database devices are organized as follows: The master, model, and tempdb databases are installed on the master device. The sybsystemprocs database is installed on a device that you specified. Three segments are created in each database: system, default, and logsegment. The master device is the default storage device for all user-created databases.
Note After initializing new devices for default storage, remove the master device from the default storage area with sp_diskdefault. Do not store user databases and objects on the master device. See Designating default devices on page 256 for more information.
If you install the audit database, sybsecurity, it is located on its own device.
241
System tables that manage storage

Two system tables in the master database and two more in each user database track the placement of databases, tables (including the transaction log table, syslogs), and indexes. The relationship between the tables is illustrated in Figure 6-1.
Figure 6-1: System tables that manage storage vstart between low, high
SYSUSAGES Transactions
One row for each fragment
SYSDEVICES Transactions
1 One row for each device
Master database User database
segmap
segmap 1 segment N segment
SYSSEGMENTS Transactions
One row for each segment 1 N One row for each data or index partition
SYSINDEXES Student Info
SYSPARTITIONS Transactions
One row for each table, index or table with text
242
CHAPTER 6
The sysdevices table

The sysdevices table in the master database contains one row for each database device and may contain a row for each dump device (tape, disk, or operating system file) available to Adaptive Server. The disk init command adds entries for database devices to master..sysdevices. Dump devices, added using sp_addumpdevice, are discussed in Chapter 11, Developing a Backup and Recovery Plan.
sysdevices stores two names for each device:
A logical name or device name, used in all subsequent storagemanagement commands, is stored in the name column of sysdevices. This is usually a user-friendly name, perhaps indicating the planned use for the device, for example logdev or userdbdev. The physical name is the actual operating system name of the device. Use this name only in the disk init command; after that, all Adaptive Server data storage commands use the logical name.
Place a database or transaction log on one or more devices by specifying the logical name of the device in the create database or alter database statement. The log on clause to create database places a databases transaction log on a separate device to ensure full recoverability. The log device must also have an entry in sysdevices before you can use log on. A database can reside on one or more devices, and a device can store one or more databases. See Chapter 6, Creating and Managing User Databases, for information about creating databases on specific database devices.
The sysusages table

The sysusages table in the master database keeps track of all of the space that you assign to all Adaptive Server databases.
create database and alter database allocate new space to the database by adding a row to sysusages for each database device or device fragment. When you allocate only a portion of the space on a device with create or alter database, that portion is called a fragment. sp_addsegment, sp_dropsegment, and sp_extendsegment change the segmap column in sysusages for the device that is mapped or unmapped to a segment. Chapter 8, Creating and Using Segments, discusses these procedures in detail.
243
The syssegments table

The syssegments table, one in each database, lists the segments in a database. A segment is a collection of the database devices and fragments available to a particular database. Tables and indexes can be assigned to a particular segment and therefore to a particular physical device or can span a set of physical devices.
create database makes default entries in syssegments. sp_addsegment and sp_dropsegment to add and remove entries from syssegments.
The sysindexes table

The sysindexes table lists each table and index and the segment where each table, clustered index, nonclustered index, and chain of text pages is stored. It also lists other information such as the max_rows_per_page setting for the table or index. The create table, create index, and alter table commands create new rows in sysindexes. Partitioning a table changes the function of sysindexes entries for the table, as described in the Performance and Tuning Guide: Basics.
The syspartitions table

The syspartitions table lists each table and index partition and the segment where the partition is stored. syspartitions maintains key storage management information such as the first page of a data or index page chain, the last page of a heap, the root page of an index partition, and so on. Use create table, create index and alter table to create new rows in syspartitions.
244
CH A PTE R
Initializing Database Devices
This chapter explains how to initialize database devices and how to assign devices to the default pool of devices.
Topic What are database devices? Using the disk init command disk init syntax Getting information about devices Dropping devices Designating default devices Increasing the size of devices with disk resize Page 245 246 246 253 255 256 257
What are database devices?

A database device stores the objects that make up databases. The term device does not necessarily refer to a distinct physical device: it can refer to any piece of a disk (such as a disk partition) or a file in the file system that is used to store databases and their objects. Each database device or file must be prepared and made known to Adaptive Server before it can be used for database storage. This process is called initialization. After a database device has been initialized, it can be: Allocated to the default pool of devices for the create and alter
database commands
Assigned to the pool of space available to a user database Assigned to a user database and used to store one or more database objects Assigned to store a databases transaction logs
245
Using the disk init command
Using the disk init command

A System Administrator initializes new database devices with the disk init command, which: Maps the specified physical disk device or operating system file to a database device name Lists the new device in master..sysdevices Prepares the device for database storage
Note Before you run disk init, see the installation documentation for your platform for information about choosing a database device and preparing it for use with Adaptive Server. You may want to repartition the disks on your computer to provide maximum performance for your Sybase databases.
disk init divides the database devices into allocation units, groups of 256 logical pages. The size of the allocation unit depends on which logical page size your server is configured for (2, 4, 8, or 16K). In each allocation unit, the disk init command initializes the first page as the allocation page, which contains information about the database (if any) that resides on the allocation unit.
Warning! After you run the disk init command, dump the master database. This makes recovery easier and safer in case master is damaged. See Chapter 13, Restoring the System Databases.
disk init syntax

The syntax of disk init is:
disk init name = "device_name" , physname = "physicalname" , [vdevno = virtual_device_number ,] size = number_of_blocks [, vstart = virtual_address , cntrltype = controller_number ] [, contiguous]
246
CHAPTER 7
[, dsync = { true | false }] [, directio = {true | false}]
disk init examples

On UNIX:
disk init name = "user_disk", physname = "/dev/rxy1a", size = "64G"
On Windows NT:
disk init name = "user_disk", physname = "d:\devices\userdisk.dat", size = "64G"
Specifying a logical device name with disk init

The device_name must be a valid identifier. This name is used in the create database and alter database commands, and in the system procedures that manage segments. The logical device name is known only to Adaptive Server, not to the operating system on which the server runs.
Specifying a physical device name with disk init

The physname of the database device gives the name of a raw disk partition (UNIX), foreign device, or the name of an operating system file. On PC platforms, you typically use operating system file names for physname.
Choosing a device number for disk init

Adaptive Server accepts, but does not require, the disk init vdevno parameter. If you specify a vdevno, you may choose any currently unused identifier from 1 to 2,147,483,647 (virtual device ID 0 is used by the master device). For example, specifying vdevno = 33 assigns virtual device ID 33 to a device. If you do not specify a vdevno, Adaptive Server chooses a number higher than the highest vdevno currently listed in sysdevices. 247
disk init syntax
The number of database devices you can create is limited by the number of devices configuration parameter. Adaptive Server is initially configured for 10 devices. Use sp_configure to change this parameter if you need more devices. For more information about sp_configure, see Chapter 5, Setting Configuration Parameters. Your operating system may also limit the number of devices your installation can use concurrently. Each Sybase device counts as one open file to the operating system. Adaptive Server automatically specifies the next available identifying number for the database device. This is the virtual device number (vdevno). You need not specify this number when you issue the disk init command. If you choose to select the vdevno manually, it must be unique among the devices used by Adaptive Server. Device number 0 represents the master device. Legal numbers are 1 2,147,483,647. You can choose any unused devno within that range. To see the numbers already in use for vdevno, look in the vdevno column of the report from sp_helpdevice, or use the following query to list all the device numbers currently in use:
select vdevno from master..sysdevices where status & 2=2
Here, status 2 specifies physical disk.
Specifying the device size with disk init

You can use the following unit specifiers to indicate the size of the device: k or K indicates kilobytes, m or M indicates megabytes, g or G indicates gigabytes, and t or T indicates terabytes. Although it is optional, Sybase recommends that you always include the unit specifier in both the disk init and create database commands to avoid confusion in the actual number of pages allocated. You must enclose the unit specifier in single or double quotes or in brackets. Theoretically, you can create as many as 2,147,483,647 disk devices, each of which can be as large as 2,147,483,648 2K-blocks. Because the number and size of possible devices are effectively unlimited, the maximum installation size becomes a function of database size, hardware, and operating system limits. The following guidelines apply to the syntax for disk init:
248
CHAPTER 7
If you do not include a unit specifier for the size argument of disk init or disk reinit, size is measured, by default, in number of virtual pages. Thus, if you enter size = 15000, Adaptive Server assumes 15,000 virtual pages. A virtual page is 2048 bytes. You can increase, but not decrease, the size of an existing database device using the disk resize command. If you are planning to use the new device for the creation of a new database, the minimum size depends on the logical page size used by the server, described in Table 7-1:
Table 7-1: Minimum database sizes Logical page size 2K 4K 8K 16K Minimum database size 3 Megabytes 6 Megabytes 12 Megabytes 24 Megabytes
You cannot have a database smaller than the model database. If your model database is larger than the minimums listed above, then this is the minimum database size. Adaptive Server allocates and manages database space in allocation units, which are groups of 256 logical pages. Because the smallest size create database permits you to specify is one megabye, the size of the smallest usable database device is the larger of one MB or 256 logical pages (for a 2k or 4k logical page size, this is one megabye, for a 8k logical page size, this is 2MB, for a 16k logical page size, this is 4MB. It is helpful to keep this grouping of 256 pages in mind when you decide how large to make a device to avoid wasting space. For example, if your installation uses a 16k logical page size, specifying a device as size = '31M' leaves three megabytes wasted at the end of the device, since an allocation unit would be 4 MB. If you are initializing a raw device, determine the size of the device from your operating system, as described in the the installation documentation for your platform. Use the total size available, up to the maximum for your platform. After you have initialized the disk for use by Adaptive Server, you cannot use any space on that raw device for any other purpose.
249
disk init syntax
disk init uses size to compute the value for the high virtual page number in sysdevices.high.
Note The numbers in sysdevices.high and sysdevices.low are virtual page numbers with blocks of 2k bytes, which is Adaptive Server's unit of physical disk management. This may not be the same as your installation's logical page size.
Warning! If the physical device does not contain the number of blocks specified by the size parameter, disk init fails. If you use the optional vstart parameter, the physical device must contain the sum of the blocks specified by both the vstart and size parameters, or the command fails.
Specifying the dsync setting with disk init (optional)

For devices initialized on UNIX operating system files, the dsync setting controls whether or not writes to those files are buffered. When the dsync setting is on, Adaptive Server opens a database device file using the UNIX dsync flag. The dsync flag ensures that writes to the device file occur directly on the physical storage media, and Adaptive Server can recover data on the device in the event of a system failure. When dsync is off (false), writes to the device file may be buffered by the UNIX file system, and the recovery of data on the device cannot be ensured. Turn off dsync only when data integrity is not required, or when the System Administrator requires performance and behavior similar to earlier Adaptive Server versions.
Note The dsync setting is ignored for devices initialized on raw partitions, and for devices initialized on Windows files. In both cases, writes to the database device take place directly to the physical media.
Performance implications of dsync

The use of the dsync setting with database device files incurs the following performance trade-offs:
250
CHAPTER 7
Adaptive Server does not support asynchronous I/O on operating system files for HP-UX. If database device files on these platforms use the dsync option, the Adaptive Server engine writing to the device file blocks until the write operation completes. This can cause poor performance during update operations. When dsync is on (true), write operations to database device files may be slower compared to earlier versions of Adaptive Server (where dsync is not supported). This is because Adaptive Server must write data to disk instead of simply copying cached data to the UNIX file system buffer. In cases where highest write performance is required (but data integrity after a system failure is not required) turning dsync off yields device file performance similar to earlier Adaptive Server versions. For example, you may consider storing tempdb on a dedicated device file with dsync disabled, if performance is not acceptable while using dsync.
Response time for read operations is generally better for devices stored on UNIX operating system files as compared to devices stored on raw partitions. Data from device files can benefit from the UNIX file system cache as well as the Adaptive Server cache, and more reads may take place without requiring physical disk access.
Limitations and restrictions of dsync

The following limitations and restrictions apply to using the dsync setting:
dsync is always set to true for the master device file. You cannot change the dsync setting for the master device. If you attempt to turn dsync off for
the master device, Adaptive Server displays a warning message. If you change a device files dsync setting using the sp_deviceattr procedure, you must restart Adaptive Server before the change takes effect. When you upgrade from an Adaptive Server earlier than version 12.x, dsync is set to true for the master device file only. Use sp_deviceattr to change the dsync setting for any other device files. Adaptive Server ignores the dsync setting for database devices stored on raw partitions. Writes to devices stored on raw partitions are always done directly to the physical media.
251
disk init syntax
The directio and dsync parameters are mutually exclusive. If a device has dsync set to true, you cannot set directio to true for this device. To enable directio for a device, you must first reset dsync to false.
Using directio to bypass operating system buffer

The directio parameter for disk init, disk reinit, and sp_deviceattr allows you to configure Adaptive Server to transfer data directly to disk, bypassing the operating system buffer cache. directio performs IO in the same manner as raw devices and provides the same performance benefit as raw devices, but has the ease of use and manageability of file system devices. directio is a static parameter that requires a restart of Adaptive Server to take effect. By default, the directio option is set to false (off) for all platforms. The directio and dsync parameters are mutually exclusive. If a device has dsync set to true, you cannot set directio to true for this device. To enable directio for a device, you must first reset dsync to false.
Note Devices used for databases for which recovery is not important (for example, tempdb), may have dsync set to false. For these devices, enabling directio may have an adverse performance effect, so you should carefully review device use before you enable directio.
The following creates a device named user_disk that uses directio to write data directly to disk:
disk init name = "user_disk", physname = "/usr/u/sybase/data/userfile1.dat", size = 5120, directio = true
Initializes 10MB of a disk on a UNIX operating system file:

disk reinit name = "user_disk", physname = "/usr/u/sybase/data/userfile1.dat", size = 5120, directio = true
By default, directio is disabled for all existing devices, and you enable it with sp_deviceattr. The syntax for sp_deviceattr is:
sp_deviceattr device_name, directio, [true | false]
252
CHAPTER 7
For example, the following enables directio disk writes for the user_disk device:
sp_deviceattr user_disk, directio, true
You must reboot the server for this change to take effect.
Other optional parameters for disk init

vstart is the starting virtual address, or the offset, for Adaptive Server to begin using the database device. vstart accepts the following optional unit specifiers:
k or K (kilobytes), m or M (megabytes), g or G (gigabytes) and t or T(terabytes). The size of the offset depends on how you enter the value for vstart: If you do not specify a unit size, vstart uses 2K pages for its starting address. For example, if you specify vstart = 13, Adaptive Server uses 13 * 2K pages as the offset for the starting address. If you specify a unit value, vstart uses this as the starting address. For example, if you specify vstart = "13M", Adaptive Server sets the starting address offset at 13 megabytes.
The default value (and usually the preferred value) of vstart is 0. If the specified device does not have the sum of vstart + size blocks available, the disk init command fails. The optional cntrltype keyword specifies the disk controller. Its default value is 0. Reset it only if instructed to do so by your system administrator.
Note To perform disk initialization, the user who started Adaptive Server must
have the appropriate operating system permissions on the device that is being initialized.
Getting information about devices

sp_helpdevice provides information about the devices in the sysdevices table.
253
Getting information about devices
When used without a device name, sp_helpdevice lists all the devices available on Adaptive Server. When used with a device name, it lists information about that device. Here, sp_helpdevice is used to report information about the master device:
device_name ----------master sp_helpdevice master physical_name description -------------- -----------------------------------------d_master special, default disk, physical disk, 30 MB
status -----3
cntrltype ---------0
vdevno ------0
vp_low -----0
vpn_high ------10239
Each row in master..sysdevices describes: A dump device (tape, disk, or file) to be used for backing up databases, or A database device to be used for database storage.
The initial contents of sysdevices are operating-system-dependent. Entries in sysdevices usually include: One for the master device One for the sybsystemprocs database, which you can use to store additional databases such as pubs2 and sybsyntax, or for user databases and logs Two for tape dump devices
If you installed auditing, there is a separate device for sybsecurity. The vpn_low and vpn_high fields represent the page numbers that have been assigned to the device. For dump devices, they represent the media capacity of the device. The status field in sysdevices is a bitmap that indicates the type of device, whether a disk device is used as a default storage device when users issue a create or alter database command without specifying a database device, disk mirroring information, and dsync settings. The status bits and their meanings are listed in Table 7-2:
Table 7-2: Status bits in sysdevices Bit 1 Meaning Default disk (may be used by any create or alter database command that does not specify a location)
254
CHAPTER 7
Bit 2 4 8 16 32 64 128 256 512 2048 4096 8192 16384
Meaning Physical disk Logical disk (not used) Skip header (used with tape dump devices) Dump device Serial writes Device mirrored Reads mirrored Secondary mirror side only Mirror enabled Used internally; set after disk unmirror, side = retain Primary device needs to be unmirrored (used internally) Secondary device needs to be unmirrored (used internally) UNIX file device uses dsync setting (writes occur directly to physical media)
For more information about dump devices and sp_addumpdevice, see Chapter 11, Developing a Backup and Recovery Plan.
Dropping devices
To drop database and dump devices, use sp_dropdevice. The syntax is:
sp_dropdevice logicalname
You cannot drop a device that is in use by a database. You must drop the database first.
sp_dropdevice removes the device name from sysdevices. sp_dropdevice does not remove an operating system file: it only makes the file inaccessible to Adaptive Server. You must use operating system commands to delete a file after using sp_dropdevice.
255
Designating default devices
Designating default devices

To create a pool of default database devices to be used by all Adaptive Server users for creating databases, use sp_diskdefault after the devices are initialized. sp_diskdefault marks these devices in sysdevices as default devices. Whenever users create (or alter) databases without specifying a database device, new disk space is allocated from the pool of default disk space. The syntax for sp_diskdefault is:
sp_diskdefault logicalname, {defaulton | defaultoff}
You are most likely to use the defaultoff option to remove the master device from the pool of default space:
sp_diskdefault master, defaultoff
The following designates sprocdev, the device that holds the sybsystemprocs database, a default device:
sp_diskdefault sprocdev, defaulton
Adaptive Server can have multiple default devices. They are used in the order in which they appear in the sysdevices table (that is, alphabetical order). When the first default device is filled, the second default device is used, and so on.
Note After initializing a set of database devices, you may want to assign them
to specific databases or database objects rather than adding them to the default pool of devices. For example, you may want to make sure a table never grows beyond the size of a particular device.
Choosing default and nondefault devices

sp_diskdefault lets you plan space usage carefully for performance and
recovery, while allowing users to create or alter databases. Make sure these devices are not default devices: The master device (use sp_diskdefault to set defaultoff after adding user devices) The device for sybsecurity Any device intended solely for logs Devices where high-performance databases reside
256
CHAPTER 7
You can use the device that holds sybsystemprocs for other user databases.
Note If you are using disk mirroring or segments, exercise caution in deciding which devices you add to the default list with sp_diskdefault. In most cases, devices that are to be mirrored or databases that contain objects placed on segments should allocate devices specifically, rather than being made part of default storage.
Increasing the size of devices with disk resize

The disk resize command allows you to increase the size of your database devices dynamically, rather than initializing a new device. For example, if /sybase/testdev.dat requires an additional 10MB of space, you can run disk resize and allocate this amount of space to the device. The create and alter database commands can use this added space. You can use disk resize to increase the size for both devices on raw partitions and for file systems. The minimum amount of space by which you can increase a device is 1MB or an allocation unit, whichever is greater. You cannot use disk resize on dump or load devices. Any properties that are set on the device continue to be set after you increase its size. That is, if a device has dsync set before you increase its size, it has dsync set afterwards. Also, any access rights that were set before you increased the size of the device remain set. A user with the sa role can execute the disk resize command, which: Updates the high value in master....sysdevices, and Prepares the additional space for database storage.
You can use audit trails on disk resize to track the number of times a device is resized. The device being resized is always online and available for users during the resize operation. See Chapter 7, Commands in the Reference Manual for syntax information about disk resize.
257
Insufficient disk space

During the physical initialization of the disk, if an error occurs due to insufficient disk space, disk resize extends the database device to the largest size possible before the error occurs. For example, on a server that uses 4K logical pages, if you try to increase the size of the device by 40MB, but only 39.5MB is available, the device is extended only by 39.5MB.
Device shrinkage
You cannot decrease the size of a device with disk resize.
disk resize syntax

disk resize has the following syntax:
disk resize name = device_name, size = additional_space
Where device_name is the name of the device you are increasing and additional_space is the additional disk space you are adding to this device. You must have already initialized the device with disk init. device_name must refer to a valid logical device name. The minimum size for disk resize is 1MB or one allocation unit, whichever is greater. You must disable mirroring while the resize operation is in progress. You can reestablish mirroring when the resize operation is complete.
Page size 2K 4K 8K 16K Allocation unit size 0.5MB 1MB 2MB 4MB Minimum incremental size 1MB 1MB 2MB 4MB
Note The new size of the device is the sum of the old device size plus the size specified in the disk resize command.
258
CHAPTER 7
Disk resize example

For example, the configuration of the device testdev from isql:
sp_helpdevice testdev device_name physical_name description status cntrltype vdevno vpn_low vpn_high ----------- ------------------------------------- --------- -------------------------------------testdev /sybase/dev/testdev.dat special, dsync on, directio off, physical disk, 10.00MB 16386 0 1 0 5119
To increase the size of testdev by 4MB using disk resize, enter:

disk resize name = "test_dev", size = "4M"
testdev.dat is now 14MB:

sp_helpdevice testdev device_name physical_name description status cntrltype vdevno vpn_low vpn_high ----------- ------------------------------------- --------- -------------------------------------testdev /sybase/dev/testdev.dat special, dsync on, directio off, physical disk, 14.00MB 16386 0 1 0 7167
Specifying a logical device name with disk resize

The device_name must have a valid identifier. The device should have already been initialized using the disk init command and it must refer to a valid Adaptive Server device.
Specifying the device size with disk resize

You can use the following unit specifiers to indicate the size of the device: k or K to indicate kilobytes, m or M to indicate megabytes, g or G to indicate gigabytes, and t or T to indicate terabytes.
259
Although it is optional, Sybase recommends that you always include the unit specifier with the disk resize command to avoid confusion in the actual number of pages allocated. You must enclose the unit specifier in single or double quotes. If you do not use a unit specifier, the size defaults to the number of disk pages. To verify the new size, use sp_helpdevice.
260
CH A PTE R
Setting Database Options
This chapter describes how to use database options.

Topic What are database options? Using the sp_dboption procedure Database option descriptions Changing database options Viewing the options on a database Page 261 261 262 270 271
What are database options?

Database options control: The behavior of transactions Defaults for table columns Restrictions to user access Performance of recovery and bcp operations Log behavior
The System Administrator and the Database Owner can use database options to configure the settings for an entire database. Database options differ from sp_configure parameters, which affect the entire server, and set options, which affect only the current session or stored procedure.
Using the sp_dboption procedure

Use sp_dboption to change settings for an entire database. The options remain in effect until they are changed. sp_dboption:
261
Database option descriptions
Displays a complete list of the database options when it is used without a parameter Changes a database option when used with parameters
You can change options for user databases only. You cannot change options for the master database. To change a database option in a user database (or to display a list of the database options), execute sp_dboption while using the master database. The syntax is:
sp_dboption [dbname, optname, {true | false}]
To make an option or options take effect for every new database, change the option in the model database.

All users with access to the master database can execute sp_dboption with no parameters to display a list of the database options. The report from sp_dboption looks like this:
sp_dboption Settable database options. -------------------abort tran on log full allow nulls by default async log service auto identity dbo use only ddl in tran delayed commit disable alias access identity in nonunique index no chkpt on recovery no free space acctg read only select into/bulkcopy/pllsort single user trunc log on chkpt trunc. log on chkpt. unique auto_identity index
262
CHAPTER 8
For a report on which options have been set in a particular database, execute sp_helpdb in that database. The following sections describe each database option in detail.
abort tran on log full

abort tran on log full determines the fate of a transaction that is running when the last-chance threshold is crossed. The default value is false, meaning that the transaction is suspended and is awakened only when space has been freed. If you change the setting to true, all user queries that must write to the transaction log are killed until space in the log has been freed.
allow nulls by default

Setting allow nulls by default to true changes the default null type of a column from not null to null, in compliance with the SQL standard. The Transact-SQL default value for a column is not null, meaning that null values are not allowed in a column unless null is specified in the create table or alter table column definition. You cannot use allow nulls by default to change the nullibility of a column during select into statements. Instead, use convert to specify the nullibility of the resulting columns.
asynch log service

Enabling async log service (ALS) allows for greater scalability in Adaptive Server, providing higher throughput in logging subsystems for high-end symmetric multiprocessor systems. You can enable ALS on any specified database that has at least one of the following performance issues, so long as your systems runs 4 or more online engines.
263
auto identity
While the auto identity option is true, a 10-digit IDENTITY column is defined in each new table that is created without specifying either a primary key, a unique constraint, or an IDENTITY column. This IDENTITY column is created only when you issue a create table command, not when you issue a select into. The column is not visible when you select all columns with the select * statement. To retrieve it, you must explicitly mention the column name, SYB_IDENTITY_COL, in the select list. To set the precision of the automatic IDENTITY column, use the size of auto identity configuration parameter. Though you can set auto identity to true in tempdb, it is not recognized or used, and temporary tables created there do not automatically include an IDENTITY column.
dbo use only

While dbo use only is set to true (on), only the Database Owner can use the database.
ddl in tran
Setting ddl in tran to true allows these commands to be used inside a user-defined transaction:
alter table (clauses other than partition and unpartition are allowed) create default create index create procedure create rule create schema create table create trigger create view drop default
264
CHAPTER 8
drop index drop procedure drop rule drop table drop trigger drop view grant revoke
Data definition statements lock system tables for the duration of a transaction, which can result in performance problems. Use them only in short transactions. These commands cannot be used in a user-defined transaction under any circumstances:
alter database alter table...partition alter table...unpartition create database disk init dump database dump transaction drop database load transaction load database select into truncate table update statistics
265
delayed commit
The delayed_commit parameter allows you to determine when log records are written to disk. With the delayed_commit parameter set to true, the log records are asynchronously written to the disk and control is returned to the client without waiting for the IO to complete. This improves the response time for the transactions for which the delayed_commit parameter is enabled.
identity in nonunique index

identity in nonunique index automatically includes an IDENTITY column in a tables index keys so that all indexes created on the table are unique. This database option makes logically nonunique indexes internally unique and allows those indexes to be used to process updatable cursors and isolation level 0 reads.
The table must already have an IDENTITY column for the identity in nonunique index option to work either from a create table statement or from setting the auto identity database option to true before creating the table. Use identity in nonunique index if you plan to use cursors and isolation level 0 reads on tables that have nonunique indexes. A unique index ensures that the cursor is positioned at the correct row the next time a fetch is performed on that cursor. Do not confuse the identity in nonunique index option with unique auto_identity index, which is used to add an IDENTITY column with a unique, nonclustered index to new tables.
no chkpt on recovery
no chkpt on recovery is set to true (on) when an up-to-date copy of a database is kept. In these situations, there is a primary database and a secondary database. Initially, the primary database is dumped and loaded into the secondary database. Then, at intervals, the transaction log of the primary database is dumped and loaded into the secondary database.
266
CHAPTER 8
If this option is set to false (off)the defaulta checkpoint record is added to the database after it is recovered by restarting Adaptive Server. This checkpoint, which ensures that the recovery mechanism is not re-run unnecessarily, changes the sequence number of the database. If the sequence number of the secondary database has been changed, a subsequent dump of the transaction log from the primary database cannot be loaded into it. Turning this option on for the secondary database causes it to not get a checkpoint from the recovery process so that subsequent transaction log dumps from the primary database can be loaded into it.
no free space acctg

no free space acctg suppresses free-space accounting and execution of threshold actions for the non-log segments. This speeds recovery time because the free-space counts are not recomputed for those segments. It disables updating the rows-per-page value stored for each table, so system procedures that estimate space usage may report inaccurate values.
read only
read only means that users can retrieve data from the database, but cannot
modify anything.
select into/bulkcopy/pllsort
select into/bulkcopy/pllsort must be set to on to perform operations that do not keep a complete record of the transaction in the log, which include:
Using the writetext utility. Doing a select into a permanent table. Doing a fast bulk copy with bcp. By default, fast bcp is used on tables that do not have indexes. Performing a parallel sort.
267
Adaptive Server performs minimal logging for these commands, recording only page allocations and deallocations, but not the actual changes made to the data pages. You do not have to set select into /bulkcopy/pllsort on to select into a user database when you issue the select into command to a temporary table. This is because temporary tables are created on tempdb and tempdb is never recovered. Additionally, you need not set the option to run bcp on a table that has indexes, because inserts are logged. After you have run select into or performed a bulk copy in a database, you cannot perform a regular transaction log dump. After you have made minimally logged changes to your database, you must perform a dump database, since changes are not recoverable from transaction logs. Setting select into/bulkcopy/pllsort does not block log dumping, but making minimally logged changes to data does block the use of a regular dump transaction. However, you can still use dump transaction...with no_log and dump transaction...with truncate_only. By default, select into/bulkcopy/pllsort is turned off in newly created databases. To change the default, turn this option on in the model database.
single user
When single user is set to true, only one user at a time can access the database. You cannot set single user to true in tempdb.
trunc log on chkpt

When trunc log on chkpt is true (on), the transaction log is truncated (committed transactions are removed) when the checkpoint checking process occurs (usually once per minute), if 50 or more rows have been written to the log. The log is not truncated if less than 50 rows were written to the log, or if the Database Owner runs the checkpoint command manually. You may want to turn this option on while doing development work during which backups of the transaction log are not needed. If this option is off (the default), and the transaction log is never dumped, the transaction log continues to grow, and you may run out of space in your database.
268
CHAPTER 8
When trunc log on chkpt is on, you cannot dump the transaction log because changes to your data are not recoverable from transaction log dumps. Use dump database instead. By default, the trunc log on chkpt option is off in newly created databases. To change the default, turn this option on in the model database.
Warning! If you set trunc log on chkpt on in model, and you need to load a set of database and transaction logs into a newly created database, be sure to turn the option off in the new database.
unique auto_identity index

When the unique auto_identity index option is set to true, it adds an IDENTITY column with a unique, nonclustered index to new tables. By default, the IDENTITY column is a 10-digit numeric datatype, but you can change this default with the size of auto identity column configuration parameter. Though you can set unique auto_identity index to true in tempdb, it is not recognized or used, and temporary tables created there do not automatically include an IDENTITY column with a unique index. The unique auto_identity index option provides a mechanism for creating tables that have an automatic IDENTITY column with a unique index that can be used with updatable cursors. The unique index on the table ensures that the cursor is positioned at the correct row after a fetch. (If you are using isolation level 0 reads and need to make logically nonunique indexes internally unique so that they can process updatable cursors, use the identity in nonunique index option.) In some cases, the unique auto_identity index option can avoid the Halloween problem for the following reasons: Users cannot update an IDENTITY column; hence, it cannot be used in the cursor update. The IDENTITY column is automatically created with a unique, nonclustered index so that it can be used for the updatable cursor scan.
For more information about the Halloween Problem, IDENTITY columns, and cursors, see the Transact-SQL Users Guide.
269
Changing database options
Do not confuse the unique auto_identity index option with the identity in nonunique index option, which is used to make all indexes in a table unique by including an IDENTITY column in the tables index keys.
Changing database options

Only a System Administrator or the Database Owner can change a users database options by executing sp_dboption. Users aliased to the Database Owner cannot change database options with sp_dboption. You must be using the master database to execute sp_dboption. Then, for the change to take effect, you must issue the checkpoint command while using the database for which the option was changed. Remember that you cannot change any master database options. To change pubs2 to read-only:
use master sp_dboption pubs2, "read only", true
sp_dboption run checkpoint automatically. For the optname parameter of sp_dboption, Adaptive Server understands any unique string that is part of the option name. To set the trunc log on chkpt option:
use master sp_dboption pubs2, trunc, true
If you enter an ambiguous value for optname, an error message is displayed. For example, two of the database options are dbo use only and read only. Using only for the optname parameter generates a message because it matches both names. The complete names that match the string supplied are printed out so that you can see how to make the optname more specific. You can turn on more than one database option at a time. You cannot change database options inside a user-defined transaction.
270
CHAPTER 8
Viewing the options on a database

Use sp_helpdb to determine the options that are set for a particular database. sp_helpdb lists each active option in the status column of its output. The following example shows that the read only option is turned on in mydb:
sp_helpdb mydb name ----mydb db_size ------20.0 MB owner ----sa dbid ---5 created -----------Mar 05, 2005 status ------------------read only free kbytes ----------1792
device_fragments ----------------master
size usage ------ -----------10.0 MB data and log
created -------Mar 05 2005
device -----------------------------master master master
segment -----------------------------default logsegment system
To display a summary of the options for all databases, use sp_helpdb without specifying a database:
sp_helpdb name db_size owner dbid created status -------------------- ----- --------------------------------master 48.0 MB sa 1 Apr 12, 2005 mixed log and data model 8.0 MB sa 3 Apr 12, 2005 mixed log and data pubs2 20.0 MB sa 6 Apr 12, 2005 select into/ bulkcopy/pllsort, trunc log on chkpt, mixed log and data sybsystemdb 8.0 MB sa 5 Apr 12, 2005 mixed log and data sybsystemprocs 112.0 MB sa 4 Apr 12, 2005 trunc log on chkpt, mixed log and data tempdb 8.0 MB sa 2 Apr 12, 2005 select into/ bulkcopy/pllsort, trunc log on chkpt, mixed log and data
271
Viewing the options on a database
272
CH A PTE R
Configuring Character Sets, Sort Orders, and Languages
This chapter discusses Adaptive Server internationalization and localization support issues.
Topic Understanding internationalization and localization Advantages of internationalized systems A sample internationalized system Elements of an internationalized system Selecting the character set for your server Selecting the sort order Selecting a language for system messages Setting up your server: examples Changing the character set, sort order, or message language Installing date strings for unsupported languages Internationalization and localization files Page 273 274 275 277 277 287 294 296 298 308 309
Understanding internationalization and localization

Internationalization is the process of enabling an application to support multiple languages and cultural conventions. An internationalized application uses external files to provide languagespecific information at execution time. Because it contains no languagespecific code, an internationalized application can be deployed in any native language environment without code changes. A single version of a software product can be adapted to different languages or regions, conforming to local requirements and customs without engineering changes. This approach to software development saves significant time and money over the lifetime of an application.
273
Advantages of internationalized systems
Localization is the process of adapting an internationalized product to meet the requirements of one particular language or region, for example Spanish, including providing translated system messages; translations for the user interface; and the correct formats for date, time, and currency. One version of a software product may have many localized versions. Sybase provides both internationalization and localization support. Adaptive Server includes the character set definition files and sort order definition files required for data processing support for the major business languages in Western Europe, Eastern Europe, the Middle East, Latin America, and Asia. Sybase Language Modules provide translated system messages and formats for Chinese (Simplified), French, German, Japanese, Korean, Brazilian Portuguese, and Spanish. By default, Adaptive Server comes with U.S. English message files. This chapter describes the available character sets and language modules and summarizes the steps necessary to change the default character set, sort order, or message language for Adaptive Server.
Advantages of internationalized systems

The task of designing an application to work outside its country of origin can seem daunting. Often, programmers think that internationalizing means hardcoding dependencies based on cultural and linguistic conventions for just one country. A better approach is to write an internationalized application: that is, one that examines the local computing environment to determine what language to use and loads files containing language-specific information at runtime. When you use an internationalized application, a single application can be deployed in all countries. This has several advantages: You write and maintain one application. The application can be deployed, without change, in new countries as needed. You need only supply the correct localization files. All sites can expect standard features and behavior.
274
CHAPTER 9
A sample internationalized system

An internationalized system may include internationalized client applications, gateways, and servers running on different platforms in different native language environments. For example, an international system might include the following components: Order processing applications in New York City, Mexico City, and Paris (Client-Library applications) An inventory control server in Germany (Adaptive Server) An order fulfillment server in France (Adaptive Server) A central accounting application in Japan (an Open Server application working with an Adaptive Server)
In this system, the order processing applications: Query the inventory control server to determine if requested items are in stock Place orders with the order fulfillment server Send financial information to the accounting application
The inventory control server and the order fulfillment server respond to queries, and the accounting application collects financial data and generates reports. The system looks like this:
275
A sample internationalized system
Figure 9-1: Example of an international system
Order processing New York City (PC) English
Order fulfillment France
Order processing Mexico City (UNIX) Spanish
Inventory control Germany
Order processing Paris (Mac) French
Accounting gateway Japan
Account server Japan
In this example, all applications and servers use local languages and character sets to accept input and output messages.
276
CHAPTER 9
Elements of an internationalized system

There are three elements that you can manipulate to configure your server language in an internationalized environment. Sybase suggests that you review these three elements and carefully plan the client/server network you want to create. Character set the language in which the server sends and receives data to and from the client servers. Select the character set after carefully planning and analyzing the language needs of all client servers. Sort order sort order options are dependent on the language and character set you select. System messages messages display in one of several languages provided by Sybase. If your server language is not one of the languages provided, your system messages display in English, the default.
The following sections provide details about each of these elements.
Selecting the character set for your server

All data is encoded in your server in a special code. For example, the letter a is encoded as 97 in decimal. A character set is a specific collection of characters (including alphabetic and numeric characters, symbols, and nonprinting control characters) and their assigned numerical values, or codes. A character set generally contains the characters for an alphabet, for example, the Latin alphabet used in the English language, or a script such as Cyrillic used with languages such as Russian, Serbian, and Bulgarian. Character sets that are platform-specific and support a subset of languages, for example, the Western European languages, are called native or national character sets. All character sets that come with Adaptive Server, except for Unicode UTF-8, are native character sets.
277
A script is a writing system, a collection of all the elements that characterize the written form of a human languagefor example, Latin, Japanese, or Arabic. Depending on the languages supported by an alphabet or script, a character set can support one or more languages. For example, the Latin alphabet supports the languages of Western Europe (see Group 1 in Table 9-1 on page 279). On the other hand, the Japanese script supports only one language, Japanese. Therefore, the Group 1 character sets support multiple languages, while many character sets, such as those in Group 101, support only one language. The language or languages that are covered by a character set is called a language group. A language group can contain many languages or only one language; a native character set is the platform-specific encoding of the characters for the language or languages of a particular language group. Within a client/server network, you can support data processing in multiple languages if all the languages belong to the same language group (see Table 91 on page 279). For example, if data in the server is encoded in a Group 1 character set, you could have French, German, and Italian data and any of the other Group 1 languages in the same database. However, you cannot store data from another language group in the same database. For example, you cannot store Japanese data with French or German data. Unlike the native character sets just described, Unicode is an international character set that supports over 650 of the worlds languages, such as Japanese, Chinese, Russian, French, and German. Unicode allows you to mix different languages from different language groups in the same server, no matter what the platform. See Unicode on page 280 for more information. Since all character sets support the Latin script, and therefore English, a character set always supports at least two languagesEnglish and one other language. Many languages are supported by more than one character set. The character set you install for a language depends on the clients platform and operating system. Adaptive Server supports the following languages and character sets:
278
CHAPTER 9
Table 9-1: Supported languages and character sets Language group Group 1 Languages Albanian, Catalan, Danish, Dutch, English, Faeroese, Finnish, French, Galician, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish Eastern European: Croatian, Czech, Estonian, Hungarian, Latvian, Lithuanian, Polish, Romanian, Slovak, Slovene (and English) Baltic (and English) Cyrillic: Bulgarian, Byelorussian, Macedonian, Russian, Serbian, Ukrainian (and English)
Western European:
Character sets ASCII 8, CP 437, CP 850, CP 860, CP 863, CP 1252a , ISO 8859-1, ISO 8859-15, Macintosh Roman, ROMAN8, ROMAN9, ISO15, CP 858 CP 852, CP 1250, ISO 8859-2, Macintosh Central European CP 1257 CP 855, CP 866, CP 1251, ISO 8859-5, Koi8, Macintosh Cyrillic CP 864, CP 1256, ISO 8859-6 CP 869, CP 1253, GREEK8, ISO 8859-7, Macintosh Greek CP 1255, ISO 8859-8 CP 857, CP 1254, ISO 8859-9, Macintosh Turkish, TURKISH8 CP 932 DEC Kanji, EUC-JIS, Shift-JIS CP 936, EUC-GB, GB18030 Big 5, CP 950b , EUC-CNS, Big 5 HKSCS EUC-KSC, cp949 CP 874, TIS 620 CP 1258 UTF-8
Group 2
Group 4 Group 5 Group 6 Group 7 Group 8 Group 9 Group 101 Group 102 Group 103 Group 104 Group 105 Group 106 Unicode
Arabic (and English) Greek (and English) Hebrew (and English) Turkish (and English) Japanese (and English) Simplified Chinese (PRC) (and English) Traditional Chinese (ROC) (and English) Korean (and English) Thai (and English) Vietnamese (and English) Over 650 languages
a. CP 1252 is identical to ISO 8859-1 except for the 0x800x9F code points which are mapped to characters in CP 1252. b. CP 950 is identical to Big 5.
279
Note The English language is supported by all character sets because the first
128 (decimal) characters of any character set include the Latin alphabet (defined as ASCll-7). The characters beyond the first 128 differ between character sets and are used to support the characters in different native languages. For example, code points 0-127 of CP 932 and CP 874 both support English and the Latin alphabet. However, code points 128-255 support Japanese characters in CP 932 and code points 128-255 support Thai characters in CP 874.
Note iso_1 and ISO 8859-1 are different names for the same character set.
The following character sets support the European currency symbol, the euro: CP 1252 (Western Europe); CP 1250 (Eastern Europe); CP 1251 (Cyrillic); CP 1256 (Arabic); CP 1253 (Greek); CP 1255 (Hebrew); CP 1254 (Turkish); CP 874 (Thai); iso15, roman9 and CP858. Unicode UTF-8 also supports: Traditional Chinese on the Windows and Solaris platforms Arabic, Hebrew, Thai, and Russian on the Linux platform
To mix languages from different language groups you must use Unicode. If your server character set is Unicode, you can support more than 650 languages in a single server and mix languages from any language group.
Unicode
Unicode is the first character set that enables all the worlds languages to be encoded in the same data set. Prior to the introduction of Unicode, if you wanted to store data in, for example, Chinese, you had to choose a character set appropriate for that languageto the exclusion of most other languages. It was either impossible or impractical to mix character sets, and thus diverse languages, in the same data set. Sybase supported Unicode in the form of three datatypes: unichar, univarchar, and unitext. These datatypes store data in the UTF-16 encoding of Unicode.
280
CHAPTER 9
UTF-16 is an encoding wherein Unicode scalar values are represented by a single 16-bit value (or, in rare cases, as a pair of 16-bit values). The three encodings are equivalent insofar as either encoding can be used to represent any Unicode character. The choice of UTF-16 datatypes, rather than a UTF-16 server default character set, promotes easy, step-wise migration for existing database applications. Adaptive Server supports Unicode literals in SQL queries and a wide range of sort orders for UTF-8. The character set model used by Adaptive Server is based on a single, configurable, server-wide character set. All data stored in Adaptive Server, using any of the character datatypes (char, varchar, nchar, nvarchar, and text), is interpreted as being in this character set. Sort orders are defined using this character set, as are language modulescollections of server messages translated into local languages. During the connection dialog, a client application declares its native character set and language. If properly configured, the server thereafter attempts to convert any character data between its own character set and that of the client (character data includes any data stored in the database, as well as server messages in the clients native language).This works well as long as the servers and clients character sets are compatible. It does not work well when characters are not defined in the other character set, as is the case for the character sets SJIS, used for Japanese, and KOI8, used for Russian and other Cyrillic languages. Such incompatibilities are the reason for Unicode, which can be thought of as a character superset, including definitions for characters in all other character sets. The Unicode datatypes unichar, univarchar, and unitext are completely independent of the traditional character set model. Clients send and receive Unicode data independently of whatever other character data they send and receive.
Character set installation

Adaptive Server version 12.5.1 and later supports the 4-byte form of UTF-8. This form is used to represent the same rare Unicode characters that are represented in UTF-16 by pairs of 16-bit values (surrogate pairs). Prior to Adaptive Server version 12.5.1, only the 3-byte forms of UTF-8 were supported. If you have installed the UTF-8 character set in an Adaptive Server server earlier than version 12.5.1, you should reinstall it to enable the use of the 4-byte form of UTF-8.
281
The UTF-16 encoding of Unicode includes surrogate pairs, which are pairs of 16-bit values that represent infrequently used characters. Additional checking is built in to Adaptive Server to ensure the integrity of surrogate pairs. You can switch this checking off by setting the configuration parameter enable surrogate processing to 0. This yields slightly higher performance, although the integrity of surrogate pairs is no longer guaranteed. Unicode also defines normalization, which is the process by which all possible representations of a single character are transformed into a single representation. Many base characters followed by combining diacritical marks are equivalent to precomposed characters, although their bit patterns are different. For example, the following two sequences are equivalent:
0x00E9 -- (LATIN SMALL LETTER E WITH ACUTE) -- e (LATIN SMALL LETTER E), (COMBINING ACUTE ACCENT)
0x00650301
The enable unicode normalization configuration parameter controls whether or not Adaptive Server normalizes incoming Unicode data. Significant performance increases are possible when the default Unicode sortorder is set to binary and the enable Unicode normalization configuration parameter is set to 1. This combination allows Adaptive Server to make several assumptions about the nature of the Unicode data, and code has been implemented to take advantage of these assumptions.
Functions
All built-in functions taking char parameters have been overloaded to accept unichar as well. Built-in functions with more than one parameter, when called with at least one unichar parameter, results in implicit conversion of any non-unichar parameters to unichar. To guarantee the integrity of surrogate pairs when enable surrogate processing is set to 1 (the default), the string functions do not allow surrogate pairs to be split. Positions are modified to fall at the beginning of a surrogate pair. Several functions have been added to round out the unichar support. Included are the functions to_unichar() and uscalar(), which are analogous to char() and ascii(). The functions uhighsurr() and ulowsurr() allow the explicit handling of surrogate pairs in user code. There are restrictions when using unitext with functions. For information , see the restriction description under the Usage section for each function.
282
CHAPTER 9
Using unichar columns

When using the isql or bcp utilities, Unicode values display in hexadecimal form unless the -Jutf8 flag is used, indicating the clients character set is UTF-8. In this case, the utility converts any Unicode data it receives from the server into UTF-8. For example:
% isql -Usa -P -Jiso_1 1> select unicode_name from people where unicode_name = 'Jones' 2> go unicode_name ------------------------------------------------------------------| 0x004a006f006e00650073 (1 row affected)
whereas:
% isql -Usa -P -Jutf8 1> select unicode_name from people where unicode_name = 'Jones' 2> go unicode_name -----------------------------------------------------------------Jones (1 row affected)
This facilitates ad hoc queries. Not all terminal windows are capable of displaying the full repertoire of Unicode characters, but simple tests involving ASCII characters are greatly simplified.
Using unitext
The variable-length unitext datatype can hold up to 1,073,741,823 Unicode characters (2,147,483,646 bytes). You can use unitext anywhere you use the text datatype, with the same semantics. unitext columns are stored in UTF-16 encoding, regardless of the Adaptive Server default character set.
Open Client interoperability

The Open Client libraries support the datatype cs_unichar, which can be bound to user variables declared as an array of short integers. This Open Client datatype interfaces directly with the servers unichar, unitext, and univarchar.
283
Java interoperability
The internal JDBC driver efficiently transfers unichar data between SQL and Java contexts. Going from SQL to Java, the class java.sql.ResultSet provides a number of get methods to retrieve data from the columns of a result set. Any of these get methods work with columns defined as unichar, unitext, or univarchar. The method getString() is particularly efficient since no conversion needs to be performed. Use the setString() method of the class java.sql.PreparedStatement to go from Java to SQL. The internal JDBC driver copies Java string data directly into the SQL parameter defined as unichar, unitext, or univarchar. The external JDBC driver (jConnect) has been modified to support the same seamless interface as the internal driver.
Limitations
Due to the lack of a Unicode-based language parser in previous releases of Adaptive Server, a restriction was imposed on the use of the new Unicode datatypes. To use the new datatypes, the server required its default character set to be configured as UTF-8. This restriction has been removed in Adaptive Server release 12.5.1 and later. Unicode datatypes can be used regardless of the servers default character set.
Selecting the server default character set

When you configure your server, you must specify a default character set for the server. The default character set is the character set in which the server stores and manipulates data. Each server can have only one default character set. By default, the installation tool assumes that the native character set of the platform operating system is the servers default character set. However, you can select any character set supported by Adaptive Server as the default on your server (see Table 9-1 on page 279). For example, if you are installing the server on IBM RS/6000 running AIX, and you select one of the Western European languages to install, the installation tool assumes the default character set to be ISO 8859-1.
284
CHAPTER 9
If you are installing a Unicode server, select UTF8 as your default character set. For non-Unicode servers, determine what platform most of your client systems use and use the character set for this platform as the default character set on the server. This has two advantages: The number of unmappable characters between character sets is minimized. Since there is usually not a complete one-to-one mapping between the characters in two character sets, there is a potential for some data loss. This is usually minor because most nonconverted characters are special symbols that are not commonly used or are specific to a platform. This minimizes the character set conversion that is required. When the character set on the client system differs from the default character set on the server, data must be converted in order to ensure data integrity. Although the measured performance decrease that results from character set conversion is insignificant, it is good practice to select the default character set that results in the fewest conversions. For example, if most of your clients use CP 850, specify CP 850 on your server. You can do this even if your server is on an HP-UX system (where its native character set for the Group 1 languages is ROMAN8).
Note Sybase strongly recommends that you decide which character set to use as your default before you create any databases or make any changes to the Sybase-supplied databases.
In the example below (Figure 9-2), 175 clients all access the same Adaptive Server. The clients are on different platforms and use different character sets. The critical factor that allows these clients to function together is that all of the character sets in the client/server system belong to the same language group (see Table 9-1 on page 279). The default language for the Adaptive Server is CP 850, which is the character set used by the largest number of clients. This allows the server to operate most efficiently, with the least amount of character set conversion.
285
Figure 9-2: Clients using different character sets in the same language group
CP 850
100 Clients
ASE CP 850 ISO 8859-1
50 Clients
Macintosh Roman
25 Clients
To help you choose the default character set for your server, the following tables list the most commonly used character sets by platform and language.
286
CHAPTER 9
Table 9-2: Popular Western European client platforms Platform Win 95, 98 Win NT 4.0 Win 2000 Sun Solaris HP-UX 10,11 IBM AIX 4.x Language U.S. English, Western Europe U.S. English, Western Europe U.S. English, Western Europe U.S. English, Western Europe U.S. English, Western Europe U.S. English, Western Europe Character set CP 1252 CP 1252 CP 1252 ISO 8859-1 ROMAN8 ISO 8859-1
Table 9-3: Popular Japanese client platforms Platform Win 95, 98 Win NT 4.0 Win 2000 Sun Solaris HP-UX 10,11 IBM AIX 4.x Language Japanese Japanese Japanese Japanese Japanese Japanese Character set CP 932 for Windows CP 932 for Windows CP 932 for Windows EUC-JIS EUC-JIS EUC-JIS
Table 9-4: Popular Chinese client platforms Platform Win 95, 98 Win NT 4.0 Win 2000 Sun Solaris HP-UX 10,11 IBM AIX 4.x Language Chinese (simplified) Chinese (simplified) Chinese (simplified) Chinese (simplified) Chinese (simplified) Chinese (simplified) Character set CP 936 for Windows CP 936 for Windows CP 936 for Windows EUC-GB EUC-GBS EUC-GB
Selecting the sort order

Different languages sort the same characters differently. For example, in English, Cho would be sorted before Co, whereas in Spanish, the opposite is true. In German, is a single character, however in dictionaries it is treated as the double character ss and sorted accordingly. Accented characters are sorted in a particular order so that amnit comes before amne, whereas if you ignored the accents, the reverse would be true. Therefore, language-specific sort orders are required so that characters are sorted correctly.
287
Each character set comes with one or more sort orders that Adaptive Server uses to collate data. A sort order is tied to a particular language or set of languages and to a specific character set. The same sort orders can be used for English, French, and German because they sort the same characters identically, for example, A, a, B, b, and so on. Or the characters are specific to one of the languagesfor example, the accented characters, , , and , are used in French but not in English or Germanand therefore, there is no conflict in how those characters are sorted. The same is not true for Spanish however, where the double letters ch and ll are sorted differently. Therefore, although the same character sets support all four languages, there is one set of sort orders for English, French and German, and a different set of sort orders for Spanish. In addition, a sort order is tied to a particular character set. Therefore, there is one set of sort orders for English, French, and German in the ISO 8859-1 character set, another set in the CP 850 character set, and so on. The sort orders available for a particular character set are located in sort order definition files (*.srt files) in the character set directory. For a list of character sets and their available sort orders, see Table 9-5 on page 290.
Using sort orders

Sort orders are used to: Create indexes Store data into indexed tables Specify an order by clause
Different types of sort orders

All character sets are offered with a binary sort order at a minimum, which blindly sorts all data based only on the arithmetic value of the code assigned to represent each letter (the binary code) in the character set. Binary sort order works well for the first 128 characters of each character set (ASCII English) and for Asian languages.When a character set supports more than one language (for example, Group 1 or Unicode) the binary sort order most likely give incorrect results, and you should select another sort order. Character sets may also have one or more of the following dictionary sort orders:
288
CHAPTER 9
Dictionary order, case-sensitive, accent-sensitive sorts uppercase and lowercase letters separately. Dictionary order recognizes the various accented forms of a letter and sorts them after the associated unaccented letter. Dictionary order, case-insensitive, accent-sensitive sorts data in dictionary order but does not recognize case differences. Uppercase letters are equivalent to their lowercase counterparts and are intermingled in sorting results. Useful for avoiding duplicate entries in tables of names. Dictionary order, case-insensitive, accent-sensitive, order with preference does not recognize case difference in determining equivalency of items. A word in uppercase is equivalent to the same word in lowercase. Preference is given to uppercase letters (they appear first) if all other conditions are equal. Using case-insensitive with preference may cause poor performance in large tables when the columns specified in an order by clause match the key of the tables clustered index. Do not select case-insensitive order with preference unless your installation requires that uppercase letters be sorted before lowercase letters in otherwise equivalent strings for order by clauses.
Dictionary order, case-insensitive, accent-insensitive treats accented forms of a letter as equivalent to the associated unaccented letter. It intermingles accented letters in sorting results.
Selecting the default sort order

Sybase servers can support only one default sort order at a time. If your users are using the same language or their languages use the same sort order, then select the desired sort order. For example, if your users are using French data and expect French sorting, then you can pick one of the French dictionary sort orders. Or if your users are using data in multiple languages and the languages use the same sort order, for example English, French, and German, you can pick one sort order and it works for all your users in all languages. However, if you have users using different languages that require different sort orders, for example French and Spanish, then you must select one of the sort orders as the default. If you pick, for example, a French sort order, your Spanish users will not see the ch and ll double characters sorted as they would expect. The installation procedure, by default, configures the server with the binary sort order.
289
You can use the sortkey function to setup customized alternative sort orders for your dataone for each language.These sort orders can be selected dynamically to meet the needs of different users. The sortkey function is separate from the default sort order, but can coexist in the same server. The range and depth of sort orders provided by the sortkey function is better than those provided by the default sort order mechanism. For more information, see sortkey and compare in the Reference Manual.
Table 9-5: Available sort orders Language or script All languages Cyrillic: Bulgarian, Byelorussian, Macedonian, Russian, Serbian, Ukrainian
Eastern European:
Character sets UTF-8 CP 855, CP 866, CP 1251, ISO 8859-5, Koi8, Macintosh Cyrillic
Sort orders Multiple sort orders, see Table 9-7 for list Dictionary order, case sensitive, accent sensitive
Czech, Slovak
CP 852, ISO 8859-2, CP 1250
Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, accent sensitive Dictionary order, case sensitive, accent sensitive, with preference Dictionary order, case insensitive, accent insensitive Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, accent sensitive Dictionary order, case sensitive, accent sensitive, with preference Dictionary order, case insensitive, accent insensitive Alternate dictionary order, case sensitive Alternate dictionary order, case sensitive, accent insensitive Alternate dictionary order, case sensitive, with preference Dictionary order, case sensitive, accent sensitive Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, accent sensitive Dictionary order, case insensitive, accent insensitive
English, French, German
ASCII 8, CP 437, CP850, CP 860, CP 863, CP 1252a, ISO 8859-1, ISO 8859-15, Macintosh Roman, ROMAN8, ROMAN9, ISO 15
English, French, German
CP 850, CP 858
Greek Hungarian
ISO 8859-7 ISO 8859-2
Russian Scandinavian
CP 866, CP 1251, ISO 8859-5, Koi8, Macintosh Cyrillic CP 850
Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, accent sensitive Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, with preference
290
CHAPTER 9
Language or script Spanish
Character sets ASCII 8, CP 437, CP850, CP 860, CP 863, CP 1252, ISO 8859-1, ISO 8859-15, Macintosh Roman, ROMAN8 CP 874, TIS 620 ISO 8859-9
Sort orders Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, accent sensitive Dictionary order, case insensitive, accent insensitive Dictionary order Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, accent insensitive Dictionary order, case insensitive, accent sensitive Dictionary order, case insensitive, case sensitive, with preference, accent insensitive, Spanish dictionary, Spanish case insensitive, Spanish accent insensitive
Thai Turkish
Western European
CP 1252
If your language does not appear here, there is no language-specific sort order for your language. Select a binary sort order and then investigate whether the sortkey function meets your needs. As this table illustrates, many languages have more than one sort order.
Selecting the default Unicode sort order

The default Unicode sort order is distinctly different from the sort order for the servers default character set. This separate configuration parameter is a static parameter that requires that you restart your server and reindex the unichar data if it is changed. This sort order is identified using a string parameter, rather than a numeric parameter, to guarantee that the sort order is unique. Table 9-6 lists the available default Unicode sort orders.
291
Table 9-6: Default Unicode sort orders Name defaultml thaidict iso14651 utf8bin binary altnoacc altdict altnocsp scandict scannocp bin_utf8 dict nocase nocasep noaccent espdict espnocs espnoac rusnocs cyrnocs elldict hundict hunnoac hunnocs turknoac ID 20 21 22 24 25 39 45 46 47 48 50 51 52 53 54 55 56 57 59 64 65 69 70 71 73 Description Default Unicode multi-lingual ordering Thai dictionary ordering Ordering as per ISO14651 standard Ordering for UTF-16 that matches the UTF-8 binary Binary sort Alternate accent-insensitive Alternate dictionary ordering Alternate case-insensitive with preference Scandinavian dictionary ordering Scandinavian case-insensitive with preference UTF-8 binary sort order General-purpose dictionary ordering General-purpose case-insensitve dictionary ordering General-purpose case-insensitve with preference General-purpose accent-insensitive dictionary ordering Spanish dictionary ordering Spanish case-insensitive dictionary ordering Spanish accent-insenitive dictionary ordering Russian case-insensitive dictionary ordering Cyrillic case-insensitive dictionary ordering Greek dictionary ordering Hungarian dictionary ordering Hungarian accent-insensitive dictionary ordering Hungarian case-insensitive dictionary ordering Turkish accent-insensitive dictionary ordering
292
CHAPTER 9
Table 9-7 lists the loadable sort orders.

Table 9-7: Loadable sort orders Name cp932bin dynix gb3213bn cyrdict turdict euckscbn gbpinyin rusdict sjisbin eucjisbn big5bin ID 129 130 137 140 155 161 163 165 179 192 194 Description Ordering that matches the binary ordering of CP932 Chinese phonetic ordering Ordering that matches the binary ordering of GB2312 Common cyrillic dictionary ordering Turkish Dictionary ordering Ordering that matches the binary ordering of EUCKSC Chinese phonetic ordering Russian dictionary ordering Ordering that matches the binary ordering of SJIS Ordering that matches the binary ordering of EUCJIS Ordering that matches the binary ordering of BIG5
To view this sort order list in Adaptive Server, use sp_helpsort. See Chapter 1, System Procedures in the Reference Manual: Procedures for more information. You can add sort orders using external files in the $SYBASE/collate/Unicode directory. The names and collation IDs are stored in syscharsets. The names of external Unicode sort orders do not have to be in syscharsets before you can set the default Unicode sort order.
Note External Unicode sort orders are provided by Sybase. Do not attempt to
create external Unicode sort orders. Sort order associated with Unicode data is completely independent of the sort order associated with traditional character data. All relational expressions involving the Unicode datatypes are performed using the Unicode sort order. This includes mixed-mode expressions involving Unicode and non-Unicode data. For example, in the following query the varchar character constant M is implicitly cast to unichar and the comparison is performed according to the Unicode sort order:
293
Selecting a language for system messages
select * from authors where unicode_name > 'M'
The same holds true for all other comparison operators, as well as the concatenation operator +, the operator in, and the operator between. Once again, the goal is to retain compatibility with existing database applications. Tables joins based on equality (equijoins) deserve special mention. These are generally optimized by the server to take advantage of indexes that defined on the participating columns. When a unichar column is joined with a char column, the latter requires a conversion, and since the character sort order and the Unicode sort order are distinct, the optimizer will ignore the index on the char column. In Adaptive Server 12.5.1, when the servers default character set is configured to UTF-8, you can configure the server's default sort order (for char data) to be any of the above sort orders. Prior to this version, the binary sort order bin_utf8 (ID=50) was the only well-behaved sort order for UTF-8. Although not required, the sort order for char data in UTF-8 can be selected so that it corresponds with the sort order for unichar. There is a potential confusion regarding choice of binary sort orders for Unicode. The sort order named binary is the most efficient one for unichar data (UTF-16), and is thus the default. This order is based on the Unicode scalar value, meaning that all 32-bit surrogate pairs are placed after all 16-bit Unicode values. The sort order named utf8bin is designed to match the order of the default (most efficient) binary order for UTF-8 char data, namely bin_utf8. The recommended matching combinations are thus binary for unichar and binary for UTF-8 char, or utf8bin for unichar and bin_utf8 for UTF-8 char. The former favors unichar efficiency, while the latter favors char efficiency. Avoid using utf8bin for UTF-8 char, since it is equivalent to bin_utf8 but less efficient.
Selecting a language for system messages

Any installation of Adaptive Server can use Language Modules containing files of messages in different languages. Adaptive Server provides Language Modules for messages in the following languages: English, Chinese (Simplified), French, German, Japanese, Korean, Brazilian Portuguese, and Spanish. If your client language is not one of these languages, you see system messages in English, the default language.
294
CHAPTER 9
Each client can choose to view messages in their own language at the same time, from the same server; for example, one client views system messages in French, another in Spanish, and another in German. To do this, however, all selected languages must be part of the same language group. For example, French, Spanish and German are all part of language group 1. Japanese, on the other hand, is part of language group 101, which contains no other languages. Therefore, if Japanese is your server language, you can display system messages only in Japanese or English. Remember that all language groups can display messages in English. There is also a server-wide default language, used if the user has not selected a specific language. If you use Unicode, you can view system messages in any of the supported languages. You can select the language for your system messages in one of two ways: Select a language as part of your user profile Enter a language in the locales.dat file
Table 9-8 displays the supported system message languages and their language groups. Each user can select only one language per session for system messages.
Table 9-8: Supported system messages Language group Group 1 System message languages French, German, Spanish, Brazilian Portuguese Character sets ASCII 8, CP 437, CP 850, CP 860, CP 863, CP 1252, ISO 8859-1, ISO 8859-15, Macintosh Roman, ROMAN8 Cp 1250, CP 852, ISO 8859-2 CP 932, DEC Kanji, EUC-JIS, Shift-JIS CP 936, EUC-GB, GB18030 EUC-KSC, CP 949 CP 874, TIS 620 UTF-8
Group 2 Group 101 Group 102 Group 104 Group 105 Unicode All Other Language Groups
Polish Japanese Simplified Chinese (PRC) Korean Thai French, German, Spanish, Brazilian Portuguese, Japanese, Simplified Chinese, Korean English
Install Language Modules for all languages in which clients will receive messages. These Language Modules, located in the locales subdirectory of the Adaptive Server installation directory, are part of a group of files called localization files. For information about localization files and the software message directory structure, see Types of localization files on page 311.
295
Setting up your server: examples
Setting up your server: examples

This section discusses setup options and the steps necessary to implement them. This is only a sample, and is meant to suggest ideas and methods for your own setup process.
A Spanish-version server
This examples shows how to set up a new server with all clients using the same language. To do this: 1 Select the server language, in this case, Spanish. By reviewing Table 9-1 on page 279, you see that Spanish is part of language group 1. Based on your platform, select a character set from language group 1. Sybase recommends that you select the character set used by the greatest number of clients. Or, if you think your company might someday expand into other countries and languages, you might consider installing Unicode (see Selecting the character set for your server on page 277). Install the Spanish Language Module in the server. This allows clients to view system messages in Spanish. Select the default sort order. By referring to Table 9-5 on page 290, you see that Spanish has three possible sort orders, in addition to binary sort order. Select a sort order. Restart the server.
2 3
A U.S.-based company in Japan

This example involves clients in Japan, who want to enter data, sort data, and receive system messages in Japanese, while submitting data to a server that is accessed by English-only users: 1 Select the default character set for your server. If you install a character set from language group 101 (Japanese), you can support both Japanese and English data in the same server. Install the Japanese Language Module so that system messages are available in Japanese.
296
CHAPTER 9
Select the sort order. By referring to Table 9-5 on page 290, you can see that a binary sort order is the only sort order available for Japanese. Therefore, both the English and Japanese clients have a default binary sort order. Consider using the sortkey function to provide solutions for both audiences. Make sure that each Japanese user requests Japanese messages by default. Since you are using a character set from language group 101, and you have already installed the Japanese Language Module, your client in Japan sees messages in Japanese, while clients in the U.S. can choose to see messages in either English or Japanese.
A Japan-based company with multinational clients

This company is located in Japan, and has clients in France, Germany, and Spain. You need to mix European and Asian languages in the same server. 1 Select the default server language and character set. Since your company is based in Japan and most of your clients are located in Japan, the default server language should be Japanese. But you also want your clients in France, Germany, and Spain to be able to send and receive data in their native languages. By reviewing Table 9-1 on page 279, you can see that Japanese is part of language group 101, while French, German, and Spanish are part of language group 1. Since the languages you need are not part of the same language group, the only way you can have all of these languages on the same server is to select Unicode as your default character set. Install the Language Modules for Japanese, French, German, and Spanish. Select the binary sort order, since this is the only sort order available for the Unicode character set. (You can, however, consider using the sortkey function inside your application code to supply data sorted according to each users preference.) Select Japanese as the default language for system messages. Clients in other countries can select their own native language for messages.
2 3
297
Changing the character set, sort order, or message language

Even after you have configured your server, a System Administrator can change the default character set, sort order, or message language used by Adaptive Server. Because a sort order is built on a specific character set, changing character sets always involves a change in sort order. However, you can change the sort order without changing character sets, because more than one sort order may be available for a character set. To display Adaptive Servers default sort order, character set, and a table of its primary sort orders, enter:
sp_helpsort
Changing the default character set

Adaptive Server can have only one default character set, the character set in which data is stored in its databases. When you install Adaptive Server, you specify a default character set.
Warning! Read the following carefully, and exercise caution when changing the default character set in Adaptive Server. Sybase strongly recommends that you perform backups before you change a default character set.
When you change the default character set in Adaptive Server, you must convert any existing data to the new default character set. Conversion is unnecessary only if: There is no user data in the server. It is acceptable to destroy user data in the server. You are absolutely certain that data in the server uses only ASCll-7. In this case, you can change the default without first copying your data out of the server.
In all other cases, you must convert the existing data as follows: 1 2 3 Copy the data out using bcp. Change the default character set. Use bcp with the appropriate flags for data conversion to copy the data back into the server.
298
CHAPTER 9
See the Utility Guide for more information about using bcp to copy data.
Warning! After converting data to a different character set (particularly to UTF-8), the data may be too large for the allocated column size. Re-create the columns affected with a larger size.
Code conversion between the character set of the existing data and the new default character set must be supported. If it is not, conversion errors will occur and the data is converted correctly. See Chapter 10, Configuring Client/Server Character Set Conversions, for more information about supported character set conversions. Even if conversions are supported between the character sets, some errors may occur due to minor differences between the character sets, or because some characters do not have equivalents in other character sets. Rows containing problematic data may not get copied back into the database, or data may contain partial or invalid characters.
Changing the sort order with a resources file

Adaptive Server character sets can be changed using the resource file. The sample resource file sqlloc.rs is located in $SYBASE/ASE12_5/init/sample_resource_files/. The resource file from the Adaptive Server 12.5.1 installation looks similar to the following:
sybinit.release_directory: USE_DEFAULT sqlsrv.server_name: PUT_YOUR_SERVER_NAME_HERE sqlsrv.sa_login: sa sqlsrv.sa_password: sqlsrv.default_language: USE_DEFAULT sqlsrv.language_install_list: USE_DEFAULT sqlsrv.language_remove_list: USE_DEFAULT sqlsrv.default_characterset: USE_DEFAULT sqlsrv.characterset_install_list: USE_DEFAULT sqlsrv.characterset_remove_list: USE_DEFAULT sqlsrv.sort_order: USE_DEFAULT # An example sqlloc resource file... # sybinit.release_directory: USE_DEFAULT # sqlsrv.server_name: PUT_YOUR_SERVER_NAME_HERE # sqlsrv.sa_login: sa # sqlsrv.sa_password:
299
# # # # # # #
sqlsrv.default_language: french sqlsrv.language_install_list: spanish,german sqlsrv.language_remove_list: USE_DEFAULT sqlsrv.default_characterset: cp437 sqlsrv.characterset_install_list: mac,cp850 sqlsrv.characterset_remove_list: USE_DEFAULT sqlsrv.sort_order: dictionary
Changing the default sort order

Adaptive Server can have only one default sort order, the collating sequence it uses to order data. When you consider changing the sort order for character data on a particular Adaptive Server, keep this in mind: all of your organizations Adaptive Servers should have the same sort order. A single sort order enforces consistency and makes distributed processing easier to administer. You may have to rebuild your indexes after changing the default sort order. For more information, see Reconfiguring the character set, sort order, or message language on page 300.
Reconfiguring the character set, sort order, or message language

This section summarizes the steps to take before and after changing Adaptive Servers default character set, sort order, or message language. For procedures on how to configure the character set, sort order, or message language for a new server, see the configuration documentation for your platform. If your data does not have to be converted to a new character set, and both the old and the new character sets use binary sort order, you can use a database dump. You can restore your database from backups that were made before the character set was reconfigured.
Note Back up all databases in Adaptive Server both before and after you
change character sets or sort orders. Usually, you cannot reload your data from a database dump when you have reconfigured the default character set and sort order. If the following is true, use bcp to copy the data out of and into your databases.
300
CHAPTER 9
If a database contains character data, and you want the data to be converted to a new character set. Do not load a database dump of the data into an Adaptive Server with the new default character set. Adaptive Server interprets the data loaded as if it is in the new character set, and the data will be corrupted. If you are changing only the default sort order and not the default character set. You cannot load a database from a dump that was performed before you changed the sort order. If you attempt to do so, an error message appears, and the load is aborted. You change the default character set, and either the old or the new sort order is not binary. You cannot load a database dump that was made before you changed the character set.
Unicode examples
In the following example, a fictitious database named xpubs will be modified to use univarchar columns.
Schema
Assume a database was created using the following script on a server that has all the installation defaults, namely character set iso_1 and default sort order ID 50, binary_iso_1.
> create database xpubs > go > use xpubs > go > create table authors (au_id int, au_lname varchar(255), au_fname varchar(255)) > go > create index au_idx on authors(au_lname, au_fname) > go
Then the data was loaded into the server using a series of inserts and updates.
Converting to UTF-8
The first step towards using Unicode is to extract the data and convert it to UTF-8 form.
% bcp xpubs..authors out authors.utf8.bcp -c -Jutf8 -Usa -P
301
The next step to install UTF-8 as the default character set in the server:
% % > > > > charset -Usa -P binary.srt utf8 isql -Usa -P sp_configure 'default sortorder id', 50, 'utf8' go shutdown go
Restart the server to modify the default character set and re-create indexes on the system tables. Restart the server a second time, then reload the data:
% > > > > > > > > > isql -Usa -P sp_dboption xpubs, 'select into', true go use xpubs go checkpoint go delete from authors go quit
% bcp xpubs..authors in authors.utf8.bcp -c -Jutf8 -Usa -P
Migrating selected columns to unichar

With a working database running with UTF-8 as the default character set, it becomes a simple matter to convert select columns to univarchar:
% isql -Usa -P > use xpubs > go > alter table authors modify au_lname univarchar(255), au_fname univarchar(255) > go
The columns are modified to the new datatypes, the data is converted in place, and the index is re-created.
302
CHAPTER 9
Migrating to or from unitext

Currently, the alter table modify command does not support text, image, or unitext columns. To migrate from a text to a unitext column, you must first use bcp, create a table with unitext columns, and then use bcp again to place data into the new table. This migration path only works when you invoke bcp with -Jutf8 option.
Preliminary steps
Before you run the installation program to reconfigure Adaptive Server: 1 2 3 Dump all user databases and the master database. If you have made changes to model or sybsystemprocs, dump them also. Load the Language Module if it is not already loaded (see the configuration documentation for your platform for complete instructions). If you are changing the Adaptive Server default character set, and your current databases contain non ASCII-7 data, use bcp to copy the existing data out of your databases.
Once you have loaded the Language Module, you can run the Adaptive Server installation program, which allows you to: Install or remove message languages and character sets included with Adaptive Server Change the default message language or character set Select a different sort order
See the configuration documentation for your platform for instructions on using the installation program
Note Before you change the character set or sort order, Adaptive Server must
have as many open databases as there are databases managed by the server. If Adaptive Server does not have a sufficent number of open databases when it is re-started after a change in sort order, Adaptive Server prints this message to the error log and the server will revert to the former sort order:
The configuration parameter 'number of open databases' must be at least as large as the number of databases, in order to change the character set or sort order." Restart Adaptive Server, use sp_configure to increase 'number of open databases' to at least %d, then re-
303
configure the character set or sort order
To reconfigure the language, character set, or sort order, use the sqlloc utility, described in Utility Guide for UNIX Platforms. If you are using Windows, use the Server Config utility, described in Configuration Guide for Windows. If you are adding a new character set that is not included with Adaptive Server, see the Sybase Character Sets manual for complete instructions. If you installed additional languages but did not change the Adaptive Server character set or sort order, you have completed the reconfiguration process. If you changed the Adaptive Server default character set, and your current databases contain non ASCII-7 data, copy your data back into your databases, using bcp with the necessary flags to enable conversion. If you changed the Adaptive Server default sort order or character set, see Reconfiguring the character set, sort order, or message language on page 300.
Setting the users default language

If you install an additional language, users running client programs can run sp_modifylogin to set that language as their default language, or set the LANG variable on the client machine, with the appropriate entries in locales.dat.
Recovery after reconfiguration

Every time Adaptive Server is stopped and restarted, recovery is performed automatically on each database. Automatic recovery is discussed in detail in Chapter 11, Developing a Backup and Recovery Plan. After recovery is complete, the new sort order and character set definitions are loaded. If you have changed the sort order, Adaptive Server switches to single-user mode to allow the necessary updates to system tables and to prevent other users from using the server. Each system table with a character-based index is automatically checked to see if any indexes have been corrupted by the sort order change. Character-based indexes in system tables are automatically rebuilt, if necessary, using the new sort order definition.
304
CHAPTER 9
After the system indexes are rebuilt, character-based user indexes are marked suspect in the sysindexes system table, without being checked. User tables with suspect indexes are marked read-only in sysobjects to prevent updates to these tables and use of the suspect indexes until they have been checked and, if necessary, rebuilt. Next, the new sort order information replaces the old information in the area of the disk that holds configuration information. Adaptive Server then shuts down so that it starts for the next session with a complete and accurate set of system information.
Using sp_indsuspect to find corrupt indexes

After Adaptive Server shuts down, restart it, and use sp_indsuspect to find the user tables that need to be reindexed. The following is the syntax, where tab_name is the optional name of a specific table:
sp_indsuspect [tab_name]
If tab_name is missing, sp_indsuspect creates a list of all tables in the current database that has indexes marked suspect when the sort order changes. In this example, running sp_indsuspect in mydb database yields one suspect index:
sp_indsuspect Suspect indexes in database mydb Own.Tab.Ind (Obj_ID, Ind_ID) = dbo.holdings.h_name_ix(160048003, 2)
Rebuilding indexes after changing the sort order

dbcc reindex checks the integrity of indexes on user tables by running a fast version of dbcc checktable. For details, see dbcc checktable on page 226. dbcc reindex drops and rebuilds the indexes where the sort order used is not consistent with the new sort order. When dbcc reindex discovers the first indexrelated error, it displays a message, and then rebuilds the inconsistent indexes. The System Administrator or table owner should run dbcc reindex after changing the sort order in Adaptive Server.
The syntax is:

dbcc reindex ({table_name | table_id})
Run this command on all tables listed by sp_indsuspect as containing suspect indexes. For example:
305
dbcc reindex(titles) One or more indexes are corrupt. They will be rebuilt.
In the preceding example, dbcc reindex discovers one or more suspect indexes in the table titles; it drops and re-creates the appropriate indexes. If the indexes for a table are already correct, or if there are no indexes for the table, dbcc reindex does not rebuild any indexes. It displays a message instead. If a table is suspected of containing corrupt data, the command is aborted. If that happens, an error message instructs the user to run dbcc checktable. When dbcc reindex finishes successfully, all suspect marks on the tables indexes are removed. The read-only mark on the table is also removed, and the table can be updated. These marks are removed whether or not any indexes have to be rebuilt.
dbcc reindex does not reindex system tables. System indexes are checked and rebuilt, if necessary, as an automatic part of recovery after Adaptive Server is restarted following a sort order change.
Upgrading text data after changing character sets

If you have changed an Adaptive Servers character set to a multibyte character set, use dbcc fix_text to upgrade text values. The syntax is:
dbcc fix_text ({table_name | table_id})
Changing to a multibyte character set makes the management of text data more complicated. A text value can be large enough to cover several pages; therefore, Adaptive Server must be able to handle characters that span page boundaries. To do so, Adaptive Server requires additional information on each of the text pages. The System Administrator or table owner must run dbcc fix_text on each table that has text data to calculate the new values needed. To see the names of all tables that contain text data, use:
select sysobjects.name from sysobjects, syscolumns where syscolumns.type = 35 and sysobjects.id = syscolumns.id
The System Administrator or table owner must run dbcc fix_text to calculate the new values needed. The syntax of dbcc fix_text is:
dbcc fix_text (table_name | table_id)
306
CHAPTER 9
The table named must be in the current database.

dbcc fix_text opens the specified table, calculates the character statistics required for each text value, and adds the statistics to the appropriate page header fields. This process can take a long time, depending on the number and size of the text values in a table. dbcc fix_text can generate a large number of log records, which may fill up the transaction log. dbcc fix_text performs updates in a series of small transactions so that if a log becomes full, only a small amount of work is lost.
If you run out of log space, clear out your log (see Chapter 12, Backing Up and Restoring User Databases). Then restart dbcc fix_text, using the same table that was being upgraded when the original dbcc fix_text halted. Each multibyte text value contains information that indicates whether it has been upgraded, so dbcc fix_text upgrades only the text values that were not processed in earlier passes. If your database stores its log on a separate segment, you can use thresholds to manage clearing the log. See Chapter 15, Managing Free Space with Thresholds. If dbcc fix_text cannot acquire a needed lock on a text page, it reports the problem and continues with the work, like this:
Unable to acquire an exclusive lock on text page 408. This text value has not been recalculated. In order to recalculate those TEXT pages you must release the lock and reissue the dbcc fix_text command.
Retrieving text values after changing character sets

If you attempt to retrieve text values after changing to a multibyte character set, and you have not run dbcc fix_text, the command fails with this error message:
Adaptive Server is now running a multi-byte character set, and this TEXT columns character counts have not been recalculated using this character set. Use dbcc fix_text before running this query again. Note If you have changed the sort order or character set and errors occurred,
see How to Manually Change Sort Order or Default Character Set in the Adaptive Server Enterprise Troubleshooting and Error Messages Guide.
307
Installing date strings for unsupported languages
Installing date strings for unsupported languages

You can use sp_addlanguage to install names for the days of the week and months of the year for languages that do not have Language Modules. With sp_addlanguage, you define: A language name and (optionally) an alias for the name A list of the full names of months and a list of abbreviations for the month names A list of the full names of the days of the week The date format for entering dates (such as month/day/year) The number of the first day of the week
This example adds the information for Italian:

sp_addlanguage italian, italiano, "gennaio,febbraio,marzo,aprile,maggio,giugno,luglio,agosto,settembre,ottobre, novembre,dicembre", "genn,feb,mar,apr,mag,giu,lug,ago,sett,ott,nov,dic", "lunedi,martedi,mercoledi,giovedi,venerdi,sabato,domenica", dmy, 1
sp_addlanguage enforces strict data entry rules. The lists of month names,
month abbreviations, and days of the week must be comma-separated lists with no spaces or line feeds (returns). Also, they must contain the correct number of elements (12 for month strings, 7 for day-of-the-week strings.) Valid values for the date formats are: mdy, dmy, ymd, ydm, myd, and dym. The dmy value indicates that the dates are in day/month/year order. This format affects only data entry; to change output format, you must use the convert function.
Server versus client date interpretation

Generally, date values are resolved on the client. When a user selects date values, Adaptive Server sends them to the client in internal format. The client uses the common.loc file and other localization files in the default language subdirectory of the locales directory on the client to convert the internal format to character data. For example, if the users default language is Spanish, Adaptive Server looks for the common.loc file in /locales/spanish/char_set. It uses the information in the file to display, for example, 12 febrero 1997.
308
CHAPTER 9
Assume that the users default language is set to Italian, a language for which Adaptive Server does not provide a Language Module, and that the date values in Italian have been added. When the client connects to the server and looks for the common.loc file for Italian, it does not find the file. The client prints an error message and connects to the server. If the user then selects date values, the dates are displayed in U.S. English format.To display the date values added with sp_addlanguage, use the convert function to force the dates to be converted to character data at the server. The following query generates a result set with the dates in U.S. English format:
select pubdate from titles
The query below, however, returns the date with the month names in Italian:
select convert(char(19),pubdate) from titles
Internationalization and localization files

Types of internationalization files
The files that support data processing in a particular language are called internationalization files. Several types of internationalization files come with Adaptive Server. Table 9-9 describes these files.
Table 9-9: Internationalization files File charset.loc Location In each character set subdirectory of the charsets directory In each character set subdirectory of the charsets directory In each character set subdirectory of the charsets directory Purpose and contents Character set definition files that define the lexical properties of each character, such as alphanumeric, punctuation, operand, and uppercase or lowercase. Used by Adaptive Server to correctly process data. Defines the sort order for alphanumeric and special characters, including ligatures, diacritics, and other language-specific considerations. Terminal-specific character translation files for use with utilities such as bcp and isql. For more information about how the.xlt files are used, see Chapter 10, Configuring Client/Server Character Set Conversions, and the Utility Guide.
*.srt
*.xlt
309
Warning! Do not alter any of the internationalization files. If you need to install a new terminal definition or sort order, contact your local Sybase office or distributor.
Character sets directory structure

Figure 9-3 shows the directory structure for the Western European character sets that come with Adaptive Server. There is a separate subdirectory for each character set in the charsets directory. Within the subdirectory for each character set (for example, cp850) are the character set and sort order definition files and terminal-specific files. If you load additional character sets, they also appear in the charsets directory:
Figure 9-3: Structure of the charsets directory charsets
cp850 charset.loc *.srt
iso_1 charset.loc *.srt *.xlt
cp437 charset.loc *.srt
mac charset.loc *.srt
roman8 charset.loc *.srt
charset_name charset.loc *.srt
The following global variables contain information about character sets:

Table 9-10: Global variables used for character sets Global variable @@char_convert @@client_csname @@client_csid @@client_csexpan sion @@maxcharlen @@ncharsize Description Contains 0 if character set conversion is not in effect. Contains 1 if character set conversion is in effect. The clients character set name. Set to NULL if client character set has never been initialized; otherwise, it contains the name of the character set for the connection. The clients character set ID. Set to -1 if client character set has never been initialized; otherwise, it contains the client character set ID from syscharsets for the connection. Returns the expansion factor used when converting from server's character set to client's character set. The maximum length, in bytes, of a character in the Adaptive Server default character set. The maximum length, in bytes, of a character set in the current server default character set.
310
CHAPTER 9
Global variable @@unicharsize
Description Equals 2.
Types of localization files

Adaptive Server includes several localization files for each Language Module, as shown in Table 9-11.
Table 9-11: Localization files File locales.dat server.loc Location In the locales directory Purpose and contents Used by client applications to identify the default message language and character set. Software messages translated into the local language. Sybase products have product-specific *.loc files. If an entry is not translated, that software message or string appears in U.S. English instead of the local language. Contains the local names of the months of the year and their abbreviations and information about the local date, time, and money formats.
In the character set subdirectories under each language subdirectory in the locales directory common.loc In each language and character set directory of the locales directory
Warning! Do not alter any of the localization files. If you need to alter any information in those files, contact your local Sybase office or distributor.
Software messages directory structure

Figure 9-4 shows how localization files are arranged. Within the locales directory is a subdirectory for each language installed. There is always a us_english subdirectory. (On PC platforms, this directory is called english.) During installation, when you are prompted to select the languages you want installed on Adaptive Server, the install program lists the supported software message languages. If you install Language Modules for additional languages, you see subdirectories for those languages. Within each language are subdirectories for the supported character sets; for example, cp850 is a supported character set for us_english. Software message files for each Sybase product reside in the character set subdirectories.
311
Figure 9-4: Messages directory structure locales locales.dat
us_english
language2
cp850 server.loc common.loc
iso_1 server.loc common.loc
cp437 server.loc common.loc
mac server.loc common.loc
roman8
char_set1
char_set2
server.loc server.loc server.loc common.loc common.loc common.loc
Message languages and global variables

The following global variables contain information about languages:
@@langid @@language Contains the local language ID of the language currently in use (specified in syslanguages.langid) Contains the name of the language currently in use (specified in syslanguages.name)
312
CH A PTE R
1 0
Configuring Client/Server Character Set Conversions
This chapter describes how to configure character set conversion when the client uses a different character set than Adaptive Server.
Topic Character set conversion in Adaptive Server Supported character set conversions Types of character set conversion Which type of conversion do I use? Enabling and disabling character set conversion Error handling in character set conversion Conversions and changes to data lengths Specifying the character set for utility programs Display and file character set command line options Page 313 314 316 317 319 320 321 322 323
Character set conversion in Adaptive Server

In a heterogeneous environment, Adaptive Server may need to communicate with clients running on different platforms using different character sets. Although different character sets may support the same language group (for example, ISO 8858-1 and CP 850 support the group 1 languages), they may encode the same characters differently. For example, in ISO 8859-1, the character is encoded as 0xE0 in hexadecimal. However, in CP 850 the same character is encoded as 0x85 in hexadecimal. To maintain data integrity between your clients and servers, data must be converted between the character sets. The goal is to ensure that an a remains an a even when crossing between machine and character set boundaries. This process is known as character set conversion.
313
Supported character set conversions
Supported character set conversions

Character set conversion occurs between a pair of character sets. The supported conversions in any particular client/server system depend on the character sets used by the server and its clients. One type of character set conversion occurs if the server uses a native character set as the default; a different type of conversion is used if the server default is Unicode UTF-8.
Conversion for native character sets

Adaptive Server supports character set conversion between native character sets belonging to the same language group. If the server has a native character set as its default, the clients character sets must belong to the same language group. Figure 10-1 is an example of a Western European client/server system. In this example, the clients character sets and the Adaptive Server default character set all belong to Group 1. Data is correctly converted between the client character sets and the server default character set. Since they all belong to the same language group, the clients can view all data on the server, no matter which client submitted the data.
Figure 10-1: Character set conversion when server and client character sets belong to the same language group
French client: Roman8 ASE CP 850 German client: ISO 8859-1 Spanish client: Macintosh Roman For a list of the language groups and supported character sets, see Table 9-1 on page 279.
314
CHAPTER 10
Conversion in a Unicode system

Adaptive Server also supports character set conversion between UTF-8 and any native character set that Sybase supports. In a Unicode system, since the server default character set is UTF-8, the client character set may be a native character set from any language group. Therefore, a Japanese client (group 101), a French client (group 1), and an Arabic client (group 6) can all send and receive data from the same server. Data from each client is correctly converted as it passes between each client and the server.
Figure 10-2: Character set conversion in a Unicode system
French client: CP 1252 (Group 1) ASE UTF-8 Japanese client: CP 932 (Group 101) Arabic client: CP 1256 (Group 6)
Each client can view data only in the language supported by its character set. Therefore, the Japanese client can view any Japanese data on the server, but it cannot view Arabic or French data. Likewise, the French client can view French or any other Western European language supported by its character set, but not Japanese or Arabic.
Figure 10-3: Viewing Unicode data
French data ASE Japanese data UTF-8 Arabic data
French: CP 1252 Japanese: CP 932 Arabic: CP 1256
An additional character set, ASCII 7, is a subset of every character set, including Unicode, and is therefore compatible with all character sets in all language groups. If either the Adaptive Server or the clients character set is ASCII 7, any 7-bit ASCII character can pass between the client and server unaltered and without conversion.
315
Types of character set conversion
Sybase does not recommend that you configure a server for ASCII-7, but you can achieve the same benefits of compatibility by restricting each client to use only the first 128 characters of each native character set.
Types of character set conversion

Character set conversion is implemented on Adaptive Server in two different ways: Adaptive Server direct conversions Unicode conversions
Adaptive Server direct conversions

Adaptive Server direct conversions support conversions between two native character sets of the same language group. For example, Adaptive Server supports conversion between CP 437 and CP 850, because both belong to the group 1 language group. Adaptive Server direct conversions exist between many, but not all, native character sets of a language group (see Table 10-1 on page 318).
Unicode conversions
Unicode conversions exists for all native character sets. When converting between two native character sets, Unicode conversion uses Unicode as an intermediate character set. For example, to convert between the server default character set (CP 437), and the client character set (CP 860), CP 437 is first converted to Unicode; Unicode is then converted to CP 860. Unicode conversions may be used either when the default character set of the server is UTF-8, or a native character set. You must specifically configure your server to use Unicode conversions (unless the servers default character set is UTF-8).
316
CHAPTER 10
Earlier versions of Adaptive Server used direct conversions, and it is the default method for character set conversions. However, Unicode conversions allow easier and less complex character set conversion. Sybase continues to support existing Adaptive Server direct conversions, but Sybase now also uses Unicode conversions to provide complete conversion support for all character sets. Sybase has no plans to add new direct conversions.
Which type of conversion do I use?

To determine the conversion options that are available for your client/server system, see Table 10-1 on page 318.
Non-Unicode client/server systems

In a non-Unicode system, the character sets of the server and clients are native character sets; therefore, you can use the Adaptive Server direct conversions. However, there are some character sets for which there is no Adaptive Server direct conversion; in this situation, you must use Unicode conversions. If all character sets in your client/server system fall into column 1 of Table 10-1, use the Adaptive Server direct conversions. The character sets must all belong to the same language group. If the character sets in your client/server system fall into column 2 of Table 10-1, or some combination of columns 1 and 2, then you must configure your server to use Unicode conversions. Again, the character sets must all belong to the same language group.
For example, assume the server default character set is CP 850 and the clients character sets are either ISO 8859-1 or ROMAN 8. Table 10-1 shows that direct conversions exist between CP 850 and the client character sets. Now, suppose you add a client using CP 1252 to this configuration. Since there is no direct conversion between CP 1252 and CP 850, (the default server character set), you must use Unicode conversions to convert between CP 1252 and CP 850. When you have a mixture of character setssome where you can use Adaptive Server direct conversions and others where you must use Unicode conversionsyou can specify that a combination of Adaptive Server direct conversion and Unicode conversion be used.
317
Which type of conversion do I use?
Unicode client/server systems

If your server default is Unicode UTF-8, then all conversions are between UTF-8 and whatever native character set is being used on the client systems. Therefore, in a Unicode system, Unicode conversions are used exclusively.
Table 10-1: Conversion methods for character sets Language group Group 1 Group 2 Group 4 Group 5 Group 6 Group 7 Group 8 Group 9 Group 101 Group 102 Group 103 Group 104 Group 105 Group 106 Unicode No conversions needed (only one character set supported) No conversions needed (only one character set supported) CP 869, CP 1253, GREEK8, ISO 8859-7, Macintosh Greek CP 1255, ISO 8859-8 CP 857, CP 1254, ISO 8859-9, Macintosh Turkish, TURKISH8 DEC Kanjii, EUC-JIS, Shift-JIS CP 932 CP 936, EUG-GB, GB18303 Big 5, CP 950, EUC-CNS EUCKSC, CP 949 CP 874, TIS 620 Column 1 Adaptive Server direct conversions and Unicode conversions CP 437, CP 850, ISO 8859-1, Macintosh Roman CP 852, CP 1250, CP 8859-1, Macintosh Central European No conversions needed (only one character set supported) CP 855, CP 866, CP 1251, ISO 8859-5, Koi8, Macintosh Cyrillic CP 864, CP 1256, ISO 8859-6 Column 2 Unicode conversions only CP 860, CP 1252, ISO 8859-15, CP 863 ISO 8859-2
Configuring the server

By default, Adaptive Server uses direct conversions to convert data between different character sets. To use the Unicode conversions, you must configure the server with the sp_configure command. Set the enable unicode conversions option to either 1 or 2. If you set sp_configure enable unicode conversions to 1: This setting uses Adaptive Server direct conversions or Unicode conversions. Adaptive Server first checks to see if an Adaptive Server direct conversion exists for the server and client character set. If a direct conversion is used; if no direct conversion exists, the Unicode conversion is used.
318
CHAPTER 10
Use this setting if the character sets in your client/server system fall into both columns 1 and 2 in Table 10-1. If you set sp_configure enable unicode conversions to 2: This setting uses Unicode conversions only. Adaptive Server uses Unicode conversions, without attempting to find an Adaptive Server direct conversion. Use this setting if the client/server conversions result in a change in the data length (see Conversions and changes to data lengths on page 321) If all character sets fall into column 2 in Table 10-1, set enable unicode conversions to 2 to always use Unicode conversions. For Adaptive Server release 15.0 and later, the default value for enable unicode conversions is 1 If the server default is UTF-8, the server automatically uses Unicode conversions only.
Enabling and disabling character set conversion

When a client requests a connection, the client identifies its character set to Adaptive Server. Adaptive Server compares the client character set with its default character set, and if the two names are identical, no conversion is required. If the names differ, Adaptive Server determines whether it supports conversion between its default and the clients character set. If it does not, it send an error message to the client and continues with the logon process. If it does, character set conversion is automatically enabled. If the default character set of the server is UTF-8, it automatically uses Unicode conversions. If the default is a native character set, the server uses Adaptive Server direct conversions, unless the user specifies that Unicode conversions be used. You can disable character set conversion at the server level. You may want to do this if: All of your clients are using the same character set as the server default, and therefore, no conversion is required. Conversion between the client character set and the server default is not supported. You want to store data in the server without converting the data, that is, without changing the encoding of the data. 319
Error handling in character set conversion
To disable character set conversion at the server level, set the disable character set conversion parameter to 1. No conversion occurs for any client connecting to the server. By default this parameter is set to 0, which enables conversions. You can also control character set conversion at the connection level using the
set char_convert command from within a client session. set char_convert off
turns conversion off between a particular client and the server. You may want to set char_convert off if the client and the server use the same character set, which makes conversion unnecessary. set char_convert on turns conversion back on.
Characters that cannot be converted

During the conversion process, some characters may not be converted. Here are two reasons: The character exists (is encoded) in the source character set, but it does not exist in the target character set. For example, the OE ligature, is part of the Macintosh character set (code point 0xCE). This character does not exist in the ISO 8859-1 character set. If the OE ligature exists in data that is being converted from the Macintosh to the ISO 8859-1 character set, it causes a conversion error. The character exists in both the source and the target character set, but in the target character set, the character is represented by a different number of bytes than in the source character set. For example, 1-byte accented characters (such as , ) are 2-byte characters in UTF-8; 2-byte Thai characters are 3-byte characters in UTF8. You can avoid this limitation by configuring the enable unicode conversion option to 1 or 2.
Error handling in character set conversion

The Adaptive Server character set conversion reports errors when a character exists in the clients character set but not in the servers character set, or vice versa. Adaptive Server must guarantee that data successfully converted on input to the server can be successfully converted back to the clients character set when the client retrieves that data. To do this effectively, Adaptive Server must avoid putting suspect data into the database.
320
CHAPTER 10
When Adaptive Server encounters a conversion error in the data being entered, it generates this message:
Msg 2402, Severity 16 (EX_USER): Error converting client characters into servers character set. Some character(s) could not be converted.
A conversion error prevents query execution on insert and update statements. If this occurs, review your data for problem characters and replace them. When Adaptive Server encounters a conversion error while sending data to the client, it replaces the bytes of the suspect characters with ASCII question marks (?). However, the query batch continues to completion. When the statement is complete, Adaptive Server sends the following message:
Msg 2403, Severity 16 (EX_INFO): WARNING! Some character(s) could not be converted into clients character set. Unconverted bytes were changed to question marks ('?').
Conversions and changes to data lengths

In some cases, converting data between the servers character set and the clients character set results in a change to the length of the data. For example, this occurs when the character set on one system uses one byte to represent each character and the character set on the other system requires two bytes per character. When character set conversion results in a change in data length, there are two possibilities: The data length decreases, as in the following examples: Greek or Russian in multibyte UTF-8 to a single-byte Greek or Russian character set Japanese two-byte Hankaku Katakana characters in EUC-JIS to single-byte characters in Shift-JIS
The data length increases, as in the following examples: Single-byte Thai to multibyte Thai in UTF-8 Single-byte Japanese characters in Shift-JIS to two-byte Hankaku Katakana in EUC-JIS
321
Specifying the character set for utility programs
Configuring your system and application

If you are using UTF-8 anywhere in your client/server system, or using a Japanese character set, you are likely to encounter changes in data length as a result of character set conversion. If either of these conditions is true, you must configure your server to handle changes in data length. You may also need to set up your client to handle changes in data length. 1 Configure the server to use Unicode conversions. See Configuring the server on page 318. If the data length increases between the server and the client, then you must also complete steps 2 and 3. The client must be using Open Client 11.1 or later. It must inform the server that it is able to handle CS_LONGCHAR data at connection time, using the Open Client ct_capability function. The capability parameter must be set to CS_DATA_LCHAR and the value parameter must be set to CS_TRUE, where connection is a pointer to a CS_CONNECTION structure:
CS_INT capval = CS_TRUE ct_capability(connection,CS_SET,CS_CAP_RESPONS, CS_DATA_LCHAR,&capval)
When conversions result in an increase in data length, char and varchar data are converted to the clients character set and are sent to the client as CS_LONGCHAR data. The client application must be coded to extract the data received as CS_LONGCHAR.
Specifying the character set for utility programs

The Sybase utility programs assume that the default character set of the client platform is the same character set the client is using. However, sometimes the client character set differs from the character set for the platform. For this reason, you may need to specify the client character set at the command line. Character set conversion can be controlled in the standalone utilities. A command line option for the isql, bcp, and defncopy utilities specifies the clients character set and temporarily overrides settings of the LANG variable or settings in locales.dat.
-J charset_name (UNIX and PC) sets the clients character set to the
charset_name.
322
CHAPTER 10
Omitting the client character sets command line flag causes the platforms default character set to be used. See the Utility Guide for information.
Display and file character set command line options

Although the focus of this chapter is on character set conversion between clients and Adaptive Server, there are two other places where you may need character set conversion: Between the client and a terminal Between the client and a file system
Figure 10-4 illustrates the paths and command line options that are available in the standalone utilities isql, bcp, and defncopy.
Figure 10-4: Where character set conversion may be needed
-a
display_charset
-J client_charset Terminal display Client File system -q datafile_charset (bcp only) Adaptive Server
As described earlier, the -J or /clientcharset command line option specifies the character set used by the client when it sends and receives character data to and from Adaptive Server.
323
Display and file character set command line options
Setting the display character set

Use the -a command line option if you are running the client from a terminal with a character set that differs from the client character set. In Figure 10-4, the -a option and the -J option are used together to identify the character set translation file (.xlt file) needed for the conversion. Use -a without -J only if the client character set is the same as the default character set.
Setting the file character set

Use the -q command line option if you are running bcp to copy character data to or from a file system that uses a character set that differs from the client character set. In Figure 10-4, use the -q or /filecharset option and the -J or /clientcharset option together to identify the character set translation file (.xlt file) needed for the conversion.
324
CH A PTE R
11
Diagnosing System Problems
This chapter discusses diagnosing and fixing system problems.

Topic How Adaptive Server uses error messages Adaptive Server error logging Backup Server error logging Killing processes Housekeeper functionality Configuring Adaptive Server to save SQL batch text Shutting down servers Learning about known problems Page 325 328 337 338 342 346 351 353
How Adaptive Server uses error messages

When Adaptive Server encounters a problem, it displays informationin an error message that describes whether the problem is caused by the user or the systemabout the problem, how serious it is, and what you can do to fix it. The error message consists of: A message number, which uniquely identifies the error message A severity level number between 10 and 24, which indicates the type and severity of the problem An error state number, which allows unique identification of the line of Adaptive Server code at which the error was raised An error message, which tells you what the problem is, and may suggest how to fix it
For example, this is what happens if you try to access a table that does not exist:
select * from publisher Msg 208, Level 16, State 1:
325
How Adaptive Server uses error messages
publisher not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
In some cases, there can be more than one error message for a single query. If there is more than one error in a batch or query, Adaptive Server usually reports only the first one. Subsequent errors are reported the next time you execute the batch or query. The error messages are stored in master..sysmessages, which is updated with each new version of Adaptive Server. Here are the first few rows (from an Adaptive Server with us_english as the default language):
select error, severity, description from sysmessages where error >=101 and error <=106 and langid is null error severity description ----- -------- -------------------------------------------------101 15 Line %d: SQL syntax error. 102 15 Incorrect syntax near '%.*s'. 103 15 The %S_MSG that starts with %.*s is too long. Maximum length is %d. 104 15 Order-by items must appear in the select-list if the statement contains set operators. 105 15 Unclosed quote before the character string '%.*s'. 106 16 Too many table names in the query. The maximum allowable is %d. (6 rows affected)
You can generate your own list by querying sysmessages. Here is some additional information for writing your query: If your server supports more than one language, sysmessages stores each message in each language. The column langid is NULL for us_english and matches the syslanguages.langid for other languages installed on the server. For information about languages on your server, use sp_helplanguage. The dlevel column in sysmessages is currently unused. The sqlstate column stores the SQLSTATE value for error conditions and exceptions defined in ANSI SQL92. Message numbers 17000 and higher are system procedure error messages and message strings.
326
CHAPTER 11
Error messages and message numbers

The combination of message number (error) and language ID (langid) uniquely identifies each error message. Messages with the same message number but different language IDs are translations.
select error, description, langid from sysmessages where error = 101 error ----101 101 101 description langid -------------------------------------- -----Line %d: SQL syntax error. NULL Ligne %1!: erreur de syntaxe SQL. 1 Zeile %1!: SQL Syntaxfehler. 2
(3 rows affected)
The error message text is a description of the problem. The descriptions often include a line number, a reference to a type of database object (a table, column, stored procedure, and so forth), or the name of a particular database object. In the description field of sysmessages, a percent sign (%) followed by a character or character string serves as a placeholder for these pieces of data, which Adaptive Server supplies when it encounters the problem and generates the error message. %d is a placeholder for a number; %S_MSG is a placeholder for a kind of database object; %.*sall within quotesis a placeholder for the name of a particular database object. Table 11-1 on page 328 lists placeholders and what they represent. For example, the description field for message number 103 is:
The %S_MSG that starts with '%.*s' is too long. Maximum length is %d.
The actual error message as displayed to a user might be:

The column that starts with 'title' is too long. Maximum length is 80.
For errors that you report to Technical Support, include the numbers, object types, and object names. (See Reporting errors on page 336.)
Variables in error message text

Table 11-1 explains the symbols that appear in the text provided with each error message explanation:
327
Adaptive Server error logging
Table 11-1: Error text symbols key Symbol %d, %D %x,%X,%.*x,%lx, %04x, %08lx %s %.*s, %*s, %*.s %S_type %c %f %ld %lf Stands for Decimal number Hexadecimal number Null-terminated string String, usually the name of a particular database object Adaptive Server-defined structure Single character Floating-point number Long decimal Double floating-point number

Error messages from Adaptive Server are sent only to the users screen. The stacktrace from fatal error messages (severity levels 19 and higher) and error messages from the kernel are also sent to an error log file. The name of this file varies; see the configuration documentation for your platform or the Utility Guide.
Note The error log file is owned by the user who installed Adaptive Server (or the person who started Adaptive Server after an error log was removed). Permissions or ownership problems with the error log at the operating system level can block successful start-up of Adaptive Server.
328
CHAPTER 11
Adaptive Server creates an error log for you if one does not already exist. You specify the location of the error log at start-up with the errorlogfile parameter in the runserver file or at the command line. The Sybase installation utility configures the runserver file with $SYBASE/install as the location of the error log if you do not choose an alternate location during installation. If you do not specify the location in the runserver file or at the command line, the location of the error log is the directory from which you start Adaptive Server. For more information about specifying the location of the error log, see dataserver in the Utility Guide.
Note Always start Adaptive Server from the same directory, or with the
runserver file or the error log flag, so that you can locate your error log. Each time you start a server, messages in the error log provide information on the success (or failure) of the start and the recovery of each database on the server. Subsequent fatal error messages and all kernel error messages are appended to the error log file. To reduce the size of the error log by deleting old or unneeded messages, prune the log while Adaptive Server is shut down.
Error log format

Entries in the error log include the following information: The engine involved for each log entry. The engine number is indicated by a 2-digit number. If only one engine is online, the display is 00. The family ID of the originating thread: In serial processing, the display is 00000. In parallel processing, the display is the server process ID number of the parent of the originating thread.
The server process ID of the originating thread: In serial processing, this is the server process ID number of the thread that generated the message. If the thread is a system task, then the display is 00000. In parallel processing, this is the server process ID number of the originating thread.
The date, displayed in the format yyyy/mm/dd, which allows you to sort error messages by date.
329
The time, displayed in 24-hour format, which includes seconds and hundredths of a second. The word server or kernel. This entry is for Sybase Technical Support use only. The error message itself.
Figure 11-1 shows two examples of a line from an error log:

Figure 11-1: Error log format
Single-engine server
00:00000:00008:1997/05/16 15:11:46.58 server Process id 9 killed by Hostname danish, Host process id 3507.
Multi-engine server Family ID Engine number
Server process ID
Date and time
00:00345:00023:1997/04/16 12:48:58.76 server The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.'
Severity levels
The severity level of a message indicates information about the type and severity of the problem that Adaptive Server has encountered. For maximum integrity, when Adaptive Server responds to error conditions, it displays messages from sysmessages, but takes action according to an internal table. A few corresponding messages differ in severity levels, so you may occasionally notice a difference in expected behavior if you are developing applications or procedures that refer to Adaptive Server messages and severity levels.
Warning! You can create your own error numbers and messages based on Adaptive Server error numbers (for example, by adding 20,000 to the Adaptive Server value). However, you cannot alter the Adaptive Server-supplied system messages in the sysmessages system table.
You can add user-defined error messages to sysusermessages with sp_addmessage. See the Reference Manual.
330
CHAPTER 11
Users should inform the System Administrator whenever problems that generate severity levels of 17 and higher occur. The System Administrator is responsible for resolving them and tracking their frequency. If the problem has affected an entire database, the System Administrator may have to use the database consistency checker (dbcc) to determine the extent of the damage. The dbcc may identify some objects that have to be removed. It can repair some damage, but you may have to reload the database. For more information, see the following chapters:
dbcc is discussed in Chapter 10, Checking Database Consistency.
Loading a user database is discussed in Chapter 12, Backing Up and Restoring User Databases. Loading system databases is discussed in Chapter 13, Restoring the System Databases.
The following sections discuss each severity level.
Security levels 1018

Error messages with severity levels 1016 are generated by problems that are caused by user errors. These problems can always be corrected by the user. Severity levels 17 and 18 do not terminate the users session. Error messages with severity levels 17 and higher should be reported to the System Administrator or Database Owner.
Level 10: Status information

Messages with severity level 10 are not errors at all. They provide additional information after certain commands have been executed and, typically, do not display the message number or severity level. For example, after a create database command has been run, Adaptive Server displays a message telling the user how much of the requested space has been allocated for the new database.
Level 11: Specified database object not found

Messages with severity level 11 indicate that Adaptive Server cannot find an object that was referenced in the command.
331
This is often because the user has made a mistake in typing the name of a database object, because the user did not specify the object owners name, or because of confusion about which database is current. Check the spelling of the object names, use the owner names if the object is not owned by you or dbo, and make sure you are in the correct database.
Level 12: Wrong datatype encountered

Messages with severity level 12 indicate a problem with datatypes. For example, the user may have tried to enter a value of the wrong datatype in a column or to compare columns of different and incompatible datatypes. To correct comparison problems, use the convert function with select. For information on convert, see the Reference Manual or the Transact-SQL Users Guide.
Level 13: User transaction syntax error

Messages with severity level 13 indicate that something is wrong with the current user-defined transaction. For example, you may have issued a commit transaction command without having issued a begin transaction, or you may have tried to roll back a transaction to a savepoint that has not been defined (sometimes there may be a typing or spelling mistake in the name of the savepoint). Severity level 13 can also indicate a deadlock, in which case the deadlock victims process is rolled back. The user must restart his or her command.
Level 14: Insufficient permission to execute command

Messages with severity level 14 mean that you do not have the necessary permission to execute the command or access the database object. You can ask the owner of the database object, the owner of the database, or the System Administrator to grant you permission to use the command or object in question.
Level 15: Syntax error in SQL statement

Messages with severity level 15 indicate that the user has made a mistake in the syntax of the command. The text of these error messages includes the line numbers on which the mistake occurs and the specific word near which it occurs.
332
CHAPTER 11
Level 16: Miscellaneous user error

Most error messages with severity level 16 reflect that the user has made a nonfatal mistake that does not fall into any of the other categories. Severity level 16 and higher can also indicate software or hardware errors. For example, the user may have tried to update a view in a way that violates the restrictions. Another error that falls into this category is unqualified column names in a command that includes more than one table with that column name. Adaptive Server has no way to determine which one the user intends. Check the command syntax and working database context. Messages that ordinarily have severities greater than 16 show severity 16 when they are raised by dbcc checktable or dbcc checkalloc so that checks can continue to the next object. When you are running the dbcc utility, check the Error Messages and Troubleshooting Guide for information about error messages between 2500 and 2599 with a severity level of 16.
Note Levels 17 and 18 are usually not reported in the error log. Users should
be instructed to notify the System Administrator when level 17 and 18 errors occur.
Level 17: Insufficient resources

Error messages with severity level 17 mean that the command has caused Adaptive Server to run out of resources or to exceed some limit set by the System Administrator. You can continue with the work you are doing, although you may not be able to execute a particular command. These system limits include the number of databases that can be open at the same time and the number of connections allowed to Adaptive Server. They are stored in system tables and can be checked with sp_configure. See Chapter 5, Setting Configuration Parameters, for more information on changing configuration variables. The Database Owner can correct the level 17 error messages indicating that you have run out of space. Other level 17 error messages should be corrected by the System Administrator.
333
Level 18: Non-fatal internal error detected

Error messages with severity level 18 indicate some kind of internal software bug. However, the command runs to completion, and the connection to Adaptive Server is maintained. You can continue with the work you are doing, although you may not be able to execute a particular command. An example of a situation that generates severity level 18 is Adaptive Server detecting that a decision about the access path for a particular query has been made without a valid reason. Since problems that generate such messages do not keep users from their work, users tend not to report them. Users should be instructed to inform the System Administrator every time an error message with this severity level (or higher) occurs so that the System Administrator can report them.
Severity levels 1926

Fatal problems generate error messages with severity levels 19 and higher. They break the users connection to Adaptive Server (some of the higher severity levels shut down Adaptive Server). To continue working, the user must restart the client program. When a fatal error occurs, the process freezes its state before it stops, recording information about what was happening. It is then killed and disappears. When the users connection is broken, he or she may or may not be able to reconnect and resume working. Some problems with severity levels in this range affect only one user and one process. Others affect all the processes in the database. In some cases, it will be necessary to restart Adaptive Server. These problems do not necessarily damage a database or its objects, but they can. They may also result from earlier damage to a database or its objects. Other problems are caused by hardware malfunctions. A backtrace of fatal error messages from the kernel is directed to the error log file, where the System Administrator can review it.
Level 19: Adaptive Server fatal error in resource

Error messages with severity level 19 indicate that some non-configurable internal limit has been exceeded and that Adaptive Server cannot recover gracefully. You must reconnect to Adaptive Server.
334
CHAPTER 11
Level 20: Adaptive Server fatal error in current process

Error messages with severity level 20 indicate that Adaptive Server has encountered a bug in a command. The problem has affected only the current process, and it is unlikely that the database itself has been damaged. Run dbcc diagnostics. You must reconnect to Adaptive Server.
Level 21: Adaptive Server fatal error in database processes

Error messages with severity level 21 indicate that Adaptive Server has encountered a bug that affects all the processes in the current database. However, it is unlikely that the database itself has been damaged. Restart Adaptive Server and run the dbcc diagnostics. You must reconnect to Adaptive Server.
Level 22: Adaptive Server fatal error: Table integrity suspect

Error messages with severity level 22 indicate that the table or index specified in the message was previously damaged by a software or hardware problem. The first step is to restart Adaptive Server and run dbcc to determine whether other objects in the database are also damaged. Whatever the report from dbcc may be, it is possible that the problem is in the cache only and not on the disk itself. If so, restarting Adaptive Server fixes the problem. If restarting does not help, then the problem is on the disk as well. Sometimes, the problem can be solved by dropping the object specified in the error message. For example, if the message tells you that Adaptive Server has found a row with length 0 in a nonclustered index, the table owner can drop the index and re-create it. Adaptive Server takes any pages or indexes offline that it finds to be suspect during recovery. Use sp_setsuspect_granularity to determine whether recovery marks an entire database or only individual pages as suspect. See sp_setsuspect_granularity in the Reference Manual for more information. You must reconnect to Adaptive Server.
Level 23: Fatal error: Database integrity suspect

Error messages with severity level 23 indicate that the integrity of the entire database is suspect due to previous damage caused by a software or hardware problem. Restart Adaptive Server and run dbcc diagnostics.
335
Even when a level 23 error indicates that the entire database is suspect, the damage may be confined to the cache, and the disk itself may be fine. If so, restarting Adaptive Server with startserver fixes the problem.
Level 24: Hardware error or system table corruption

Error messages with severity level 24 reflect some kind of media failure or (in rare cases) the corruption of sysusages. The System Administrator may have to reload the database. You may need to call your hardware vendor.
Level 25: Adaptive Server internal error

Level 25 errors are not displayed to the user; this level is only used for Adaptive Server internal errors.
Level 26: Rule error

Error messages with severity level 26 reflect that an internal locking or synchronization rule was broken. You must shut down and restart Adaptive Server.
Reporting errors
When you report an error, include: The message number, level number, and state number. Any numbers, database object types, or database object names that are included in the error message. The context in which the message was generated, that is, which command was running at the time. You can help by providing a hard copy of the backtrace from the error log.
336
CHAPTER 11
Backup Server error logging

Like Adaptive Server, Backup Server creates an error log if one does not already exist.You specify the location of the error log at start-up with the error_log_file parameter in the runserver file or at the command line. The Sybase installation utility configures the runserver file with $SYBASE/install as the location of the error log if you do not choose an alternate location during installation. If you do not specify the location in the runserver file or at the command line, the location of the error log is the directory from which you start Backup Server. Use the backupserver -V option (bcksvr -V on Windows NT) to limit the messages printed to the error log. For more information about specifying the location of the error log, see the sections describing Backup Server in the Utility Guide. Backup Server error messages are in the form:
MMM DD YYY: Backup Server:N.N.N.N: Message Text
Backup Server message numbers consist of 4 integers separated by periods, in the form N.N.N.N. Messages in the form N.N.N are sent by Open Server. The four components of a Backup Server error message are major.minor.severity.state: The major component generally indicates the functional area of the Backup Server code where the error occurred: 1 System errors 2 Open Server event errors 3 Backup Server remote procedure call errors 4 I/O service layer errors 5 Network data transfer errors 6 Volume handling errors 7 Option parsing errors
Major error categories 1 6 may result from Backup Server internal errors or a variety of system problems. Major errors in category 7 are almost always due to problems in the options you specified in your dump or load command. minor numbers are assigned in order within a major category. severity is: 1 informational, no user action necessary.
337
Killing processes
2, 3 an unexpected condition, possibly fatal to the session, has occurred. The error may have occurred with usage, environment, or internal logic, or any combination of these factors. 4 an unexpected condition, fatal to the execution of the Backup Server, has occurred. The Backup Server must exit immediately.
state codes have a one-to-one mapping to instances of the error report within the code. If you need to contact Technical Support about Backup Server errors, the state code helps determine the exact cause of the error.
Killing processes
A process is a unit of execution carried out by Adaptive Server. Each process is assigned a unique process identification number when it starts. This number is called a spid. These numbers are stored, along with other information about each process, in master..sysprocesses. Processes running in a parallelprocesses environment create child processes, each of which has its own spids. Several processes create and assign spids: starting Adaptive Server, login tasks, checkpoints, the housekeeper tasks, and so on. You can see most of the information by running sp_who. Running sp_who on a single-engine server shows the sp_who process running and all other processes that are runnable or in one of the sleep states. In multiengine servers, there can be a process running for each engine. The kill command gets rid of an ongoing process. The most frequent reason for killing a process is that it interferes with other users and the person responsible for running it is not available. The process may hold locks that block access to database objects, or there may be many sleeping processes occupying the available user connections. A System Administrator can kill processes that are: Waiting for an alarm, such as a waitfor command Waiting for network sends or receives Waiting for a lock Waiting for synchronization messages from another process in a family Most running or runnable processes
338
CHAPTER 11
Adaptive Server allows you to kill processes only if it can cleanly roll back any uncompleted transactions and release all system resources that are used by the process. For processes that are part of a family, killing any of the child processes also kilsl all other processes in the family. However, it is easiest to kill the parent process. For a family of processes, the kill command is detected more quickly if the status of the child processes is sync sleep. Table 11-2 shows the values that sp_who reports and when the kill command takes effect.
Table 11-2: Status values reported by sp_who Status
recv sleep send sleep alarm sleep lock sleep sync sleep
Indicates Waiting on a network read Waiting on a network send Waiting on an alarm such as:
waitfor delay "10:00"
Effects of kill command Immediate. Immediate. Immediate. Immediate. Immediate. Other processes in the family must also be brought to state in which they can be killed. Killed when it wakes up, usually immediate; a few sleeping processes do not wake up and require a Server restart to clear. Immediate. Immediate.
kill command not recommended. Server
Waiting on a lock acquisition Waiting on a synchronization message from another process in the family. Waiting on a disk I/O, or some other resource. Probably indicates a process that is running, but doing extensive disk I/O In the queue of runnable processes Actively running on one of the server engines Server has detected serious error condition; extremely rare A process, such as a threshold procedure, run by Adaptive Server rather than by a user process
sleeping
runnable running infected background
restart probably required to clear process. Immediate; use kill with extreme care. Recommend a careful check of sysprocesses before killing a background process. Immediate.
log suspend
Processes suspended by reaching the last-chance threshold on the log
Only a System Administrator can issue the kill command; permission to use it cannot be transferred. The syntax is:
kill spid
You can kill only one process at a time, but you can perform a series of kill commands in a batch. For example:
1> kill 7
339
Killing processes
2> kill 8 3> kill 9 4> go
A kill command is not reversible and cannot be included in a user-defined transaction. spid must be a numeric constant; you cannot use a variable. Here is some sample output from sp_who:
fid --0 0 0 0 0 0 0 0 0 0 (10 spid status loginame origname ---- --------- -------- -------1 recv sleep howard howard 2 sleeping NULL NULL 3 sleeping NULL NULL 4 sleeping NULL NULL 5 sleeping NULL NULL 6 sleeping NULL NULL 7 recv sleep bill bill 8 recv sleep wilbur wilbur 9 recv sleep joan joan 10 running foote foote rows affected, return status = 0) hostname -------svr30eng blk --0 0 0 0 0 0 0 0 0 0 dbname -----master master master master master master master master master master cmd ---------------AWAITING COMMAND NETWORK HANDLER DEADLOCK TUNE MIRROR HANDLER CHECKPOINT SLEEP HOUSEKEEPER AWAITING COMMAND AWAITING COMMAND AWAITING COMMAND SELECT
bigblue hazel luv2work svr47hum
In the example above, processes 26 cannot be killed: they are system processes. The login name NULL and the lack of a host name identify them as system processes. You will always see NETWORK HANDLER, MIRROR HANDLER, HOUSEKEEPER, and CHECKPOINT SLEEP (or, rarely, CHECKPOINT). AUDIT PROCESS becomes activated if you enable auditing. Processes 1, 8, 9, and 10 can be killed, since they have the status values recv sleep, send sleep, alarm sleep, and lock sleep. In sp_who output, you cannot tell whether a process whose status is recv sleep belongs to a user who is using Adaptive Server and may be pausing to examine the results of a command, or whether the process indicates that a user has restarted a PC or other terminal, and left a stranded process.You can learn more about a questionable process by querying the sysprocesses table for information. For example, this query shows the host process ID and client software used by process 8:
select hostprocess, program_name from sysprocesses where spid = 8 hostprocess program_name ----------- ---------------3993 isql
340
CHAPTER 11
This query, plus the information about the user and host from the sp_who results, provides additional information for tracking down the process from the operating system level.
Using kill with status only

The kill ...statusonly command reports on the progress of a server process ID (spid) in rollback status. It does not terminate the spid. The statusonly report displays the percent of rollback completed and the estimated length of time in seconds before the rollback completes. The syntax is:
kill spid with statusonly
Where spid is the number of the process you are terminating. For example, the following reports on the process of the rollback of spid number 13:
kill 13 with statusonly spid: 13 Transaction rollback in Estimated time left: 13 seconds spid: 13 Transaction rollback in Estimated time left: 9 seconds spid: 13 Transaction rollback in Estimated time left: 8 seconds spid: 13 Transaction rollback in Estimated time left: 7 seconds spid: 13 Transaction rollback in Estimated time left: 6 seconds spid: 13 Transaction rollback in Estimated time left: 5 seconds spid: 13 Transaction rollback in Estimated time left: 4 seconds spid: 13 Transaction rollback in Estimated time left: 3 seconds spid: 13 Transaction rollback in Estimated time left: 2 seconds spid: 13 Transaction rollback in Estimated time left: 0 seconds progress. Estimated rollback completion: 17% progress. Estimated rollback completion: 29% progress. Estimated rollback completion: 40% progress. Estimated rollback completion: 47% progress. Estimated rollback completion: 55% progress. Estimated rollback completion: 65% progress. Estimated rollback completion: 73% progress. Estimated rollback completion: 76% progress. Estimated rollback completion: 83% progress. Estimated rollback completion: 94%
If the rollback of the spid has completed when you issue kill...statusonly or if Adaptive Server is not rolling back the specified spid, kill...statusonly returns the following message:
Status report cannot be obtained. KILL spid:nn is not in progress.
341
Housekeeper functionality
Using sp_lock to examine blocking processes

In addition to sp_who, sp_lock can help identify processes that are blocking other processes. If the blk column in the sp_who report indicates that another process has been blocked while waiting to acquire locks, sp_lock can display information about the blocking process. For example, process 10 in the sp_who output above is blocked by process 7. To see information about process 7, execute:
sp_lock 7
For more information about locking in Adaptive Server, see the Performance and Tuning Guide.
The housekeeper provides important functionalities: The housekeeper feature consists of three tasks: housekeeper wash, housekeeper garbage collection, and housekeeper chores. sp_who recognizes all three tasks, as the following output shows:
blk_sp
fid id 0 0 0 0
spid status loginame origname hostname dbname cmd block_xloid 8 sleeping NULL NULL 0 master HK WASH 0 9 sleeping NULL NULL 0 master HK GC 0 10 sleeping NULL NULL 0 master HK CHORES 0 12 recv sleep sa sa chaucer 0
(11 rows affected, return status = 0)
The general automatic restart of housekeeper-related system tasks: you need not restart the server if these system tasks quit unexpectedly. A System Administrator can change all housekeeper task priorities.
sp_showpsexe, as well as sp_who, recognizes all three housekeeper
names. For more information about sp_who and sp_showpsexe, see the Reference Manual.
342
CHAPTER 11
Three housekeepers
The housekeeper work is divided among three separate tasks: Housekeeper wash task Housekeeper chores task Housekeeper garbage collection task
The output for all three tasks appears in the output for sp_who.
Housekeeper wash
Washing buffers is an optional task and runs at idle times only. You can turn off this task using the configuration parameter housekeeper free write percent. The housekeeper wash task is the only housekeeper task for which you use this configuration parameter.
Housekeeper chores
The housekeeper chores task runs at idle times only and does not use a common configuration parameter. It manages miscellaneous chores, such as: Flushing table statistics. Flushing account statistics. Handling timeout of detached transactions. You can turn off this chore using the configuration parameter dtm detach timeout period. Checking licence usage. You can turn this task off using the configuration parameter license information.
Housekeeper garbage collection

There are two forms of garbage collection, lazy and aggressive. These terms describe two distinct tests for finding empty pages.
343
Lazy garbage collection refers to an inexpensive test to find empty pages. This test may not be effective during long-running transactions, and empty pages may accumulate. Lazy garbage collection is inexpensive to use, but can lower performance. Performance is affected by the fragmentation of space allocated to a table, and by the accumulation of empty pages that must be evaluated during queries. Aggressive garbage collection refers to a sophisticated test for empty pages. This test is more expensive than the lazy garbage collection test, because it checks each deleted row in a page to determine whether that deleting transactions are committed. Both the delete command and the housekeeper garbage collection task can be configured for aggressive or lazy garbage collection, through the configuration parameter enable housekeeper GC. The aggressive housekeeper garbage collection self-tunes the frequency with which the housekeeper garbage collection task examines the housekeeper list, so that the frequency of examination matches the rate at which the application generates empty pages.
Running at user priority

The housekeeper garbage collection task operates at the priority level of an ordinary user, competing for CPU time with ordinary user tasks. This behavior prevents the list of empty pages from growing faster than the housekeeper can delete them.
Configuring enable housekeeper GC

To configure Adaptive Server for garbage collection task, use:
sp_configure "enable housekeeper GC", value
For example, enter:

sp_configure "enable housekeeper GC", 4
The following are the valid values for enable housekeeper GC configuration parameter:
344
CHAPTER 11
0 disables the housekeeper garbage collection task, but enables lazy garbage collection by the delete command. You must use reorg reclaim_space to deallocate empty pages. This is the cheapest option with the lowest performance impact, but it may cause performance problems if many empty pages accumulate. Sybase does not recommend using this value. 1 enables lazy garbage collection, by both the housekeeper garbage collection task and the delete command. This is the default value. If more empty pages accumulate than your application allows, consider options 4 or 5. You can use the optdiag utility to obtain statistics of empty pages. 2 reserved for future use. 3 reserved for future use. 4 enables aggressive garbage collection for both the housekeeper garbage collection task and the delete command. This option is the most effective, but the delete command is the most expensive. This option is ideal if the deletes on your data-only locked tables are in a batch. 5 enables aggressive garbage collection for the housekeeper, and lazy garbage collection by delete. This option is less expensive for deletes than option 4. This option is suitable when deletes are caused by concurrent transactions.
Using the reorg command

Garbage collection is most effective when you set enable housekeeper GC to 4 or 5. Sybase recommends that you set the parameter value to 5. However, if performance considerations prevent setting this parameter to 4 or 5, and you have an accumulation of empty pages, run reorg on the affected tables. You can obtain statistics on empty pages through the optdiag utility. When the server is shut down or crashes, requests to deallocate pages that the housekeeper garbage collection task has not yet serviced are lost. These pages, empty but not deallocated by the housekeeper garbage collection task, remain allocated until you remove them by running reorg. See Chapter 9, Using the reorg Command for more information on running reorg.
345
Configuring Adaptive Server to save SQL batch text

Occasionally a query or procedure causes Adaptive Server Monitor to hang. Users with the System Administrator role can configure Adaptive Server to grant Adaptive Server Monitor access to the text of the currently executing SQL batch. Viewing the SQL text of long-running batches helps you debug hung processes or fine-tune long statements that are heavy resource consumers. Adaptive Server must be configured to collect the SQL batch text and write it to shared memory, where the text can be read by Adaptive Server Monitor Server (the server component of Adaptive Server Monitor). The client requests might come from Monitor Viewer, which is a plug-in to Sybase Central, or other Adaptive Server Monitor Server applications. Configuring Adaptive Server to save SQL batch text also allows you to view the current query plan in showplan format (as you would see after setting showplan on). You can view the current query plan from within Adaptive Server; see Viewing the query plan of a SQL statement on page 349. SQL batches are viewable only through Adaptive Server Monitor Server. See the Adaptive Server Monitor Server documentation for more information about displaying the batch text. Because the query or procedure you are viewing may be nested within a batch of SQL text, the sysprocesses table now includes columns for the line number, statement number and spid of a hung statement to view its query plan. By default, Adaptive Server is not configured to save SQL batch text, so you must configure Adaptive Server to allocate memory for this feature. Adaptive Server Monitor access to SQL has no effect on performance if you have not configured any memory to save SQL batches.
Allocating memory for batch text

You can configure the amount of the SQL text batch you want to save. When text saving is enabled, Adaptive Server copies the subsequent SQL text batches to memory shared with SQL Server Monitor. Because each new batch clears the memory for the connection and overwrites the previous batch, you can view only currently executing SQL statements.
Saving SQL text
Configure the amount of SQL text retained in memory (see Configuring the amount of SQL text retained in memory on page 347).
346
CHAPTER 11
Enable Adaptive Server to start saving SQL text (see Enabling Adaptive Server to start saving SQL text on page 348).
Note You must have System Administration privileges to configure and
save SQL text batches.
Configuring the amount of SQL text retained in memory

After installation, you must decide the maximum amount of SQL text that can be copied to shared memory. Consider the following to help you determine how much memory to allocate per user: SQL batches exceeding the allocated amount of memory are truncated without warning. If you do not allocate enough memory for the batch statements, the text you are interested in viewing might be the section of the batch that is truncated. For example, if you configure Adaptive Server to save the amount of text designated by bracket A in the illustration, but the statement that is running occurs in the text designated by bracket B, Adaptive Server will not display the statement that is running. The more memory you allocate for SQL text from shared memory, the less chance the problem statement will be truncated from the batch copied to shared memory. However, Adaptive Server immediately rejects very large values because they do not leave enough memory for data and procedure caches.
Sybase recommends an initial value of 1024 bytes per user connection. Use sp_configure with the max SQL text monitored configuration parameter to allocate shared memory, where bytes_per_connection (the maximum number of bytes saved for each client connection) is between 0 (the default) and 2,147,483,647 (the theoretical limit):
sp_configure "max SQL text monitored", bytes_per_connection
Since memory for SQL text is allocated by Adaptive Server at start-up, you must restart Adaptive Server for this parameter to take effect. The total memory allocated for the SQL text from shared memory is the product of bytes_per_connection multiplied by the number of user connections.
347
Enabling Adaptive Server to start saving SQL text

After you allocate shared memory for SQL text, Adaptive Server saves a copy of each SQL batch whenever you enable an Adaptive Server Monitor event summary that includes SQL batches. You may also have to reconfigure Adaptive Server Monitors event buffer scan interval for SQL text. See the Adaptive Server Monitor documentation for more information.
SQL commands not represented by text

If you use Client-Library functions not represented by text (such as ct_cursor or ct_dynamic) to issue SQL commands, Client-Library encodes the information for efficiency, and Adaptive Server generally decodes and displays key command information. For example, if you open a cursor with ct_cursor and the command is running, the Adaptive Server Monitor event summary displays the cursor name and the cursor declare statement. Table 11-3 lists a complete list of the Client-Library functions not represented by text:
Table 11-3: SQL commands not represented by text Client-Library routine
ct_cursor ct_cursor ct_cursor ct_cursor ct_fetch (when processing the results of ct_cursor) ct_cursor CURSOR_ROWS, or ct_cancel when the connection has
DB-Library routine N/A N/A N/A N/A N/A N/A
Presentation name CLOSE_CURSOR DECLARE_CURSOR DELETE_AT_CURSOR FETCH_CURSOR FETCH_CURSOR CURSOR_INFO
Presentation data Cursor name, statement Cursor name, statement Cursor name, statement Cursor name, statement Cursor name, statement Cursor name, statement Cursor name, statement Cursor name, statement
Client-Library cursors
ct_cursor ct_cursor
N/A N/A
OPEN_CURSOR UPDATE_AT_CURSOR
348
CHAPTER 11
Client-Library routine ct_command (CS_RPC_CMD) (default behavior)

ct_dynamic
DB-Library routine dbrpcinit (only in version 10.0.1 or later) N/A
Presentation name DBLIB_RPC DYNAMIC_SQL
Presentation data RPC name Dynamic statement name, statement None None None RPC name
ct_command (CS_MSG_CMD ct_param ct_param ct_command (CS_RPC_CMD) (only when a TDS version earlier than 5.0 is used)
N/A
dbrpcparam dbrpcparam dbrpcparam (in
MESSAGE PARAM_FORMAT PARAMS RPC
DB-Library versions earlier than 10.0.1)
For more information about SQL commands not represented by text, see your Open Client documentation.
Viewing the query plan of a SQL statement

Use sp_showplan and the spid of the user connection in question to retrieve the query plan for the statement currently running on this connection. You can also use sp_showplan to view the query plan for a previous statement in the same batch. The syntax is:
declare @batch int declare @context int declare @statement int execute sp_showplan <spid_value>, @batch_id= @batch output, @context_id= @context output, @stmt_num=@statement output
where: batch_id is the unique number for a batch. context_id is a unique number for every procedure (or trigger) executed in the batch. stmt_num is the number of the current statement within a batch.
349
Adaptive Server uses the unique batch ID to synchronize the query plan with the batch text and other data retrieved by Adaptive Server Monitor.
Note You must be a System Administrator to execute sp_showplan.
For example, to see the query plan for the current statement for spid 99, enter:
declare @batch int declare @context int declare @statement int exec sp_showplan 99, @batch output, @context output, @statement output
You can run the query plan procedure independently of Adaptive Server Monitor, regardless of whether or not Adaptive Server has allocated shared memory for SQL text.
Viewing previous statements

To see the query plan for the previous statement in the same batch, issue sp_showplan with the same values as the original query, but subtract one from the statement number. Using this method, you can view all the statements in the statement batch back to query number one.
Viewing a nested procedure

Although sp_showplan allows you to view the query plan for the current statement, the actual statement that is running may exist within a procedure (or within a nested chain of procedures) called from the original SQL batch. Table 11-4 shows the columns in sysprocesses that contain information about these nested statements.
Table 11-4: Columns added to sysprocesses Column
id stmtnum linenum
Datatype Integer Integer Integer
Specifies The object ID of the running procedure (or 0 if no procedure is running) The current statement number within the running procedure (or the SQL batch statement number if no procedure is running) The line number of the current statement within the running stored procedure (or the line number of the current SQL batch statement if no procedure is running)
This information is saved in sysprocesses, regardless of whether SQL text is enabled or any memory is allocated for SQL text.
350
CHAPTER 11
To display the id, stmtnum, and linenum columns, enter:

select id, stmtnum, linenum from sysprocesses where spid = spid_of_hung_session Note You do not need the sa_role to run this select statement.
Shutting down servers

A System Administrator can shut down Adaptive Server or Backup Server with the shutdown command. The syntax is:
shutdown [backup_server_name] [with {wait|nowait}]
The default for the shutdown command is with wait. That is, shutdown and shutdown with wait do exactly the same thing.
Shutting down Adaptive Server

If you do not provide a server name, shutdown shuts down the Adaptive Server you are using. When you issue a shutdown command, Adaptive Server: 1 2 3 Disables logins, except for System Administrators Performs a checkpoint in each database, flushing pages that have changed from memory to disk Waits for currently executing SQL statements or procedures to finish
In this way, shutdown minimizes the amount of work that automatic recovery must do when you restart Adaptive Server. The with nowait option shuts down Adaptive Server immediately. User processes are aborted, and recovery may take longer after a shutdown with nowait. You can help minimize recovery time by issuing a checkpoint command before you issue a shutdown with nowait command.
351
Shutting down servers
Shutting down a Backup Server

To shut down a Backup Server, give the Backup Servers name:
shutdown SYB_BACKUP
The default is with wait, so any dumps or loads in progress complete before the Backup Server process halts. After you issue a shutdown command, no new dump or load sessions can be started on the Backup Server. To see the names of the Backup Servers that are accessible from your Adaptive Server, execute sp_helpserver. Use the value in the name column in the shutdown command. You can shut down a Backup Server only if it is: Listed in sysservers on your Adaptive Server, and Listed in your local interfaces file.
Use sp_addserver to add a Backup Server to sysservers.
Checking for active dumps and loads

To see the activity on your Backup Server before executing a shutdown command, run sp_who on the Backup Server:
SYB_BACKUP...sp_who spid status loginame hostname blk cmd ----- -------- -------- ---------- --- -------------1 sleeping NULL NULL 0 CONNECT HANDLER 2 sleeping NULL NULL 0 DEFERRED HANDLER 3 runnable NULL NULL 0 SCHEDULER 4 runnable NULL NULL 0 SITE HANDLER 5 running sa heliotrope 0 NULL
Using nowait on a Backup Server

The shutdown backup_server with nowait command shuts down the Backup Server, regardless of current activity. Use it only in severe circumstances. It can leave your dumps or loads in incomplete or inconsistent states. If you use shutdown with nowait during a log or database dump, check for the message indicating that the dump completed. If you did not receive this message, or if you are not sure whether the dump completed, your next dump should be a dump database, not a transaction dump. This guarantees that you are not relying on possibly inconsistent dumps.
352
CHAPTER 11
If you use shutdown with nowait during a load of any kind, and you did not receive the message indicating that the load completed, you may not be able to issue further load transaction commands on the database. Run a full database consistency check (dbcc) on the database before you use it. You may have to reissue the full set of load commands, starting with load database.
Learning about known problems

The release bulletin is a valuable resource for learning about known problems or incompatibilities with Adaptive Server and Backup Server. Reading the release bulletin in advance can save you the time and guesswork of troubleshooting known problems. The Adaptive Server installation program also installs files that list all system problem reports (SPRs) and closed problem reports (CPRs) for Adaptive Server. Problem reports are organized by functional areas of the product. For example, a file named cpr_bus would contain a listing of closed (fixed) problem reports pertaining to the Backup Server, and the file spr_bus would contain a list of currently open problem reports for the Backup Server. See the release bulletin to learn the location of CPR and SPR files.
353
Learning about known problems
354
PA RT
Security Administration
The following chapters discuss security administation in Adaptive Server: Chapter 13, Getting Started With Security Administration in Adaptive Server, provides an overview of the security features available in Adaptive Server. Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections, describes methods for managing Adaptive Server login accounts and database users. Chapter 15, Managing Remote Servers, discusses the steps the System Administrator and System Security Officer of each Adaptive Server must execute to enable remote procedure calls (RPCs). Chapter 16, External Authentication, describes the network-based security services that enable you to authenticate users and protect data transmitted among machines on a network. Chapter 17, Managing User Permissions, describes the use and implementation of user permissions. Chapter 18, Auditing, describes how to set up auditing for your installation. Chapter 19, Confidentiality of Data, how to configure Adaptive Server to ensure that all data is secure and confidential
CH A PTE R
1 2
Introduction to Security
This chapter provides an overview of the security features available in Adaptive Server.
Topic Introduction to security What is information security? Information security standards Page 357 358 359
Introduction to security
Information is an asset to your company, and possibly your company's greatest asset. Information needs protection just like any other asset. Your company locks its doors at the end of the day, allowing only employees with a key to the building to enter. Similarly, your company needs to determine how best to protect the information contained in the databases, and who has access to the information. In the past, organizations relied on physical separation and dedicated systems to ensure that sensitive information did not fall into the wrong hands. However, this approach is inadequate because of significant hardware and software costs, and the inability to meet operational requirements. As a counter-measure, individual database server need strong, yet flexible, security support. Users and the data they access can be anywhere in the world, connected by untrusted networks, and ensuring the confidentiality and integrity of sensitive data and transactions in this environment is critical. The same systems that allow users to access the data from anywhere in the world also open up the information for users who should not have access to the information. Information is only useful if it gets to the people who need it, when they need it, regardless of where they are. With complex and dynamically changing business relationships, it is critical that information gets only to authorized users.
357
What is information security?
What is information security?

It is important for your organization to determine what information security means to the organization. This is not a one-size-fits-all concept. One organizations acceptable level of security could be another organizations worst nightmare. Although everybody has different definitions, these are guidelines for considering security Sensitive information should be kept confidential you need to determine who should have access to what information The system should enforce integrity the server should enforce the rules and constraints to ensure the information remains accurate and complete. The information should be available even with all the safeguards in place, anybody who needs access to the information should have it available when the information is needed..
You should identify where your organizations security requirements originate from. That is, what is it that your organization wants to protect and what does the outside world require of your organization: Identify the information assets and the security risks associated with them if they become vulnerable or compromised. Identify and understand any laws, statutes, regulations, and contractual agreements that apply to your organization and the information assets. Identify your organizations business processes and the requirements they impose on information assets, to balance practical considerations with the security risks.
Remember that these requirements can change over time. You will probably have to revisit and reassess the security requirements to make sure they still reflect your organizations needs. After you and your organization determines what information security means, you must set up a series of controls and policies that meet the company's security objectives. One desirable outcome of these efforts is an information security policy document that clarifies decisions made for information security. For more information about security features in Adaptive Server, see Chapter 13, Getting Started With Security Administration in Adaptive Server.
358
CHAPTER 12
Information security standards

Over the years Adaptive Server has been certified to various security standards, including the NSA Class C2 criteria and, more recently, the Common Criteria certification. Adaptive Server release 15.0 uses FIPS-140-2 certified modules for SSL encryption. This section describes these certifications.
Adaptive Server version 12.5.2 available for common criteria configuration

Adaptive Server version 12.5.2 is available for the common criteria configuration (called the Evaluated Configuration). The Evaluated Configuration consists of Adaptive Server version 12.5.2 with the security and directory services options, but enables only the row level access control and auditing features. Adaptive Servers evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the Adaptive Server Enterprise Target of Evaluation (TOE) was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 2.1 and International Interpretations effective on April 1, 2004. If you configure Adaptive Server as specified in the Supplement for Installing Adaptive Server for Common Criteria Configuration, Adaptive Server satisfies all of the security functional requirements stated in the Sybase Adaptive Server Enterprise Security Target (Version 1.0). Adaptive Server supports seven security functions: Security audit an audit mechanism that checks access, authentication attempts, and administrator functions. The security audit records the date, time, responsible individual and other details describing the event in the audit trail. User data protection Adaptive Server implements the discretionary access control policy over applicable database objects: databases, tables, views, and stored procedures. Identification and authentication Adaptive Server provides its own identification and authentication mechanism in addition to the underlying operating system mechanism.
359
Security management functions that allow you to manage users and associated privileges, access permissions, and other security functions such as the audit trail. These functions are restricted based on discretionary access control policy rules, including role restrictions. Protection of the TSF Adpative Server protects itself by keeping its context separate from that of its users and by using operating system mechanisms to ensure that memory and files used by Adaptive Server have the appropriate access settings. Adaptive Server interacts with users through well-defined interfaces designed to ensure that its security policies are enforced. Resource utilization Adaptive Server provides resource limits to prevent queries and transactions from monopolizing server resources. TOE access: Adaptive Server allows authorized administrators to construct login triggers that restrict logins to a specific number of sessions and restrict access based on time. Authorized administrators can also restrict access based on user identities.
Adaptive Server 15.0 contains all of the security features included in Adaptive Server cersion 12.5.2 and additional new security features. The additional security features are listed in Whats New in Adaptive Server 15.0?
C2 security evaluation for Adaptive Server release 11.0.6

SQL Server version 11.0.6 passed the security evaluation by the National Security Agency (NSA) at the Class C2 criteria. (The requirements for the C2 criteria are given by the Department of Defense in DOD 52.00.28-STD, Department of Defense Trusted Computer System Evaluation Criteria [TCSEC], also known as the Orange Book.) The configuration of SQL Server version 11.0.6 that was evaluated at the C2 security level by the NSA in 1996 on the HP 9000 HP-UX BLS, 9.09+ platform is referred to as the evaluated configuration. Certain features of SQL Server, such as remote procedures and direct updates to system tables, were excluded from the evaluated configuration. Notes in the Adaptive Server documentation indicate particular features that were not included in the evaluated configuration. For a complete list of features that were excluded from the evaluated configuration, see Appendix A in the SQL Server Installation and Configuration Guide for HP 9000 HP-UX BLS, 9.09+.
360
CHAPTER 12
SSL is the standard for securing the transmission of sensitive information, such as credit card numbers, stock trades, and banking transactions over the Internet. It relies on public key cryptography. SSL implementation uses FIPS 140-2 Validated level 1 cryptographic modules using Certicom Security Builder GSE for products running on Windows, Solaris, AIX and HPUX operating systems. Adaptive Server release 15.0 contains all of the security features included in SQL Server version 11.0.6 plus some new security features. Table 13-4 on page 367 summarizes the major features.
FIPS 140-2 Validated cryptographic module

SSL is the standard for securing the transmission of sensitive information, such as credit card numbers, stock trades, and banking transactions over the Internet. It relies on public key cryptography. SSL implementation uses FIPS 140-2 Validated level 1 cryptographic modules using Certicom Security Builder GSE for products running on Windows, Solaris, AIX and HPUX operating systems. For more information, see validation certificate #542, dated June 2, 2005 at NIST website, http://csrc.nist.gov/cryptval/140-1/1401val.htm.
361
362
CH A PTE R
1 3
Getting Started With Security Administration in Adaptive Server
This chapter provides an overview of the security features available in Adaptive Server.
Topic General process of security administration Recommendations for setting up security An example of setting up security Discretionary access controls Introduction to Security Features in Adaptive Server Identification and authentication External authentication Managing remote servers Discretionary access controls Division of roles Auditing for accountability Confidentiality of data Page 363 364 366 369 367 368 368 369 369 371 372 372
General process of security administration

Table 13-1 describes the major tasks that are required to administer Adaptive Server in a secure manner and refers you to the documentation that contains the instructions for performing each task.
363
Recommendations for setting up security
Table 13-1: General process for security administration Task 1. Install Adaptive Server, including auditing. Description This task includes preparing for installation, loading files from your distribution medium, performing the actual installation, and administering the physical resources that are required. This includes enabling auditing, granting roles to individual users to ensure individual accountability, assigning login names to System Administrators and System Security Officers and establishing password and login policies. Add logins, create groups, add users to databases, drop and lock logins, and assign initial passwords. Assign roles to users, create user-defined roles, and define role hierarchies and mutual exclusivity of roles. Grant and revoke permissions for certain SQL commands, executing certain system procedures, and accessing databases, tables, particular table columns, and views. Establish and administer the access that is permitted between servers, add and drop remote server access, and map remote login names to local login names. Determine what is to be audited, audit the use of Adaptive Server, and use the audit trail to detect penetration of the system and misuse of resources. Configure the server to use services, such as LDAP, PAM or Kerberos- based User Authentication, Windows unified Login, , data confidentiality with encryption, data integrity.. See The the installation documentation for your platform
2. Set up a secure administrative environment.
Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections
3. Add user logins to the server; add users to databases; establish groups and roles; set proxy authorization. 4. Administer permissions for users, groups, and roles. 5. Administer the use of remote servers.
Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections
Chapter 17, Managing User Permissions
Chapter 15, Managing Remote Servers, and the Adaptive Server installation and configuration documentation for your platform Chapter 18, Auditing, and the Adaptive Server installation and configuration documentation for your platform Chapter 16, External Authentication and Chapter 19, Confidentiality of Data.
6. Set up and maintain auditing.
7. Set up your installation for advanced authentication mechanisms and network security..
Recommendations for setting up security

The following describes logins and how they relate to security.
364
CHAPTER 13
Using the sa login

When Adaptive Server is installed, a single login called sa is configured with the System Administrator and System Security Officer roles. This means that the sa login has unlimited power. Use the sa login only during initial setup. Instead of allowing several users to use the sa account, establish individual accountability by assigning specific roles to individual administrators.
Warning! When logging in to Adaptive Server, do not use the -P option of isql to specify your password because another user may have an opportunity to see it.
Changing the sa login password

The sa login is configured initially with a NULL password. Use sp_password to change the password immediately after installation.
When to enable auditing

Enable auditing early in the administration process so that you have a record of privileged commands that are executed by System Security Officers and System Administrators. You might also want to audit commands that are executed by those with other special roles, such as operators when they dump and load databases.
Assigning login names

Assign Adaptive Server login names that are the same as their respective operating system login names. This makes logging in to Adaptive Server easier, simplifies management of server and operating system login accounts, and makes it easier to correlate the audit data generated by Adaptive Server with that of the operating system.
365
An example of setting up security
An example of setting up security

Suppose you have decided to assign special roles to the users listed in Table 132.
Table 13-2: Users to whom you will assign roles Name Rajnish Smith Catharine Macar-Swan Soshi Ikedo Julio Rozanski Alan Johnson Priviledge s
sso_role sa_role sa_role oper_role dbo
Operating system login name rsmith cmacar sikedo jrozan ajohnson
Table 13-3 shows the sequence of commands you might use to set up a secure operating environment for Adaptive Server, based upon the role assignments shown in Table 13-2. After logging in to the operating system, you would issue these commands using the initial sa account.
Table 13-3: Examples of commands used to set up security Commands isql -Usa sp_audit security, all, all, on sp_audit all, sa_role, all, on sp_audit all, sso_role, all, on sp_configure auditing, 1 Enables auditing. Result Logs in to Adaptive Server as sa. Both sa_role and sso_role are active. Sets auditing options for server-wide, security-relevant events and the auditing of all actions that have sa_role or sso_role active.
Note Before you enable auditing, set up a threshold procedure for the audit trail and determine how to handle the
transaction log in sybsecurity. For details, see Chapter 18, Auditing. sp_addlogin rsmith, js&2P3d,
@fullname = "Rajnish Smith"
Adds logins and passwords for Rajnish, Catharine, Soshi, and Julio. A default database is not specified for any of these users, so their default database is master.
sp_addlogin cmacar, Fr3ds#1,

@fullname = "Catharine Macar-Swan"
sp_addlogin sikedo, mi5pd1s,

@fullname = "Soshi Ikedo"
sp_addlogin jrozan, w1seCrkr,

@fullname = "Julio Rozanski"
366
CHAPTER 13
Commands grant role sso_role to rsmith grant role sa_role to sikedo grant role sa_role to cmacar grant role oper_role to jrozan use sybsecurity sp_changedbowner rsmith
use master sp_addlogin ajohnson, j06n50n, @fulname = "Alan Johnson" create database sales_summary use sales_summary sp_changedbowner ajohnson sp_modifylogin ajohnson, 'defdb', sales_summary sp_locklogin sa,"lock"
Result Grants the sso_role to Rajnish, the sa_role to Soshi and Catharine, and the oper_role to Julio.
Grants access to the auditing database, sybsecurity, by making Rajnish, who is the System Security Officer, the database owner. Alan is not granted any system-defined roles. Creates a new database sales_summary and makes Alan the owner of this database. Because he is the database owner, Alan can now create users, create new database objects and grant permissions to other users in this database.
Locks the sa login so that no one can log in as sa. Individuals can assume only the roles that are configured for them.
Note Do not lock the sa login until you have granted individual users the sa_role and sso_role roles and have
verified that the roles operate successfully.
Introduction to Security Features in Adaptive Server

Table 13-4 describes the security features in Adaptive Server.
Table 13-4: Major security features Security feature Identification and authentication controls Discretionary Access Controls (DAC) Description Ensures that only authorized users can log into the system. In addition to password based login authentication, Adaptive Server supports external authentication using Kerberos, LDAP, or PAM. Provides access controls that give object owners the ability to restrict access to objects, usually with the grant and revoke commands. This type of control is dependent upon an object owners discretion.
367
Identification and authentication
Security feature Division of roles
Description Allows an administrator to grant privileged roles to specified users so only designated users can perform certain tasks. Adaptive Server has predefined roles, called system roles, such as System Administrator and System Security Officer. In addition, Adaptive Server allows System Security Officers to define additional roles, called user-defined roles. Provides the ability to audit events such as logins, logouts, server start operations, remote procedure calls, accesses to database objects, and all actions performed by a specific user or with a particular role active. Adaptive Server also provides a single option to audit a set of server-wide security-relevant events. Maintains a confidentiality of data using encrytion for Client-Server communications, available with Kerberos or SSL. Data that is not active is kept confidential with password-protected database backup.
Accountability
Identification and authentication

Adaptive Server uses the Server User Identity (SUID) to uniquely identify a user with a login account name. This identity is linked to a particular User Identity (UID) in each database. Access controls use the identity when determining whether to allow access for the user with this SUID to an object. Authentication verifies that a user is actually the person they claim to be. Adaptive Server allows both internal and external mechanisms for authentication. Identification and authentication controls are discussed in Chapter 14, Managing Adaptive Server Logins, Database Users, and Client Connections. In addition, see Using proxy authorization on page 556 and Chapter 15, Managing Remote Servers.
External authentication
Security is often enhanced in large, heterogeneous applictions by authenticating logins with a central repository. Adaptive Server supports a variety of external authentication methods:
368
CHAPTER 13
Kerberos provides a centralized and secure authentication mechanism in enterprise environments that include the Kerberos infrastructure. Authentication occurs with a trusted, third-party server calls a Key Distribution Center (KDC) to verify both the client and the server. LDAP User Authentication Lightweight Directory Access Protocol (LDAP) provides a centralized authentication mechanism based on a users login name and password. PAM User Authentication Pluggable Authentication Module (PAM) provides a centralized authentication mechanism that uses interfaces provided by the operating system for both administration and runtime application interfaces.
For more information about each of these methods of external authentication, see Chapter 16, External Authentication.
Managing remote servers

Internal mechanisms for administering logins and users between Adaptive Servers are described in Chapter 15, Managing Remote Servers.
Discretionary access controls

Owners of objects can grant access to those objects to other users. Object owners can also grant other users the ability to pass the access permission to other users. With Adaptive Servers discretionary access controls, you can give various kinds of permissions to users, groups, and roles with the grant command. Use the revoke command to rescind these permissions. The grant and revoke commands give users permission to execute specified commands and to access specified tables, views, and columns. Some commands can be used at any time by any user, with no permission required. Others can be used only by users of a certain status such as a System Administrator and are not transferable.
369
Discretionary access controls
The ability to assign permissions for the commands that can be granted and revoked is determined by each users status (as System Administrator, Database Owner, or database object owner), and by whether or not a particular user has been granted a permission with the option to grant that permission to other users. Discretionary access controls are discussed in Chapter 17, Managing User Permissions.
Policy-Based Access Control

The policy-based access control provides a powerful and flexible means of protecting data, down to the row level. Administrators define security policies that are based on the value of individual data elements, and the server enforces these policies transparently. Once an administrator defines a policy, it is automatically invoked whenever the affected data is queried through applications, ad hoc queries, stored procedures, views, and so on. Using the policy-based access control simplifies both the security administration of an Adaptive Server installation and the application development process because it is the server, not the application, that enforces security. This allows developers to concentrate on implementing business functionality while administrators focus on defining a security policy to enforce consistently across the entire server. These are the features that allow you to implement policy-based access control: Access Rules Application Context Facility Login Triggers Domain Integrity Rules
For more information on how to implement policy-based access controls, see Using row-level access control on page 528.
370
CHAPTER 13
Division of roles
An important feature in Adaptive Server is the division of roles. The roles supported by Adaptive Server enable you to enforce and maintain individual accountability. Adaptive Server provides system roles, such as System Administrator and System Security Officer, and user-defined roles, which are created by a System Security Officer. Roles provide individual accountability for users performing operational and administrative tasks. Their actions can be audited and attributed to them.
Role hierarchy
A System Security Officer can define role hierarchies such that if a user has one role, the user automatically has roles lower in the hierarchy. For example, the chief_financial_officer role might contain both the financial_analyst and the salary_administrator roles. The Chief Financial Officer can perform all tasks and see all data that can be viewed by the Salary Administrators and Financial Analysts.
Mutual exclusivity
Two roles can be defined to be mutually exclusive for: Membership a single user cannot be granted both roles. For example, an installation might not want a single user to have both the payment_requestor and payment_approver roles to be granted to the same user. Activation a single user cannot activate, or enable, both roles. For example, a user might be granted both the senior_auditor and the equipment_buyer roles, but the installation may not want to permit the user to have both roles enabled at the same time.
System roles, as well as user-defined roles, can be defined to be in a role hierarchy or to be mutually exclusive. For example, you might want a super_user role to contain the System Administrator, Operator, and Tech Support roles. In addition, you might want to define the System Administrator and System Security Officer roles to be mutually exclusive for membership; that is, a single user cannot be granted both roles.
371
Auditing for accountability
See Creating and assigning roles to users on page 387 for information on administering and using roles.
Auditing for accountability

Adaptive Server includes a comprehensive audit system. The audit system consists of a system database called sybsecurity, configuration parameters for managing auditing, a system procedure, sp_audit, to set all auditing options, and a system procedure, sp_addauditrecord, to add user-defined records to the audit trail. When you install auditing, you can specify the number of audit tables that Adaptive Server will use for the audit trail. If you use two or more tables to store the audit trail, you can set up a smoothly running audit system with no manual intervention and no loss of records. A System Security Officer manages the audit system and is the only user who can start and stop auditing, set up auditing options, and process the audit data. As a System Security Officer, you can establish auditing for events such as: Server-wide, security-relevant events Creating, deleting, and modifying database objects All actions by a particular user or all actions by users with a particular role active Granting or revoking database access Importing or exporting data Logins and logouts
Auditing functionality is discussed in Chapter 18, Auditing.
Adaptive server allows you to maintain the confidentiality of data by encrypting client-server communications using the secure socket layer (SSL) standard or using Kerberos. For more information about SSL, see Chapter 19, Confidentiality of Data.
372
CHAPTER 13
For more information about Kerberos, see Chapter 16, External Authentication.
Password-Protected Database Backup

dump and load database include a password parameter that allows you to password-protect your database dumps. For more information, see Reference Manual: Commands and Chapter 12, Backing Up and Restoring User Databases, in Volume 2 of the System Administration Guide.
373
374
CH A PTE R
1 4
Managing Adaptive Server Logins, Database Users, and Client Connections
This chapter describes how to manage Adaptive Server login accounts and database users.
Topic Overview Choosing and creating a password Adding logins to Adaptive Server Login failure to Adaptive Server Creating groups Adding users to databases Number of user and login IDs Creating and assigning roles to users Dropping users, groups, and user-defined roles Locking or dropping Adaptive Server login accounts Changing user information Using aliases in databases Getting information about users Establishing a password and login policy Monitoring license use Getting information about usage: chargeback accounting Page 376 377 377 380 380 381 385 387 399 401 403 408 411 417 428 431
375
Overview
Overview
The responsibility of adding new logins to Adaptive Server, adding users to databases, and granting them permission to use commands and database objects is divided among the System Security Officer, System Administrator, and Database Owner.
Note The Adding new users procedure creates login accounts for a particular server using sp_addlogin, which stores account information in the
syslogins table on that server. You can also create and store login accounts on a LDAP server.
Adding new users
1 2
A System Security Officer uses sp_addlogin to create a server login account for a new user. A System Administrator or Database Owner uses sp_adduser to add a user to a database. This command can also give the user an alias or assign the user to a group. For more information, see Creating groups on page 380. A System Security officer grants specific roles to the user. A System Administrator, Database Owner, or object owner grants the user or group specific permissions on specific commands and database objects. Users or groups can also be granted permission to grant specific permissions on objects to other users or groups. See Chapter 17, Managing User Permissions for detailed information about permissions.
3 4
Table 14-1 summarizes the system procedures and commands used for these tasks.
Table 14-1: Adding users to Adaptive Server and databases Task Create new logins, assign passwords, default databases, default language, and full name Create groups Create and assign roles Add users to database, assign aliases, and assign groups Required role System Security Officer Command or procedure
sp_addlogin
Database Any database
Database Owner or System Administrator System Security Officer Database Owner or System Administrator
sp_addgroup create role sp_adduser
User database
User database
376
CHAPTER 14
Task Grant groups, users, or roles permission to create or access database objects
Required role Database Owner, System Administrator, or object owner
Command or procedure
grant
Database User database
Choosing and creating a password

Your password helps prevent access by unauthorized people. When you create your password, follow these guidelines: Do not use information such as your birthday, street address, or any other word or number that has anything to do with your personal life. Do not use names of pets or loved ones. Do not use words that appear in the dictionary or words spelled backwards.
The most difficult passwords to guess are those that combine uppercase and lowercase letters and numbers. Never give anyone your password, and never write it down where anyone can see it. Follow these rules to create a password: Passwords must be at least 6 bytes long. Passwords can consist of any printable letters, numbers, or symbols. A password must be enclosed in quotation marks in sp_addlogin if it: Includes any character other than AZ, az, 09,_, #, valid single-byte or multibyte alphabetic characters, or accented alphabetic characters Begins with a number 09
Adding logins to Adaptive Server

Use sp_addlogin to add a new login name to Adaptive Server. You do not use it to give the user permission to access user databases. Use sp_adduser for that purpose. Only the System Security Officer can execute sp_addlogin. The syntax is:
377
Adding logins to Adaptive Server
sp_addlogin loginame, passwd [, defdb] [, deflanguage [, fullname]]]
where: loginame is the new users login name. The login name must follow the rules for identifiers and must be unique on Adaptive Server. To simplify both the login process and server administration, make the Adaptive Server login name the same as the users operating system login name. This makes logging in to Adaptive Server easier because many client programs use the operating system login name as a default. It also simplifies management of server and operating system login accounts, and makes it easier to correlate usage and audit data generated by Adaptive Server and by the operating system. passwd is the password for the new user. For guidelines on choosing and creating secure passwords, see Choosing and creating a password on page 377. For information on changing a password, see Changing passwords on page 404. defdb is the default database, where the user starts each session of Adaptive Server.
Note The default database is master. To discourage users from creating database objects in the master database, assign a default database other than master to most users.
A System Administrator can change anyones default database with sp_modifylogin. Other users can change only their own default database. After specifying the default database, add the user to the default database with sp_adduser so that he or she can log in directly to the default database. deflanguage is the default language in which the users prompts and messages are displayed. If you omit this parameter, Adaptive Servers default language is used. A System Administrator can change any users default language with sp_modifylogin. Other users can change only their own language. fullname is the full name of the user. This is useful for documentation and identification purposes. If omitted, no full name is added. A System Administrator can change any users full name with sp_modifylogin. Other users can change only their own full name.
378
CHAPTER 14
The following statement sets up an account for the user maryd with the password 100cents, the default database (master), the default language, and no full name:
sp_addlogin "maryd", "100cents"
The password requires quotation marks because it begins with 1. After this statement is executed, maryd can log in to Adaptive Server. She is automatically treated as a guest user in master, with limited permissions, unless she has been specifically given access to master. The following statement sets up a login account (omar_khayyam) and password (rubaiyat) and makes pubs2 the default database for this user:
sp_addlogin omar_khayyam, rubaiyat, pubs2
To specify a full name for a user and use the default database and language, specify null in place of the defdb and deflanguage parameters. For example:
sp_addlogin omar, rubaiyat, null, null, "Omar Khayyam"
Alternatively, you can specify a parameter name, in which case you do not have to specify all the parameters. For example:
sp_addlogin omar, rubaiyat, @fullname = "Omar Khayyam"
When you execute sp_addlogin, Adaptive Server adds a row to master.dbo.syslogins, assigns a unique user ID (suid) for the new user, and fills in other information. When a user logs in, Adaptive Server looks in syslogins for the name and password provided by the user. The password column is encrypted with a one-way algorithm so it is not human-readable. The suid column in syslogins uniquely identifies each user on Adaptive Server. A users suid remains the same, no matter what database he or she is using. The suid 1 is always assigned to the default sa account that is created when Adaptive Server is installed. Other users server user IDs are integers assigned consecutively by Adaptive Server each time sp_addlogin is executed.
379
Login failure to Adaptive Server
Login failure to Adaptive Server

Adaptive Server must successfully authenticate a user before they are able to access data in Adaptive Server. If the authentication attempt fails, Adaptive Server returns the following message and the network connection is terminated:
isql -U bob -P badpass Msg 4002, Level 14, State 1: Server 'ACCOUNTING' Login failed. CT-LIBRARY error: ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed
This message is a generic login failure message that does not tell the connecting user whether the failure resulted from a bad user name or a bad password. This generic message guards against malicious attempts to gain access to Adaptive Server.
Creating groups
Groups provide a convenient way to grant and revoke permissions to more than one user in a single statement. Groups enable you to provide a collective name to a group of users. They are especially useful if you administer an Adaptive Server installation that has a large numbers of users. Every user is a member of the group public and can also be a member of one other group. (Users remain in public, even when they belong to another group.) It is probably most convenient to create groups before adding users to a database, since sp_adduser can assign users to groups as well as add them to the database. A System Administrator or the Database Owner can create a group at any time with sp_addgroup. The syntax is:
sp_addgroup grpname
The group name, a required parameter, must follow the rules for identifiers. The System Administrator can assign or reassign users to groups with sp_changegroup. To set up the Senior Engineering group, use the following command while using the database to which you want to add the group:
380
CHAPTER 14
sp_addgroup senioreng
sp_addgroup adds a row to sysusers in the current database. Therefore, each group in a database, as well as each user, has an entry in sysusers.
Adding users to databases

The Database Owner or a System Administrator can use sp_adduser to add a user to a specific database. The user must already have an Adaptive Server login. The syntax is:
sp_adduser loginame [, name_in_db [, grpname]]
where: loginame is the login name of an existing user. name_in_db specifies a name that is different from the login name by which the user is to be known inside the database. You can use this feature to accommodate users preferences. For example, if there are five Adaptive Server users named Mary, each must have a different login name. Mary Doe might log in as maryd, Mary Jones as maryj, and so on. However, if these users do not use the same databases, each might prefer to be known simply as mary inside a particular database. If no name_in_db parameter is given, the name inside the database is the same as loginame.
Note This capability is different from the alias mechanism described in
Using aliases in databases on page 408, which maps the identity and permissions of one user to another. grpname is the name of an existing group in the database. If you do not specify a group name, the user is made a member of the default group public. Users remain in public even if they are a member of another group. See Changing a users group membership on page 406 for information about modifying a users group membership.
sp_adduser adds a row to the sysusers system table in the current database. When a user has an entry in the sysusers table of a database, he or she:
Can issue use database_name to access that database
381
Will use that database by default, if the default database parameter was issued as part of sp_addlogin Can use sp_modifylogin to make that database the default
This example shows how a Database Owner could give access permission to maryh of the engineering group eng, which already exists:
sp_adduser maryh, mary, eng
This example shows how to give maryd access to a database, keeping her name in the database the same as her login name:
sp_adduser maryd
This example shows how to add maryj to the existing eng group, keeping her name in the database the same as her login name by using null in place of a new user name:
sp_adduser maryj, null, eng
Users who have access to a database still need permissions to read data, modify data, and use certain commands. These permissions are granted with the grant and revoke commands, discussed in Chapter 17, Managing User Permissions.
Adding a guest user to a database

Creating a user named guest in a database enables any user with an Adaptive Server account to access the database as a guest user. If a user issues the use database_name command, and his or her name is not found in the databases sysusers or sysalternates table, Adaptive Server looks for a guest user. If there is one, the user is allowed to access the database, with the permissions of the guest user. The Database Owner can add a guest entry to the sysusers table of the database with sp_adduser:
sp_adduser guest
The guest user can be removed with sp_dropuser, as discussed in Dropping users on page 400.
382
CHAPTER 14
If you drop the guest user from the master database, server users who have not yet been added to any databases cannot log in to Adaptive Server.
Note Although more than one individual can be a guest user in a database, you
can still use the users server user ID, which is unique within the server, to audit each users activity. For more information about auditing, see Chapter 18, Auditing.
guest user permissions

guest inherits the privileges of public. The Database Owner and the owners of database objects can use grant and revoke to make the privileges of guest either more or less restrictive than those of public. See Chapter 17, Managing User Permissions, for a description of the public privileges. When you install Adaptive Server, master..sysusers contains a guest entry. The installation script for the pubs2 database also contains a guest entry for its sysusers table.
guest user in user databases

In user databases, the Database Owner adds a guest user that permits all Adaptive Server users to use that database. This saves the owner from having to use sp_adduser to explicitly name each one as a database user. You can use the guest mechanism to restrict access to database objects while allowing access to the database. For example, the owner of the titles table could grant select permission on titles to all database users except guest by executing these commands:
grant select on titles to public sp_adduser guest revoke all on titles from guest
guest user in pubs2 and pubs3

The guest user entry in the sample databases allows new Adaptive Server users to follow the examples in the Transact-SQL Users Guide. The guest is given a wide range of privileges, including:
select permission and data modification permission on all of the user
tables
383
execute permission on all of the procedures create table, create view, create rule, create default, and create procedure
permissions
Adding a guest user to the server

The System Security Officer can use sp_addlogin to enter a login name and password that visiting users are instructed to use. Typically, such users are granted restricted permissions. A default database may be assigned.
Warning! A visitor user account is not the same as the guest user account. All users of the visitor account have the same server user ID; therefore, you cannot audit individual activity. Each guest user has a unique server ID, so you can audit individual activity and maintain individual accountability. Setting up a visitor account to be used by more than one user is not recommended because you lose individual accountability.
You can add a visitor user account named guest to master..syslogins using sp_addlogin. This guest user account takes precedence over the system guest user account. If you add a visitor user named guest with sp_adduser, this impacts system databases such as sybsystemprocs and sybsystemdb, which are designed to work with system guest user in them.
Adding remote users

You can allow users on another Adaptive Server to execute stored procedures on your server by enabling remote access. Working with the System Administrator of the remote server, you can also allow users of your server to execute remote procedure calls to the remote server. To enable remote procedure calls, both the local and the remote server must be configured. For information about setting up remote servers and adding remote users, see Chapter 15, Managing Remote Servers.
384
CHAPTER 14
Number of user and login IDs

Adaptive Server supports over 2,000,000,000 logins per server and users per database. Adaptive Server uses negative numbers as well as positive numbers to increase the range of possible numbers available for IDs.
Limits and ranges of ID numbers

Table 14-2 describes the valid ranges for the ID types.
Table 14-2: Ranges for ID types ID type Logins per server (suid) Users per database (uid) Groups per database (guid) Server limits 2 billion plus 32K 2 billion less 1032193 16,390 to 1,048,576
Figure 14-1 illustrates the limits and ranges for logins, users, and groups.
Figure 14-1: Users, groups, and logins available in Adaptive Server
-32768 (@@minsuid)
0 1 2 sa suid probe suid
16383
1048576
2 billion (@@maxsuid)
User IDs
Group IDs 16384 (@@mingroupid) -32768 SUIDs 1048576 (@@maxgroupid) 2 billion
Login connection limitations

Although Adaptive Server allows you to define over 2,000,000,000 logins per server, the actual number of users that can connect to Adaptive Server at one time is limited by the: Value of the number of user connections configuration parameter, and
385
Number of user and login IDs
Number of file descriptors available for Adaptive Server. Each login uses one file descriptor for the connection.
Note The maximum number of concurrent tasks running on the server is
still 32,000.
Allowing the maximum number of logins and simultaneous connections
1 2
Configure the operating system on which Adaptive Server is running for at least 32,000 file descriptors. Set the value of number of user connections to at least 32,000.
Note Before Adaptive Server can have more than 64K logins and
simultaneous connections, you must first configure the operating system for more than 64K file descriptors. See your operating system documentation for information about increasing the number of file descriptors.
Viewing server limits for logins, users, and groups

Table 14-3 lists the global variables for the server limits of logins, users, and groups:
Table 14-3: Global variables for logins, users, and groups Name of variable @@invaliduserid @@minuserid @@guestuserid @@mingroupid @@maxgroupid @@maxuserid @@minsuid @@probesuid @@maxsuid What it displays Invalid user ID Lowest user ID Guest user ID Lowest group user ID Highest group user ID Highest user ID Lowest server user ID Probe server user ID Highest server user ID Value -1 -32768 2 16384 1048576 2147483647 -32768 2 2147483647
To issue a global variable, enter:

select variable_name
For example:
386
CHAPTER 14
select @@minuserid -----------32768
Creating and assigning roles to users

The final steps in adding database users are assigning them special roles, as required, and granting permissions. For more information on permissions, see Chapter 17, Managing User Permissions. The roles supported by Adaptive Server enable you to enforce individual accountability. Adaptive Server provides system roles, such as System Administrator and System Security Officer, and user-defined roles, which are created by a System Security Officer. Object owners can grant database access as appropriate to each role.
System-defined roles
Table 14-4 lists the system roles, the value to use for the role_granted option of the grant role or revoke role command, and the tasks usually performed by a person with that role.
387
Table 14-4: System roles and related tasks Role System Administrator System Security Officer Operator Sybase technical support Replication Distributed transaction manager High availability Monitor and diagnosis Job Scheduler administration Job Scheduler user Real Time messaging Web Services Value for role_granted
sa_role sso_role oper_role sybase_ts_role replication_role dtm_tm_role ha_role mon_role js_admin_role js_user_role messaging_role web_services
Description Manages and maintains Adaptive Server databases and disk storage Performs security-related tasks Backs up and loads databases server-wide Analysis and repair of database structures Replicate user data Coordinate transactions across servers Administer and execute Failover Administer and execute performance and diagnostic monitoring Administer Job Scheduler Create and run jobs through Job Scheduler Administer and execute Real Time Messaging Administer Web Services
System Administrator privileges

This section describes the roles available for Adaptive Server. System Administrators: Handle tasks that are not specific to applications Work outside Adaptive Servers discretionary access control system
The role of System Administrator is usually granted to individual Adaptive Server logins. All actions taken by that user can be traced to his or her individual server user ID. If the server administration tasks at your site are performed by a single individual, you may instead choose to use the sa account that is installed with Adaptive Server. At installation, the sa account user has permission to assume the System Administrator, System Security Officer, and Operator roles. Any user who knows the sa password can log in to that account and assume any or all of these roles.
388
CHAPTER 14
The fact that a System Administrator operates outside the protection system serves as a safety precaution. For example, if the Database Owner accidentally deletes all the entries in the sysusers table, the System Administrator can restore the table (as long as backups exist). There are several commands that can be issued only by a System Administrator. They include disk init, disk refit, disk reinit, shutdown, kill, and the disk mirror commands. In granting permissions, a System Administrator is treated as the object owner. If a System Administrator grants permission on another users object, the owners name appears as the grantor in sysprotects and in sp_helprotect output. In addition, System Administrators are responsible for dropping logins and can lock and unlock logins. System Security Officers share login management responsibilities with System Administrators. System Security Officers are responsible for adding logins and can also lock and unlock logins.
System Security Officer privileges

System Security Officers perform security-sensitive tasks in Adaptive Server, including: Granting the System Security Officer and Operator roles Administering the audit system Changing passwords Adding new logins Locking and unlocking login accounts Creating and granting user-defined roles Administering network-based security Granting permission to use the set proxy or set session authorization commands
The System Security Officer can access any databaseto enable auditing but, in general, has no special permissions on database objects. An exception is the sybsecurity database, where only a System Security Officer can access the sysaudits table. There are also several system procedures that can be executed only by a System Security Officer.
389
System Security Officers can repair any damage inadvertently done to the protection system by a user. For example, if the Database Owner forgets his or her password, a System Security Officer can change the password to allow the Database Owner to log in. System Security Officers can also create and grant user-defined roles to users, other roles, or groups. For information about creating and granting user-defined roles, see Creating and assigning roles to users on page 387.
Operator privileges
Users who have been granted the Operator role can back up and restore databases on a server-wide basis without having to be the owner of each database. The Operator role allows a user to use these commands on any database:
dump database dump transaction load database load transaction
Sybase technical support

The Sybase Tech Support role allows access for a Sybase Technical Support engineer to display internal memory and on-disk data structures through trace output, consistency checking, and patching data structures. This role is used for analyzing problems and recovering data by hand. Some actions necessary for resolving these issues may require additional system roles for access. Sybase recommends that this role be granted only to a knowledgeable Sybase engineer by the system security officer while this analysis or repair is being done.
Replication role
The user maintaining Replication Server and ASE Replicator requires the Replication role. See the Replication Server Administration Guide and the ASE Replicator User's Guide for information about this role.
390
CHAPTER 14
Distributed Transaction Manager role

The Distributed Transaction Manager (DTM) transaction coordinator uses this role to allow system stored procedures to administer transactions across servers. Clients using the DTM XA interface require this role. See Using Adaptive Server Distributed Transaction Management Features for more information.
High availability role

You must have the high availability role to configure the high availability subsystem to administer primary and companion servers through commands and stored procedures. See Using Sybase Failover in a High Availability System for more information..
Monitoring and diagnosis

This role is required to administer the Adaptive Server Monitoring and Diagnostics (MDA) subsystem. You must have this role to execute a MDA remote Ppocedure call and to administer the collection of monitored data. See the Performance and Tuning Guide: Monitoring for more information.
Job Scheduler roles

The Job Scheduler has three system roles to manage permissions for its operation:
js_admin_role required to administer Job Scheduler, and provides access to the stored procedures and allow you to modify, delete, and perform Job Scheduler administrative operations. js_user_role required for a user to create, modify, delete, and run
scheduled jobs using the Job Scheduler stored procedures. See the Job Scheduler User's Guide for more information.
391
Real-Time Messaging role

Used by the Real-Time Messaging (RTMS) subsystem execute msgsend, msgrecv, and certain sp_msgadmin commands. See the Messaging Services Users Guide for more information.
Web Services role

Used by the Web Services subsystem to execute create service, create existing service, drop service, and alter service. See the Web Services Users Guide for more information.
User-defined roles
Planning user-defined roles
Before you implement user-defined roles, decide: The roles you want to create The responsibilities for each role The position of each in the role hierarchy Which roles in the hierarchy are mutually exclusive Whether such exclusivity is at the membership level or activation level
User-defined role names cannot duplicate user names. Avoid name conflicts when you create user-defined roles by following a naming convention. For example, you could use the _role suffix for role names. Adaptive Server does not check for such restrictions. If a role must have the same name as a user, you can avoid conflict by creating a new role, having it contain the original role, and then granting the new role to the user.
Configuring user-defined roles

After you have planned the roles to create and the relationships among them, configure your system for user-defined roles with the max roles enabled per user configuration parameter.
392
CHAPTER 14
The maximum number of roles that a user can activate per user session is 127. The default value is 20. The minimum number of roles, which is 10, includes the system roles that come with Adaptive Server. The maximum number of roles that can be activated server-wide is 992. The first 32 roles are reserved for Sybase system roles.
Creating a user-defined role

Use the create role command to create a role. The syntax is:
create role role_name [with passwd "password"]
where: role_name is the name of a new role. password is an optional password that must be specified by the user who will use the role.
For example, to create the intern_role without a password, enter:

create role intern_role
To create the doctor_role and assign the password physician, enter:

create role doctor_role with passwd "physician"
Adding and removing passwords from a role

Only a System Security Officer can add or drop a password from a role. Use the alter role command to add or drop a password from either a system or user-defined role. The syntax is:
alter role role_name [add passwd password | drop passwd]
For example, to require the password oper8x for the oper_role, enter:
alter role oper_role add passwd oper8x
To drop the password from the role, enter:

alter role oper_role drop passwd
393
Role hierarchies and mutual exclusivity

A System Security Officer can define role hierarchies such that if a user has one role, the user also has roles lower in the hierarchy. For example, the chief_financial_officer role might contain both the financial_analyst and the salary_administrator roles, as shown in Figure 14-2.
Figure 14-2: Role hierarchy
Chief Financial Officer Financial Analyst Salary Administrator
The Chief Financial Officer can perform all tasks and see all data that can be viewed by the Salary Administrators and Financial Analysts. Roles can be defined to be mutually exclusive for: Membership one user cannot be granted two different roles. For example, you might not want the payment_requestor and payment_approver roles to be granted to the same user. Activation one user cannot activate, or enable, two different roles. For example, a user might be granted both the senior_auditor and the equipment_buyer roles, but not permitted to have both roles enabled at the same time.
System roles, as well as user-defined roles, can be defined to be in a role hierarchy or to be mutually exclusive. For example, you might want a super_user role to contain the System Administrator, Operator, and tech_support roles. You might also want to define the System Administrator and System Security Officer roles to be mutually exclusive for membership; that is, one user cannot be granted both roles.
Role heirarchies and mutual exclusivity

This section describes role heirarchies.
Defining and changing mutual exclusivity of roles

To define mutual exclusivity between two roles, use:
alter role role1 { add | drop } exclusive { membership | activation } role2
394
CHAPTER 14
For example, to define intern_role and specialist_role as mutually exclusive at the membership level, enter:
alter role intern_role add exclusive membership specialist_role
To define sso_role and sa_role as mutually exclusive at the activation level, enter:
alter role sso_role add exclusive activation sa_role
Defining and changing a role hierarchy

Defining a role hierarchy involves choosing the type of hierarchy and the roles, then implementing the hierarchy by granting roles to other roles. For example:
grant role intern_role to specialist_role grant role doctor_role to specialist_role Figure 14-3: Creating a role hierarchy
specialist intern doctor
In Figure 14-3, the specialist role contains the doctor and intern roles. This means that specialist has all the privileges of both doctor and intern. To establish a hierarchy with a super_user role containing the sa_role and oper_role system roles, specify:
grant role sa_role to super_user grant role oper_role to super_user Note If a role that requires a password is contained within another role, the
user with the role that contains the other does not need to use the password for the contained role. For example, in Figure 14-3, say the doctor role usually requires a password. The user who has the specialist role does not need to enter the doctor password because doctor is contained within specialist. Role passwords are only required for the highest level role. When creating role hierarchies:
395
You cannot grant a role to another role that directly contains it. This prevents duplication. For example, in Figure 14-3, you cannot grant doctor to specialist because specialist already contains doctor.
You can grant a role to another role that does not directly contain it. For example, in Figure 14-4, you can grant the intern role to the specialist role, even though specialist already contains the doctor role, which contains intern. If you subsequently dropped doctor from specialist, then specialist still contains intern. In Figure 14-4, doctor has consultant role permissions because consultant has been granted doctor. The specialist role also has consultant role permissions because specialist contains the doctor role, which in turn contains the consultant. However, intern does not have consultant role privileges, because intern does not contain the consultant role, either directly or indirectly.
Figure 14-4: Explicitly and implicitly granted privileges
specialist doctor consultant intern
You cannot grant a role to another role that is contained by the first role. This prevents loops within the hierarchy. For example, in Figure 14-5, you cannot grant the specialist role to the consultant role; consultant is already contained in specialist.
396
CHAPTER 14
Figure 14-5: Granting a role to a role contained by grantor
NOT ALLOWED specialist doctor consultant intern
When the System Security Officer grants a user a role that contains other roles, the user implicitly gets membership in all roles contained by the granted role. However, a role can only be activated or deactivated directly if the user has explicit membership in that role. The System Security Officer cannot grant one role to another role that is explicitly or implicitly mutually exclusive at the membership level with the first role. For example, in Figure 14-6, if the intern role is defined as mutually exclusive at the membership level with the consultant role, the System Security Officer cannot grant intern to the doctor.
Figure 14-6: Mutual exclusivity at membership
specialist doctor consultant
intern
The user can activate or deactivate only directly granted roles. For example, in the hierarchy shown in Figure 14-6, assume that you have been granted the specialist role. You have all the permissions of the specialist role, and, implicitly, because of the hierarchy, you have all the permissions of the doctor and consultant roles. However, you can activate only the specialist role. You cannot activate doctor or consultant because they were not directly granted to you. For information, see Activating and deactivating roles on page 399.
397
Revoking roles from other roles is similar to granting roles to other roles. It removes a containment relationship, and the containment relationship must be a direct one, as shown in Figure 14-7:
Figure 14-7: Effect of revoking roles on role hierarchy
specialist doctor consultant intern
For example, in Figure 14-7: If the System Security Officer revokes the doctor role from specialist, specialist no longer contains the consultant role or the intern role. The System Security Officer cannot revoke the intern role from specialist because intern is not directly contained by specialist.
Setting up default activation at login

A System Security Officer can change a roles default setting for any user. Individual users can change only their own default settings. When a user logs in to Adaptive Server, the users roles are not necessarily active, depending upon the default that is set for the role. If a role has a password associated with it, the user must use the set role command to activate the role. The System Security Officer or user determines whether to activate any roles granted by default at login. sp_modifylogin sets the default status of user roles individually for each user. sp_modifylogin only effects user roles, not system roles. By default, user-defined roles are not activated at login, but system roles are automatically activated, if they do not have passwords associated with them. To set up a role to activate at login:
sp_modifylogin loginname, "add default role", role_name
To ensure that a role is inactive at login:

sp_modifylogin loginname, "drop default role", role_name
398
CHAPTER 14
For example, to change the default setting for Ralphs intern_role to be active automatically at login, execute:
sp_modifylogin ralph, "add default role", intern_role
Activating and deactivating roles

Roles must be active to have the access privileges of each role. Depending on the default set for a role, the role may or may not be active at login. If the role has a password, it is always inactive at login. To activate or deactivate a role:
set role role_name [on|off]
To activate or deactivate a role that has an attached password, use:

set role role_name with passwd "password" [on|off]
For example, to activate the financial_analyst role with the password sailing19, enter:
set role financial_analyst with passwd "sailing19" on
Activate roles only when you need them, and turn them off when you no longer need them. For example, when the sa_role is active, you assume the identity of Database Owner within any database that you use. To turn off the System Administrator role and assume your real user identity, use:
set role sa_role off
If you are granted a role during a session, and you want to activate it immediately, use set role to turn it on.
Dropping users, groups, and user-defined roles

Table 14-5 list the system procedures that allow a System Administrator or Database Owner to drop users and groups.
Table 14-5: Dropping users and groups Task Drop user from database Drop group from database Required role Database Owner or System Administrator Database Owner or System Administrator System procedure
sp_dropuser sp_dropgroup
Database User database User database
399
Dropping users, groups, and user-defined roles
Dropping users
A Database Owner or a System Administrator can use sp_dropuser to deny an Adaptive Server user access to the database in which sp_dropuser is executed. (If a guest user is defined in that database, the user can still access that database as guest.) The following is the syntax, where name_in_db is usually the login name, unless another name has been assigned:
sp_dropuser name_in_db
You cannot drop a user who owns objects. Since there is no command to transfer ownership of objects, you must drop objects owned by a user before you drop the user with sp_dropuser. To deny access to a user who owns objects, use sp_locklogin to lock his or her account. You also cannot drop a user who has granted permissions to other users. Use revoke with cascade to revoke permissions from all users who were granted permissions by the user to be dropped, then drop the user. You must then grant permissions to the users again, if appropriate.
Dropping groups
Use sp_dropgroup to drop a group. The syntax is:
sp_dropgroup grpname
You cannot drop a group that has members. If you try to do so, the error report displays a list of the members of the group you are attempting to drop. To remove users from a group, use sp_changegroup, discussed in Changing a users group membership on page 406.
Dropping user-defined roles

To drop a role, use the following, where role_name is the name of a user-defined role:
drop role role_name [with override]
with override revokes all access privileges granted to the role in every database
server-wide.
400
CHAPTER 14
If the role has any access privileges already granted, you must revoke all privileges granted to the role in all databases before you can drop the role. If you do not, the command fails. To revoke privileges: Use the revoke command, or Use the with override option with the drop role command. The with override option ensures that Adaptive Server automatically removes permission information for the role from all databases.
You need not drop memberships before dropping a role. Dropping a role automatically removes any users membership in that role, regardless of whether you use the with override option.
Locking or dropping Adaptive Server login accounts

To prevent a user from logging in to Adaptive Server, you can either lock or drop an Adaptive Server login account. Locking a login is safer than dropping it because locking a login account maintains the suid so that it cannot be reused.
Warning! Adaptive Server may reuse the server user ID (suid) of a dropped login account when the next login account is created. This occurs only when the dropped login holds the highest suid in syslogins; however, it can compromise accountability if execution of sp_droplogin is not being audited. Also, it is possible for a user with the reused suid to access database objects that were authorized for the old suid.
You cannot drop a login when: The user is in any database. The login belongs to the last remaining System Security Officer or System Administrator.
Table 14-6: Locking or dropping login accounts Task Lock login account, which maintains the suid so that it cannot be reused Drop login account, which allows reuse of suid Required role System Administrator or System Security Officer System Administrator System procedure
sp_locklogin sp_droplogin
Database
master master
401
Locking or dropping Adaptive Server login accounts
Locking and unlocking login accounts

Use sp_locklogin to lock and unlock accounts or to display a list of locked accounts. You must be a System Security Officer to use sp_locklogin. The syntax is:
sp_locklogin [ {login_name | "all"}, { "lock" | "unlock" } ]
where: loginame is the name of the account to be locked or unlocked. It must be an existing valid account.
all indicates to lock or unlock all login accounts on an Adaptive Server, except those with sa_role. lock | unlock specifies whether the account is to be locked or unlocked.
To display a list of all locked logins, use sp_locklogin with no parameters. You can lock an account that is currently logged in, and the user is not locked out of the account until he or she logs out. You can lock the account of a Database Owner, and a locked account can own objects in databases. In addition, you can use sp_changedbowner to specify a locked account as the owner of a database. Adaptive Server ensures that there is always at least one unlocked System Security Officers account and one unlocked System Administrators account.
Dropping login accounts

A System Administrator can use sp_droplogin to deny a user access to Adaptive Server. The syntax is:
sp_droplogin loginame
You cannot use sp_droplogin to drop a user from any database on the server. Use sp_dropuser to drop the user from a database. You cannot drop a user from a database if that user owns any objects in the database. For more information, see Dropping users on page 400.
Locking logins that own thresholds

This section discusses thresholds and how they are affected by locked user logins.
402
CHAPTER 14
As a security measure, threshold stored procedures are executed using the account name and roles of the login that created the procedure. You cannot drop the login of a user who owns a threshold. If you lock the login of a user who owns a threshold, the threshold cannot execute the stored procedure.
Threshold procedures are executed with the most limited set of the roles assigned to the user. The user must have both of the following: The set of roles active for the user at the time the threshold was added or last modified, and The set of roles directly granted to the user at the time the threshold fires.
If a threshold requires a particular role, that role must be active for the user when the threshold is created. If that role is later revoked, the threshold cannot execute the procedure. The last-chance threshold, and thresholds created by the sa login are not affected by sp_locklogin. If you lock the sa login, the last chance threshold and thresholds created or modified by the sa user still fire.
Changing user information

Table 14-7 lists the system procedures you use to change passwords, default database, default language, full name, or group assignment.
Table 14-7: System procedures for changing user information Task Change your password Change another users password Change authentication mechanism Change your default database, default language, or full name Change a login accounts default database, default language, or full name Change the group assignment of a user Required role None System Security Officer System Security Officer None System Administrator System Administrator, Database Owner System procedure
sp_password sp_password sp_modifylogin sp_modifylogin sp_modifylogin sp_changegroup
Database Any database Any database Any database Any database Any database User database
403
Changing passwords
All users can change their passwords at any time using sp_password. The System Security Officer can use sp_password to change any users password. The syntax is:
sp_password caller_passwd, new_passwd [, loginame]
where: caller_passwd is the password of the login account that is currently executing sp_password. new_passwd is the new password for the user executing sp_password, or for the user indicated by loginame. For guidelines on choosing and creating secure passwords, see Choosing and creating a password on page 377. loginame can be used only by a System Security Officer to change another users password.
For example, a user can change his or her own password from 3blindmice to 2mediumhot using:
sp_password "3blindmice", "2mediumhot"
These passwords are enclosed in quotes because they begin with numbers. In the following example, the System Security Officer whose password is 2tomato changes Victorias password to sesame1:
sp_password "2tomato", sesame1, victoria
Requiring new passwords

You may choose to use the systemwide password expiration configuration parameter to establish a password expiration interval, which forces all Adaptive Server users to change their passwords on a regular basis. For information, see Chapter 5, Setting Configuration Parameters. Even if you do not use systemwide password expiration, it is important, for security reasons, that users change their passwords periodically. The column pwdate in the syslogins table records the date of the last password change. The following query selects all login names whose passwords have not changed since September 15, 1997:
select name, pwdate from syslogins where pwdate < "Sep 15 1997"
404
CHAPTER 14
Null passwords
Do not assign a null password. When Adaptive Server is installed, the default sa account has a null password. The following example shows how to change a null password to a valid one:
sp_password null, "8M4LNCH" Note null is not enclosed in quotes in the statement.
Logging in after lost password

If your site encounters any of these situations: All System Administrator login accounts are locked. All System Security Officer login accounts are locked. The password for sa_role or sso_role has been lost,
You can restart Adaptive Server with the dataserver -plogin_name parameter, which allows you to set a new password for these accounts and roles if there is no way to recover a lost password. login_name is the name of the user or the name of the role (sa_role or sso_role) whose password needs to be reset. This allows you to set a new password for these account if there is no way to recover a lost password. When you start with the -p parameter, Adaptive Server generates, displays, and encrypts a random password and saves it in master..syslogins and in master..syssrvroles as that accounts new password. Sybase highly recommends that you change the password when the server restarts. For example, to reset the password for user rsmith who has sa_role:
dataserver -prsmith
To reset the password of the sso_role:

dataserver -psso_role
Changing user defaults

Any user can use sp_modifylogin to change his or her default database, default language, or full name. sp_modifylogin only affects user roles, not system roles. A System Administrator can change these settings for any user. The syntax is:
405
sp_modifylogin account, column, value
where: account is the name of the user whose account you are modifying. column specifies the option that you are changing. See sp_modifylogin in the Reference Manual: Procedures for a list of available options. value is the new value for the specified option.
After you execute sp_modifylogin to change the default database, the user is connected to the new default database the next time he or she logs in. However, sp_modifylogin does not automatically give the user access to the database. Unless the Database Owner has set up access with sp_adduser, sp_addalias, or with a guest user mechanism, the user is connected to master even after his or her default database has been changed. This example changes the default database for anna to pubs2:
sp_modifylogin anna, defdb, pubs2
This example changes the default language for claire to French:

sp_modifylogin claire, deflanguage, french
This example changes the full name for mtwain to Samuel Clemens.
sp_modifylogin mtwain, fullname, "Samuel Clemens"
Changing a users group membership

A System Administrator or the Database Owner can use sp_changegroup to change a users group affiliation. Each user can be a member of only one group other than public, of which all users are always members. Before you execute sp_changegroup: The group must exist. Use sp_addgroup to create a group. The user must have access to the current database (must be listed in sysusers).
The syntax for sp_changegroup is:

sp_changegroup grpname, username
For example, to change the user jim from his current group to the group manage, use:
sp_changegroup manage, jim
406
CHAPTER 14
To remove a user from a group without assigning the user to another group, you must change the group affiliation to public:
sp_changegroup "public", jim
The name public must be in quotes because it is a reserved word. This command reduces Jims group affiliation to public only. When a user changes from one group to another, the user loses all permissions that he or she had as a result of belonging to the old group, but gains the permissions that have been granted to the new group. The assignment of users into groups can be changed at any time.
Changing the user process information

The set command includes options that allow you to assign each client an individual name, host name, and application name. This is useful for differentiating among clients in a system where many clients connect to Adaptive Server using the same name, host name, or application name. The partial syntax for the set command is:
set [clientname client_name | clienthostname host_name | clientapplname application_name]
Where client_name is the name you are assigning the client, host_name is the name of the host from which the client is connecting, and application_name is the application that is connecting to Adaptive Server. These parameters are stored in the clientname, clienthostname, clientapplname columns of the sysprocesses table. For example, if a user logs in to Adaptive Server as client1, you can assign them an individual client name, host name, and application name using commands similar to:
set clientname 'alison' set clienthostname 'money1' set clientapplname 'webserver2'
This user now appears in the sysprocesses table as user alison logging in from host money1 and using the webserver2 application. However, although the new names appear in sysprocesses, they are not used for permission checks, and sp_who still shows the client connection as belonging to the original login (in the case above, client1). set clientname does not perform the same function as set proxy, which allows you to assume the permissions, login name, and suid of another user.
407
Using aliases in databases
You can set a client name, host name, or application name for only your current client session (although you can view the connection information for any client connection). Also, this information is lost when a user logs out. These parameters must be reassigned each time a user logs in. For example, the user alison cannot set the client name, host name, or application name for any other client connection. Use the clients spid to view their connection information. For example, if the user alison described above connects with a spid of 13, issue the following command to view all the connection information for this user:
select * from sysprocesses where spid = 13
To view the connection information for the current client connection (for example, if the user alison wanted to view her own connection information), enter:
select * from sysprocesses where spid = @@spid

The alias mechanism allows you to treat two or more users as the same user inside a database so that they all have the same privileges. This mechanism is often used so that more than one user can assume the role of Database Owner. A Database Owner can use the setuser command to impersonate another user in the database. You can also use the alias mechanism to set up a collective user identity. For example, suppose that several vice presidents want to use a database with identical privileges and ownerships. If you add the login vp to Adaptive Server and the database and have each vice president log in as vp, there is no way to tell the individual users apart. Instead, alias all the vice presidents, each of whom has his or her own Adaptive Server account, to the database user name vp.
Note Although more than one individual can use the alias in a database, you
can still maintain individual accountability by auditing the database operations performed by each user. For more information about auditing, see Chapter 18, Auditing.
408
CHAPTER 14
Table 14-8 lists the system procedures used to manage aliases:

Table 14-8: System procedures for managing aliases Task Add an alias for a user Drop an alias Require role Database Owner or System Administrator Database Owner or System Administrator System procedure
sp_addalias sp_dropalias
Database User database User database
Note As of version 12.0, you cannot drop the alias of a login if that login
created objects in the database. In most cases, you should use aliases only for users who do not own tables, procedures, views or triggers.
Adding aliases
To add an alias for a user, use sp_addalias. The syntax is:
sp_addalias loginame, name_in_db
where: loginame is the name of the user who wants an alias in the current database. This user must have an account in Adaptive Server but cannot be a user in the current database. name_in_db is the name of the database user to whom the user specified by loginame is to be linked. The name_in_db must exist in both master..syslogins and in sysusers in the current database.
Executing sp_addalias maps the user name specified by loginame to the user name specified by name_in_db. It does this by adding a row to the system table sysalternates. When a user tries to use a database, Adaptive Server checks for the users server user ID number (suid) in sysusers. If it is not found, Adaptive Server then checks sysalternates. If the users suid is found there, and it is mapped to a database users suid, the first user is treated as the second user while the first user is using the database. For example, suppose that Mary owns a database. She wants to allow both Jane and Sarah to use the database as if they were its owner. Jane and Sarah have logins on Adaptive Server but are not authorized to use Marys database. Mary executes the following commands:
sp_addalias jane, dbo
409
exec sp_addalias sarah, dbo Warning! Users who are aliased to the Database Owner have all the permissions and can perform all the actions that can be performed by the real Database Owner, with respect to the database in question. A Database Owner should carefully consider the implications of vesting another user with full access to a database.
Dropping aliases
Use sp_dropalias to drop the mapping of an alternate suid to a user ID. Doing this deletes the relevant row from sysalternates. The syntax is the following, where loginame is the name of the user specified by loginame when the name was mapped with sp_addalias:
sp_dropalias loginame
After a users alias is dropped, the user no longer has access to the database. You cannot drop an alias for a user who owns objects in the database that were created with version 12.0 or later. You must drop the objects (re-creating them under a different login, if needed) before you can drop the alias.
Getting information about aliases

To display information about aliases, use sp_helpuser. For example, to find the aliases for dbo, execute:
sp_helpuser dbo Users_name ---------dbo ID_in_db -------1 Group_name ---------public Login_name ---------sa
(1 row affected) Users aliased to user. Login_name ---------------------andy christa howard linda
410
CHAPTER 14
(4 rows affected)
Getting information about users

Table 14-9 lists procedures you can use to obtain information about users, groups, and current Adaptive Server usage.
Table 14-9: Reporting information about Adaptive Server users and groups Task Report current Adaptive Server users and processes Display information about login accounts Report users and aliases in a database Report groups within a database Procedure
sp_who sp_displaylogin sp_helpuser sp_helpgroup
Getting reports on users and processes

Use sp_who to report information about current users and processes on Adaptive Server:
sp_who [loginame | "spid"]
where: loginame is the users Adaptive Server login name. If you give a login name, sp_who reports information about processes being run by that user. spid is the number of a specific process.
For each process being run, sp_who reports the server process ID, its status, the login name of the process user, the name of the host computer, the server process ID of a process that is blocking this one (if any), the name of the database, and the command being run. If you do not provide a login name or spid, sp_who reports on processes being run by all users. The following example shows the results of executing sp_who without a parameter:
spid status loginame hostname blk dbname cmd ------ -------- -------- -------- --- ------ ----------------
411
1 2 3 4 5
running sleeping sleeping sleeping sleeping
sa NULL NULL NULL NULL
sunbird
0 0 0 0 0
pubs2 master master master master
SELECT NETWORK HANDLER MIRROR HANDLER AUDIT PROCESS CHECKPOINT SLEEP
(5 rows affected, return status = 0)

sp_who reports NULL for the loginame for all system processes.
Getting information about login accounts

Use sp_displaylogin to display information about a specified login account, including any roles granted to that account, where loginame is the user login account about which you want information:
sp_displaylogin [loginame]
If you are not a System Security Officer or System Administrator, you can display information only about your own account. If you are a System Security Officer or System Administrator, you can use the loginame parameter to access information about any account.
sp_displaylogin displays your server user ID, login name, full name, any roles that have been granted to you, date of last password change, default database, default language, whether your account is locked, any auto login script, password expiration interval, whether password has expired, and the authentication mechanism specified for the login. sp_displaylogin displays all roles that have been granted to you, so even if you have made a role inactive with the set command, that role is displayed.
Getting information about database users

Use sp_helpuser to report information about authorized users of the current database, where name_in_db is the users name in the current database:
sp_helpuser [name_in_db]
If you give a users name, sp_helpuser reports information about that user. If you do not give a name, it reports information about all users. The following example shows the results of executing sp_helpuser without a parameter in the database pubs2:
412
CHAPTER 14
sp_helpuser Users_name ---------dbo marcy sandy judy linda anne jim
ID_in_db -------1 4 3 5 6 2 7
Group_name ---------public public public public public public senioreng
Login_name ---------sa marcy sandy judy linda anne jim
Finding user names and IDs

To find a users server user ID or login name, use suser_id and suser_name.
Table 14-10: System functions suser_id and suser_name To find Server user ID Server user name (login name) Use
suser_id suser_name
With the argument

(["server_user_name"]) ([server_user_ID])
The arguments for these system functions are optional. If you do not provide one, Adaptive Server displays information about the current user. This example shows how to find the server user ID for the user sandy:
select suser_id("sandy") -----3
413
This example shows how a System Administrator whose login name is mary issues the commands without arguments:
select suser_name(), suser_id() ------------------------------ -----mary 4
To find a users ID number or name inside a database, use user_id and user_name.
Table 14-11: System functions user_id and user_name To find User ID User name Use
user_id user_name
With the argument

([db_user_name]) ([db_user_ID])
The arguments for these functions are optional. If you do not provide one, Adaptive Server displays information about the current user. For example:
select user_name(10) select user_name( ) select user_id("joe")
Displaying information about roles

Table 14-12 lists the system procedures and functions to use to find information about roles, and the section in this chapter that provides details.
Table 14-12: Finding information about roles To display information about The role ID of a role name The role name of a role ID System roles Role hierarchies and roles that have been granted to a user or users Whether one role contains another role in a role hierarchy Whether two roles are mutually exclusive Roles that are active for the current session Use
role_id system function role_name system
See Finding role IDs and names on page 415 Finding role IDs and names on page 415 Viewing active roles on page 415 Displaying a role hierarchy on page 416 Viewing user roles in a hierarchy on page 416 Determining mutual exclusivity on page 416 Determining role activation on page 416
function
show_role system function sp_displayroles system
procedure
role_contain system
function
mut_excl_roles system
function
sp_activeroles system
procedure
414
CHAPTER 14
To display information about Whether you have activated the correct role to execute a procedure Logins, including roles that have been granted Permissions for a user, group, or role
Use
proc_role system function sp_displaylogin system
See Checking for roles in stored procedures on page 417 Getting information about login accounts on page 412 Reporting on permissions on page 560
procedure
sp_helprotect system
procedure
Finding role IDs and names

To find a role ID when you know the role name, use role_id:
role_id(role_name)
Any user can execute role_id. If the role is valid, role_id returns the server-wide ID of the role (srid). The syssrvroles system table contains an srid column with the role ID and a name column with the role name. If the role is not valid, role_id returns NULL. To find a role name when you know the role ID, use role_name:
role_name(role_id)
Any user can execute role_name.
Viewing active roles

Use show_role to display the currently active system roles for the specified login:
show_role()
If you have not activated any system role, show_role returns NULL. If you are a Database Owner, and you execute show_role after using setuser to impersonate another user, show_role returns your own active system roles, not those for whom you are impersonating. Any user can execute show_role.
Note The show_role function does not give information about user-defined
roles.
415
Displaying a role hierarchy

You can see all roles granted to your login name or see the entire hierarchy tree of roles displayed in table format using sp_displayroles:
sp_displayroles {login_name | rolename [, expand_up | expand_down]}
Any user can execute sp_displayroles to see his or her own roles. Only the System Security Officer or the System Administrator can view information about roles granted to other users.
Viewing user roles in a hierarchy

Use role_contain to determine whether any role you specify contains any other role you specify:
role_contain (["role1", "role2"])
If role1 contains role2, role_contain returns 1. Any user can execute role_contain.
Determining mutual exclusivity

Use the mut_excl_roles function to determine whether any two roles assigned to you are mutually exclusive, and the level at which they are mutually exclusive:
mut_excl(role1, role2, {membership | activation})
Any user can execute mut_excl_roles. If the specified roles, or any role contained by either specified role, are mutually exclusive, mut_excl_roles returns 1; if the roles are not mutually exclusive, mut_excl_roles returns 0.
Determining role activation

To find all active roles for the current login session of Adaptive Server, use sp_activeroles:
sp_activeroles [expand_down]
expand_down displays the hierarchy of all roles contained by any roles granted
to you. Any user can execute sp_activeroles.
416
CHAPTER 14
Checking for roles in stored procedures

Use proc_role within a stored procedure to guarantee that only users with a specific role can execute the procedure. Only proc_role provides a fail-safe way to prevent inappropriate access to a particular stored procedure. You can use grant execute to grant execute permission on a stored procedure to all users who have been granted a specified role. Similarly, revoke execute removes this permission. However, grant execute permission does not prevent users who do not have the specified role from being granted execute permission on a stored procedure. If you want to ensure, for example, that all users who are not System Administrators can never be granted permission to execute a stored procedure, use proc_role within the stored procedure itself. It checks to see whether the invoking user has the correct role to execute the procedure.
proc_role takes a string for the required role and returns 1 if the invoker possesses it. Otherwise, it returns 0.
For example, here is a procedure that uses proc_role to see if the user has the sa_role role:
create proc test_proc as if (proc_role("sa_role") = 0) begin print "You dont have the right role" return -1 end else print "You have System Administrator role" return 0
Establishing a password and login policy

Adaptive Server includes several controls for setting policies for logins and passwords for internal authentication. In Adaptive Server the System Security Officer can: Specify the maximum allowable number of times an invalid password can be entered for a login or role before that login or role is automatically locked
417
Lock and unlock roles manually Ensure that all user passwords have at least one digit Specify the minimum password length required server-wide or for a specific login or role Display all security-related information for logins and roles Associate a password expiration value with a specified login or role
Negative values may be used for user IDs (uid). The server user ID (suid) associated with a group or a role in sysusers is not equal to the negation of their user ID (uid). Every suid associated with a group or a role in sysusers is set to -2 (INVALID_SUID).
Setting and changing the maximum login attempts

Setting the maximum number of login attempts allowed provides protection against brute-force or dictionary-based attempts to guess passwords. A System Security Officer can specify a maximum number of consecutive login attempts allowed, after which the login or role is automatically locked. The number of allowable failed login attempts can be set for the entire server or for individual logins and roles. Individual settings override the server-wide setting. The number of failed logins is stored in the logincount column in master..syslogins. A successful login resets the number of failed logins to 0.
Setting the server-wide maximum failed logins
To set the server-wide maximum failed logins for logins and roles, use the maximum failed logins configuration parameter. This example sets the system-wide maximum failed logins to 5:
sp_configure "maximum failed logins", 5
For details on the syntax and rules for using maximum failed logins, see sp_configure in the Reference Manual: System Procedures.
Setting the maximum failed logins for specific logins
To set the maximum failed logins for a specific login at creation, use sp_addlogin.
418
CHAPTER 14
This example creates the new login joe with the password Djdiek3 and sets the maximum number of failed login attempts for the login joe to 2:
sp_addlogin joe, "Djdiek3", pubs2, null, null, null, null, 2
For details on the syntax and rules for using maximum failed logins, see sp_addlogin Reference Manual: System Procedures.
Setting the maximum failed logins for specific roles
To set the maximum failed logins for a specific role at creation, use create role. This example creates the intern_role role with the password temp244, and sets the maximum failed logins for intern_role to 20:
create role intern_role with passwd "temp244", maximum failed logins 20
For details on the syntax and rules for using maximum failed logins, see create role.
Changing the maximum failed logins for specific logins
Use sp_modifylogin to set or change the maximum failed logins for an existing login.
Example 1 Changes the maximum failed logins for the login joe to 40: sp_modifylogin "joe", "max failed_logins", "40" Note The value parameter is a character datatype; therefore, quotes are
required for numeric values.

Example 2 Changes the overrides for maximum failed logins for all logins
to 3:
sp_modifylogin "all overrides", "max failed_logins", "3" Example 3 Removes the overrides for maximum failed logins option for all
logins:
sp_modifylogin "all overrides", "max failed_logins", "-1"
sp_modifylogin only effects user roles, not system roles. For details on the syntax and rules, see sp_modifylogin.
419
Changing the maximum failed logins for specific roles
Use alter role to set or change the maximum failed logins for an existing role.
Example 1 Changes the maximum failed logins allowed for physician_role
to 5:
alter role "all overrides" set maximum failed logins -1 Example 2 Removes the overrides for the maximum failed logins for all
roles:
alter role physician_role set maximum failed logins 5
For details on the syntax and rules for using maximum failed logins, see alter role.
Logging in after lost password

Use the dataserver -plogin_name parameter to specify the name of the System Security Officer or System Administrator at the server startup. This allows you to set a new password for these account if there is no way to recover a lost password. When you start with the -p parameter, Adaptive Server generates, displays, and encrypts a random password and saves it in master..syslogins as that accounts new password. You can use dataserver -p to reset the password for sa_role and sso_role. Use dataserver -p when you have lost the password for either of these roles, but they require a password to become active. For example, if the server is started with:
dataserver -psa_role
Adaptive Server displays this message:

New password for role 'sa_role' : qjcdyrbfkxgyc0
If sa_role does not have a password, and it is started with -psa_role, Adaptive Server prints an error message in the errorlog. Sybase highly recommends that you change the password for the login or role when the server restarts.
420
CHAPTER 14
Locking and unlocking logins and roles

A login or role can be locked when:
Its password expires, or The maximum number of failed login attempts occur, or The System Security Officer locks the login or role manually.
Locking and unlocking logins
The System Security Officer can use sp_locklogin to lock or unlock a login manually. For example:
sp_locklogin "joe" , "lock" sp_locklogin "joe" , "unlock"
Information about the lock status of a login is stored in the status column of syslogins. For details on the syntax and rules for using sp_locklogin, see sp_locklogin.
Locking and unlocking roles
The System Security Officer can use alter role to lock or unlock a role manually. For example:
alter role physician_role lock alter role physician_role unlock
Information about the lock status of a role is stored in the status column of syssrvroles. For details on the syntax and rules for using lock and unlock, see alter role Reference Manual: Commands.
Unlocking logins and roles at server start-up
Automatic login lockouts can cause a site to end up in a situation where all accounts capable of unlocking logins (System Administrators and System Security Officers) are locked. In these situations, use the -u flag with the dataserver utility to unlock a specific login or role when you start Adaptive Server. For details on the syntax and rules for using the -u flag, see the Utility Guide.
421
Displaying password information

This section discusses displaying password information for logins and roles.
Displaying password information for specific logins
Use sp_displaylogin to display the password settings for a login. This example displays information about the login joe:
sp_displaylogin joe Suid: 2 Loginame: joe Fullname: Joseph Resu Default Database: master Default Language: Configured Authorization: intern_role (default OFF) Locked: NO Date of Last Password Change: Nov 24 1997 3:35PM Password expiration interval : 5 Password expired : NO Minimum password length:4 Maximum failed logins : 10 Current failed logins : 3
For details on the syntax and rules, see sp_displaylogin in the Reference Manual: System Procedures.
Displaying password information for specific roles
Use sp_displayroles to display the password settings for a role. This example displays information about the physician_role role:
sp_displayroles physician_role, "display_info" Role name = physician_role Locked : NO Date of Last Password Change : Nov 24 1997 3:35PM Password expiration interval = 5 Password expired : NO Minimum password length = 4 Maximum failed logins = 10 Current failed logins = 3
For details on the syntax and rules, see sp_displayroles in the Reference Manual: System Procedures.
422
CHAPTER 14
Checking passwords for at least one digit

The System Security Officer can tell the server to check for at least one digit in a password using the server-wide configuration parameter, check password for digit. If set, this parameter does not affect existing passwords. By default, checking for digits is off. This example activates the check password functionality:
This deactivates the check password functionality:

For details on the syntax and rules for using check password, see sp_configure in the Reference Manual: System Procedures..
Setting and changing minimum password length

In earlier versions of Adaptive Server, the minimum password length was a nonconfigurable, hard-coded value of six characters. The configurable password allows you to customize passwords to fit your needs such as using four-digit personal identification numbers (PINs) or anonymous logins with NULL passwords.
Note Adaptive Server uses a default value of 6 for minimum password length.
Sybase recommends that you use a value of 6 or more for this parameter. The System Security Officer can specify: A globally enforced minimum password length A per-login or per-role minimum password length
The per-login or per-role value overrides the server-wide value. Setting minimum password length affects only new passwords created after setting the value. It does not affect existing passwords.
Setting the server-wide minimum password length
Use the minimum password length configuration parameter to specify a server-wide value for minimum password length for both logins and roles. This example sets the minimum password length for all logins and roles to 7 characters:
423
sp_configure "minimum password length", 7
For details on the syntax and rules for using minimum password length, see sp_configure in the Reference Manual: System Procedures..
Setting minimum password length for a specific login
To set the minimum password length for a specific login at creation, use sp_addlogin. This example creates the new login joe with the password Djdiek3, and sets the minimum password length for joe to 8:
sp_addlogin joe, "Djdiek3", @minpwdlen=8
For details on the syntax and rules for using minimum password length, see sp_addlogin in the Reference Manual: System Procedures..
Setting minimum password length for a specific role
To set the minimum password length for a specific role at creation, use create role. This example creates the new role intern_role with the password temp244 and sets minimum password length for intern_role to 0:
create role intern_role with passwd "temp244", min passwd length 0
The original password is seven characters, but the password can be changed to one of any length because minimum password length is set to 0. For details on the syntax and rules for using minimum password length, see create role in the Reference Manual: Commands.
Changing minimum password length for a specific login
Use sp_modifylogin to set or change minimum password length for an existing login. sp_modifylogin effects only user roles, not system roles.
Example 1 Changes minimum password length for the login joe to 8
characters.
sp_modifylogin "joe", @option="min passwd length", @value="8" Note The value parameter is a character datatype; therefore, quotes are
424
CHAPTER 14
Example 2 Changes the value of the overrides for minimum password length for all logins to eight characters. sp_modifylogin "all overrides", @option="min passwd length", @value="8" Example 3 Removes the overrides for the minimum password length for
all logins.
sp_modifylogin "all overrides", "min passwd length", @value="-2"
For details on the syntax and rules for using minimum password length, see sp_modifylogin.
Changing minimum password length for a specific role
Use alter role to set or change minimum password length for an existing role.
Example 1 Sets the minimum length for physician_role, an existing role, to 5 characters: alter role physician_role set min passwd length 5 Example 2 Overrides the minimum password length for all roles: alter role "all overrides" set min passwd length -1
For details on the syntax and rules for using minimum password length, see alter
role in the Reference Manual: Commands.
Setting the expiration interval for a password

System Administrators and System Security Officers can:
Use
sp_addlogin sp_modifylogin create role alter role
To Specify the expiration interval for a login password at creation Change the expiration interval for a login password. sp_modifylogin affects only user roles, not system roles. Specify the expiration interval for a role password at creation Change the expiration interval for a role password
The following rules apply to password expiration for logins and roles:
425
A password expiration interval assigned to individual login accounts or roles overrides the global password expiration value. This allows you to specify shorter expiration intervals for sensitive accounts or roles, such as System Security Officer passwords, and more relaxed intervals for less sensitive accounts such as an anonymous login. A login or role for which the password has expired is not directly activated.
For details on the syntax and rules for the commands and system procedures, see the Reference Manual.
Password expiration turned off for pre-12.x passwords

Password expiration did not affect roles in versions prior to Adaptive Server 12.x. Therefore, in Adaptive Server 12.x and later, password expiration is deactivated for any existing user-defined role passwords. During the upgrade, all user-defined role passwords are stamped as having a password interval of 0.
Message for impending password expiration

When a password for a login or role is about to expire, a warning message asks the user to contact the System Security Officer.
Circumventing password protection

Circumventing the password-protection mechanism may be necessary in the case of automated login systems. You can create a role that could access other roles without passwords. If a System Security Officer wants to bypass the password mechanism for certain users, the System Security Officer can grant the password-protected role to another role and grant this new role to one or more users. Activation of this role automatically activates the password-protected role without having to provide a password. For example: Jane is the System Security Officer for the fictitious company ABC Inc., which uses automated login systems. Jane creates the following roles:
financial_assistant
create role financial_assistant with passwd "L54K3j"
accounts_officer
426
CHAPTER 14
create role accounts_officer with passwd "9sF6ae"
chief_financial_officer
create role chief_financial_officer
Jane grants the roles of financial_assistant and accounts_officer to the chief_financial_officer role:
grant role financial_assistant, accounts_officer to chief_financial_officer
Jane then grants the chief_financial_officer role to Bob:

grant role chief_financial_officer to bob
Bob logs in to Adaptive Server and activates the chief_financial_officer role:

set role chief_financial_officer on
The roles of financial_assistant and accounts_officer are automatically activated without Bob providing a password. Bob can now access everything under the financial_assistant and accounts_officer roles without having to enter the passwords for those roles.
Creating a password expiration interval for a new login

Use sp_addlogin to set the password expiration interval for a new login. This example creates the new login joe with the password Djdiek3, and sets the password expiration interval for joe to 2 days:
sp_addlogin joe, "Djdiek3", null, null, null, 2
For details on the syntax and rules for using the new parameter, see sp_addlogin in the Reference Manual: System Procedures.
Creating a password expiration interval for a new role

Use create role to set the password expiration interval for a new role. This example creates the new role intern_role with the password temp244, and sets the password expiration interval for intern_role to 7 days:
create role intern_role with passwd "temp244", passwd expiration 7
For details on the syntax and rules for using passwd expiration, see create role in the Reference Manual: Commands.
427
Monitoring license use
Creation date added for passwords

Passwords are stamped with a creation date equal to the upgrade date of a given server. The creation date for login passwords is stored in the pwdate column of syslogins. The creation date for role passwords is stored in the pwdate column of syssrvroles.
Changing or removing password expiration interval for login or role

Use sp_modifylogin to change the password expiration interval for an existing login, add a password expiration interval to a login that did not have one, or remove a password expiration interval. sp_modifylogin only effects user roles, not system roles.
Example 1
Changes the password expiration interval for the login joe to 5
days:
sp_modifylogin "joe", @option="passwd expiration", @value="5" Note The value parameter is a character datatype; therefore, quotes are

Example 2 Changes the value of the overrides for the password expiration for all logins to 3 days: sp_modifylogin "all overrides", @option="passwd expiration", @value="3" Example 3 Removes the value of the overrides for the password expiration for all logins: sp_modifylogin "all overrides", @option="passwd expiration", @value="-1"
For details on the syntax and rules for using passwd expiration, see sp_modifylogin in the Reference Manual: System Procedures.

The License Use Monitor allows a System Administrator to monitor the number of user licenses used in Adaptive Server, and to securely manage the license agreement data. That is, you can ensure that the number of licenses used on your Adaptive Server does not exceed the number specified in your license agreement.
428
CHAPTER 14
The License Use Monitor tracks the number of licenses issued; it does not enforce the license agreement. If the License Use Monitor reports that you are using more user licenses than specified in your license agreement, see your Sybase sales representative. You must have System Administrator privileges to configure the License Use Monitor. By default, the License Use Monitor is turned off when Adaptive Server is first installed or upgraded. The System Administrator must configure the License Use Monitor to monitor license usage. See Configuring the License Use Manager to monitor user licenses on page 429 for configuration information.
How licenses are counted

A license is the combination of a host computer name and a user name. If a user logs in to Adaptive Server multiple times from the same host machine, it counts as one license. However, if the user logs in once from host A, and once from host B, it counts as two licenses. If multiple users log in to Adaptive Server from the same host, but with different user names, each distinct combination of user name and host name is counted.
Configuring the License Use Manager to monitor user licenses

Use sp_configure to specify the number of licenses in your license agreement, where number is the number of licenses:
sp_configure "license information" , number
This example sets the maximum number of user licenses to 300, and reports an overuse for license number 301:
sp_configure "license information", 300
If you increase the number of user licenses, you must also change the license
information configuration parameter.
The configuration parameter housekeeper free write percent must be set to 1 or more in for the License Use Manager to track license use.
429
Monitoring license use with the housekeeper task

After you configure the License Use Monitor, the housekeeper task determines how many user licenses are in use, based on the user ID and the host name of each user logged in to Adaptive Server. When the housekeeper task checks licenses, the License Use Monitor updates a variable that tracks the maximum number of user licenses in use: If the number of licenses in use is the same or has decreased since the previous housekeeper run, the License Use Monitor does nothing. If the number of licenses in use has increased since the previous housekeeper run, the License Use Monitor sets this number as the maximum number of licenses in use. If the number of licenses in use is greater than the number allowed by the license agreement, the License Use Monitor issues message to the error log:
Exceeded license usage limit. Contact Sybase Sales for additional licenses.
The housekeeper chores task runs during Adaptive Servers idle cycles. The housekeeper monitors the number of user licenses only if the license information configuration parameter is set to 1 or greater. For more information about the housekeeper chores task, see Chapter 4, Using ENgines and CPUs, in the Performance and Tuning Guide:Basics.
Logging the number of user licenses

The syblicenseslog system table is created in the master database when you install or upgrade Adaptive Server. The License Use Monitor updates the columns in syblicenseslog at the end of each 24-hour period, as shown in Table 14-13.
430
CHAPTER 14
Table 14-13: Columns in syblicenseslog table Column

status
Description -1 housekeeper cannot monitor licenses. 0 number of licenses not exceeded. 1 number of licensees exceeded. Date and time the log information was inserted. Maximum number of licenses used during the previous 24 hours.
logtime maxlicenses
syblicenseslog looks similar to this:
status logdate maxlicenses ------ -------------------------- ----------0 Jul 17 1998 11:43AM 123 0 Jul 18 1998 11:47AM 147 1 Jul 19 1998 11:51AM 154 0 Jul 20 1998 11:55AM 142 0 Jul 21 1998 11:58AM 138 0 Jul 21 1998 3:14PM 133
In this example, the number of user licenses used exceeded the limit on July 19, 1998. If Adaptive Server is shut down, License Manager updates syblicenseslog with the current maximum number of licenses used. Adaptive Server starts a new 24-hour monitoring period when it is restarted. The second row for July 21, 1998 was caused by a shutdown and restart of the server.
Getting information about usage: chargeback accounting

When a user logs in to Adaptive Server, the server begins accumulating CPU and I/O usage for that user. Adaptive Server can report total usage for an individual or for all users. Information for each user is kept in the syslogins system table in the master database.
431
Reporting current usage statistics

The System Administrator can use sp_reportstats or sp_clearstats to get or clear current total usage data for individuals or for all users on Adaptive Server.
Displaying current accounting totals

sp_reportstats displays current accounting totals for Adaptive Server users. It reports total CPU and total I/O, as well as the percentage of those resources used. It does not record statistics for the sa login (processes with an suid of 1), checkpoint, network, and mirror handlers.
Initiating a new accounting interval

Adaptive Server accumulates CPU and I/O statistics until you clear the totals from syslogins by running sp_clearstats. sp_clearstats initiates a new accounting interval for Adaptive Server users and executes sp_reportstats to print out statistics for the previous period. Choose the length of your accounting interval by deciding how you want to use the statistics at your site. For example, to do monthly cross-department charging for the percentage of Adaptive Server CPU and I/O usage, the System Administrator would run sp_clearstats once a month. For detailed information about these stored procedures, see the Reference Manual.
Specifying the interval for adding accounting statistics

A System Administrator can use configuration parameters to decide how often accounting statistics are added to syslogins. To specify how many machine clock ticks accumulate before accounting statistics are added to syslogins, use the cpu accounting flush interval configuration parameter. The default value is 200. For example:
sp_configure "cpu accounting flush interval", 600
To find out how many microseconds a tick is on your system, run the following query in Adaptive Server:
select @@timeticks
432
CHAPTER 14
To specify how many read or write I/Os accumulate before the information is added (flushed) to syslogins, use the i/o accounting flush interval configuration parameter. The default value is 1000. For example:
sp_configure "i/o accounting flush interval", 2000
I/O and CPU statistics are flushed when a user accumulates more I/O or CPU usage than the specified value. The information is also flushed when the user exits an Adaptive Server session. The minimum value allowed for either configuration parameter is 1. The maximum value allowed is 2,147,483,647.
433
434
CH A PTE R
1 5
Managing Remote Servers
This chapter discusses the steps the System Administrator and System Security Officer of each Adaptive Server must execute to enable remote procedure calls (RPCs).
Topic Overview Managing remote servers Adding remote logins Password checking for remote users Getting information about remote logins Configuration parameters for remote logins Page 435 436 442 446 447 447
Overview
Users on a local Adaptive Server can execute stored procedures on a remote Adaptive Server. Executing an RPC sends the results of the remote process to the calling processusually displayed on the users screen. To enable RPCs, the System Administrator and System Security Officer of each Adaptive Server must execute the following steps: On the local server: System Security Officer use sp_addserver to list the local server and remote server in the system table master..sysservers. List the remote server in the interfaces file or directory service for the local server. Restart the local server so the global variable @@servername is set to the name of the local server. If this variable is not set properly, users cannot execute RPCs from the local server on any remote server.
On the remote server:
435
System Security Officer use sp_addserver to list the server originating the RPC in the system table master..sysservers. To allow the user who is originating the remote procedure access to the server, a System Security Officer uses sp_addlogin, and a System Administrator uses sp_addremotelogin. Add the remote login name as a user of the appropriate database and grant that login permission to execute the procedure. (If execute permission is granted to public, the user does not need to be granted specific permission.)
Figure 15-1 shows how to set up servers for remote access.

Figure 15-1: Setting up servers to allow remote procedure calls
The user joe on ROSE needs to access stored procedures on ZINNIA ROSE ZINNIA
sp_addserver ROSE, local sp_addserver ZINNIA interfaces files must have an entry for ZINNIA
sp_addserver ROSE sp_addlogin joe sp_addremotelogin ROSE, joe sp_adduser joe (in the appropriate database) grant execute on procedure_name to joe
For operating-system-specific information about handling remote servers, see the the installation documentation for your platform.

Table 15-1 lists the tasks related to managing remote servers and the system procedures you use to perform the tasks.
436
CHAPTER 15
Table 15-1: Tasks related to managing remote servers To Add a remote server Manage remote server names Change server connection options Display information about servers Drop a server Use
sp_addserver sp_addserver sp_serveroption sp_helpserver sp_dropserver
See Adding a remote server on page 437 Managing remote server names on page 438 Setting server connection options on page 439 Getting information about servers on page 441 Dropping remote servers on page 441
Adding a remote server

A System Security Officer uses sp_addserver to add entries to the sysservers table. On the server originating the call, you must add one entry for the local server, and one for each remote server that your server will call. When you create entries for a remote server, you can either: Refer to them by the name listed in the interfaces file, or Provide a local name for the remote server. For example, if the name in the interfaces file is MAIN_PRODUCTION, you may want to call it simply main.
The syntax is:

sp_addserver lname [{, local | null} [, pname]]
where: lname provides the local call name for the remote server. If this name is not the same as the remote servers name in the interfaces file, you must provide that name as the third parameter, pname. The remote server must be listed in the interfaces file on the local machine. If it is not listed, copy the interfaces file entry from the remote server and append it to your existing interfaces file. Keep the same port numbers.
437
local identifies the server being added as a local server. The local value is used only after start-up, or after a restart, to identify the local server name so that it can appear in messages printed out by Adaptive Server. null specifies that this server is a remote server.
Note For users to be able to run RPCs successfully from the local server, the local server must be added with the local option and restarted. The restarting is required to set the global variable @@servername.
pname is the remote server listed in the interfaces file for the server named lname. This optional argument permits you to establish local aliases for any other Adaptive Server, Open Server, or Backup Server that you may need to communicate with. If you do not specify pname, it defaults to lname.
Examples of adding remote servers

This example creates an entry for the local server named DOCS:
sp_addserver DOCS, local
This example creates an entry for a remote server named GATEWAY:

sp_addserver GATEWAY
To run a remote procedure such as sp_who on the GATEWAY server, execute either:
GATEWAY.sybsytemprocs.dbo.sp_who
or:
GATEWAY...sp_who
This example gives a remote server called MAIN_PRODUCTION the local alias main:
sp_addserver main, null, MAIN_PRODUCTION
The user can then enter:

main...sp_who
Managing remote server names

The master.dbo.sysservers table has two name columns:
438
CHAPTER 15
srvname is the unique server name that users must supply when executing remote procedure calls. srvnetname is the servers network name, which must match the name in the interfaces file.
To add or drop servers from your network, you can use sp_addserver to update the servers network name in srvnetname. For example, to remove the server MAIN from the network, and move your remote applications to TEMP, you can use the following statement to change the network name, while keeping the local alias:
sp_addserver MAIN, null, TEMP
sp_addserver displays a message telling you that it is changing the network name of an existing server entry.
Setting server connection options

sp_serveroption sets the server options timeouts, net password encryption, rpc security model A, and rpc security model B, which affect connections with
remote servers. Additionally, if you have set the remote procedure security model to rpc security model B, you can use sp_serveroption to set these additional options: security mechanism, mutual authentication, use message confidentiality, and use message integrity. The options you specify for sp_serveroption do not affect the communication between Adaptive Server and Backup Server. The following sections describe timeouts, net password encryption, rpc security model A, and rpc security model B. For information about the additional options you can specify when rpc security model B is on, see Establishing security for remote procedures on page 468.
Using the timeouts option

A System Administrator can use the timeouts option to disable and enable the normal timeout code used by the local server. By default, timeouts is set to true, and the site handler process that manages remote logins times out if there has been no remote user activity for one minute. By setting timeouts to false on both of the servers involved in remote procedure calls, the automatic timeout is disabled. This example changes timeouts to false:
439
sp_serveroption GATEWAY, "timeouts", false
After you set timeouts to false on both servers, when a user executes an RPC in either direction, the site handler on each machine runs until one of the servers is shut down. When the server is brought up again, the option remains false, and the site handler is reestablished the next time a user executes an RPC. If users execute RPCs frequently, it is probably efficient in terms of system resources to set this option to false, since there is some system overhead involved in setting up the physical connection.
Using the net password encryption option

A System Security Officer can use net password encryption to specify whether connections with a remote server are to be initiated with a client-side password encryption handshake or with the usual unencrypted password handshake sequence. The default is false. If net password encryption is set to true: 1 2 3 4 The initial login packet is sent without passwords. The client indicates to the remote server that encryption is desired. The remote server sends back an encryption key, which the client uses to encrypt its plain text passwords. The client then encrypts its own passwords, and the remote server uses the key to authenticate them when they arrive.
This example sets net password encription to true:

sp_serveroption GATEWAY, "net password encryption", true
This option does not affect Adaptive Servers interaction with Backup Server.
Using the rpc security model options

The rpc security model A and rpc security model B options determine what kind of security is available for RPCs. If you use model A, which is the default, Adaptive Server does not support security services such as message confidentiality via encryption between the two servers.
440
CHAPTER 15
For security model B, the local Adaptive Server gets a credential from the security mechanism and uses the credential to establish a secure physical connection with the remote Adaptive Server. With this model, you can choose one or more of these security services: mutual authentication, message confidentiality via encryption, and message integrity. To set security model A for the server GATEWAY, execute:
sp_serveroption GATEWAY, "rpc security model A", true
For information about how to set up servers for security model B, see Establishing security for remote procedures on page 468.
Getting information about servers

sp_helpserver reports on servers. Without an argument, it provides information about all the servers listed in sysservers. When you include a server name, it
provides information about that server only. The syntax is:

sp_helpserver [server]
sp_helpserver checks for both srvname and srvnetname in the master..sysremotelogins table.
For operating-system-specific information about setting up remote servers, see the installation documentation for your platform.
Dropping remote servers

A System Security Officer can use sp_dropserver to drop servers from sysservers. The syntax is:
sp_dropserver server [, droplogins]
where: server is the name of the server you want to drop.

droplogins allows you to drop a remote server and all of that servers remote login information in one step. If you do not use droplogins, you
cannot drop a server that has remote logins associated with it. The following statement drops the GATEWAY server and all of the remote logins associated with it:
sp_dropserver GATEWAY, droplogins
441
Adding remote logins
You do not have to use droplogins to drop the local server; that entry does not have remote login information associated with it.

The System Security Officer and System Administrator of any Adaptive Server share control over which remote users can access the server, and what identity the remote users assume. The System Administrator uses sp_addremotelogin to add remote logins and sp_dropremotelogin to drop remote logins. The System Security Officer uses sp_remoteoption to control whether password checking is required.
Mapping users server IDs

Logins from a remote server can be mapped to a local server in three ways: A particular remote login can be mapped to a particular local login name. For example, user joe on the remote server might be mapped to joesmith. All logins from one remote server can be mapped to one local name. For example, all users sending remote procedure calls from the MAIN server might be mapped to remusers. All logins from one remote server can use their remote names.
The first option can be combined with the other two options, and its specific mapping takes precedence over the other two more general mappings. The second and third options are mutually exclusive; you can use either of them, but not both.
Changing the mapping option
Use sp_dropremotelogin to remove the old mapping. Use sp_addremotelogin to add remote logins. The syntax is:
sp_addremotelogin remoteserver [, loginame [, remotename]]
If the local names are not listed in master..syslogins, add them as Adaptive Server logins with sp_addlogin before adding the remote logins. Only a System Administrator can execute sp_addremotelogin. For more information, see the Reference Manual.
442
CHAPTER 15
Mapping remote logins to particular local names

The following example maps the login named pogo from a remote system to the local login name bob. The user logs in to the remote system as pogo. When that user executes remote procedure calls from GATEWAY, the local system maps the remote login name to bob.
sp_addlogin bob sp_addremotelogin GATEWAY, bob, pogo
Mapping all remote logins to one local name

The following example creates an entry that maps all remote login names to the local name albert. All names are mapped to albert, except those with specific mappings, as described in the previous section. For example, if you mapped pogo to bob, and then the rest of the logins to albert, pogo still maps to bob.
sp_addlogin albert sp_addremotelogin GATEWAY, albert
If you use sp_addremotelogin to map all users from a remote server to the same local name, use sp_remoteoption to specify the trusted option for those users. For example, if all users from server GATEWAY that are mapped to albert are to be trusted, specify:
sp_remoteoption GATEWAY, albert, NULL, trusted, true
If you do not specify the logins as trusted, the logins are not allowed to execute RPCs on the local server unless they specify passwords for the local server when they log in to the remote server. Users, when they use Open Client Client-Library, can use the routine ct_remote_pwd to specify a password for server-to-server connections. isql and bcp do not permit users to specify a password for RPC connections. See Password checking for remote users on page 446 for more information about sp_remoteoption.
Warning! Do not map more than one remote login to a single local login, as it reduces individual accountability on the server. Audited actions can be traced only to the local server login, not to the individual logins on the remote server.
443
If you are using network based security
If users are logged in to the remote server using unified login, the logins must also be trusted on the local server, or they must specify passwords for the server when they log into the remote server. For more information, see Using unified login on page 463.
Warning! Using the trusted mode of sp_remoteoption reduces the security of your server, as passwords from such trusted users are not verified.
Keeping remote login names for local servers

To enable remote users to keep their remote login names while using a local server: 1 2 Use sp_addlogin to create a login for each login from the remote server. Use sp_addremotelogin for the server as a whole to create an entry in master..sysremotelogins with a null value for the remote login name and a value of -1 for the suid. For example:
sp_addremotelogin GATEWAY
Example of remote user login mapping

This statement displays the local and remote server information recorded in master..sysservers:
select srvid ----0 1 2 3 4 srvid, srvname from sysservers srvname ---------SALES CORPORATE MARKETING PUBLICATIONS ENGINEERING
The SALES server is local. The other servers are remote. This statement displays information about the remote servers and users stored in master..sysremotelogins:
select remoteserverid, remoteusername, suid from sysremotelogins
444
CHAPTER 15
remoteserverid -------------1 1 1 3 4
remoteusername -------------joe nancy NULL NULL NULL
suid -----1 2 3 4 -1
By matching the value of remoteserverid in this result and the value of srvid in the previous result, you can find the name of the server for which the remoteusername is valid. For example, in the first result, srvid 1 indicates the CORPORATE server; in the second result remoteserverid 1 indicates that same server. Therefore, the remote user login names joe and nancy are valid on the CORPORATE server. The following statement shows the entries in master..syslogins:
select suid, name from syslogins suid name ----------------1 sa 2 vp 3 admin 4 writer
The results of all three queries together show: The remote user name joe (suid 1) on the remote CORPORATE server (srvid and remoteserverid 1) is mapped to the sa login (suid 1). The remote user name nancy (suid 2) on the remote CORPORATE server (srvid and remoteserverid 1) is mapped to the vp login (suid 2). The other logins from the CORPORATE server (remoteusername NULL) are mapped to the admin login (suid 3). All logins from the PUBLICATIONS server (srvid and remoteserverid 3) are mapped to the writer login (suid 4). All logins from the ENGINEERING server (srvid and remoteserverid 4) are looked up in master..syslogins by their remote user names (suid -1). There is no remoteserverid entry for the MARKETING server in sysremotelogins. Therefore, users who log in to the MARKETING server cannot run remote procedure calls from that server.
445
Password checking for remote users
The remote user mapping procedures and the ability to set permissions for individual stored procedures give you control over which remote users can access local procedures. For example, you can allow the vp login from the CORPORATE server to execute certain local procedures and all other logins from CORPORATE to execute the procedures for which the admin login has permission.
Note In many cases, the passwords for users on the remote server must match
passwords on the local server.
Password checking for remote users

A System Security Officer can use sp_remoteoption to determine whether passwords are checked when remote users log in to the local server. By default, passwords are verified (untrusted mode). In trusted mode, the local server accepts remote logins from other servers and front-end applications without user-access verification for the particular login. When sp_remoteoption is used with arguments, it changes the mode for the named user. The syntax is:
sp_remoteoption [remoteserver, loginame, remotename, optname, {true | false}]
The following example sets trusted mode for the user bob:
sp_remoteoption GATEWAY, pogo, bob, trusted, true
Effects of using the untrusted mode

The effects of the untrusted mode depend on the users client program. isql and some user applications require that logins have the same password on the remote server and the local server. Open Client applications can be written to allow local logins to have different passwords on different servers.
446
CHAPTER 15
To change your password in untrusted mode, you must first change it on all the remote systems you access before changing it on your local server. This is because of the password checking. If you change your password on the local server first, when you issue the remote procedure call to execute sp_password on the remote server ,your passwords no longer match. The syntax for changing your password on the remote server is:
remote_server...sp_password caller_passwd, new_passwd
On the local server, the syntax is:

sp_password caller_passwd, new_passwd
See Changing passwords on page 404 for more information about changing your password.
Getting information about remote logins

sp_helpremotelogin prints information about the remote logins on a server. The following example shows the remote login pogo mapped locally to login name bob, with all other remote logins keeping their remote names:
sp_helpremotelogin server --------GATEWAY GATEWAY remote_user_name ---------------**mapped locally** pogo local_user_name ----------------**use local name** bob options -------untrusted untrusted
Configuration parameters for remote logins

Table 15-2 shows the configuration parameters that affect RPCs. All these configuration parameters are set using sp_configure and do not take effect until Adaptive Server is restarted.
447
Table 15-2: Configuration parameters that affect RPCs Configuration parameter

allow remote access number of remote logins number of remote sites number of remote connections remote server pre-read packets
Default 1 20 10 20 3
Allowing remote access

To allow remote access to or from a server, including Backup Server, set allow remote access to 1:
sp_configure "allow remote access", 1
To disallow remote access at any time, set allow remote access to 0:

sp_configure "allow remote access", 0
Only a System Security Officer can set the allow remote access parameter.
Note You cannot perform database or transaction log dumps while the allow remote access parameter is set to 0.
Controlling the number of active user connections

To set the number of active user connections from this site to remote servers, use number of remote logins. This command sets number of remote logins to 50:
sp_configure "number of remote logins", 50
Only a System Administrator can set the number of remote logins parameter.
448
CHAPTER 15
Controlling the number of remote sites

To control the number of remote sites that can access a server simultaneously, use number of remote sites. All accesses from an individual site are managed by one site handler. This parameter controls the number of site handlers, not the number of individual, simultaneous procedure calls. For example, if you set number of remote sites to 5, and each site initiates three remote procedure calls, sp_who shows 5 site handler processes for the 15 processes. Only a System Administrator can set the number of remote sites.
Controlling the number of active remote connections

To control the limit on active remote connections that are initiated to and from a server, use the number of remote connections parameter. This parameter controls connections initiated from the server and connections initiated from remote sites to the server. Only a System Administrator can set number of remote connections.
Controlling number of preread packets

To reduce the needed number of connections, all communication between two servers is handled through one site handler. This site handler can preread and keep track of data packets for each user before the user process that needs them is ready. To control how many packets a site handler prereads, use remote server pre-read packets. The default value, 3, is adequate in all cases; higher values can use too much memory. Only a System Administrator can set remote server pre-read packets. For more information, see remote server pre-read packets on page 204.
449
450
CH A PTE R
1 6
External Authentication
This chapter describes the Adaptive Server features that enable you to authenticate users with authentication data stored in repositories external to Adaptive Server..
Topic Overview Configuring Adaptive Server for Network-Based Security Configuring Adaptive Server for LDAP User Authenticaiton Configuring Adaptive Server for authentication using PAM Enhanced login controls Page 451 452 486 493 497
Overview
You can enhance the security for large, heterogeneous applications by authenticating logins with a central repository. Adaptive Server supports a variety of external authentication methods: Kerberos A security mechanism available with Network-Based Security. Kerberos provides a centralized and secure authentication mechanism in enterprise environments that employ the Kerberos infrastructure. Authentication occurs with a trusted, third-party server called a Key Distribution Center (KDC) that verifies both the client and the server. LDAP User Authentication Lightweight Directory Access Protocol (LDAP) provides a centralized authentication mechanism based on a users login name and password. PAM User Authentication Pluggable Authentication Module (PAM) provides a centralized authentication mechanism that uses interfaces provided by the operating system for administration and runtime application interfaces.
451
Configuring Adaptive Server for Network-Based Security

In a distributed client/server computing environment, intruders can view or tamper with confidential data. Adaptive Server works with third-party providers to provide security services that: Authenticate users, clients, and servers make sure they are who they say they are. Provide data confidentiality with encryption ensure that data cannot be read by an intruder. Provide data integrity prevent data tampering, and detect when it has occurred.
How applications use security services

The following illustration shows a client application using a security mechanism to ensure a secure connection with Adaptive Server.
Figure 16-1: Establishing secure connections between a client and Adaptive Server
Security mechanism
connection Client Application Adaptive Server
The secure connection between a client and a server can be used for: Login authentication Message protection
452
CHAPTER 16
Login authentication
If a client requests authentication services: 1 The client validates the login with the security mechanism. The security mechanism returns a credential, which contains security-relevant information. The client sends the credential to Adaptive Server. Adaptive Server authenticates the clients credential with the security mechanism. If the credential is valid, a secure connection is established between the client and Adaptive Server.
2 3
Message protection
If the client requests message protection services: 1 The client uses the security mechanism to prepare the data packet it sends to Adaptive Server. Depending upon which security services are requested, the security mechanism might encrypt the data or create a cryptographic signature associated with the data. 2 3 4 The client sends the data packet to Adaptive Server. When Adaptive Server receives the data packet, it uses the security mechanism to perform any required decryption and validation. Adaptive Server returns results to the client, using the security mechanism to perform the security functions that were requested; for example, Adaptive Server may return the results in encrypted form.
Security services and Adaptive Server

Depending upon the security mechanism you choose, Adaptive Server allows you to use one or more of these security services: Unified login authenticates users once without requiring them to supply a name and password every time they log in to an Adaptive Server. Message confidentiality encrypts data over the network. Mutual authentication verifies the identity of the client and the server. This must be requested by the client and cannot be required by Adaptive Server.
453
Message integrity verifies that data communications have not been modified. Replay detection verifies that data has not been intercepted by an intruder. Out-of-sequence check verifies the order of data communications. Message origin checks verifies the origin of the message. Remote procedure security establishes mutual authentication, message confidentiality, and message integrity for remote procedure communications.
Note The security mechanism you are using may not employ all of these
services. For information about the services available to you, see Getting information about available security services on page 478.
Administering network-based security

Table 16-1 provides an overall process for using the network-based security functions provided by Adaptive Server. You must install Adaptive Server before you can complete the steps in Table 16-1.
Table 16-1: Process for administering network-based security Step 1. Set up the configuration files: libtcl.cfg objectid.dat interfaces (or Directory Service) 2. Make sure the security administrator for the security mechanism has created logins for each user and for the Adaptive Server and Backup Server. 3. Configure security for your installation. 4. Restart Adaptive Server. Description Edit the libtcl.cfg file. Edit the objectid.dat file. Edit the interfaces file or Directory Service. The security administrator must add names and passwords for users and servers in the security mechanism. For DCE, the security administrator must create a keytab file for server entries. Use sp_configure. Activates the use security services parameter. See Setting up configuration files for security on page 455 The Open Client/Server Configuration Guide for your platform The documentation supplied with your security mechanism Identifying users and servers to the security mechanism on page 461 Configuring Adaptive Server for security on page 462 Restarting the server to activate security services on page 466
454
CHAPTER 16
Step 5. Add logins to Adaptive Server to support enterprise-wide login. 6. Determine the security model for remote procedures and set up the local and remote servers for RPC security. 7. Connect to the server and use security services.
Description Use sp_addlogin to add users. Optionally, specify a default secure login with sp_configure. Use sp_serveroption to choose the security model A or B.
See Adding logins to support unified login on page 467 Establishing security for remote procedures on page 468
Use isql_r or Open Client Client-Library to connect to Adaptive Server, specifying the security services you want to use.
Connecting to the server and using the security services on page 475 The Open Client/Server Configuration Guide for your platform Security Features topics page in the Open Client Client-Library/C Reference Manual
8. Check the security services and security mechanisms that are available.
Use the functions show_sec_services and is_sec_services_on to check which security services are available. For a list of security mechanisms and their security services supported by Adaptive Server, use select to query the syssecmechs system table.
Getting information about available security services on page 478
Setting up configuration files for security

Configuration files are created during installation at a default location in the Sybase directory structure. Table 16-2 provides an overview of the configuration files required for using network-based security.
Table 16-2: Names and locations for configuration files File name libtcl.cfg Description The driver configuration file contains information regarding directory, security, and network drivers and any required initialization information. The object identifiers file maps global object identifiers to local names for character set, collating sequence, and security mechanisms. Location UNIX platforms: $SYBASE/$SYBASE_OCS/config Windows platforms: %SYBASE%\%SYBASE_OCS%\ini UNIX platforms: $SYBASE/config Windows platforms: %SYBASE%\ini
objectid.dat
455
File name UNIX: interfaces Desktop platforms: sql.ini
Description The interfaces file contains connection and security information for each server listed in the file.
Note As of Adaptive Server version 12.5.1, you can use a Directory Service instead of the interfaces file.
Location UNIX platforms: $SYBASE Desktop platforms: SYBASE_home\ini
For a detailed description of the configuration files, see the Open Client/Server Configuration Guide for your platform.
Preparinglibtcl.cfg to use network-based security

libtcl.cfg and libtcl64.cfg (for 64bit applications) contains information about three types of drivers: Network (Net-Library) Directory Services Security
A driver is a Sybase library that provides an interface to an external service provider. Drivers are dynamically loaded so that you can change the driver used by an application without relinking the application.
Entries for network drivers
The syntax for a network driver entry is:

driver=protocol description
where: driver is the name of the network driver. protocol is the name of the network protocol.
456
CHAPTER 16
description is a description of the entry. This element is optional.

Note If you do not specify a network driver, an appropriate driver for your
application and platform is automatically used. For example, for UNIX platforms, a driver that can handle threads is automatically chosen when security services are being used.
Entries for Directory Services
Entries for Directory Services apply if you want to use a Directory Service instead of the interfaces file. For information about directory entries, see the configuration documentation for your platform, and the Open Client/Server Configuration Guide for your platform.
Entries for security drivers
The syntax for a security driver entry is:

provider=driver init-string
where: provider is the local name for the security mechanism. The mapping of the local name to a global object identifier is defined in objectid.dat. The default local names are: dce for the DCE security mechanism. csfkrb5 for the CyberSAFE or MIT Kerberos security mechanism. LIBSMSSP for Windows LAN Manager on Windows NT or Windows 95 (clients only).
If you use a local mechanism name other than the default, you must change the local name in the objectid.dat file (see The objectid.dat file on page 459 for an example). driver is the name of the security driver. The default location of all drivers for Unix platforms is $SYBASE/$SYBASE_OCS/lib. The default location for Windows platform is %SYBASE%\%SYBASE_OCS%\dll. init-string is an initialization string for the driver. This element is optional. The value for init-string varies by driver: DCE driver the following is the syntax for init-string, where cell_name is the name of your DCE cell:
457
secbase=/.../cell_name
Kerberos driver the following is the syntax for init-string, where realm is the default Kerberos realm name:
secbase=@realm
UNIX platform information
Windows NT LAN Manager init-string is not applicable.
This section contains information specific to UNIX platforms. For more information, see the Open Client/Server Configuration Guide for UNIX. No special tools for editing the libtcl.cfg file are available. Use your favorite editor to comment and uncomment the entries that are already in place after you install Adaptive Server. The libtcl.cfg file, after installation of Adaptive Server on a UNIX platform, already contains entries for the three sections of the file: [DRIVERS] [DIRECTORY] [SECURITY]
The sections do not have to be in a specific order. Make sure that the entries you do not want to use are commented (begin with ;) and the entries you want are uncommented (do not begin with ;).
Sample libtcl.cfg for Sun Solaris [DRIVERS] ;libtli.so=tcp unused ; This is the non-threaded tli driver. ;libtli_r.so=tcp unused ; This is the threaded tli driver. [DIRECTORY] ;dce=libsybddce.so ditbase=/.:/subsys/sybase/dataservers ;dce=libsybddce.so ditbase=/.:/users/cfrank [SECURITY] dce=libsybsdce.so secbase=/.../svrsole4_cell
This libtcl.cfg file is set up to use the DCE security service. This file does not use Directory Services because all [DIRECTORY] section entries are commented.
458
CHAPTER 16
Because all entries in the [DRIVERS] section for network drivers are also commented, appropriate drivers are chosen automatically by the system. A threaded driver is chosen automatically when security services are being used, and a nonthreaded driver is chosen automatically for applications that cannot work with threaded drivers. For example, Backup Server does not support security services and does not work with a threaded driver.
Desktop platform information
This section contains information specific to desktop platforms. For more information, see the Open Client/Server Configuration Guide for Desktop Platforms. Use the ocscfg utility to edit the libtcl.cfg file. See the Open Client/Server Configuration Guide for Desktop Platforms for instructions for using ocscfg. The ocscfg utility creates section headings automatically for the libtcl.cfg file.
Sample libtcl.cfg file for desktop platforms [NT_DIRECTORY] ntreg_dsa=LIBDREG
ditbase=software\sybase\serverdsa
[DRIVERS] NLWNSCK=TCP Winsock TCP/IP Net-Lib driver NLMSNMP=NAMEPIPE Named Pipe Net-Lib driver NLNWLINK=SPX NT NWLINK SPX/IPX Net-Lib driver NLDECNET=DECNET DecNET Net-Lib driver [SECURITY] NTLM=LIBSMSSP
The objectid.dat file

The objectid.dat file maps global object identifiers, such as the one for the DCE service (1.3.6.1.4.1.897.4.6.1) to local names, such as dce. The file contains sections such as [CHARSET] for character sets and [SECURITY] for security services. Of interest here is the security section. Following is a sample objectid.dat file:
[secmech] 1.3.6.1.4.1.897.4.6.1 1.3.6.1.4.1.897.4.6.3 1.3.6.1.4.1.897.4.6.6 = dce = NTLM = csfkrb5
To change this file only if you have changed the local name of a security service in the libtcl.cfg file. Use a text editor to edit the file.
459
For example, if you changed:

[SECURITY] dce=libsybsdce.so secbase=/.../svrsole4_cell
to:
[SECURITY] dce_group=libsybsdce.so secbase=/.../svrsole4_cell
in libtcl.cfg, change the objectid.dat file to reflect the change. Simply change the local name in the line for DCE in objectid.dat:
1.3.6.1.4.1.897.4.6.1 = dce_group
Note You can specify only one local name per security mechanism.
Specifying security information for the server

You can choose to use an interfaces file or a Directory Service to provide information about the servers in your installation. The interfaces file contains network and security information for servers. To use security services, the interfaces file must include a secmech line, which gives the global identifier or identifiers of the security services you plan to use. Instead of using the interfaces file, Adaptive Server supports Directory Services to keep track of information about servers. A Directory Service manages the creation, modification, and retrieval of information about network servers. The advantage of using a Directory Service is that you do not need to update multiple interfaces files when a new server is added to your network or when a server moves to a new address. To use security services with a Directory Service, the secmech security attribute must be defined. It must point to one or more global identifiers of the security services you plan to use.
UNIX tools for specifying the security mechanism
To specify the security mechanism or mechanisms: If you are using the interfaces file, use the dscp utility.
460
CHAPTER 16
If you are using a Directory Service, use the dscp_r utility.

Note The dsedit tool, which helps you create entries for either the interfaces file or a Directory Service, is available on UNIX platforms. However, it does not support the creation of secmech entries for security mechanisms.
For more information about dscp, see the Open Client/Server Configuration Guide for UNIX.
Desktop tools for specifying server attributes
To provide information about the servers for your installation in the sql.ini file or a Directory Service, use the dsedit utility. This utility provides a graphical user interface for specifying server attributes such as the server version, name, and security mechanism. For the security mechanism attribute, you can specify one or more object identifiers for the security mechanisms you plan to use. For information about using dsedit, see the Open Client/Server Configuration Guide for Desktop Platforms.
Identifying users and servers to the security mechanism

The security administrator for the security mechanism must define principals, which include both users and servers, to the security mechanism. Table 16-3 lists tools you can use to add users and servers.
Table 16-3: Defining users and servers to the security mechanism Security mechanism DCE Command or tool Use the DCE dcecp tools user create command to create a new principal (user or server). In addition, use the keytab create command to create a DCE keytab file, which contains a principals password in encrypted form. When you are defining a server to DCE, use command options that specify that the new principal can act as a server. See your Kerberos vendor-specific tools for information about defining users and servers. See Using Kerberos on page 480 for more information about Kerberos and Adaptive Server. Run the User Manager tool to define users to the Windows NT LAN Manager. Be sure to define the Adaptive Server name as a user to Windows NT LAN Manager and bring up Adaptive Server as that user name.
Kerberos
Windows NT LAN Manager
461
Note In a production environment, you must control the access to files that
contain the keys of the servers and users. If users can access the keys, they can create a server that impersonates your server. Refer to the documentation available from the third-party provider of the security mechanism for detailed information about how to perform required administrative tasks.
Configuring Adaptive Server for security

Adaptive Server includes several configuration parameters for administering network-based security. To set these parameters, you must be a System Security Officer. All parameters for network-based security are part of the Security-Related configuration parameter group. Configuration parameters are used to: Enable network-based security Require unified login Require message confidentiality with data encryption Require one or more message integrity security services
Enabling network-based security

To enable or disable network-based security, use sp_configure to set the use security services configuration parameter. Set this parameter to 1 to enable network-based security. If this parameter is 0 (the default), network-based security services are not available. The syntax is:
sp_configure "use security services", [0|1]
For example, to enable security services, execute:

sp_configure "use security services", 1 Note This configuration parameter is static; you must restart Adaptive Server
for it to take effect. See Restarting the server to activate security services on page 466.
462
CHAPTER 16
Using unified login

Configuration parameters are available to: Require unified login Establish a default secure login
All the parameters for unified login take effect immediately. You must be a System Security Officer to set the parameters.
Requiring unified login
To require all users, other than the user with System Security Officer (sso) role, to be authenticated by a security mechanism, set the unified login required configuration parameter to 1. Only the user with the sso_role can log in to the server with a user name and password when this configuration parameter is set:
sp_configure "unified login required", [0|1]
For example, to require all logins to be authenticated by a security mechanism, execute:

sp_configure "unified login required", 1 Establishing a secure default login
When a user with a valid credential from a security mechanism logs in to Adaptive Server, the server checks whether the user name exists in master..syslogins. If it does, that user name is used by Adaptive Server. For example, if a user logs in to the DCE security mechanism as ralph, and ralph is a name in master..syslogins, Adaptive Server uses all roles and authorizations defined for ralph in the server. However, if a user with a valid credential logs in to Adaptive Server, but is unknown to the server, the login is accepted only if a secure default login is defined with sp_configure. Adaptive Server uses the default login for any user who is not defined in master..syslogins, but who is preauthenticated by a security mechanism. The syntax is:
sp_configure "secure default login", 0, login_name
The default value for secure default login is guest. This login must be a valid login in master..syslogins. For example, to set the login gen_auth to be the default login: 1 Use sp_addlogin to add the login as a valid user in Adaptive Server:
sp_addlogin gen_auth, pwgenau
463
This procedure sets the initial password to pwgenau. 2 Use sp_configure to designate the login as the security default.
sp_configure "secure default login", 0, gen_auth
Adaptive Server uses this login for a user who is preauthenticated by a security mechanism but is unknown to Adaptive Server.
Note More than one user can assume the suid associated with the secure
default login. Therefore, you might want to activate auditing for all activities of the default login. You may also want to consider using sp_addlogin to add all users to the server. For more information about adding logins, see Adding logins to support unified login on page 467 and Adding logins to Adaptive Server on page 377.
Mapping security mechanism login names to server names
Some security mechanisms may allow login names that are not valid in Adaptive Server. For example, login names that are longer than 30 characters, or login names containing special characters such as !, %, *, and & are invalid names in Adaptive Server. All login names in Adaptive Server must be valid identifiers. For information about what identifiers are valid, see Chapter 3, Expressions, Identifiers, and Wildcard Characters, in the Reference Manual. Table 16-4 shows how Adaptive Server converts invalid characters in login names:
Table 16-4: Conversion of invalid characters in login names Invalid characters Ampersand & Apostrophe Backslash \ Colon : Comma , Equals sign = Left quote Percent % Right angle bracket > Right quote Tilde ~ Converts to Underscore _
464
CHAPTER 16
Invalid characters Caret ^ Curly braces { } Exclamation point ! Left angle bracket < Parenthesis ( ) Period . Question mark ? Asterisk * Minus sign Pipe | Plus sign + Quotation marks " Semicolon ; Slash / Square brackets [ ]
Converts to Dollar sign $
Pound sign #
Requiring message confidentiality with encryption

To require all messages into and out of Adaptive Server to be encrypted, set the msg confidentiality reqd configuration parameter to 1. If this parameter is 0 (the default), message confidentiality is not required but may be established by the client. The syntax for setting this parameter is:
sp_configure configuration_parameter, [0 | 1]
For example, to require that all messages be encrypted, execute:

sp_configure "msg confidentiality reqd", 1
Requiring data integrity

Adaptive Server allows you to use the msg integrity reqd configuration parameters to require that one or more types of data integrity be checked for all messages. msg integrity reqd sets this parameter to 1 to require that all messages be checked for general tampering. If this parameter is 0 (the default), message integrity is not required but may be established by the client if the security mechanism supports it.
465
Memory requirements for network-based security

Allocate approximately 2K additional memory per secure connection. The value of the max total_memory configuration parameter specifies the amount of memory that Adaptive Server requires at start-up. For example, if your server uses 2K logical pages, and if you expect the maximum number of secure connections occurring at the same time to be 150, increase the max total_memory parameter by 150, which increases memory allocation by 150 2K blocks. The syntax is:
sp_configure max total_memory, value
For example, if Adaptive Server requires 75,000 2K blocks of memory, including the increased memory for network-based security, execute:
sp_configure "max total_memory", 75000
For information about estimating and specifying memory requirements, see the Chapter 3, Configuring Memory.
Restarting the server to activate security services

Once you have configured security services, you must restart Adaptive Server. Windows NT see the configuration documentation for your platform. UNIX platforms note that: After you complete the installation of Adaptive Server, your runserver file contains an invocation of the dataserver utility to start Adaptive Server. Two versions of the dataserver utility are available: dataserver, and dataserver. The utility you use depends on the platform you use: For Sun Solaris platforms, use dataserver if you plan to use security services and dataserver if you do not plan to use security services. For HP and RS/6000 platforms, use dataserver and diagserver. You can use a single binary, whether or not you are using security services.
If you are using the DCE security service, be sure you have defined the keytab file. You can specify the -K option to dataserver to specify the location of the keytab file. If you do not specify a location, Adaptive Server assumes the file is located in $SYBASE/config/$DSLISTEN_key. Optionally, you can specify the location as follows:
$SYBASE/bin/dataserver -Stest4 -dd_master
466
CHAPTER 16
-K/opt/dcelocal/keys/test4_key
This dataserver command starts the server using the master device d_master and the keytab file stored in /opt/dcelocal/keys/test4_key. If you are using the default location for keytab, and $DSLISTEN is set to the name of your server (test4), you can execute:
$SYBASE/bin/dataserver -dd_master
Then, Adaptive Server looks for the keytab file in $SYBASE/config/test4_key.
Determining security mechanisms to support

If use security services is set to 0, Adaptive Server supports no security mechanisms. If use security services is set to 1, Adaptive Server supports a security mechanism when both of the following circumstances are true: The security mechanisms global identifier is listed in the interfaces file or Directory Service. The global identifier is mapped in objectid.dat to a local name that is listed in libtcl.cfg.
For information about how Adaptive Server determines which security mechanism to use for a particular client, see Using security mechanisms for the client on page 478.
Adding logins to support unified login

When users log in to Adaptive Server with a preauthenticated credential, Adaptive Server: 1 Checks whether the user is a valid user in master..syslogins. If the user is listed in master..syslogins, Adaptive Server accepts the login without requiring a password. If the user name is not in master..syslogins, Adaptive Server checks whether a default secure login is defined. If the default login is defined, the user is logged in successfully as that login. If a default login is not defined, Adaptive Server rejects the login.
467
Therefore, consider whether you want to allow only those users who are defined as valid logins to use Adaptive Server, or whether you want users to be able to log in with the default login. You must add the default login in master..syslogins and use sp_configure to define the default. For details, see Establishing a secure default login on page 463.
General procedure for adding logins

Follow the general procedure described in Table 16-5 to add logins to the server and, optionally, to add users to one or more databases with appropriate roles and authorizations to one or more databases.
Table 16-5: Adding logins and authorizing database access Task 1. Add a login for the user. 2. Add the user to one or more databases. Required role System Security Officer System Administrator or Database Owner Command or procedure
sp_addlogin sp_adduser
execute this procedure from within the database.

sp_changegroup
See Adding logins to Adaptive Server on page 377 Adding users to databases on page 381
3. Add the user to a group in a database.
System Administrator or Database Owner
execute this procedure from within the database.

grant role
Changing a users group membership on page 406 sp_changegroup in the Reference Manual Creating and assigning roles to users on page 387 grant in the Reference Manual Creating and assigning roles to users on page 387 in the Reference Manual grant in the Reference Manual create role in the Reference Manual Chapter 17, Managing User Permissions
4. Grant system roles to the user. 5. Create user-defined roles and grant the roles to users. 6. Grant access to database objects.
System Administrator or System Security Officer System Security Officer
create role grant role
Database object owners
Establishing security for remote procedures

Adaptive Server acts as the client when it connects to another server to execute a remote procedure call (RPC) as shown in Figure 16-2.
468
CHAPTER 16
Figure 16-2: Adaptive Server acting as client to execute an RPC
Remote Local RPC
One physical connection is established between the two servers. The servers use the physical connection to establish one or more logical connectionsone logical connection for each RPC. Adaptive Server 11.5 and later supports two security models for RPCs: security model A and security model B.
Security model A
For security model A, Adaptive Server does not support security services such as message confidentiality via encryption between the two servers. Security model A is the default.
Security model B
For security model B, the local Adaptive Server gets a credential from the security mechanism and uses the credential to establish a secure physical connection with the remote Adaptive Server. With this model, you can use one or more of these security services: Mutual authentication the local server authenticates the remote server by retrieving the credential of the remote server and verifying it with the security mechanism. With this service, the credentials of both servers are authenticated and verified. Message confidentiality via encryption messages are encrypted when sent to the remote server, and results from the remote server are encrypted. Message integrity messages between the servers are checked for tampering.
469
Unified login and the remote procedure models

If the local server and remote server are set up to use security services, you can use unified login on both servers with either model, using one of these two methods: The System Security Officer defines a user as trusted with sp_remoteoption on the remote server. With this method, a security mechanism such as DCE authenticates the user and password. The user gains access to the local server via unified login and executes an RPC on the remote server. The user is trusted on the remote server and does not need to supply a password. A user specifies a password for the remote server when he or she connects to the local server. The facility to specify a remote server password is provided by the ct_remote_pwd routine available with Open Client Client-Library/C. For more information about this routine, see the Open Client Client-Library/C Reference Manual.
Establishing the security model for RPCs

To establish the security model for RPCs, use sp_serveroption. The syntax is:
sp_serveroption server, optname, [true | false]
To establish the security model, set optname to rpc security model A or rpc security model B. server names the remote server. For example, to set security model B for remote server TEST3, execute:
sp_serveroption test3, "rpc security model B", true
The default model is A, that is, remote procedure calls are handled the same as in versions earlier than 11.5. No server options need to be set for model A.
Setting server options for RPC security model B

For RPC security model B, you can set options with sp_serveroption. The syntax is:
sp_serveroption server, optname, optvalue
where: server is the name of the remote server. optname is the name of the option. Values can be:
470
CHAPTER 16
security mechanism the name of the security mechanism to use when running an RPC on a remote server. mutual authentication set this option to 1 for the local Adaptive Server to authenticate and verify the remote server. If this parameter is 0 (the default), the remote server still verifies the local server when it sends an RPC, but the local server does not check the validity of the remote server. use message confidentiality set this option to 1 for all messages for the RPCs to be encrypted when they are sent to the remote server and received from the remote server. If this parameter is 0 (the default), data for the RPCs are not encrypted. use message integrity set this option to 1 to require that all RPC
messages be checked for tampering. If this parameter is 0 (the default), RPC data will not be checked for tampering. optvalue must be equal to true or false for all values of optname, except security mechanism. If the option you are setting is security mechanism, specify the name of the security mechanism. To find the list of security mechanisms, execute:
select * from syssecmechs
For information about the syssecmechs system table, see Determining enabled security services on page 479. For example, to set up the local server to execute RPCs on a remote server, TEST3, which uses the dce security mechanism, and to use mutual authentication for all RPCs between the two servers, execute:
sp_serveroption TEST3, "security mechanism", dce sp_serveroption TEST3, "mutual authentication", true
Rules for setting up security model B for RPCs

Follow these rules when setting up security model B for RPCs: Both servers must be using security model B. Both servers must be using the same security mechanism, and that security mechanism must support the security services set with sp_serveroption.
471
The System Security Officer of the local server must specify any security services that are required by the remote server. For example, if the remote server requires that all messages use the message confidentiality security service, the System Security Officer must use sp_serveroption to activate use message confidentiality. Logins that are authenticated by a security mechanism and log in to Adaptive Server using unified login are not permitted to execute RPCs on the remote procedure unless the logins are specified as trusted on the remote server or the login specifies the password for the remote server. Users, when they use Open Client Client-Library can use the routine ct_remote_pwd to specify a password for server-to-server connections. A System Administrator on Adaptive Server can use sp_remoteoption to specify that a user is trusted to use the remote server without specifying a password.
Preparing to use security model B for RPCs

Table 16-6 provides steps for using security model B to establish security for RPCS.
Table 16-6: Process for using security model B for RPCs Task, who performs it, and where System Administrator from the operating system: 1. Make sure the interfaces file or the Directory Service contains an entry for both servers and a secmech line listing the security mechanism. System Security Officer on remote server: 2. Add the local server to master..sysservers. System Security Officer on remote server: 3. Add logins to
master..syslogins.
Command, system procedure, or tool UNIX: dscp Desktop: dsedit
See Specifying security information for the server on page 460

dscp in the Open Client/Server Configuration Guide for UNIX dsedit in the Open Client/Server
Configuration Guide for Desktop Platforms

sp_addserver
Example:
sp_addserver "lcl_server" sp_addlogin
Adding a remote server on page 437

sp_addserver in the Reference
Manual. Example:
sp_addlogin user1, "pwuser1"
Adding logins to Adaptive Server on page 377

sp_addlogin in the Reference Manual
472
CHAPTER 16
Task, who performs it, and where System Security Officer on remote server: 4. Set use security services on, and set the rpc security model B as the model for connections with the local server.
Command, system procedure, or tool See sp_configure to set use security services Establishing the security model for sp_serveroption to set the RPC security RPCs on page 470 model. Example:
sp_configure "use security services", 1 sp_serveroption lcl_server, "rpc security model B", true sp_remoteoption
Enabling network-based security on page 462 use security services (Windows only) in Chapter 5, Setting Configuration Parameters
sp_configure and sp_serveroption in
System Administrator on remote server: 5. Optionally, specify certain users as trusted to log in to the remote server from the local server without supplying a password. System Security Officer on local server: 6. Add both the local server and the remote server to
master..sysservers.
Example:
sp_remoteoption lcl_server, user1, user1, trusted, true
the Reference Manual Password checking for remote users on page 446
sp_remoteoption in the Reference
Manual
sp_addserver
Example:
sp_addserver lcl_server, local sp_addserver rem_server sp_addlogin
Adding a remote server on page 437

sp_addserver in the Reference
Manual Adding logins to Adaptive Server on page 377

sp_addlogin in the Reference Manual
System Security Officer on local server: 7. Add logins to master..logins. System Security Officer on local server: 8. Set use security services on, and set the rpc security model B as the model for connections with the remote server.
Example: sp_addlogin user1, "pwuser1"

sp_configure to set use security services. sp_serveroption to set the RPC security
Establishing the security model for RPCs on page 470 Enabling network-based security on page 462 use security services (Windows only) in Chapter 5, Setting Configuration Parameters
sp_configure and sp_serveroption in
model. Example:
sp_configure "use security services", 1 sp_serveroption rem_server, "rpc security model B", true sp_serveroption
System Security Officer on local server: 9. Specify the security mechanism and the security services to use for connections with the remote server.
Example:
sp_serveroption rem_server, "security mechanism", dce sp_serveroption rem_server, "use message integrity", true
the Reference Manual Setting server connection options on page 439

sp_serveroption in the Reference
Manual
473
Example of setting up security model B for RPCs

Assume that: A local server, lcl_serv, will run RPCs on a remote server, rem_serv. Both servers will use security model B and the DCE security service. These RPC security services will be in effect: mutual authentication and message integrity. Users user1 and user2 will use unified login to log in to the local server, lcl_serv, and run RPCs on rem_serv. These users will be trusted on rem_serv and will not need to specify a password for the remote server. User user3 will not use unified login, will not be trusted, and must supply a password to Adaptive Server when logging in.
Use the following sequence of commands to set up security for RPCs between the servers: System Security Officer on remote server (rem_serv):
sp_addserver lcl_serv sp_addlogin user1, "eracg12" sp_addlogin user2, "esirpret" sp_addlogin user3, "drabmok" sp_configure "use security services", 1 sp_serveroption lcl_serv, "rpc security model B", true sp_serveroption lcl_serv, "security mechanism", dce
System Administrator on remote server (rem_serv):

sp_remoteoption lcl_serv, user1, user1, trusted, true sp_remoteoption lcl_serv, user2, user2, trusted, true
System Security Officer on local server (lcl_serv):

sp_addserver lcl_serv, local sp_addserver rem_serv sp_addlogin user1, "eracg12" sp_addlogin user2, "esirpret" sp_addlogin user3, "drabmo1" sp_configure "use security services", 1 sp_configure rem_serv, "rpc security model B", true sp_serveroption rem_serv, "security mechanism", dce sp_serveroption rem_serv, "mutual authentication" true
474
CHAPTER 16
sp_serveroption rem_serv, "use message integrity" true
In addition, the interfaces file or Directory Service must have entries for rem_serv and lcl_serv. Each entry should specify the dce security service. For example, you might have these interfaces entries, as created by the dscp utility:
## lcl_serv (3201) lcl_serv master tli tcp /dev/tcp \x00020c8182d655110000000000000000 query tli tcp /dev/tcp \x00020c8182d655110000000000000000 secmech 1.3.6.1.4.1.897.4.6.1 ## rem_serv (3519) rem_serv master tli tcp /dev/tcp \x000214ad82d655110000000000000000 query tli tcp /dev/tcp \x000214ad82d655110000000000000000 secmech 1.3.6.1.4.1.897.4.6.1 Note To actually use the security services on either server, you must restart the server so that the static parameter use security services takes effect.
For detailed information about setting up servers for remote procedure calls, see Chapter 15, Managing Remote Servers.
Getting information about remote servers

sp_helpserver displays information about servers. When it is used without an argument, it provides information about all the servers listed in sysservers. You
can specify a particular server to receive information about that server. The syntax is:
sp_helpserver [server]
For example, to display information about the GATEWAY server, execute:

sp_helpserver GATEWAY
Connecting to the server and using the security services

The isql and bcp utilities include the following commandline options to enable network-based security services on the connection:
-K keytab_file -R remote_server_principal
475
-V security_options -Z security_mechanism
These options are described in the following paragraphs.

-K keytab_file can be used only with DCE security, and specifies a DCE
keytab file that contains the security key for the user logging in to the server. You can create keytab files with the DCE dcecp utilitysee your DCE documentation for more information. If the -K option is not supplied, the user of isql must be logged in to DCE. If the user specifies the -U option, the name specified with -U must match the name defined for the user in DCE.
-R remote_server_principal specifies the principal name for the server
as defined to the security mechanism. By default, a servers principal name matches the servers network name (which is specified with the -S option or the DSQUERY environment variable). The -R option must be used when the servers principal name and network name are not the same.
-V security_options specifies network-based user authentication. With
this option, the user must log in to the networks security system before running the utility. In this case, if a user specifies the -U option, the user must supply the network user name known to the security mechanism; any password supplied with the -P option is ignored. -V can be followed by a security_options string of key-letter options to enable additional security services. These key letters are:
c enable data confidentiality service. i enable data integrity service. m enable mutual authentication for connection establishment. o enable data origin stamping service. r enable data replay detection. q enable out-of-sequence detection.
-Z security_mechanism specifies the name of a security mechanism to use on the connection.
Security mechanism names are defined in the libtcl.cfg configuration file. If no security_mechanism name is supplied, the default mechanism is used. For more information about security mechanism names, see the Open Client/Server Configuration Guide for your platform.
476
CHAPTER 16
If you log in to the security mechanism and then log in to Adaptive Server, you do not need to specify the -U option on the utility because Adaptive Server gets the user name from the security mechanism. For example, consider the following session:
svrsole4% dce_login user2 Enter Password: svrsole4% $SYBASE/bin/isql_r -V 1> select suser_name() 2> go -----------------------------user2
For this example, user2 logs in to DCE with dce_login and then logs in to Adaptive Server without specifying the -U option. The -V option without parameters implicitly specifies one security service: unified login. For more information about Adaptive Server utilities, see the Utility Guide. If you are using Client-Library to connect to Adaptive Server, you can define security properties before connecting to the server. For example, to check message sequencing, set the CS_SEC_DETECTSEQ property. For information about using security services with Client-Library, see the Open Client Client-Library/C Reference Manual.
Example of using security services

Assume that your login is mary and you want to use the DCE security mechanism with unified login (always in effect when you specify the -V option of isql or bcp), message confidentiality, and mutual authentication for remote procedures. You want to connect to server WOND and run remote procedures on GATEWAY with mutual authentication. Assuming that a System Security Officer has set up both WOND and GATEWAY for rpc Model B, added you as a user on both servers, and defined you as a remote, trusted user on GATEWAY, you can use the following process: 1 Log in to the DCE security mechanism and receive a credential:
dce_login mary
Log in to the Adaptive Server with isql:

isql -SWOND -Vcm
Run:
GATEWAY...sp_who GATEWAY...mary_prc1
477
GATEWAY...mary_prc2
Now, all messages that Mary sends to the server and receives from the server are encrypted (message confidentiality), and when she runs remote procedures, both the WOND and GATEWAY servers are authenticated.
Using security mechanisms for the client

Adaptive Server, when it is started, determines the set of security mechanisms it supports. (See Determining security mechanisms to support on page 467. From the list of security mechanisms that Adaptive Server supports, it must choose the one to be used for a particular client. If the client specifies a security mechanism (for example with the -Z option of isql), Adaptive Server uses that security mechanism. Otherwise, it uses the first security mechanism listed in the libtcl.cfg file.
Getting information about available security services

Adaptive Server enables you to: Determine what security mechanisms and services are supported by Adaptive Server Determine what security services are active for the current session Determine whether a particular security service is enabled for the session
Determining supported security services and mechanisms

A system table, syssecmechs, provides information about the security mechanisms and security services supported by Adaptive Server. The table, which is dynamically built when you query it, contains these columns:
sec_mech_nameis the name of the security mechanism; for example, the
security mechanism might be dce or NT LANMANAGER.

available_serviceis the name of a security service supported by the security mechanism; for example, the security service might be unified login.
The table may have several rows for a single security mechanism: one row for each security service supported by the mechanism.
478
CHAPTER 16
To list all the security mechanisms and services supported by Adaptive Server, run this query:
select * from syssecmechs
The result might look something like this:

sec_mech_name available_service ------------------------------ -------------------dce unifiedlogin dce mutualauth dce delegation dce integrity dce confidentiality dce detectreplay dce detectseq
Determining enabled security services

To determine which security services are enabled for the current session, use the function show_sec_services. For example:
select show_sec_services() -------------------------------------------------unifiedlogin mutualauth confidentiality (1 row affected)
Determining whether a security service Is enabled

To determine whether a particular security service, such as mutualauth is enabled, use the function is_sec_service_on. The following is the syntax, where security_service_nm is a security service that is available:
is_sec_service_on(security_service_nm)
Use the name that is displayed when you query syssecmechs. For example, to determine whether mutualauth is enabled, execute:
select is_sec_service_on("mutualauth") ----------1 (1 row affected)
A result of 1 indicates the security service is enabled for the session. A result of 0 indicates the service is not in use.
479
Using Kerberos
Kerberos is a network authentication protocol that uses secret key cryptography so that a client can prove its identity to a server across a network connection. User credentials are obtained when the user logs in to the operating system, or by executing an authentication program. These credentials are then used by each application to perform authentication. Users only have to log in once, instead of having to log in to each application. Kerberos assumes the KDC is running and properly configured for your realm, and the client libraries are installed under or on each client host in your realm. For configuration information, consult the documentation and the reference pages that come with the Kerberos software. Adaptive Server supports Kerberos through: CyberSafe Kerberos libraries MIT Kerberos libraries, version 1.3.1 Native libraries
Note To enable Kerberos security options, you must have ASE_SECDIR, the
Security and directory services package.
Kerberos compatibility
Table 16-7 shows which variation of Kerberos is supported on which platforms.
Table 16-7: Adaptive Server Kerberos Interoperability Hardware platforms Solaris 32 Solaris 64 Linux 32 Windows 32 AIX 32 KDC server CSF, AD, MIT CSF, AD, MIT CSF, AD, MIT CSF, AD CSF GSS client CSF, MIT, Native CSF, MIT, Native MIT, Native CSF CSF
Use the following keys to read the interoperability matrix: CSF CyberSafe Ltd. AD Microsoft Active Directory MIT MIT version 1.3.1
480
CHAPTER 16
For the latest Adaptive Server feature matrix, see http://www.sybase.com/detail?id=1034492.
Starting Adaptive Server under Kerberos

To start Adaptive Server under Kerberos, add the Adaptive Server name to the KDC and extract the service key to a key table file. For example:
/krb5/bin/admin admin/ASE -k -t /krb5/v5srvtab -R addrn my_ase; mod my_ase attr nopwchg; ext -n my_ase eytabfile.krb5 Connecting as: admin/ASE Connected to csfA5v01 in realm ASE. Principal added. Principal modified. Key extracted. Disconnected. Note The administrator can also be authenticated using a password on the command line. In this example, the -k option is used, which tells the administrator to search the /krb5/v5srvtab file (specified using the -t option) for
the administrator and the Adaptive Server key, instead of prompting for a password, which is useful for writing shell scripts.
Configuring Kerberos
The configuration process is similar, regardless of which variety of Kerberos is used. To configure Kerberos: 1 Set up Kerberos third-party software and create a Kerberos administrative user. To do this, you must: Install Kerberos client software on machines where Open Client Server clients or Adaptive Server will run. The following client packages have been verified to be working: CyberSafe TrustBroker 4.0 MIT Kerberos version 1.3.1
481
Install the Kerberos KDC server on a separate, dedicated machine.

Note KDCs from CyberSafe TrustBroker 4.0, MIT Kerberos v.1.3.1,
and Microsoft Windows Active Directory have been verified for use with Adaptive Server. Create an administrator account on the Kerberos server with administration privileges. This account is used for subsequent client actions such as creating principals from the client machines.
Note Execute the remainder of these steps on the Kerberos client
machine. 2 3 Add Kerberos principal for Adaptive Server ase120srv or ase120srv@MYREALM. Extract the keytab file for principal ase120srv@MYREALM and store it as a file:
/krb5/v5srvtab
The following UNIX examples use the command line tool kadmin, available with CyberSafe or MIT Kerberos.There are also GUI tools available to aid in administration of Kerberos and users:
CyberSafe Kadmin: % kadmin aseadmin Principal - aseadmin@MYREALM Enter password: Connected to csfA5v01 in realm ASE. Command: add ase120srv Enter password: Re-enter password for verification: Principal added. Command: ext -n ase120srv Service Key Table File Name (/krb5/v5srvtab): Key extracted. Command: quit Disconnected.
In a production environment, you must control the access to the keytab file. If a user can read the keytab file, he or she can create a server that impersonates your server. Use chmod and chgrp so that /krb5/v5srvtab is:
-rw-r----- 1 root sybase 45 Feb 27 15:42 /krb5/v5srvtab
482
CHAPTER 16
When using Active Directory as the KDC, log in to the Domain Controller to add users and Adaptive Server principals. Use the Active Directory Users and Computers wizard to guide you through the creation of users and principals. Extracting the keytab file for use with Adaptive Server requires an optional tool called ktpass, which is included in the Microsoft Support Tools package. With Active Directory, extracting the keytab with ktpass is done as a separate step from creating the principal. The keytab file on Windows for Adaptive Server is located with the CyberSafe program files. For example, c:\Program Files\CyberSafe\v5srvtab is the expected location of Adaptive Servers keytab file when CyberSafe software is installed on the C: drive. 4 5 Add a Kerberos principal for the user sybuser1 as sybuser1@MYREALM. Start Adaptive Server and use isql to log in as sa. The following steps configure Adaptive Server parameters to use Kerberos security services, and create the user login account. These are the same on both Windows or UNIX machines: Change configuration parameter use security services to 1:
1> sp_configure 'use security services', 1
Add new login for user, sybuser1 and then add the user:
1> sp_addlogin sybuser1, password
Shut down Adaptive Server and modify administrative files and connectivity configuration files. On UNIX platforms, the interfaces file is under $SYBASE/ and has an entry that looks similar to:
ase120srv master tli tcp myhost 2524 query tli tcp myhost 2524 secmech 1.3.6.1.4.1.897.4.6.6
On Windows platforms, the sql.ini file is in %SYBASE%\ini, and has an equivalent server entry that looks like:
[ase120srv] master=TCP,myhost,2524 query=TCP,myhost,2524 secmech=1.3.6.1.4.1.897.4.6.6
483
The libtcl.cfg or libtcl64.cfg file is located in $SYBASE/$SYBASE_OCS/config/ on UNIX platforms.The SECURITY section should have an entry that looks similar to the following for CyberSafe Kerberos client libraries:
[SECURITY] csfkrb5=libsybskrb.so secbase=@MYREALM libgss=/krb5/lib/libgss.so
A 64-bit CyberSafe Kerberos client library entry follows:

[SECURITY] csfkrb5=libsybskrb64.so secbase=@MYREALM libgss= \ /krb5/appsec-rt/lib/64/libgss.so
For a machine that uses MIT Kerberos client libraries, the entry looks something like:
[SECURITY] csfkrb5=libsybskrb.so secbase=@MYREALM libgss=/opt/mitkrb5/lib/libgssapi_krb5.so
For a machine that uses Native OS provided libraries, such as Linux, it looks similar to:
[SECURITY] csfkrb5=libsybskrb.so secbase=@MYREALM libgss=/usr/kerberos/lib/libgssapi_krb5.so
On Windows NT, the %SYBASE%\%SYBASE_OCS%\ini\libtcl.cfg file contains an entry like:

[SECURITY] csfkrb5=libskrb secbase=@MYREALM libgss=C:\WinNT\System32\gssapi32.dll Note Note the libgss=<gss shared object path> that specifies the GSS API library to be used. It is important that you distinctly locate the Kerberos Client libraries being used, especially when multiple versions are installed on a machine.
Also check the objectid.dat under $SYBASE/$SYBASE_OCS/config/ and make sure the [secmech] section has an entry for csfkrb5:
[secmech] 1.3.6.1.4.1.897.4.6.6 = csfkrb5
484
CHAPTER 16
You can use environment variables to override default locations of keytab files, Kerberos configuration, and realm configuration files. This is Kerberos-specific behavior and may not work consistently on all platforms. For example, the CSFC5KTNAME environment variable can be used on CyberSafe UNIX platforms to specify the keytab file:
% setenv CSFC5KTNAME /krb5/v5srvtab
For MIT Kerberos, the equivalent environment variable is KRB5_KTNAME. See the vendor documentation for information about these environment variables. Your application may also need to modify the environment variable for dynamic library search paths. On UNIX, the most commonly used environment variable is LD_LIBRARY_PATH; on Windows, PATH is typically set to include DLL locations. You may need to modify these environment variables to enable applications to load the third-party objects correctly. For example this command adds the location of CyberSafe 32-bit libgss.so shared object to the search path in a C-Shell environment:
% set path = ( /krb5/lib $path )
Restart Adaptive Server. You should see the following log message during start-up:
00:00000:00000:2001/07/25 11:43:09.91 server Successfully initialized the security mechanism 'csfkrb5'. The SQL Server will support use of this security mechanism.
Use isql as UNIX user sybuser1 (without the -U and -P arguments) to connect:
% $SYBASE/$SYBASE_OCS/bin/isql -Sase120srv -V 1>...
You can also use the encryption option:

$SYBASE/$SYBASE_OCS/bin/isql -Sase120srv Vc
485
Configuring Adaptive Server for LDAP User Authenticaiton

The LDAP user authentication allows client applications to send user name and password information to Adaptive Server for authentication by the LDAP server instead of syslogins. Authentication using the LDAP server allows you to use server-wide passwords instead of Adaptive Server or applicationspecific passwords. LDAP user authentication is ideal for organizations with an existing computing environment who want to simplify and centralize user administration, or for users in a new computing environment who want to avoid unnecessary complexities for administering users. LDAP user authentication works with directory servers that meet Version 3 of the LDAP protocol standard, including Active Directory, iPlanet, and OpenLDAP Directory Server. You can use two authentication algorithms with LDAP user authentication,. which differ in how they obtain a users Distinguished Name (DN). The algorithms use either: Composed DN for authentication, available for Adaptive Server version 12.5.1 or later, or, Searched DN for authentication, available for Adaptive Server version 12.5.2 and later.
The primary data structure used with the LDAP protocol is the LDAP URL. An LDAP URL specifies a set of objects or values on an LDAP server. Adaptive Server uses LDAP URLs to specify an LDAP server and search criteria to use to authenticate login requests. The LDAP URL uses this syntax:
ldapurl::=ldap://host:port/node/?attributes?base | one | sub?filter
where: host is the host name of the LDAP server. port is the port number of the LDAP server. node specifies the node in the object hierarchy at which to start the search. attributes is a list of attributes to return in the result set. Each LDAP server may support a different list of attributes.
486
CHAPTER 16
base | one | sub qualifies the search criteria. base specifies a search of the base node; one specifies a search of the base node and one sublevel below the base node; sub specifies a search of the base node and all node sublevels. filter specifies the attribute or attributes to be authenticated. The filter can be simple, such as uid=*, or compound, such as (uid=*)(ou=group).
Composed DN algorithm
The following steps describe the login sequence when you use the composed DN algorithm: 1 2 3 4 5 Open Client connects to an Adaptive Server listener port. The Adaptive Server listener accepts the connection. Open Client sends an internal login record Adaptive Server reads the login record. Adaptive Server binds to the LDAP server with a DN composed from the primary URL and the login name from the login record. This bind also uses the password from the login record. The LDAP server authenticates the user, returning either a success or failure message. If the Primary URL specifies a search, then Adaptive Server sends the search request to the LDAP server. The LDAP server returns the results of the search. Adaptive Server accepts or rejects the login, based on the search results.
6 7 8 9
Searched DN algorithm
The following steps describe the login sequence when you use the searched DN algorithm: 1 2 3 4 Open Client connects to an Adaptive Server listener port. The Adaptive Server listener accepts the connection. Open Client sends an internal login record. Adaptive Server reads the login record.
487
Adaptive Server binds to the LDAP Server with a directory server access account. The connection established in steps 5 and 6 may persist between authentication attempts from Adaptive Server to reuse connections to DN searches.
6 7 8 9
The LDAP server authenticates the user, returning either a success or failure message. Adaptive Server sends search requests to LDAP server based on the login name from the login record and the DN lookup URL. The LDAP server returns the results of the search. Adaptive Server reads the results to obtain an a value of attribute from the DN lookup URL.
10 Adaptive Server uses the value of attribute as the DN and the password from the login record to bind to the LDAP server. 11 The LDAP server authenticates the user, returning either a success or failure message. 12 If the primary URL specifies a search, Adaptive Server sends the search request to the LDAP server. 13 The LDAP Server returns the results of the search. 14 Adaptive Server accepts or rejects the login, based on the search results. Adaptive Server reports a generic login failure to the client if any of these authentication criteria are not met. You may skip steps 12 and 13 by not specifying search criteria in the primary or secondary URL strings. When you do not specify criteria in the primary or secondary URL strings, the authentication completes, displaying the success or failure returned by step 11.
Configuring LDAP
These are the steps for configuring Adaptive Server for LDAP authentication.
Configuring LDAP in new Adaptive Server installations
1 2
Specify the Adaptive Server LDAP URL search strings and access account values. Set enable ldap user auth to 2.
488
CHAPTER 16
3 4
Add users in the LDAP directory server using LDAP vendor-supplied tools. Add users to Adaptive Server using sp_addlogin. You can also use sp_maplogin to automatically create login accounts upon authentication or apply other login controls.
Migrating existing Adaptive Servers to LDAP
To avoid disruption of service in existing server installations, migrate Adaptive Server to LDAP: Specify an LDAP URL search string to Adaptive Server. Set the configuration parameter enable ldap user auth to 1. Add users in the LDAP directory server. When all users are added to the LDAP server, set enable ldap user auth to 2 to require all authentications to be performed with LDAP, or use sp_maplogin to override configuration parameters with login controls.
LDAP administration
Use sp_ldapadmin to create and maintain LDAP URL search strings and administrative access account information. You must have the SSO role to execute sp_ldapadmin. The syntax is:
sp_ldapadmin { set_primary_url, 'ldapurl' | set_secondary_url, { 'ldapurl' | null } | set_access_acct, account_distinguished_name, account_password | set_dn_lookup_url, ldapurl | list_urls | list_access_acct | check_url, 'ldapurl' | check_login, 'login_name' }
See the Reference Manual: Commands for more information about sp_ldapadmin.
Composed DN examples
You can use a composed DN algorithm for user authentication if you use a simple LDAP server topology and schema. If you use commercially available schemas (for example, iPlanet Directory Servers or OpenLDAP Directory Servers), users are created as objects in the same container in the LDAP server tree, and Adaptive Server determines the users DN from the objects location. However, there are restrictions on the LDAP servers schema:
489
You must specify the filter with the attribute name that uniquely identifies the user to be authenticated. You must specify the filter with the attribute name=*. The asterisk is a wildcard character. The appropriate attribute name to use in the filter depends on the schema used by the LDAP server, The Adaptive Server login name is the same as the short user name for example, a UNIX user name. The DN uses the short user name rather than a full name with embedded spaces or punctuation. For example, jqpublic meets the restriction for a DN, but John Q. Public as the DN does not.
iPlanet example
LDAP vendors may use different object names, schema, and attributes than those used in these examples. There are many possible LDAP URL search strings, and valid sites may also extend schemas locally or use them in ways different from each other: This example uses the uid=* filter. To compose the DN, Adaptive Server replaces the wildcard with the Adaptive Server login name to be authenticated, and appends the resulting filter to the node parameter in the LDAP URL. The resulting DN is:
uid=myloginname,ou=People,dc=mycomany,dc=com
After a successful bind operation, Adaptive Server uses the connection to search for attribute names such as uid, that are equal to the login name:
sp_ldapadmin set_primary_url, 'ldap://myhost:389/ou=People,dc=mycompany,dc=com??sub?uid=*'
This example uses the schema defined in OpenLDAP 2.0.25, with an attribute name of cn. The composed DN is cn=myloginname,dc=mycompany,dc=com:
sp_ldapadmin set_primary_url, 'ldap://myhost:389/dc=mycompany,dc=com??sub?cn=*'
Searched DN examples
Use the searched DN to use an Active Directory server or other LDAP server environment that does not meet the restrictions to use the composed DN algorithm. Perform these steps for an Active Directory server using commercially available user schema from a Windows 2000 Server. a Set the access account information:
sp_ldapadmin set_access_acct, 'cn=Admin Account, cn=Users, dc=mycompany, dc=com',
490
CHAPTER 16
'Admin Account secret password'
Set the primary URL:
sp_ldapadmin set_primary_url, 'ldap://hostname:389/
Set the DN lookup URL search string:
sp_ldapadmin set_dn_lookup_url, 'ldap://hostname:389/cn=Users,dc=mycompany,dc=com?distinguishedName ?one?samaccountname=*'
On Windows 2000, the short name is typically referred to as the User Logon Name and is given the attribute name samaccountname in the default schema. This is the attribute name used to match the Adaptive Server login name. The DN for a user contains a full name with punctuation and embedded spaces (for example, cn=John Q. Public, cn=Users, dc=mycomany, dc=com. The DN on Windows does not use the short name, so the searched DN algorithm is appropriate for sites using the Active Directory schema (the default) for their LDAP server. The primary URL does not specify a search. Instead, it relies on the bind operation for the authentication.
Examples using search filters to restrict Adaptive Server access
You can use LDAP URL search strings to restrict access to groups of users on LDAP servers. For example, to restrict logins to users in an accounting group, use a compound filter to restrict access to the group of users where attribute group=accounting. The following LDAP URL string uses the composed DN algorithm for an iPlanet server:
sp_ldapadmin set_primary_url, 'ldap://myhost:389/ou=People,dc=mycompany, dc=com??sub?(&(uid=*)(group=accounting))'
Adaptive Server binds with DN

uid=mylogin,ou=People,dc=mycompany,dc=com. After successfully
binding with this identity, it searches for:

"ou=People,dc=mycompany,dc=com??sub?(&(uid=mylogin)(group=accounting))"
Authentication succeeds if this search returns any objects. These examples use LDAP URL strings with compound filters:
sp_ldapadmin set_primary_url, 'ldap://myhost:389/ou=people,dc=mycompany,dc=com??s ub?(&(uid=*)(ou=accounting) (l=Santa Clara))' sp_ldapadmin, set_primary_url, 'ldap://myhost:389/ou=people,dc=mycompany,dc=com??s ub?(&(uid=*)(ou=Human%20Resources))'
491
Failover support
When a major failure occurs in the LDAP directory server specified by the primary URL and the server no longer responds to network requests, Adaptive Server attempts to connect to the secondary LDAP directory server specified by the secondary URL. Adaptive Server uses the LDAP function ldap_init to determine if it can open a connection to the LDAP directory server. A NULL or invalid primary URL string causes Adaptive Server to attempt failover to a secondary URL. Failures returned by LDAP bind or search operations do not cause Adaptive Server to fail over to the secondary URL.
Adaptive Server logins and LDAP user accounts

Once you enable LDAP user authentication, choose and set an authentication algorithm and URL strings, you must configure the user accounts. The LDAP administrator creates and maintain accounts in the LDAP server, and the database administrator creates and maintains accounts in Adaptive Server. Alternatively, the database administrator can choose administration options that allow flexibility with login accounts when integrating Adaptive Server with external authentication mechanisms such as LDAP server. The database administrator continues to administer the Adaptive Server account roles, default database, default language, and other login-specific attributes using traditional commands and procedures. Table 16-8 describes the updates to syslogins table Adaptive Server makes at login time. These updates assume that LDAP user authentication is configured, the login is not restricted from using LDAP, and you have not set the create login mapping.
492
CHAPTER 16
Table 16-8: Updates to syslogins from LDAP Does the row exist in syslogins? No No Yes Yes LDAP server authentication succeeds? Yes No Yes No
Changes in syslogins No change, login fails No change, login fails Update row if password has changed No change
Configuring Adaptive Server for authentication using PAM

The pluggable authentication modules (PAM) support allows multiple authentication service modules to be stacked and made available without modifying the applications that require the authentication. PAM integrates Adaptive Server with Solaris and Linux operating systems and simplifies the management and administration of user accounts and authentication mechanisms, thus reducing the total cost of ownership. An additional benefit is that users can customize or write their own authentication and authorization modules.
Note PAM support is currently available on Linux and on Solaris platforms.
For more information on PAM user authentication, see your operating system documentation.
493
Figure 16-3: PAM architecture
Client
Server Authentication Account management Password management

Session management
syslogins
LDAP server PAM

Authentication Account management
PAM API
PAM SPI
Intergrated login, DCE and so on
Custom Authentication Adaptive Server passes the login name and credentials obtained from the login packet to the PAM API. PAM loads a service provider module as specified in the operating system configuration files and calls appropriate functions to complete the authentication process.
Enabling PAM in Adaptive Server

Perform the tasks in this section to enable PAM on Adaptive Server.
494
CHAPTER 16
Determining which PAM module to use

Both Linux and Solaris have predefined PAM modules. You can choose to either use one of these modules or to create one of your own. When creating your own modules, follow the guidelines in your operating system documentation on creating a PAM module.
Note PAM modules you create should comply with RFC 86.0 Unified Login With Pluggable Authentication Modules (PAM). Adaptive Server supports the authentication management module of the RFC. It does not support the account management, session management, or password management modules.
Configuring operating system files

To enable PAM support, configure your operating system as follows: For Solaris, add the following line to /etc/pam.conf:
ase auth required /user/lib/security/$ISA/pam_unix.so.1
For Linux, create a new file called /etc/pam.d/ase, and add:

auth requried /lib/security/pam_unix.so
For more information on how to create these entries, see your operating system documentation.
Running a 32- and 64-bit server on the same machine

$ISA is an environment variable that stands for Instruction Set Architecture. It allows 32- and 64-bit libraries to run together. On Solaris 32-bit machines, $ISA is replaced by an empty string, while on 64bit machines, it is replaced by the string sparcv9. To use both 32- and 64-bit servers, place the 32-bit PAM module in a directory, and to place the 64-bit version in a subdirectory of this directory. The entry in pam.conf should look similar to:
$ ls /usr/lib/security/pam_whatever.so.1 pam_whatever.so.1 -> /wherever/pam_whatever_32bits.so.1 $ ls /usr/lib/security/sparcv9/pam_whatever.so.1
495
pam_whatever.so.1 -> /wherever/pam_whatever_64bits.so.1 ase auth required /usr/lib/security/$ISA/pam_whatever.so.1 Note $ISA is the only variable allowed in pam.conf.
Configuring Adaptive Server for PAM user authentication

enable pam user auth is a new configuration parameter that enables PAM user authentication support. It can be set as follows:
sp_configure "enable pam user auth", 0 | 1 | 2
where: 0 disables PAM authentication. This is the default. 1 indicates Adaptive Server will try PAM authentication first, and then fall back to syslogins authentication if PAM authentication fails. 2 indicates only PAM authentication may be used.
Note When PAM is enabled, password management is delegated to the PAM
service providers.
Adaptive Server logins and PAM user accounts

After you have set enable PAM user authentication and completed the PAM configuration for both Adaptive Server and the operating system, you must configure the user accounts. The operating system or network security administrator creates and maintains user accounts in the PAM service provider, and the database administrator creates and maintains accounts in Adaptive Server. Alternatively, the database administrator can choose administration options that allow flexibility with login accounts when integrating Adaptive Server with external authentication mechanisms such as PAM. The database administrator continues to administer the Adaptive Server account roles, default database, default language, and other login-specific attributes using traditional commands and procedures.
496
CHAPTER 16
Table 16-9 describes updates to syslogins made at login time. It assumes that PAM user authentication is configured, the login is not restricted from using PAM, and you have not set the create login mapping.
Table 16-9: Updates to syslogins from PAM Does the row exist in syslogins? No No Yes Yes PAM authentication succeeds? Yes No Yes No Changes in syslogins No change, login fails No change, login fails Update row if password has changed No change
Enhanced login controls

You can configure Adaptive Server to allow the server-wide authentication mechanism according to the methods discussed in the LDAP and PAM sections earlier. You can also configure Adaptive Server to specify the authentication mechanism for each individual login on the server using its Enhanced login controls. Login specific controls are useful when a server is transitioning between the authentication mechanisms or for server-specific logins that local server administration may require and are not associated with a centrally managed user login.
Forcing authentication
You can force a login to use a specific authentication process by using these parameters for sp_modifylogin and sp_addlogin:
ASE use Adaptive Server internal authentication using passwords from
syslogins table.
LDAP use external authentication with an LDAP server. PAM use external authentication with PAM.
497
ANY by default, users are authenticated using this authentication method. A user with ANY authentication means that Adaptive Server checks if there is any external authentication mechanism defined, and if there is, it is used. Otherwise, it uses Adaptive Servers authentication.
Adaptive Server checks for external authentication mechanisms in the following order: 1 2 3 LDAP. Pluggable Authentication Modules (PAM). If both LDAP and PAM are enabled, PAM authentication is never attempted for a user. If neither PAM nor LDAP is enabled, Adaptive Server uses syslogins to authenticate the login.
Login accounts such as sa continue to be validated using the syslogins catalog. Only the SSO role can set authenticate for a login. For example, the following authenticates the login with sp_modifylogin:
sp_modifylogin "nightlyjob", "authenticate with", "ASE" sp_displaylogin "nightlyjob"
Displays output similar to:

Suid: 1234 Loginname: nightlyjob Fullname: Batch Login Default Database: master . . . Date of Last Password Change: Oct 2 2003 7:38 PM Password expiration interval: 0 Password expired: N Minimum password length: 6 Maximum failed logins: 0 Current failed login attempts: Authenticate with: ASE
Mapping logins using sp_maplogin

Use sp_maplogin to map logins:
sp_maplogin (authentication_mech | null), (client_username | null), (action | login_name | null)
Where:
498
CHAPTER 16
authentication_mech is one of the valid values specified for authenticate with option in sp_modifylogin.
client_username is an external user name, which can be an operating system name, a user name for an LDAP server, or anything else the PAM library understands. A null value indicates that any login name is valid. action indicates create login or drop. When you use create login the login is created as soon as is is authenticated. Use drop to remove logins. login_name is an Adaptive Server login that already exists in syslogins.
This example maps external user jsmith to the Adaptive Server user guest. Once authenticated, jsmith has the privileges of guest. The audit login record shows both the client_username and the Adaptive Server user name:
sp_maplogin NULL, "jsmith", "guest"
This example tells Adaptive Server to create a new login for all external users authenticated with LDAP, if a login does not already exist:
sp_maplogin LDAP, NULL, "create login"
Displaying mapping information

sp_helpmaplogin displays mapping information:
sp_helpmaplogin [ (authentication_mech | null), (client_username | null) ]
Where authentication_mech is one of the valid values specified for authenticate with option in sp_modifylogin, and client_username is is an external user name. If you do not include any parameters, sp_helpmaplogin displays login information about all users currently logged in to Adaptive Server. You can restrict the output to specific sets of client user names or authentication mechanists by using the parameters listed above. This displays information about all logins:
sp_helpmaplogin authentication -------------NULL LDAP client name ----------jsmith NULL login name -----------------guest create login
Determining the authentication mechanism

Use the @@authmech global variable to determine the authentication mechanism Adaptive Server uses.
499
For example, if Adaptive Server is enabled for LDAP user authentication with failover (enable ldap user auth = 2) and user Joe is an external user with authentication set to ANY, when Joe logs in, Adaptive Server attempts to authenticate Joe, using LDAP user authentication. If Joe fails authentication as a user in LDAP, Adaptive Server authenticates Joe using Adaptive Server authentication, and if that succeeds, he logs in successfully. @@authmech global has this value:
select @@authmech ---------------------------------ase
If Adaptive Server is configured for strict LDAP user authentication (enable ldap user auth = 2) and Joe is added as a valid user in LDAP, when Joe logs in, the value for @@authmech is:
select @@authmech ---------------------------------ldap
500
CH A PTE R
1 7
Managing User Permissions
This chapter describes the use and implementation of user permissions.

Topic Overview Database Owner privileges Other database user privileges Database object owner privileges Granting and revoking permissions Granting and revoking roles Using row-level access control Acquiring the permissions of another user Reporting on permissions Using views and stored procedures as security mechanisms Page 501 504 506 506 507 525 528 555 560 565
Overview
Discretionary access controls (DACs) allow you to restrict access to objects and commands based on a users identity, group membership and active roles. The controls are discretionary because a user with a certain access permission, such as an object owner, can choose whether to pass that access permission on to other users. Adaptive Servers discretionary access control system recognizes the following types of users: Users possessing one or more system defined roles: System Administrator, System Security Officer, Operator, and other roles Database Owners Database object owners Other users
501
Overview
System Administrators operate outside the DAC system and have access permissions on all database objects at all times. System Security Officers can always access the audit trail tables in the sybsecurity database. Database Owners do not automatically receive permissions on objects owned by other users; however, they can: Temporarily acquire all permissions of a user in the database by using the setuser command to assume the identity of that user. Permanently acquire permission on a specific object by using the setuser command to assume the identity of the object owner, and then using grant commands to grant the permissions.
For details on assuming another users identity to acquire permissions on a database or object, see Acquiring the permissions of another user on page 555. Object owners can grant access to those objects to other users and can also grant other users the ability to pass the access permission to other users. You can give various permissions to users, groups, and roles with the grant command, and rescind them with the revoke command. Use grant and revoke to give users permission to:: Create databases Create objects within a database Execute certain commands such as dbcc and set proxy Execute dbcc Access specified tables, views, and columns
grant and revoke can also be used to set permissions on system tables.
For permissions that default to public, no grant or revoke statements are needed. Some commands can be used at any time by any user, with no permission required. Others can be used only by users of a particular status and they are not transferable. The ability to assign permissions for the commands that can be granted and revoked is determined by each users role or status (as System Administrator, Database Owner, or database object owner), and by whether the user was granted a role with permission that includes the option to grant that permission to other users.
502
CHAPTER 17
You can also use views and stored procedures as security mechanisms. See Using views and stored procedures as security mechanisms on page 565.
Permissions for creating databases

Only a System Administrator can grant permission to use the create database command. The user that receives create database permission must also be a valid user of the master database because all databases are created while using master. In many installations, the System Administrator maintains a monopoly on create database permission to centralize control of database placement and database device space allocation. In these situations, a System Administrator creates new databases on behalf of other users, and then transfers ownership to the appropriate user. To create a database that is to be owned by another user: 1 2 3 Issue the create database command in the master database. Switch to the new database with the use command. Execute sp_changedbowner.
Changing database ownership

Use sp_changedbowner to change the ownership of a database. Often, System Administrators create the user databases, then give ownership to another user after some of the initial work is complete. Only the System Administrator can execute sp_changedbowner. Sybase suggests that you transfer ownership before the user has been added to the database, and before the user has begun creating objects in the database. The new owner must already have a login name on Adaptive Server, but cannot be a user of the database, or have an alias in the database. You may have to use sp_dropuser or sp_dropalias before you can change a databases ownership, and you may have to drop objects before you can drop the user. Issue sp_changedbowner in the database whose ownership is to be changed. The syntax is:
sp_changedbowner loginame [, true ]
503
Database Owner privileges
This example makes albert the owner of the current database and drops aliases of users who could act as the old dbo:
sp_changedbowner albert
Include the true parameter to transfer aliases and their permissions to the new dbo.
Note You cannot change the ownership of the master database and should not
change the ownership of any other system databases.
Database Owner privileges

Database Owners and System Administrators are the only users who can grant object creation permissions to other users. The Database Owner has full privileges to do anything inside that database, and must explicitly grant permissions to other users with the grant command. Permission to use the following commands is automatically granted to the Database Owner and cannot be transferred to other users:
checkpoint dbcc drop database dump database dump transaction grant (object creation permissions) load database load transaction revoke (object creation permissions) setuser
Database Owners can grant permission to use the following commands to other users:
create default
504
CHAPTER 17
create procedure create rule create table create view grant (permissions on system tables) grant (select, insert, delete, update, references, truncate table, delete statistics, update statistics, and execute permissions on database objects) revoke (permissions on system tables) revoke (select, insert, delete, update, references, truncate table, delete statistics, update statistics, and execute permissions on database objects)
Permissions on system procedures

Set permissions on system procedures in the sybsystemprocs database, where the system procedures are stored. Security-related system procedures can be run only by System Security Officers. Certain other system procedures can be run only by System Administrators. Some of the system procedures can be run only by Database Owners. These procedures make sure that the user executing the procedure is the owner of the database from which they are being executed. Other system procedures can be executed by any user who has been granted permission. A user must have permission to execute a system procedure in all databases, or in none of them. Users who are not listed in sybsystemprocs..sysusers are treated as guest in sybsystemprocs, and are automatically granted permission on many of the system procedures. To deny a user permission on a system procedure, the System Administrator must add him or her to sybsystemprocs..sysusers and issue a revoke statement that applies to that procedure. The owner of a user database cannot directly control permissions on the system procedures from within his or her own database.
505
Database object owner privileges
Database object owner privileges

A user who creates a database object (a table, view, or stored procedure) owns the object and is automatically granted all object access permissions on it. Users other than the object owner, including the owner of the database, are automatically denied all permissions on that object, unless they are explicitly granted by either the owner or a user who has grant permission on that object. As an example, suppose that Mary is the owner of the pubs2 database, and has granted Joe permission to create tables in it. Now Joe creates the table new_authors; he is the owner of this database object. Initially, object access permissions on new_authors belong only to Joe. Joe can grant or revoke object access permissions for this table to other users. The following object creation permissions default to the owner of a table and cannot be transferred to other users:
alter table drop table create index truncate table update statistics
Permission to use the grant and revoke commands to grant specific users select, insert, update, delete, references, and execute permissions on specific database objects can be transferred, using the grant with grant option command. Permission to drop an objecta table, view, index, stored procedure, rule, or defaultdefaults to the object owner and cannot be transferred.
Other database user privileges

At the bottom of the hierarchy are other database users. Permissions are granted to or revoked from them by object owners, Database Owners, users who were granted permissions, or a System Administrator. These users are specified by user name, group name, or the keyword public.
506
CHAPTER 17
Granting and revoking permissions

You can control the following types of permissions with grant and revoke: Object access permissions Permission to select from functions Permission to execute commands Permission to execute dbcc commands Default permissions on system tables
Each database has its own independent protection system. Having permission to use a certain command in one database does not give you permission to use that command in other databases.
Object access permissions

Object access permissions regulate the use of certain commands that access certain database objects. For example, you must explicitly be granted permission to use the select command on the authors table. Object access permissions are granted and revoked by the object owner (and System Administrators), who can grant them to other users. Table 17-1 lists the types of object access permissions and the objects to which they apply.
507
Table 17-1: Permissions and the objects to which they apply Permission
select update insert delete references execute truncate table delete statistics update statistics
Object Table, view, column Table, view, column Table, view Table, view Table, column Stored procedure Table Table Table
The references permission refers to referential integrity constraints that you can specify in an alter table or create table command. The other permissions refer to SQL commands. Object access permissions default to System Administrators and the objects owner, and can be granted to other users. Use the grant command to grant object access permissions. The syntax is:
grant {all [privileges]| permission_list} on { table_name [(column_list)] | view_name[(column_list)] | stored_procedure_name} to {public | name_list | role_name} [with grant option] grant [truncate table | update statistics | delete statistics] on table_name to {user_name | role_name}
Use the revoke command to revoke object access permissions. The syntax is:
revoke [grant option for] {all [privileges] | permission_list} on { table_name [(column_list)] | view_name [(column_list)] | stored_procedure_name} from {public | name_list | role_name} [cascade] revoke [truncate table | update statistics | delete statistics] on table_name from {user_name | role_name}
508
CHAPTER 17
all or all privileges specifies all permissions applicable to the specified object. All object owners can use all with an object name to grant or revoke permissions on their own objects. If you are granting or revoking permissions on a stored procedure, all is the same as execute.
Note insert, update statistics, delete statistics, truncate table, and delete permissions do not apply to columns, so you cannot include them in a permission list (or use the keyword all) if you specify a column list.
permission_list is the list of permissions that you are granting. If you name more than one permission, separate them with commas. Table 17-2 illustrates the access permissions that can be granted on each type of object:
Table 17-2: Object access permissions
Object Table or view Column
permission_list can include

select, insert, delete, update, references, truncate table, update statistics, delete statistics references applies to tables but not views; the other permissions apply to both tables and views. select, update, references, update statistics, delete statistics, truncate table
Stored procedure execute
You can specify columns in the permission_list or the column_list, but not both.
on specifies the object for which the permission is being granted or
revoked. You can grant or revoke permissions for only one table, view, or stored procedure object at a time. You can grant or revoke permissions for more than one column at a time, but all the columns must be in the same table or view. You can grant or revoke permissions only on objects in your current database.
public refers to the group public, which includes all Adaptive Server users. public means slightly different things for grant and revoke:
For grant, public includes the object owner. Therefore, if you have revoked permissions from yourself on your object, and later you grant permissions to public, you regain the permissions along with the rest of public. For more information, see Granting and revoking permissions for update statistics, delete statistics, and truncate table on page 513. For revoke, public excludes the owner.
name_list includes:
509
Group names User names A combination of user and group names, each separated from the next by a comma
role_name is an Adaptive Server system-defined or user-defined role. You can create and define a hierarchy of user-defined roles and grant them privileges based on the specific role granted. System-defined roles include sa_role (System Administrator), sso_role (System Security Officer), and oper_role (Operator). You cannot create or modify system-defined roles.
with grant option in a grant statement allows the users specified in name_list
to grant the specified object access permissions to other users. If a user has
with grant option permission on an object, that permission is not revoked when permissions on the object are revoked from public or a group of
which the user is a member.

grant option for revokes with grant option permissions, so that the users
specified in name_list can no longer grant the specified permissions to other users. If those other users have granted permissions to other users, you must use the cascade option to revoke permissions from them as well. The user specified in name_list retains permission to access the object, but can no longer grant access to other users. grant option for applies only to object access permissions, not to object creation permissions. The cascade option in a revoke statement removes the specified object access permissions from the user(s) specified in name_list, and also from any users they granted those permissions to.
You may grant and revoke permissions only on objects in the current database. If several users grant access to an object to a particular user, the users access remains until access is revoked by all those who granted access or until a System Administrator revokes the access. That is, if a System Administrator revokes access, the user is denied access even though other users have granted access. Only a System Security Officer can grant or revoke permissions to create triggers. The Database Owner can create triggers on any user table. Users can create triggers only on tables that they own. Permission to issue the create trigger command is granted to users by default.
510
CHAPTER 17
When the System Security Officer revokes permission for a user to create triggers, a revoke row is added in the sysprotects table for that user. To grant permission to that user to issue create trigger, issue two grant commands: the first command removes the revoke row from sysprotects; the second inserts a grant row. If permission to create triggers is revoked, the user cannot create triggers even on tables that the user owns. Revoking permission to create triggers from a user affects only the database where the revoke command was issued.
Concrete identification
Adaptive Server identifies users during a session by login name. This identification applies to all databases in the server. When the user creates an object, the server associates both the owners database user ID (uid) and the creators login name with the object in the sysobjects table. This information concretely identifies the object as belonging to that user, which allows the server to recognize when permissions on the object can be granted implicitly. If an Adaptive Server user creates a table and then creates a procedure that accesses the table, any user who is granted permission to execute the procedure does not need permission to access the object directly. For example, by giving user mary permission on proc1, she can see the id and descr columns from table1, though she does not have explicit select permission on the table:
create table table1 (id int, amount money, descr varchar(100)) create procedure proc1 as select id, descr from table1 grant execute on proc1 to mary
There are, however, some cases where implicit permissions are only useful if the objects can be concretely identified. One case is where aliases and cross-database object access are both involved. You cannot drop an alias if the aliased login created any objects or thresholds. Before using sp_dropalias to remove an alias that has performed these actions, remove the objects or procedures. If you still need them after dropping the alias, re-create them with a different owner.
511
Special requirements for SQL92 standard compliance

When you have used the set command to turn ansi_permissions on, additional permissions are required for update and delete statements. Table 17-3 summarizes the required permissions.
Table 17-3: ANSI permissions for update and delete Permissions required: set ansi_permissions off
update update permission on columns
Permissions required: set ansi_permissions on

update permission on columns where values are being set
where values are being set
and
select permission on all columns appearing in the where clause select permission on all columns on the right side of the set clause
delete
delete permission on the table
delete permission on the table from which rows are being deleted
and
select permission on all columns appearing in the where clause
If ansi_permissions is on and you attempt to update or delete without having all the additional select permissions, the transaction is rolled back and you receive an error message. If this occurs, the object owner must grant you select permission on all relevant columns.
Examples of granting object access permissions

This statement gives Mary and the sales group permission to insert into and delete from the titles table:
grant insert, delete on titles to mary, sales
This statement gives Harold permission to use the stored procedure makelist:
grant execute on makelist to harold
This statement grants permission to execute the custom stored procedure sa_only_proc to users who have been granted the System Administrator role:
grant execute on sa_only_proc to sa_role
This statement gives Aubrey permission to select, update, and delete from the authors table and to grant the same permissions to other users:
512
CHAPTER 17
grant select, update, delete on authors to aubrey with grant option
Examples of revoking object access permissions

These two statements both revoke permission for all users except the table owner to update the price and total_sales columns of the titles table:
revoke update on titles (price, total_sales) from public revoke update(price, total_sales) on titles from public
This statement revokes permission from Clare to update the authors table, and simultaneously revokes that permission from all users to whom she had granted that permission:
revoke update on authors from clare cascade
This statement revokes permission from operators to execute the custom stored procedure new_sproc:
revoke execute on new_sproc from oper_role
Granting and revoking permissions for update statistics, delete statistics, and truncate table
Adaptive Server allows you to grant and revoke permissions for users, roles, and groups for the update statistics, delete statistics, and truncate table commands. Table owners can also provide permissions through an implicit grant by adding update statistics, delete statistics, and truncate table to a stored procedure and then granting execute permissions on that procedure to a user or role. You cannot grant or revoke permissions for update statistics at the column level. You must have the sso_role to run update statistics or delete statistics on sysroles, syssrvroles, and sysloginroles security tables.
513
By default, users with the sa_role have permission to run update statistics and delete statistics on system tables other than sysroles, syssrvroles and sysloginroles, and can transfer this privilege to other users. The partial syntax for grant and revoke is:
grant [truncate table | update statistics | delete statistics] on table_name to {user_name | role_name} revoke [truncate table | update statistics | delete statistics] on table_name from {user_name | role_name}
You can also issue grant all to grant permissions on update statistics, delete statistics, and truncate table. For example, the following allows user harry to use truncate table and updates statistics on the authors table:
grant truncate table on authors to harry grant update statistics on authors to harry
The following revokes truncate table and update statistics privileges from harry on the authors table:
revoke truncate table on authors from harry revoke update statistics on authors from harry
The following allows user billy to use the delete statistics command on the authors table:
grant delete statistics on authors to billy
The following revokes the delete statistics privileges from user billy on the authors table:
revoke delete statistics on authors from billy
The following grants truncate table and update and delete statistics privileges to all users with the oper_role (if users billy and harry possess the oper_role, they can now run these commands on authors):
grant truncate table on authors to oper_role grant update statistics on authors to oper_role grant delete statistics on authors to oper_role
The following revokes truncate table and update and delete statistics privileges from all users with the oper_role:
revoke truncate table on authors from oper_role revoke update statistics on authors from oper_role revoke delete statistics on authors from oper_role
Users billy and harry can no longer run these commands on authors.
514
CHAPTER 17
You can also implicitly grant permissions for truncate table, delete statistics, and update statistics through a stored procedure. For example, assuming billy owns the authors table, he can run the following to grant harry privileges to run truncate table and update statistics on authors:
create procedure sproc1 as truncate table authors update statistics authors go grant execute on sproc1 to harry go
You can also implicitly grant permissions at the column level for update
statistics and delete statistics through stored procedures.
Note Once you grant permission to execute update statistics to a user, they also have permission to execute variations of this command, such as update all statistics, update partition statistics, update index statistics, update statistics
table, and so on. For example, the following grants billy permission to run all variations of update statistics on the authors table:
grant update statistics on authors to billy
If you revoke a users permission to execute update statistics, you also revoke their ability to execute the variations of this command. You cannot grant variants of update statistics (for example, update index statistics) separately. That is, you cannot issue:
grant update all statistics to harry
However, you can write stored procedures that control who executes these commands. For example, the following grants billy execute permission for update index statistics on the authors table:
create proc sp_ups as update index statistics on authors go revoke update statistics on authors from billy go grant execute on sp_ups to billy
You cannot grant and revoke delete statistics permissions at the column level.
515
Although Adaptive Server audits truncate table as a global, miscellaneous audit, it does not audit update statistics. To retain clear audit trails for both truncate table and update statistics, Sybase recommends that you include both commands in a stored procedure to which you grant users execute permission, as described above. The command fails and generates error number 10330 if a user issues update
statistics, delete statistics or truncate table and they:
Do not own the table. Do not have the sa_role. Are not a database owner who has successfully used setuser to become the user who is the owner of the table. Have not been granted update statistics, delete statistics, or truncate table privileges.
Granting permissions on functions

Use grant select on builtin function_name to grant a user permission to use the functions set_appcontext, get_appcontext, list_appcontext, and rm_appcontext. The syntax is:
grant select on [builtin] function_name to {name_list | role_list}
Where:
builtin Used to distinguish between a table and a grantable function with
the same name. function_name Name of the function for which you are granting permission. Functions for which select permission can be granted are set_appcontext, get_appcontext, list_appcontext, and rm_appcontext. name_list List of users database names and group names. role_list List of the name of system or user-defined roles to permission is being granted, and cannot be a variable.
This grants select permission on the get_appcontext function to public:

grant select on builtin get_appcontext to public
516
CHAPTER 17
Granting and revoking permissions to execute commands

This section describes how to grant and revoke permissions for users to execute specific commands.
Object creation permissions regulate the use of commands that create objects. These permissions can be granted only by a System Administrator or a Database Owner. The object creation commands are:
create database create default create procedure create rule create table create view
The syntax for object creation permissions differs slightly from the syntax for object access permissions. The syntax for grant is:
grant {all [privileges] | command_list} to {public | name_list | role_name}
The syntax for revoke is:

revoke {all [privileges] | command_list} from {public | name_list | role_name}
where:
all or all privileges can be used only by a System Administrator or the Database Owner. When used by a System Administrator in the master database, grant all assigns all create permissions, including create database. If the System Administrator executes grant all from another database, all create permissions are granted except create database. When the Database Owner uses grant all, Adaptive Server grants all create permissions except create database, and prints an informational message.
517
command_list is the object creation permissions that you are granting or revoking. Separate commands with commas. The list can include create database, create default, create procedure, create rule, create table, and create view. create database permission can be granted only by a System Administrator, and only from within the master database.
public is all users except the Database Owner (who owns object
creation permissions within the database). name_list is a list of user or group names, separated by commas. role_name is the name of an Adaptive Server system or user-defined role. You can create and define a hierarchy of user-defined roles and grant them privileges based on the specific role granted.
Examples of granting object creation permissions

The first example grants Mary and John permission to use create database and create table. Because create database permission is being granted, this command can be executed only by a System Administrator within the master database. Mary and Johns create table permission applies only to the master database.
grant create table, create database to mary, john
This command grants permission to create tables and views in the current database to all users:
grant create table, create view to public
Example of revoking object creation permissions

This example revokes permission to create tables and rules from mary:
revoke create table, create rule from mary
Granting proxy authorization

System Security Officers use the grant set proxy or grant set session authorization command to give a user permission to impersonate another user within the server. The user with this permission can then execute either set proxy or set session authorization to become another user.
518
CHAPTER 17
To grant proxy authorization permission, you must be a System Security Officer and execute the grant command from the master database. The syntax is:
grant set proxy to user | role [restricted role user_list | role_list | all | system]
where: user_or_role_list list of roles you are restricting for the target login. Both the grantee and target login must have all roles on this list or the command fails. all ensures that all roles belonging to the grantee are granted to the target login. system ensures the grantee has the same set of system roles as the target login.

Example 1
Example 1: This example grants set proxy to user joe but restricts him from switching identities to any user with the sa, sso, or admin roles (however, if he already has these roles, he can set proxy for any user with these roles):
grant set proxy to joe restricted role sa_role, sso_role, admin_role
When joe tries to switch his identity to a user with admin_role (in this example, Our_admin_role), the command fails unless he already has admin_role:
set proxy Our_admin_role Msg 10368, Level 14, State 1: Server 's', Line 2:Set session authorization permission denied because the target login has a role that you do not have and you have been restricted from using.
After joe is granted the admin_role and retries the command, it succeeds:
grant role admin_role to joe set proxy Our_admin_role Example 2
Example 2: Restricts joe from being granted any new roles when switching identities:
grant set proxy to joe restricted role all
joe can grant set proxy only to users who have the same (or lessor) roles than he has.
519
Example 3
Example 3: Restricts Joe from acquiring any new system roles when using set proxy:
grant set proxy to joe restricted role system
set proxy fails if the target login has system roles that joe lacks.
Granting permissions on dbcc commands

System Administrators can grant the execution of dbcc commands to users and roles that do not have System Administrator-level privileges in Adaptive Server. This discretionary access control allows System Administrators to control access to database objects or to certain database- and server-level actions.
Server-wide and database-specific dbcc commands

dbcc commands are either:
Database-specific dbcc commands such as checkalloc and checkstorage that execute on a particular target database. Although these commands are database-specific, only System Administrators can grant or revoke them. Server-wide dbcc commands such as tune that are effective server-wide and are not associated with any particular database. These commands are granted server-wide by default and are not associated with any database.
System Administrators can allow users to execute the grant dbcc command in all databases by making them valid users in the master database. However, it may be more convenient to allow grant dbcc to roles instead of individual users, since this allows users to use databases as a guest user instead of requiring that they each be added manually to the database. From a security administration perspective, System Administrators may prefer to grant permission to execute database-specific dbcc commands server-wide. For example, you can set a grant dbcc checkstorage command on all databases to a user-defined role called storage_admin_role, thereby eliminating the need to set grant dbcc checkstorage to storage_admin_role in every database. The following commands are are effective server-wide, but are not database-specific: Server-wide dbcc commands such as tune.
520
CHAPTER 17
Database-specific dbcc commands that are granted server-wide, such as grant dbcc checkstorage granted to storage_admin_role.
dbcc grantees and users in databases

grant dbcc and revoke dbcc work on users in databases.
Since roles are automatically added as users in a database on their first grant in a database, there are no additional requirements when roles are granted dbcc privileges. Logins must be valid users in the database where permissions are granted. Valid users include guest. For server-wide dbcc commands, the login must be a valid user in master, and the System Administrator must be in master when granting the permission. For database-specific dbcc commands the login should be a valid user in the target database.
Permissions on system tables

Permissions for use of the system tables can be controlled by the Database Owner, just like permissions on any other tables. When a database is created, select permission on some system tables is granted to public, and select permission on some system tables is restricted to administrators. For some other tables, a few columns have restricted select permissions for public. To determine the current permissions for a particular system table, execute:
sp_helprotect system_table_name
For example, to check the permissions of syssrvroles in the master database, execute:
use master go sp_helprotect syssrvroles go
521
The default situation is that no usersincluding Database Ownerscan modify the system tables directly. Instead, the T-SQL commands and the system procedures supplied with Adaptive Server modify the system tables. This helps guarantee integrity.
Warning! Although Adaptive Server provides a mechanism that allows you to modify system tables, Sybase strongly recommends that you do not do so.
Granting default permissions to system tables and stored procedures

The grant and revoke commands include the default permissions parameter. installmodel or installmaster do not grant default permissions for some system tables (see the table below). Instead, the default permissions on the system tables are assigned when Adaptive Server builds a new database. The partial syntax is:
grant default permissions on system tables revoke default permissions on system tables
where default permissions on system tables specifies that you grant or revoke the default permissions for the following system tables when you issue it from any database:
sysalternates sysattributes syscolumns syscomments sysconstraints sysdepends sysindexes sysjars syskeys syslogs sysobjects syspartitions sysprocedures sysprotects sysqueryplans sysreferences sysroles syssegments sysstatistics systabstats systhresholds systypes sysusermessages sysusers sysxtypes
default permissions on system tables also makes the following changes:
Revokes select on syscolumns(encrkeyid) from public Revokes select on syscolumns(encrkeydb) from public Grants select on syscolumns to sso_role Revokes sysobjects(audflags) permissions from public Grants permissions for sysobjects to sso_role
If you run this command from the master database, default permissions for the following system tables are granted or revoked:
522
CHAPTER 17
syscharsets sysconfigures syscurconfigs sysdatabases sysdevices
syslanguages syslocks syslogins sysmessages sysprocesses
sysremotelogins sysresourcelimits sysservers systimeranges systransactions
sysusages
The command also makes the following changes: Revokes select on sysdatabases(audflags) from public Revokes select on syscolumns(encrkeyid) from public Revokes select on syscolumns(encrkeydb) from public Grants select on syscolumns to sso_role Revokes select on sysdatabases(deftabaud) from public Revokes select on sysdatabases(defvwaud) from public Revokes select on sysdatabases(defpraud) from public Revokes select on sysdatabases(audflags2) from public Grants seelct on sysdatabases to sso_role. Revokes select on syslogins(password) to public Revokes select on syslogins(audflags) from public Grants select on syslogins to sso_role
Combining grant and revoke statements

You can assign specific permissions to specific users, or, if most users are going to be granted most privileges, it may be easier to assign all permissions to all users, and then revoke specific permissions from specific users. For example, a Database Owner can grant all permissions on the titles table to all users by issuing:
grant all on titles to public
The Database Owner can then issue a series of revoke statements, for example:
revoke update on titles (price, advance)
523
from public revoke delete on titles from mary, sales, john

grant and revoke statements are order-sensitive: in case of a conflict, the most
recently issued statement supersedes all others.

Note Under SQL rules, you must use the grant command before using the revoke command, but the two commands cannot be used within the same
transaction. Therefore, when you grant public access to objects, and then revoke that access from an individual, there is a short period of time during which the individual has access to the objects in question. To prevent this situation, use the create schema command to include the grant and revoke clauses within one transaction.
Understanding permission order and hierarchy

grant and revoke statements are sensitive to the order in which they are issued. For example, if Joses group has been granted select permission on the titles table and then Joses permission to select the advance column has been revoked, Jose can select all the columns except advance, while the other users in his group can still select all the columns.
A grant or revoke statement that applies to a group or role changes any conflicting permissions that have been assigned to any member of that group or role. For example, if the owner of the titles table has granted different permissions to various members of the sales group, and wants to standardize, he or she might issue the following statements:
revoke all on titles from sales grant select on titles(title, title_id, type, pub_id) to sales
Similarly, a grant or revoke statement issued to public changes, for all users, all previously issued permissions that conflict with the new regime. The same grant and revoke statements issued in different orders can create entirely different situations. For example, the following set of statements leaves Jose, who belongs to the public group, without any select permission on titles:
grant select on titles(title_id, title) to jose
524
CHAPTER 17
revoke select on titles from public
In contrast, the same statements issued in the opposite order result in only Jose having select permission and only on the title_id and title columns:
revoke select on titles from public grant select on titles(title_id, title) to jose
When you use the keyword public with grant, you are including yourself. With revoke on object creation permissions, you are included in public unless you are the Database Owner. With revoke on object access permissions, you are included in public unless you are the object owner. You may want to deny yourself permission to use your own table, while giving yourself permission to access a view built on it. To do this, you must issue grant and revoke statements explicitly setting your permissions. You can reinstitute the permission with a grant statement.
Grant dbcc and set proxy issue warning for fipsflagger

grant dbcc and set proxy issue the following warning when they are issued while set fipsflagger option is enabled:
SQL statement on line number 1 contains Non-ANSI text. The error is caused due to the use of DBCC.
Granting and revoking roles

After a role is defined, it can be granted to any login account or role in the server, provided that it does not violate the rules of mutual exclusivity and hierarchy. Table 17-4 lists the tasks related to roles, the role required to perform the task, and the command to use.
525
Granting and revoking roles
Table 17-4: Tasks, required roles, and commands to use Task Grant the sa_role role Grant the sso_role role Grant the oper_role role Grant user-defined roles Create role hierarchies Modify role hierarchies Revoke system roles Revoke user-defined roles Required role System Administrator System Security Officer System Security Officer System Security Officer System Security Officer System Security Officer System Security Officer System Security Officer Command
grant role grant role grant role grant role grant role revoke role revoke role revoke role
Granting roles
To grant roles to users or other roles, use:
grant role role_granted [{, role_granted}...] to grantee [{, grantee}...]
where: role_granted is the role being granted. You can specify any number of roles to be granted. grantee is the name of the user or role. You can specify any number of grantees.
All roles listed in the grant statement are granted to all grantees. If you grant one role to another, it creates a role hierarchy. For example, to grant Susan, Mary, and John the financial_analyst and the payroll_specialist roles, enter:
grant role financial_analyst, payroll_specialist to susan, mary, john
Understanding grant and roles

You can use the grant command to grant permission on objects to all users who have been granted a specified role, whether system or user-defined. This allows you to restrict use of an object to users who have been granted any of these roles: Any system-defined role
526
CHAPTER 17
Any user-defined role
A role can be granted only to a login account or another role. However, grant permission does not prevent users who do not have the specified role from being granted execute permission on a stored procedure. To ensure, for example, that only System Administrators can successfully execute a stored procedure, use the proc_role system function within the stored procedure itself. See Displaying information about roles on page 414 for more information. Permissions granted to roles override permissions granted to users or groups. For example, assume John has been granted the System Security Officer role, and sso_role has been granted permission on the sales table. If Johns individual permission on sales is revoked, he can still access sales when he has sso_role active because his role permissions override his individual permissions. In granting permissions, a System Administrator is treated as the object owner. If a System Administrator grants permission on another users object, the owners name appears as the grantor in sysprotects and in sp_helprotect output. If several users grant access to an object to a particular user, the users access remains until access is revoked by all those who granted access. If a System Administrator revokes access, the user is denied access, even though other users have granted access.
Revoking roles
Use revoke role to revoke roles from users and other roles:
revoke role role_name [{, role_name}...]from grantee [{, grantee}...]
where: role_name is the role being revoked. You can specify any number of roles to be revoked. grantee is the name of the user or role. You can specify any number of grantees.
All roles listed in the revoke statement are revoked from all grantees. You cannot revoke a role from a user while the user is logged in.
527
Using row-level access control

Row-level access control enables the Database Owner or table owner to create a secure data access environment automatically, by providing: More granular data security: you can set permissions for individual rows, not just tables and columns Automatic data filtering according to group, role, and application Data-level security encoded in the server
Row-level access control restricts access to data in a tables individual rows, through three features: Access rules that the database owner defines and binds to the table Application Context Facility, which provides built-in functions that define, store, and retrieve user-defined contexts Login triggers that the Database Owner, sa_role, or the user can create
Adaptive Server enforces row-level access control for all data manipulation languages (DMLs), preventing users from bypassing the access control to get to the data. The syntax for configuring your system for row-level access control is:
sp_configure "enable row level access", 1
This option slightly increases the amount of memory Adaptive Server uses, and you need an ASE_ASM license option. Row-level access control is a dynamic option, so you need not restart Adaptive Server.
Access rules
To use the row-level access control feature, add the access option to the existing create rule syntax. Access rules restrict any rows that can be viewed or modified. Access rules are similar to domain rules, which allow table owners to control the values users can insert or update on a column. The domain rule applies restrictions to added data, functioning on update and insert commands.
528
CHAPTER 17
Access rules apply restrictions to retrieved data, enforced on select, update, and delete operations. Adaptive Server enforces the access rules on all columns that are read by a query, even if the columns are not included in the select list. In other words, in a given query, Adaptive Server enforces the domain rule on the table that is updated, and the access rule on all tables that are read. For example:
insert into orders_table select * from old_orders_table
In this query, if there are domain rules on the orders_table and access rules on the old_orders_table, Adaptive Server enforces the domain rule on the orders_table, because it is updated, and the access rule on the old_orders_table, because it is read. Using access rules is similar to using views, or using an ad hoc query with where clauses. The query is compiled and optimized after the access rules are attached, so it does not cause performance degradation. Access rules provide a virtual view of the table data, the view depending on the specific access rules bound to the columns. Access rules can be bound to user-defined datatypes, defined with sp_addtype. Adaptive Server enforces the access rule on user tables, which frees the table owner or Database Owner from the maintenance task of binding access rules to columns in the normalized schema. For instance, you can create a userdefined type, whose base type is varchar(30), call it username, and bind an access rule to it. Adaptive Server enforces the access rule on any tables in your application that have columns of type username. Application developers can write flexible access rules using Java and application contexts, described in Access rules as user-defined Java functions on page 534, and Using the Application Context Facility on page 538.
Syntax for access rules

Use the access parameter in the create rule syntax to create access rules.
create [or|and] access rule (access_rule_name) as (condition) Creating a sample table with access rules
This section shows the process of creating a table and binding an access rule to it.
529
Creating a table
A table owner creates and populates table T (username char(30), title char(20), classified_data char(1024)):
AA, "Administrative Assistant","Memo to President" AA, "Administrative Assistant","Tracking Stock Movements" VP1, "Vice President", "Meeting Schedule" VP2, "Vice President", "Meeting Schedule"
Creating and binding access rules
The table owner creates access rule uname_acc_rule and binds it to the username column on table T.
create access rule uname_acc_rule as @username = suser_name() ----------sp_bindrule uname_acc_rule, "T.username"
Querying the table
When you issue the following query:

select * from T
Adaptive Server processes the access rule that is bound to the username column on table T and attaches it to the query tree. The tree is then optimized and an execution plan is generated and executed, as though the user had executed the query with the filter clause given in the access rule. In other words, Adaptive Server attaches the access rule and executes the query as:
select * from T where T.username = suser_name().
The condition where T.username = suser_name() is enforced by the server. The user cannot bypass the access rule. The result of an Administrative Assistant executing the select query is:
AA, "Administrative Assistant","Memo to President" AA, "Administrative Assistant","Tracking Stock Movements" Dropping an access rule
Before you drop an access rule, you must unbind it from any columns or datatypes, using sp_unbindrule, as in the following example:
sp_unbindrule "T.username", NULL, "all"
sp_unbindrule unbinds any domain rules attached to the column by default.
After you unbind the rule, you can drop it:

drop rule "rule_name"
For example:
530
CHAPTER 17
drop rule "T.username" Syntax for extended access rule
Each access rule is bound to one column, but you can have multiple access rules in a table. create rule provides AND and OR parameters to handle evaluating multiple access rules. To create AND access rules and OR access rules, use extended access rule syntax:
AND access rule:
create and access rule rule_name
OR access rule
create or access rule rule_name as
You can bind AND access rules and OR access rules to a column or user-defined datatype. With the extended access rule syntax, you can bind multiple access rules to the table, although you can bind only one per column. When the table is accessed, the access rules go into effect, the AND rules bound first by default, and then the OR access rules. If you bind multiple access rules to a table without defining AND or OR access, the default access rule is AND. If there is only one access rule on a row of the table and it is defined as an OR access rule, it behaves as an AND access rule.
Using access and extended access rules

Create access rules
The following steps create access rules:

create access rule empid1_access as @empid = 1 create access rule deptno1_access as @deptid = 2
The following steps create OR access rules:

create or access rule name1_access as @name = "smith" create or access rule phone_access as @phone = "9999" Create table
This step creates a test table:

create table testtab1 (empno int, deptno int,name
531
char(10), phone char(4)) Bind rules to table
The following steps bind access rules to the test table columns:
sp_bindrule empid1_access, "testtab1.empno" /*Rule bound to table column.*/ (return status = 0) sp_bindrule deptno1_access,"testtab1.deptno" /*Rule bound to table column.*/ (return status = 0) sp_bindrule name1_access,"testtab1.name" /*Rule bound to table column.*/ (return status = 0) sp_bindrule phone_access,"testtab1.phone" /*Rule bound to table column.*/ (return status = 0)
Insert data into table
The following steps insert values into the test table:

insert testtab1 values (1,1,"smith","3245") (1 row affected) insert testtab1 values(2,1,"jones","0283") (1 row affected) insert testtab1 values(1,2,"smith","8282")(1 row affected) insert testtab1 values(2,2,"smith","9999") (1 row affected)
Access rule examples

The following examples show how access rules return specific rows containing information limited by access rules.
Example 1
This example returns information from two rows:

/* return rows when empno = 1 and deptno = 2 and ( name = "smith" or phone = "9999" ) */ select * from testtab1 empno deptno name phone
------------ ----------- ---------- -----
532
CHAPTER 17
1 1
2 smith 2 jones
8282 9999
(2 rows affected) /* unbind access rule from specific column */ sp_unbindrule "testtab1.empno",NULL,"accessrule" /*Rule unbound from table column.*/ (return status = 0) Example 2
This example returns information from four rows:

/* return rows when deptno = 2 and ( name = "smith" or phone = "9999" )*/ select * from testtab1 empno deptno name phone
----------- ----------- ---------- ----1 2 3 1 2 smith 2 smith 2 smith 2 jones 8282 9999 8888 9999
(4 rows affected)
/* unbind all deptno rules from specific column */ sp_unbindrule "testtab1.deptno",NULL,"all" /*Rule unbound from table column.*/ (return status = 0) Example 3
This example returns information from six rows:

/* return the rows when name = "smith" or phone = "9999" */ select * from testtab1 empno deptno name phone
----------- ----------- ---------- -----
533
1 1 2 3 1 2
1 smith 2 smith 2 smith 2 smith 2 jones 3 jones
3245 8282 9999 8888 9999 9999
Access rules and alter table command

When the table owner uses the alter table command, Adaptive Server disables access rules during the execution of the command and enables them upon completion of the command. The access rules are disabled to avoid filtering the table data during the alter table command.
Access rules and bcp

Adaptive Server enforces access rules when data is copied out of a table using the bulk copy utility (bcp). Adaptive Server cannot disable access rules, as it does with alter table, because bcp can be used by any user who has select permission on the table. For security purposes, the Database Owner should lock the table exclusively and disable access rules during bulk copy out. The lock disables access to other users while the access rules are disabled. The Database Owner should bind the access rules and unlock the table after the data has been copied.
Access rules as user-defined Java functions

Access rules can use user-defined Java functions. For example, you can use Java functions to write sophisticated rules using the profile of the application, the user logged in to the application, and the roles that the user is currently assigned for the application. The following Java class uses the method GetSecVal to demonstrate how you can use Java methods that use JDBC as user-defined functions inside access rules:
import java.sql.*; import java.util.*; public class sec_class { static String _url = "jdbc:sybase:asejdbc";
534
CHAPTER 17
public static int GetSecVal(int c1) { try { PreparedStatement pstmt; ResultSet rs = null; Connection con = null; int pno_val; pstmt = null; Class.forName("sybase.asejdbc.ASEDriver"); con = DriverManager.getConnection(_url); if (con == null) { return (-1); } pstmt = con.prepareStatement("select classification from sec_tab where id = ?"); if (pstmt == null) { return (-1); } pstmt.setInt(1, c1); rs = pstmt.executeQuery(); rs.next(); pno_val = rs.getInt(1); rs.close(); pstmt.close(); con.close(); return (pno_val); } catch (SQLException sqe) {
535
return(sqe.getErrorCode()); } catch (ClassNotFoundException e) { System.out.println("Unexpected exception : " + e.toString()); System.out.println("\nThis error usually indicates that " + "your Java CLASSPATH environment has not been set properly."); e.printStackTrace(); return (-1); } catch (Exception e) { System.out.println("Unexpected exception : " + e.toString()); e.printStackTrace(); return (-1); } } }
After compiling the Java code, you can run the same program from isql, as follows. For example:
javac sec_class.java jar cufo sec_class. jar sec_class.class installjava -Usa -Password f/work/work/FGAC/sec_class.jar -D testdb
From isql:
/*to create new user datatype class_level*/ sp_addtype class_level, int /*to create the sample secure data table*/ create table sec_data (c1 varchar(30), c2 varchar(30), c3 varchar(30), clevel class_level) /*to create the classification table for each user*/ create table sec_tab (userid int, clevel class-level int) insert into sec_tab values (1,10)
536
CHAPTER 17
insert insert insert insert insert insert
into into into into into into
sec_tab sec_tab sec_tab sec_tab sec_tab sec_tab
values values values values values values
(2,9) (3,7) (4,7) (5,4) (6,4) (7,4)
declare @v1 int select @v1 = 5 while @v1 > 0 begin insert into sec_data 'aaaaaaaaaa', 8) insert into sec_data 'aaaaaaaaaa', 7) insert into sec_data 'aaaaaaaaaa', 5) insert into sec_data 'aaaaaaaaaa', 5) insert into sec_data 'aaaaaaaaaa', 2) insert into sec_data 'aaaaaaaaaa', 3) select @v1 = @v1 -1 end go
values('8', 'aaaaaaaaaa', values('7', 'aaaaaaaaaa', values('5', 'aaaaaaaaaa', values('5', 'aaaaaaaaaa', values('2', 'aaaaaaaaaa', values('3', 'aaaaaaaaaa',
create access rule clevel_rule @clevel <= sec_class.GetSecVal(suser_id()) go create default clevel_def as sec_class.GetSecVal(suser_id()) go sp_bindefault clevel_def, class_level go sp_bindrule clevel, class_level go grant all on sec_data to public go grant all on sec_tab to public go
537
Using the Application Context Facility

Applications on a database server must limit access to the data. Applications are carefully coded to consider the profile of the user. For example, a Human Resources application is coded to know which users are allowed to update salary information. The attributes that enable this coding comprise an application context. The Application Context Facility (ACF) consists of three built-in functions that provide a secure environment for data access, by allowing access rules to compare against the intrinsic values assigned to users in a session. An application context consists of context_name, attribute_name, and attribute_value. Users define the context name, the attributes, and the values for each context. You can use the default read-only application context that Sybase provides, SYS_SESSION, to access some session-specific information. This application context is shown as Table 17-5 on page 545. You can also create your own application contexts, as described in Creating and using application contexts on page 540. The user profile, combined with the application profile, which is defined in a table created by the System Administrator, permits cumulative and overlapping security schemes. ACF allows users to define, store, and retrieve: User profiles (the roles authorized to a user and the groups to which the user belongs) Application profiles currently in use
Any number of application contexts per session are possible, and any context can define any number of attribute/value pairs. ACF context rows are specific to a session, and not persistent across sessions; however, unlike local variables, they are available across nested levels of statement execution. ACF provides built-in functions that set, get, list, and remove these context rows.
Setting permissions for using application context functions

You execute an application context function in a select statement. The owner of the function is the System Administrator of the server. You can create, set, retrieve, and remove application contexts using built-in functions. The data used in the built-in functions is defined in a table that contains all logins for all tables, which created by the System Administrator. For more information about this table, see Using login triggers on page 547.
538
CHAPTER 17
set_appcontext() stores:
select set_appcontext ("titles", "rlac", "1")
get_appcontext() supplies two parts of a context in a session, and retrieves
the third:
select get_appcontext ("titles", "rlac") -----------------------1
For more information on these functions and on list_appcontext and rm_appcontext, see Creating and using application contexts on page 540.
Granting and revoking
You can grant and revoke privileges to users, roles, and groups in a given database to access objects in that database. The only exceptions are create database, set session authorization, and connect. A user granted these privileges should be a valid user in the master database. To use other privileges, the user must be a valid user in the database where the object is located. The use of built-in functions means that unless special arrangements are made, any logged-in user can reset the profiles of the session. Although Adaptive Server audits built-in functions, security may be compromised before the problem is noticed. To restrict access to these built-in functions, use grant and revoke privileges. Only users with the sa_role can grant or revoke privileges on the built-in functions. Only the select privilege is checked as part of the server-enforced data access control checks performed by the functions.
Valid users
Built-in functions do not have an object ID and they do not have a home database. Therefore, each Database Owner must grant the select privilege for the functions to the appropriate user. Adaptive Server finds the users default database and checks the permissions against this database. With this approach, only the owner of the users default database needs to grant the select privilege. If other databases should be restricted, the owner of those databases must explicitly revoke permission from the user in those databases. Only the application context built-in functions perform data access control checks on the user when you grant and revoke privileges on them. Granting or revoking privileges for other functions has no effect in Adaptive Server. Privileges granted to public affect only users named in the table created by the System Administrator. For information about the table, see Using login triggers on page 547. Guest users have privileges only if the sa_role specifically grants it by adding them to the table. A System Administrator can execute the following commands to grant or revoke select privileges on specific application context functions:
539
grant select on set_appcontext to user_role grant select on set_appcontext to joe_user revoke select on set_appcontext from joe_user
Creating and using application contexts

The following built-in functions are available for creating and maintaining application contexts. For more information, see the Reference Manual.
set_appcontext get_appcontext list_appcontext rm_appcontext
set_appcontext
Sets an application context name, attribute name, and attribute value, defined by the attributes of an application, for a specified user session.
set_appcontext ("context_name", "attribute_name", "attribute_value")
context_name a row that specifies an application context name, saved as the datatype char(30). attribute_name a row that specifies an application context name, saved as the datatype char(30) attribute_value a row that specifies an application attribute value, saved as the datatype char(2048).
Examples
This example creates an application context called CONTEXT1, with an attribute ATTR1 that has the value VALUE1:
select set_appcontext ("CONTEXT1", "ATTR1", "VALUE1") --------------0
This example shows an attempt to override the existing application context. The attempt fails, returning -1:
select set_appcontext("CONTEXT1", "ATTR1", "VALUE1")
540
CHAPTER 17
--------------1
This example shows how set_appcontext can include a datatype conversion in the value:
declare@val numeric select @val = 20 select set_appcontext ("CONTEXT1", "ATTR2", convert(char(20), @val)) -----------0
This example shows the result when a user without appropriate permissions attempts to set the application context. The attempt fails, returning -1:
select set_appcontext("CONTEXT1", "ATTR2", "VALUE1") --------------1 Usage
set_appcontext returns 0 for success and -1 for failure.
If you set values that already exist in the current session, set_appcontext returns -1.
set_appcontext cannot override the values of an existing application context. To assign new values to a context, remove the context and recreate it using the new values. set_appcontext saves attributes as char datatypes. If you create an access rule that must compare the attribute value to another datatype, the rule should convert the char data to the appropriate datatype.
All arguments in this function are required.
get_appcontext
Returns the value of the attribute in a specified context.
get_appcontext ("context_name", "attribute_name")
context_name a row specifying an application context name, saved as datatype char(30). attribute_name a row specifying an application context attribute name, saved as datatype char(30).
541
Examples
This example shows VALUE1 returned for ATTR1:

select get_appcontext ("CONTEXT1", "ATTR1") ----------VALUE1
ATTR1 does not exist in CONTEXT2:

select get_appcontext("CONTEXT2", "ATTR1") -----------NULL
This example shows the result when a user without appropriate permissions attempts to get the application context:
select get_appcontext("CONTEXT1", "ATTR2") select permisssion denied on built-in get_appcontext, database dbid ----------1 Usage
get_appcontext returns 0 for success and -1 for failure.
If the attribute you require does not exist in the application context, get_appcontext returns null.
get_appcontext saves attributes as char datatypes. If you create an access
rule that compares the attribute value to other datatypes, the rule should convert the char data to the appropriate datatype. All arguments in this function are required.
list_appcontext
Lists all the attributes of all the contexts in the current session.
list_appcontext ("context_name")
context_name names all the application context attributes in the session. list_appcontext has a datatype of char(30).
Examples
To use list_appcontext, the user must have appropriate permissions. For more information, see Setting permissions for using application context functions on page 538.
542
CHAPTER 17
This example shows the results of a user with appropriate permissions listing the application contexts:
select list_appcontext ("*", "*") Context Name: (CONTEXT1) Attribute Name: (ATTR1) Value: (VALUE2) Context Name: (CONTEXT2) Attribute Name: (ATTR1) Value: (VALUE!) ----------0
This example shows a user without appropriate permissions attempting to list the application contexts. The attempt fails, returning -1.
select list_appcontext() Select permission denied on built-in list_appcontext, database DBID ---------1 Usage
list_appcontext returns 0 for success and -1 for failure.
Since built-in functions do not return multiple result sets, the client application receives list_appcontext returns as messages.
rm_appcontext
Removes a specific application context, or all application contexts.
rm_appcontext ("context_name", "attribute_name")
context_name a row specifying an application context name, saved as datatype char(30). attribute_name a row specifying an application context attribute name, saved as datatype char(30).
Examples
The following three examples show how to remove an application context by specifying some or all attributes. Use an asterisk ("*") to remove all attributes in the specified context.
select rm_appcontext("CONTEXT1", "*") --------0
543
Use an asterisk ("*") to remove all the contexts and attributes.

select rm_appcontext("*", "*") --------0
This example shows a user attemptimg to remove a nonexistent context. The attempt fails, returning -1.
select rm_appcontext("NON_EXISTING_CTX", "ATTR2") ---------1
This example shows the result of a user without appropriate permissions attempting to remove an application context.
select rm_appcontext("CONTEXT1", "ATTR2") ---------1 Usage
rm_appcontext returns 0 for success, -1 for failure.
All arguments in this function are required.
SYS_SESSION system application context

The SYS_SESSION context shows the default predefined application context, which provides session-specific pairs of attributes and values. The syntax for using the context is:
select list_appcontext ("SYS_SESSION", "*")
Then:
select get_appcontext ("SYS_SESSION", "<attribute>")
544
CHAPTER 17
Table 17-5: SYS_SESSION attributes and values Attribute

username hostname applname suserid groupid dbid dbname spid proxy_suserid client_name client_applname client_hostname language character_set dateformat is_showplan_on is_noexec_on
Value Login name Host name from which the client has connected Name of the application as set by the client User ID of the user in the current database Group ID of the user in the current database ID of the users current database Current database Server process ID The server user ID of the proxy Client name set by the middle-tier application, using the set client_name command Client application name set by the middle-tier application, using the set client_applname command Client host name set by the middle-tier application, using the set client_hostname command Current language the client is using by default or after using the set language command (@@language) Character set the client is using (@@client_csname) Date expected by the client, set using the set dateformat command Returns YES if set showplan is on, NO if it is off Returns YES if set no exec is on, NO if it is off
Solving a problem using an access rule and ACF

This section shows the solution of a problem: each of five users, on different security levels, should see only rows with a value less than or equal to his or her security level. This solution uses access rules, with the Application Context Facility, to display only the rows that one of the users, Dave, sees. There are five logins: Anne has security level 1. Bob has security level 1. Cassie has security level 2. Dave has security level 2.
545
Ellie has security level 4.
Users should see only rows with a value in rlac that is less than or equal to their own security level. To accomplish this, create an access rule and apply ACF. The rlac column is type integer, and appcontext arguments are type char.
create access rule rlac_rule as @value <= convert(int, get_appcontext("titles", "rlac")) sp_bindrule rlac_rule, "titles.rlac" /* log in as Dave and apply ACF value of 2*/ select set_appcontext("titles", "rlac", "2") /*this value persists throughout the session*/ /*select all rows*/ select title_id, rlac from titles --------------------title_id PC8888 BU1032 PS7777 PS3333 BU1111 PC1035 BU2075 PS2091 PS2106 BU7832 PS1372 rlac 1 2 1 1 2 1 2 1 1 2 1
(11 rows affected)
546
CHAPTER 17
Using login triggers

Note Some of the information in this section is from the article Login
Triggers in ASE 12.5. Copyright 19982002, Rob Verschoor/ Sypron B.V., at

http://www.sypron.nl/logtrig.html.
Login triggers execute a specified stored procedure every time a user logs in. The login trigger is an ordinary stored procedure, except it executes in the background. It is the last step in a successful login process, and sets the application context for the user logging in. Only the System Security Officer can register a login trigger to users in the server. To provide a secure environment, the System Administrator must: 1 Revoke select privilege on the set_appcontext function. The owner of a login trigger must have explicit permission to use set_appcontext, even if the owner has sa_role. Configure a login trigger from a stored procedure for each user, and register the login trigger to the user. Provide execute privilege to the login trigger that the user executes.
2 3
Creating login triggers

Create a login trigger as a stored procedure. Do not use the create trigger command. The following sample creates a login trigger stored procedure in the pubs2 database:
create loginproc as declare @appname varchar(20) declare @attr varchar(20) declare @value varchar(20) declare @retvalue int declare apctx cursor for select appname, attr, value from pubs2.dbo.lookup where login = suser_name() open apctx fetch apctx into @appname, @attr, @value While (@@sqlstatus = 0) begin select f@retval = set_appcontext (rtrim (@appname),
547
rtrim(@attr), rtrim(@value)) fetch apctx into @appname, @attr, @value end go grant execute on loginproc to public go
To associate a specific user with the login trigger, run sp_modifylogin in the users default database.
Configuring login triggers

You must have sso_role enabled to set, change, or drop a login trigger. The object ID of the login trigger is stored in the syslogins.procid column. Login triggers do not exist by default. They must be registered using sp_modifylogin. The syntax is:
sp_modifylogin <login_name>, "login script", <sproc_name >
login_name the users login name.

"login script" type in as shown; login script tells sp_modifylogin that the next parameter, sproc_name, is a login trigger.
sproc_name the name of the stored procedure configured as a login trigger for this user.
Run this procedure from the users default database. The stored procedure you are registering as a login trigger must be available in the users default database, because Adaptive Server searches the sysobjects table in the users default database to find the login trigger object.
Configuring the login trigger
The following example configures the stored procedure my_proc (which must exist in the database you want to configure) as a login trigger for Adaptive Server login my_login:
sp_modifylogin my_login, "login script", my_proc
Again, you must execute the command from within the users default database. Adaptive Server checks to see whether the login has execute permissions on the stored procedure, but not until the user actually logs in and executes the login trigger.
Dropping and changing the login trigger
Once you have configured a stored procedure as a login trigger, you cannot drop it. You must unconfigure it first, either by dropping the login trigger altogether, or by changing the login trigger to a different stored procedure. To drop the login trigger, enter:
548
CHAPTER 17
sp_modifylogin my_login, "login script", NULL
To change the login trigger to a different stored procedure, enter:

sp_modifylogin my_login, "login script", diff_proc Displaying the login trigger
To display the current login trigger, use sp_displaylogin:

sp_displaylogin my_login go (....) Default Database: my_db Default Language: Auto Login Script: my_proc ....
Executing a login trigger

Login triggers are different from ordinary stored procedures in that once they are registered they execute in the background, without active user connections. Once you have configured a login trigger, Adaptive Server automatically executes it in the background as soon as the user logs in, but before the server executes any commands from the client application. If one login makes multiple concurrent connections, the login trigger executes independently during each session. Similarly, multiple logins can configure the same stored procedure to be a login trigger. Background execution means that you cannot use some standard features of stored procedures in a stored procedure configured as a login trigger. For instance, you cannot pass any parameters without default values to or from the procedure, nor does the procedure pass back any result values. This special execution mode affects any stored procedures that are called by the login trigger stored procedure, as well as any output generated by the login trigger stored procedure itself. You can also execute a login trigger stored procedure as a normal stored procedure, for example, from isql. The procedure executes and behaves normally, showing all output and error messages as usual.
Understanding login trigger output

The main effect of executing the stored procedure as a background task is that output from the login trigger is not written to the client application, but to the Adaptive Server error log file, as are some, but not all, error messages.
549
Output from print or raiserror messages is prefixed by the words background task message or background task error in the error log. For example, the statements print Hello! and raiserror 123456 in a login trigger appear in the Adaptive Server error log as:
(....) background task message: Hello! (....) background task error 123456: This is test message 123456
However, not all output goes to the Adaptive Server error log: No result sets from select statements (which are normally sent to a client connection) appear anywhere, not even in the Adaptive Server error log. This information disappears. The following statements execute normally: insert...select and select...into statements, as well as other DML statements which do not ordinarily send a result set to the client application, and DDL statements ordinarily allowed in a stored procedure.
Using login triggers for other applications

Login triggers are part of the row-level access control feature in Adaptive Server. In this context, you can use a login trigger in combination with the features for access rules and application contexts to set up row-level access controls, once a session logs in to Adaptive Server. However, you can use login triggers for other purposes as well.
Limiting the number of concurrent connections
The following example limits the number of concurrent connections to Adaptive Server that a specific login can make. Each of the commands described in steps 1 and 2 in the example are executed in the default database of the user for whom the access needs to be restricted: 1 As System Administrator, create the limit_user_sessions stored procedure:
create procedure limit_user_sessions as declare @cnt int, @limit int, @loginname varchar(32) select @limit = 2 -- max nr. of concurrent logins /* determine current #sessions */ select @cnt = count(*) from master.dbo.sysprocesses where suid = suser_id()
550
CHAPTER 17
/* check the limit */ if @cnt > @limit begin select @loginname = suser_name() print "Aborting login [%1!]: exceeds session limit [%2!]", @loginname, @limit /* abort this session */ select syb_quit() end go grant exec on limit_user_sessions to public go
As System Security Officer, configure this stored procedure as a login trigger for user bob:
sp_modifylogin "bob", "login script", "limit_user_sessions" go
Now, when user bob creates a third session for Adaptive Server, this session is terminated by the login trigger calling the syb_quit() function:
% isql -SASE125 -Ubob -Pbobpassword 1> select 1 2> go CT-LIBRARY error: ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect
This message appears in the Adaptive Server error log file:

(...) background task message: Aborting login [ my_login]: exceeds session limit [2]
Enforcing timed-based restrictions
This example describes how System Administrators can create a login trigger to enforce time-based restrictions on user sessions. Each of the commands described in steps 1 4 are executed in the default database of the user for whom the access needs to be restricted: 1 As System Administraor, create this table:
create table access_times ( suid int not null,
551
dayofweek tinyint, shiftstart time, shiftend time)
As System Administrator, insert the following rows in table access_times. These rows indicate that user bob is allowed to log into Adaptive Server on Mondays between 9:00am and 5:00pm, and user mark is allowed to login to Adaptive Server on Tuesdays between 9:00Am and 5:00PM
insert select go insert select go into access_times suser_id(bob), 1, 9:00, 17:00 into access_times suser_id(mark), 2, 9:00, 17:00
As System Administrator, create the limit_access_time stored procedure, which references the access_time table to determine if login access should be granted:
create procedure limit_access_time as declare @curdate date, @curdow tinyint, @curtime time, @cnt int, @loginname varchar(32) -- setup variables for current day-of-week, time select @curdate = current_date() select @curdow = datepart(cdw,@curdate) select @curtime = current_time() select @cnt = 0 -- determine if current user is allowed access select @cnt = count(*) from access_times where suid = suser_id() and dayofweek = @curdow and @curtime between shiftstart and shiftend if @cnt = 0 begin select @loginname = suser_name() print "Aborting login [%1!]: login attempt past normal working hours", @loginname -- abort this session return -4
552
CHAPTER 17
end go grant exec on limit_access_time to public go
As System Security Officer, configure the limit_access_time stored procedure as a login trigger for users bob and mark:
sp_modifylogin "bob", "login script", "limit_access_time" go sp_modifylogin "mark", "login script", "limit_access_time" go
On Mondays, user bob can successfully create a session:

isql -Ubob -Ppassword 1> select 1 2> go ----------1 (1 row affected)
However, user mark is denied access to Adpative Server:

isql -Umark -Ppassword 1> select 1 2> go CT-LIBRARY error: ct_results(): network packet layer: internal net library error: Net-Library operation terminated due to disconnect
The following message is logged in the errorlog:

(...) server back-ground task message: Aborting login [mark]: login attempt past normal working hours
The above examples show how you can limit the number of concurrent connections for a specific login and restrict access to specific times of day for that login, but it has one disadvantage: the client application cannot easily detect the reason the session was terminated. To display a message to the user, such as Too many users right nowplease try later, use a different approach. Instead of calling the built-in function syb_quit(), which causes the server to simply terminate the current session, you can deliberately cause an error in the stored procedure to abort the login trigger stored procedure.
553
For example, dividing by zero aborts the login trigger stored procedure, terminates the session, and causes a message to appear.
Login trigger restrictions

The following actions are restricted. You cannot use a login trigger to set session-specific options, such as set nocount on, set rowcount on, and so on. Setting session options in any stored procedure has an effect only inside that stored procedure. You cannot create #temp tables to use later in the session. Once the procedure completes, the #temp tables drop away automatically and the original session settings are restored, as in any other stored procedure. You should not use login triggers on the sa login; a failing login trigger can lock you out of Adaptive Server. Do not use a login trigger for anything that may take longer than a few seconds to process, or that risks processing problems.
Issues and information

If you do not have access to the Adaptive Server error log, do not use login triggers. Always check the Adaptive Server error log for error messages. A client application, like isql, is unaware of the existence or execution of a login trigger; it presents a command prompt immediately after the successful login, though Adaptive Server does not execute any commands before the login trigger successfully executes. This isql prompt displays even if the login trigger has terminated the user connection. The user logging in to Adaptive Server must have execute permission to use the login trigger stored procedure. If no execute permission has been granted, an error message appears in the Adaptive Server error log and the user connection closes immediately (though isql still shows a command prompt). Adaptive Server error log shows a message similar to the following:
EXECUTE permission denied on object my_proc, database my_db, owner dbo
The login trigger stored procedure cannot contain parameters without specified default values. If parameters without default values appear in the stored procedure, the login trigger fails and an error similar to the following appears in the Adaptive Server error log:
554
CHAPTER 17
Procedure my_proc expects parameter @param1, which was not supplied...
Disabling execute privilege on login triggers

A Database Owner or administrator can disable execute privilege on the login trigger, or code the login trigger to permit access only at certain times. For example, you may want to prohibit regular users from using the server while the Database Owner or administrator is updating the table.
Note If the login trigger returns a minus number, the login fails.
Acquiring the permissions of another user

Adaptive Server provides two ways to acquire another users identity and permissions status: A Database Owner can use the setuser command to impersonate another users identity and permissions status in the current database. See Using setuser on page 555. proxy authorization allows one user to assume the identity of another user on a server-wide basis. See Using proxy authorization on page 556.
Using setuser
A Database Owner may use setuser to: Access an object owned by another user Grant permissions on an object owned by another user Create an object that will be owned by another user Temporarily assume the DAC permissions of another user for some other reason
While the setuser command enables the Database Owner to automatically acquire another users DAC permissions, the command does not affect the roles that have been granted.
555
setuser permission defaults to the Database Owner and cannot be transferred.
The user being impersonated must be an authorized user of the database. Adaptive Server checks the permissions of the user being impersonated. System Administrators can use setuser to create objects that will be owned by another user. However, System Administrators operate outside the DAC permissions system; therefore, they need not use setuser to acquire another users permissions. The setuser command remains in effect until another setuser command is given, the current database is changed, or the user logs off. The syntax is:
setuser ["user_name"]
where user_name is a valid user in the database that is to be impersonated. To reestablish your original identity, use setuser with no value for user_name. This example shows how the Database Owner would grant Joe permission to read the authors table, which is owned by Mary:
setuser "mary" grant select on authors to joe setuser /*reestablishes original identity*/
Using proxy authorization

With the proxy authorization capability of Adaptive Server, System Security Officers can grant selected logins the ability to assume the security context of another user, and an application can perform tasks in a controlled manner on behalf of different users. If a login has permission to use proxy authorization, the login can impersonate any other login in Adaptive Server.
Warning! The ability to assume another users identity is extremely powerful and should be limited to trusted administrators and applications. grant set proxy ... restricted role can be used to restrict which roles users cannot acquire when switching identities.
556
CHAPTER 17
A user executing set proxy or set session authorization operates with both the login name and server user ID of the user being impersonated. The login name is stored in the name column of master..syslogins and the server user ID is stored in the suid column of master..syslogins. These values are active across the entire server in all databases.
Note set proxy and set session authorization are identical in function and can be used interchangeably. The only difference between them is that set session authorization is ANSI-SQL92-compatible, and set proxy is a Transact-SQL
extension.
Using set proxy to restrict roles

You can grant set proxy...restricted role, which allows you to restrict which roles cannot be acquired when switching identities. The syntax for set proxy is:
grant set proxy to user | role [restricted role user_list | role_list | all | system]
where: user_or_role_list list of roles you are restricting for the target login. Both the grantee and target login must have all roles on this list or the command fails. all ensures that all roles belonging to the grantee are granted to the target login. system ensures the grantee has the same set of system roles as the target login.
For example, this grants set proxy to user joe but restricts him from switching identities to any user with the sa, sso, or admin roles (however, if he already has these roles, he can set proxy for any user with these roles):
grant set proxy to joe restricted role sa_role, sso_role, admin_role
When joe tries to switch his identity to a user with admin_role (in this example, Our_admin_role), the command fails unless he already has admin_role:
set proxy Our_admin_role Msg 10368, Level 14, State 1: Server 's', Line 2:Set session authorization permission
557
denied because the target login has a role that you do not have and you have been restricted from using.
After joe is granted the admin_role and retries the command, it succeeds:
grant role admin_role to joe set proxy Our_admin_role
For more information about the set proxy command, see the Reference Manual: Commands.
Executing proxy authorization

Follow these rules when you execute set proxy or set session authorization: You cannot execute set proxy or set session authorization from within a transaction. You cannot use a locked login for the proxy of another user. For example, if joseph is a locked login, the following command is not allowed:
set proxy "joseph"
You can execute set proxy or set session authorization from any database you are allowed to use. However, the login_name you specify must be a valid user in the database, or the database must have a guest user defined for it. Only one level is permitted; to impersonate more than one user, you must return to your original identity between impersonations. If you execute set proxy or set session authorization from within a procedure, your original identity is automatically resumed when you exit the procedure.
If you have a login that has been granted permission to use set proxy or set session authorization, you can set proxy to impersonate another user. The following is the syntax, where login_name is the name of a valid login in
master..syslogins:
set proxy login_name
or
set session authorization login_name
Enclose the login name in quotation marks. For example, to set proxy to mary, execute:
set proxy "mary"
558
CHAPTER 17
After setting proxy, check your login name in the server and your user name in the database. For example, assume that your login is ralph and that you have been granted set proxy authorization. You want to execute some commands as sallyn and as rudolph in pubs2 database. sallyn has a valid name (sally) in the database, but Ralph and Rudolph do not. However, pubs2 has a guest user defined. You can execute:
set proxy "sallyn" go use pubs2 go select suser_name(), user_name() go ------------------------------ ------------------sallyn sally
To change to Rudolph, you must first change back to your own identity. To do so, execute:
set proxy "ralph" select suser_name(), user_name() go ------------------------------ -------------------ralph guest
Notice that Ralph is a guest in the database. Then execute:

set proxy "rudolph" go select suser_name(), user_name() go ------------------------------ -------------------rudolph guest
Rudolph is also a guest in the database because Rudolph is not a valid user in the database. Now, impersonate the sa account. Execute:
set proxy "ralph" go set proxy "sa" go select suser_name(), user_name() go --------------------------- -------------------sa dbo
559
Reporting on permissions
Proxy authorization for applications

Figure 17-1 shows an application server logging in to Adaptive Server with the generic login appl to execute procedures and commands for several users. While appl impersonates Tom, the application has Toms permissions. Likewise, when appl impersonates Sue and John, the application has only Sues and Johns permissions, respectively.
Figure 17-1: Applications and proxy authorization
Tom, Sue, and John establish sessions with the Application Server: Tom Sue John Application Server logs in as appl with set proxy permission.
The application server (appl) on Adaptive Server executes: set proxy "tom" (SQL command for Tom) set proxy "sue" (SQL command for Sue) set proxy "John" (SQL command for John)
Application Server
Adaptive Server
Table 17-6 lists the system procedures for reporting information about proxies, object creation, and object access permissions:
560
CHAPTER 17
Table 17-6: System procedures for reporting on permissions To report information on Proxies Users and processes Permissions on database objects or users Permissions on specific tables Permissions on specific columns in a table Use system tables
sp_who sp_helprotect sp_table_privileges sp_column_privileges
Querying the sysprotects table for proxy authorization

To display information about permissions that have been granted toor revoked fromusers, groups, and roles, query the sysprotects table. The action column specifies the permission. For example, the action value for set proxy or set session authorization is equal to 167. You might execute this query:
select * from sysprotects where action = 167
The results provide the user ID of the user who granted or revoked the permission (column grantor), the user ID of the user who has the permission (column uid), and the type of protection (column protecttype). The protecttype column can contain these values: 0 for grant with grant 1 for grant 2 for revoke
For more information about the sysprotects table, see the Reference Manual.
Displaying information about users and processes

sp_who displays information about all current Adaptive Server users and processes or about a particular user or process. The results of sp_who include the loginame and origname. If a user is operating under a proxy, origname
contains the name of the original login. For example, assume that ralph executes the following, then executes some SQL commands:
set proxy susie
sp_who returns susie for loginame and ralph for origname.
561
sp_who queries the master..sysprocesses system table, which contains columns for the server user ID (suid) and the original server user ID (origsuid).
For more information, see sp_who in the Reference Manual.
Reporting permissions on database objects or users

Use sp_helprotect to report on permissions by database object or by user, and (optionally) by user for a specified object. Any user can execute this procedure. The syntax is:
sp_helprotect [name [, username [, "grant" [,"none"|"granted"|"enabled"|role_name]]]]]
where: name is either the name of the table, view, or stored procedure, or the name of a user, group, or role in the current database. If you do not provide a name, sp_helprotect reports on all permissions in the database. username is a users name in the current database. If you specify username, only that users permissions on the specified object are reported. If name is not an object, sp_helprotect checks whether name is a user, group, or role and if it is, lists the permissions for the user, group, or role. If you specify the keyword grant, and name is not an object, sp_helprotect displays all permissions granted by with grant option.
grant displays the permissions granted to name with grant option. none ignores roles granted to the user. granted includes information on all roles granted to the user. enabled includes information on all roles activated by the user.
role_name displays permission information for the specified role only, regardless of whether this role has been granted to the user.
For example, suppose you issue the following series of grant and revoke statements:
grant select on titles to judy grant update on titles to judy revoke update on titles(contract) from judy grant select on publishers to judy with grant option
562
CHAPTER 17
To determine the permissions Judy now has on each column in the titles table, enter:
grantor ------dbo dbo dbo dbo dbo dbo dbo dbo dbo dbo grantee type ------ ----judy Grant judy Grant judy Grant judy Grant judy Grant judy Grant judy Grant judy Grant judy Grant judy Grant sp_helprotect titles, judy action object column ---------------Select titles All Update titles advance Update titles notes Update titles price Update titles pub_id Update titles pubdate Update titles title Update titles title_id Update titles total_sales Update titles type grantable ------FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE
The first row shows that the Database Owner (dbo) gave Judy permission to select all columns of the titles table. The rest of the lines indicate that she can update only the columns listed in the display. Judy cannot give select or update permissions to any other user. To see Judys permissions on the publishers table, enter:
sp_helprotect publishers, judy
In this display, the grantable column indicates TRUE, meaning that Judy can grant the permission to other users.
grantor grantee type ------- ------ ----dbo judy Grant action -----Select object -----publishers column -----all grantable ------TRUE
Reporting permissions on specific tables

Use sp_table_privileges to return permissions information about a specified table. The syntax is:
sp_table_privileges table_name [, table_owner [, table_qualifier]]
where: table_name is the name of the table, and is required.
563
table_owner can be used to specify the name of the table owner, if it is not dbo or the user executing sp_table_privileges. table_qualifier is the name of the current database.
Use null for parameters that you want to skip. For example, this statement returns information about all permissions granted on the titles table:
sp_table_privileges titles
For more information about the output of sp_table_privileges, see the Reference Manual.
Reporting permissions on specific columns

Use sp_column_privileges to return information about permissions on columns in a table. The syntax is:
sp_column_privileges table_name [, table_owner [, table_qualifier [, column_name]]]
where: table_name is the name of the table. table_owner can be used to specify the name of the table owner, if it is not dbo or the user executing sp_column_privileges. table_qualifier is the name of the current database. column_name is the name of the column on which you want to see permissions information.
Use null for parameters that you want to skip. For example, this statement returns information about the pub_id column of the publishers table:
sp_column_privileges publishers, null, null, pub_id
For more information about the output of sp_column_privileges, see the Reference Manual.
564
CHAPTER 17
Using views and stored procedures as security mechanisms

Views and stored procedures can serve as security mechanisms. You can give users controlled access to database objects via a view or stored procedure without granting them direct access to the data. For example, you might give a clerk execute permission on a procedure that updates cost information in a projects table without letting the user see confidential data in the table. To use this feature, you must own the procedure or view as well as its underlying objects. If you do not own the underlying objects, users must have permission to access the objects. For more information about when permissions are required, see Understanding ownership chains on page 568. Adaptive Server makes permission checks, as required, when the view or procedure is used. When you create the view or procedure, Adaptive Server makes no permission checks on the underlying objects.
Using views as security mechanisms

Through a view, users can query and modify only the data they can see. The rest of the database is neither visible nor accessible. Permission to access the view must be explicitly granted or revoked, regardless of the permissions on the views underlying tables. If the view and underlying tables are owned by the same owner, no permissions need to be given to the underlying tables. Data in an underlying table that is not included in the view is hidden from users who are authorized to access the view but not the underlying table. By defining different views and selectively granting permissions on them, a user (or any combination of users) can be restricted to different subsets of data. Access can be restricted to: A subset of the rows of a base table (a value-dependent subset). For example, you might define a view that contains only the rows for business and psychology books to keep information about other types of books hidden from some users. A subset of the columns of a base table (a value-independent subset). For example, you might define a view that contains all the rows of the titles table, but omits the price and advance columns, since this information is sensitive. A row-and-column subset of a base table.
565
The rows that qualify for a join of more than one base table. For example, you might define a view that joins the titles, authors, and titleauthor tables. This view hides personal data about authors and financial information about the books. A statistical summary of data in a base table. For example, you might define a view that contains only the average price of each type of book. A subset of another view, or of some combination of views and base tables.
Lets say you want to prevent some users from accessing the columns in the titles table that display money and sales amounts. You can create a view of the titles table that omits those columns, and then give all users permission on the view but only the Sales Department permission on the table:
grant all on bookview to public grant all on titles to sales
An equivalent way of setting up these privilege conditions, without using a view, is to use the following statements:
grant all on titles to public revoke select, update on titles (price, advance, total_sales) from public grant select, update on titles (price, advance, total_sales) to sales
One possible problem with the second solution is that users not in the sales group who enter the select * from titles command might be surprised to see the message that includes the phrase:
permission denied
Adaptive Server expands the asterisk into a list of all the columns in the titles table, and since permission on some of these columns has been revoked from nonsales users, access to these columns is denied. The error message lists the columns for which the user does not have access. To see all the columns for which they do have permission, the nonsales users must name them explicitly. For this reason, creating a view and granting the appropriate permissions on it is a better solution. You can also use views for context-sensitive protection. For example, you can create a view that gives a data entry clerk permission to access only those rows that he or she has added or updated. To do so, add a column to a table in which the user ID of the user entering each row is automatically recorded with a default. You can define this default in the create table statement, like this:
566
CHAPTER 17
create table testtable (empid int, startdate datetime, username varchar(30) default user)
Next, define a view that includes all the rows of the table where uid is the current user:
create view context_view as select * from testtable where username = user_name() with check option
The rows retrievable through this view depend on the identity of the person who issues the select command against the view. By adding with check option to the view definition, you make it impossible for any data entry clerk to falsify the information in the username column.
Using stored procedures as security mechanisms

If a stored procedure and all underlying objects are owned by the same user, that owner can grant users permission to use the procedure without granting permissions on the underlying objects. For example, you might give a user permission to execute a stored procedure that updates a row-and-column subset of a specified table, even though that user does not have any other permissions on that table.
Roles and stored procedures

Use the grant execute command to grant execute permission on a stored procedure to all users who have been granted a specified role. revoke execute removes this permission. But grant execute permission does not prevent users who do not have the specified role from being granted execute permission on the stored procedure.
567
For further security, you can restrict the use of a stored procedure by using the proc_role system function within the procedure to guarantee that a procedure can be executed only by users who have a given role. proc_role returns 1 if the user has a specific role (sa_role, sso_role, oper_role, or any user-defined role) and returns 0 if the user does not have that role. For example, here is a procedure that uses proc_role to see if the user has the System Administrator role:
create proc test_proc as if (proc_role("sa_role") = 0) begin print "You dont have the right role" return -1 end else print "You have SA role" return 0
See System Functions in the Reference Manual for more information about proc_role.
Understanding ownership chains

Views can depend on other views or tables. Procedures can depend on other procedures, views, or tables. These dependencies can be thought of as an ownership chain. Typically, the owner of a view also owns its underlying objects (other views and tables), and the owner of a stored procedure owns all the procedures, tables, and views referenced by the procedure. A view and its underlying objects are usually all in the same database, as are a stored procedure and all the objects it references; however, this is not required. If objects are in different databases, a user wanting to use the view or stored procedure must be a valid user or guest user in all of the databases containing the objects. This prevents users from accessing a database unless the Database Owner has authorized it. When a user who has been granted execute permission on a procedure or view uses it, Adaptive Server does not check permissions on any of the underlying objects if: These objects and the view or procedure are owned by the same user, and
568
CHAPTER 17
The user accessing the view or procedure is a valid user or guest user in each of the databases containing the underlying objects.
However, if all objects are not owned by the same user, Adaptive Server checks object permissions when the ownership chain is broken. That is, if object A references object B, and B is not owned by the user who owns object A, Adaptive Server checks the permissions for object B. In this way, Adaptive Server allows the owner of the original data to retain control over who is authorized to access it. Ordinarily, a user who creates a view needs worry only about granting permissions on that view. For example, say Mary has created a view called auview1 on the authors table, which she also owns. If Mary grants select permission to Sue on auview1, Adaptive Server allows Sue to access it without checking permissions on authors. However, a user who creates a view or stored procedure that depends on an object owned by another user must be aware that any permissions he or she grants depend on the permissions allowed by those other owners.
Example of views and ownership chains

Say Joe creates a view called auview2, which depends on Marys view auview1. Joe grants Sue select permission on auview2.
Figure 17-2: Ownership chains and permission checking for views, case 1
Sues permission select
Objects auview2
Ownership Joe
Checks Sue not owner Check permissions
select
auview1
Mary
Different owner Check permissions
none
authors
Mary
Same owner No permission check
Adaptive Server checks the permissions on auview2 and auview1, and finds that Sue can use them. Adaptive Server checks ownership on auview1 and authors and finds that they have the same owner. Therefore, Sue can use auview2.
569
Taking this example a step further, suppose that Joes view, auview2, depends on auview1, which depends on authors. Mary decides she likes Joes auview2 and creates auview3 on top of it. Both auview1 and authors are owned by Mary. The ownership chain looks like this:
Figure 17-3: Ownership chains and permission checking for views, case 2
Sues permission select
Objects auview3
Ownership Mary
select
auview2
Joe
select
auview1
Mary
none
authors
Mary
When Sue tries to access auview3, Adaptive Server checks permissions on auview3, auview2, and auview1. If Joe has granted permission to Sue on auview2, and Mary has granted her permission on auview3 and auview1, Adaptive Server allows the access. Adaptive Server checks permissions only if the object immediately before it in the chain has a different owner (or if it is the first object in the chain). For example, it checks auview2 because the object before itauview3is owned by a different user. It does not check permission on authors, because the object that immediately depends on it, auview1, is owned by the same user.
Example of procedures and ownership chains

Procedures follow the same rules as views. For example, suppose the ownership chain looks like this:
570
CHAPTER 17
Figure 17-4: Ownership chains and permission checking for stored procedures
Sues permission execute
Objects proc4
Ownership Mary
none
proc3
Mary
Same owner No permissions check
execute
proc2
Joe
execute
proc1
Mary
none
authors
Mary
To execute proc4, Sue must have permission to execute proc4, proc2, and proc1. Permission to execute proc3 is not necessary because proc3 and proc4 have the same owner. Adaptive Server checks Sues permissions on proc4 and all objects it references each time she executes proc4. Adaptive Server knows which referenced objects to check: it determined this the first time Sue executed proc4, and it saved the information with the procedures execution plan. Unless one of the objects referenced by the procedure is dropped or redefined, Adaptive Server does not change its initial decision about which objects to check. This protection hierarchy allows every objects owner to fully control access to the object. Owners can control access to views and stored procedures, as well as to tables.
571
Permissions on triggers
A trigger is a special kind of stored procedure used to enforce integrity, especially referential integrity. Triggers are never executed directly, but only as a side effect of modifying a table. You cannot grant or revoke permissions for triggers. Only an object owner can create a trigger. However, the ownership chain can be broken if a trigger on a table references objects owned by different users. The protection hierarchy rules that apply to procedures also apply to triggers. While the objects that a trigger affects are usually owned by the user who owns the trigger, you can write a trigger that modifies an object owned by another user. If this is the case, any users modifying your object in a way that activates the trigger must have permission on the other object as well. If Adaptive Server denies permission on a data modification command because a trigger affects an object for which the user does not have permission, the entire data modification transaction is rolled back. For more information on triggers, see the Transact-SQL Users Guide or the Reference Manual.
572
CH A PTE R
1 8
Auditing
This chapter describes how to set up auditing for your installation.

Topic Introduction to auditing in Adaptive Server Installing and setting up auditing Setting global auditing options Querying the audit trail Understanding the audit tables Page 573 578 594 603 603
Introduction to auditing in Adaptive Server

A principal element of a secure system is accountability. One way to ensure accountability is to audit events on the system. Many events that occur in Adaptive Server can be recorded. Auditing is an important part of security in a database management system. An audit trail can be used to detect penetration of the system and misuse of resources. By examining the audit trail, a System Security Officer can inspect patterns of access to objects in databases and can monitor the activity of specific users. Audit records are traceable to specific users, which may act as a deterrent to users who are misusing the system. Each audit record can log the nature of the event, the date and time, the user responsible for it, and the success or failure of the event. Among the events that can be audited are logins and logouts, server boots, use of data access commands, attempts to access particular objects, and a particular users actions. The audit trail, or log of audit records, allows the System Security Officer to reconstruct events that have occurred on the system and evaluate their impact. The System Security Officer is the only user who can start and stop auditing, set up auditing options, and process the audit data. As a System Security Officer, you can establish auditing for events such as:
573
Server-wide, security-relevant events Creating, deleting, and modifying database objects All actions by a particular user or all actions by users with a particular role active Granting or revoking database access Importing or exporting data Logins and logouts
Correlating Adaptive Server and operating system audit records

The easiest way to link Adaptive Server audit records with operating system records is to make Adaptive Server login names the same as operating system login names. Alternatively, the System Security Officer can map users operating system login names to their Adaptive Server login names. However, this approach requires ongoing maintenance, as login names for new users must be recorded manually.
The audit system

The audit system consists of: The sybsecurity database, which contains global auditing options and the audit trail The in-memory audit queue, to which audit records are sent before they are written to the audit trail Configuration parameters for managing auditing System procedures for managing auditing
The sybsecurity database

The sybsecurity database is created during the auditing installation process. In addition to all the system tables found in the model database, it contains sysauditoptions, a system table for keeping track of server-wide auditing options, and system tables for the audit trail.
574
CHAPTER 18
Auditing
sysauditoptions contains the current setting of global auditing options, such as whether auditing is enabled for disk commands, remote procedure calls, ad hoc user-defined auditing records, or all security-relevant events. These options affect the entire Adaptive Server.
The audit trail
Adaptive Server stores the audit trail in system tables named sysaudits_01 through sysaudits_08. When you install auditing, you determine the number of audit tables for your installation. For example, if you choose to have two audit tables, they are named sysaudits_01 and sysaudits_02. At any given time, only one audit table is current. Adaptive Server writes all audit data to the current audit table. A System Security Officer can use sp_configure to set, or change, which audit table is current. The recommended number of tables is two or more with each table on a separate audit device. This allows you to set up a smoothly running auditing process in which audit tables are archived and processed with no loss of audit records and no manual intervention.
Warning! Sybase strongly recommends against using a single audit table on production systems. If you use only a single audit table, you may lose audit records. If you must use only a single audit table because of limited system resources, see Single-table auditing on page 590 for instructions.
Figure 18-1 shows how the auditing process works with multiple audit tables.
575
Figure 18-1: Auditing with multiple audit tables
User processes
Audit queue
Audit process
pool of empty audit tables currently active audit tables
pool of full audit tables Archive
database on another device (then normal dump and load) The auditing system writes audit records from the in-memory audit queue to the current audit table. When the current audit table is nearly full, a threshold procedure can automatically archive the table to another database. The archive database can be backed up and restored with the dump and load commands. For more information about managing the audit trail, see Setting up audit trail management on page 582.
The audit queue

When an audited event occurs, an audit record first goes to the in-memory audit queue. The record remains in memory until the audit process writes it to the audit trail. You can configure the size of the audit queue with the audit queue size parameter of sp_configure.
576
CHAPTER 18
Auditing
Before you configure the size of the audit queue, consider the trade-off between the risk of losing records in the queue if the system crashes and the loss of performance when the queue is full. As long as an audit record is in the queue, it can be lost if the system crashes. However, if the queue repeatedly becomes full, overall system performance is affected. If the audit queue is full when a user process tries to generate an audit record, the process sleeps until space in the queue becomes available.
Note Because audit records are not written directly to the audit trail, you
cannot count on an audit records being stored immediately in the current audit table.
Auditing configuration parameters

Use these configuration parameters to manage the auditing process:
auditing enables or disables auditing for the entire Adaptive Server. The parameter takes effect immediately upon execution of sp_configure. Auditing occurs only when this parameter is enabled. audit queue size establishes the size of the audit queue. Because the
parameter affects memory allocation, the parameter does not take effect until Adaptive Server is restarted.
suspend audit when device full controls the behavior of the audit process when an audit device becomes full. The parameter takes effect immediately upon execution of sp_configure. current audit table sets the current audit table. The parameter takes effect immediately upon execution of sp_configure.
System procedures for auditing

Use these system procedures to manage the auditing process:
sp_audit enables and disables auditing options. This is the only system procedure required to establish the events to be audited. sp_displayaudit displays the active auditing options. sp_addauditrecord adds user-defined audit records (comments) into the
audit trail. Users can add these records only if a System Security Officer enables ad hoc auditing with sp_audit.
577
Installing and setting up auditing

Table 18-1 provides a general procedure for setting up auditing.
Table 18-1: General procedure for auditing Action 1. Install auditing. Description Set the number of audit tables and assign devices for the audit trail and the syslogs transaction log in the sybsecurity database. See Installing the audit system on page 578 and the Adaptive Server installation and configuration documentation Setting up audit trail management on page 582 For single-table auditing, Single-table auditing on page 590 Setting up transaction log management on page 588
2. Set up audit trail management.
Write and establish a threshold procedure that receives control when the current audit table is nearly full. The procedure automatically switches to a new audit table and archives the contents of the current table. In addition, this step involves setting the audit queue size and the suspend audit when device full configuration parameters.
3. Set up transaction log management in the sybsecurity database. 4. Set auditing options. 5. Enable auditing.
Determine how to handle the syslogs transaction log in the sybsecurity database, how to set the trunc log on chkpt database option and establishing a last-chance threshold procedure for syslogs if trunc log on chkpt is off. Use sp_audit to establish the events to be audited. Use sp_configure to turn on the auditing configuration parameter. Adaptive Server begins writing audit records to the current audit table. Use sp_audit restart to restart auditing if it fails.
Setting global auditing options on page 594 Enabling and disabling auditing on page 589 Restarting auditing on page 593
6. Restarting auditing.
Installing the audit system

The audit system is usually installed with auditinit, the Sybase installation program. Alternatively, you can install auditing without auditinit. For details, see Installing auditing with installsecurity on page 579. Installation and auditinit are discussed in the Adaptive Server installation and configuration documentation for your platform. When you install auditing, you can establish the number of system tables you want to use for the audit trail, the device for each audit system table, and the device for the syslogs transaction log.
578
CHAPTER 18
Auditing
Tables and devices for the audit trail

You can specify up to eight system tables (sysaudits_01 through sysaudits_08). Plan to use at least two tables for the audit trail. Put each table on its own device separate from the master device. If you do this, you can use a threshold procedure to automatically archive the current audit table before it fills up and switch to a new empty table for the subsequent audit records.
Device for the syslogs transaction log table

When you install auditing, you must specify a separate device for the transaction log, which consists of the syslogs system table. The syslogs table, which exists in every database, contains a log of the transactions that are executed in the database.
Installing auditing with installsecurity

The $SYBASE/ASE-15_0/scripts directory contains installsecurity, a script for installing auditing.
Note This example assumes a server that uses a logical page size of 2K.
To use installsecurity to install auditing: 1 Create the auditing devices and auditing database with the disk init and create database commands. For example:
disk init name = "auditdev", physname = "/dev/dsk/c2d0s4", size = "10M" disk init name = "auditlogdev", physname = "/dev/dsk/c2d0s5", size = "2M" create database sybsecurity on auditdev log on auditlogdev
Use isql to execute the installsecurity script:

cd $SYBASE/ASE-12_5/scripts setenv DSQUERY server_name isql -Usa -Ppassword -Sserver_name < installsecurity
Shut down and restart Adaptive Server.
579
When you have completed these steps, the sybsecurity database has one audit table (sysaudits_01) created on its own segment. You can enable auditing at this time, but should add more auditing tables with sp_addaudittable. For information about disk init, create database, and sp_addaudittable, see the Reference Manual.
Moving the auditing database to multiple devices

Place the sybsecurity database on its own device, separate from the master database. If you have more than one audit table, place each table on its own device. It can also be helpful to put each table on a separate segment which points to a separate device. If you currently have sybsecurity on the same device as master, or if you want to move sybsecurity to another device, use one of the procedures described in the following sections. When you move the database, you can specify whether to save your existing global audit settings.
Moving sybsecurity without saving global audit settings
To move the sybsecurity database without saving the global audit settings: 1 Execute the following to remove any information related to logins from the syslogins system table:
sp_audit "all","all","all","off"
2 3
Drop the sybsecurity database. Install sybsecurity again using the installation procedure described in either: The configuration documentation for your platform, or Installing auditing with installsecurity on page 579.
During the installation process, place the sybsecurity database on one or more devices, separate from the master device.
Moving sybsecurity and saving global audit settings To move the sybsecurity database and save the global audit settings
Dump the sybsecurity database:

dump database sybsecurity to "/remote/sec_file"
Drop the sybsecurity database:

drop database sybsecurity
580
CHAPTER 18
Auditing
Initialize the first device on which you want to place the sybsecurity database:
disk init name = "auditdev", physname = "/dev/dsk/c2d0s4", size = "10M"
Initialize the device where you want to place the security log:
disk init name = "auditlogdev", physname = "/dev/dsk/c2d0s5", size = "2M"
Create the new sybsecurity database:

create database sybsecurity on auditdev log on auditlogdev
Load the contents of the old sybsecurity database into the new database. The global audit settings are preserved:
load database sybsecurity from "/remote/sec_file"
Run online database, which upgrades sysaudits and sysauditoptions if necessary:

online database sybsecurity
Load the auditing system procedures using the configuration documentation for your platform.
Creating more than one sysaudits table in sybsecurity
Initialize the device where you want to place the additional table:
disk init name = "auditdev2", physname = "/dev/dsk/c2d0s6", size = "10M"
Extend the sybsecurity database to the device you initialized in step 1:

alter database sybsecurity on auditdev2 = "2M"
Run sp_addaudittable to create the next sysaudits table on the device you initialized in step 1:
sp_addaudittable auditdev2
Repeat steps 1 3 for each sysaudits table.
581
Setting up audit trail management

To effectively manage the audit trail: 1 2 3 Be sure that auditing is installed with two or more tables, each on a separate device. If not, consider adding additional audit tables and devices. Write a threshold procedure and attach it to each audit table segment. Set configuration parameters for the audit queue size and to indicate appropriate action should the current audit table become full.
The following sections assume that you have installed auditing with two or more tables, each on a separate device. If you have only one device for the audit tables, skip to Single-table auditing on page 590.
Setting up threshold procedures

Before enabling auditing, establish a threshold procedure to automatically switch auditing tables when the current table is full. The threshold procedure for the audit device segments should: Make the next empty audit table current using sp_configure. Archive the audit table that is almost full using the insert and select commands.
Changing the current audit table
The current audit table configuration parameter establishes the table where Adaptive Server writes audit rows. As a System Security Officer, you can change the current audit table with sp_configure, using the following syntax, where n is an integer that determines the new current audit table:
sp_configure "current audit table", n [, "with truncate"]
The valid values for n are: 1 means sysaudits_01, 2 means sysaudits_02, and so forth. 0 tells Adaptive Server to automatically set the current audit table to the next table. For example, if your installation has three audit tables, sysaudits_01, sysaudits_02, and sysaudits_03, Adaptive Server sets the current audit table to: 582 2 if the current audit table is sysaudits_01 3 if the current audit table is sysaudits_02
CHAPTER 18
Auditing
1 if the current audit table is sysaudits_03
The with truncate option specifies that Adaptive Server should truncate the new table if it is not already empty. If you do not specify this option and the table is not empty, sp_configure fails.
Note If Adaptive Server truncates the current audit table and you have not
archived the data, the tables audit records are lost. Archive the audit data before you use the with truncate option. To execute sp_configure to change the current audit table, you must have the sso_role active. You can write a threshold procedure to automatically change the current audit table.
Archiving the audit table
You can use insert with select to copy the audit data into an existing table having the same columns as the audit tables in sybsecurity. Be sure that the threshold procedure can successfully copy data into the archive table in another database: 1 2 Create the archive database on a separate device from the one containing audit tables in sybsecurity. Create an archive table with columns identical to those in the sybsecurity audit tables. If such a table does not already exist, you can use select into to create an empty one by having a false condition in the where clause. For example:
use aud_db go select * into audit_data from sybsecurity.dbo.sysaudits_01 where 1 = 2
The where condition is always false, so an empty duplicate of sysaudits_01 is created. The select into/bulk copy database option must be turned on in the archive database (using sp_dboption) before you can use select into. The threshold procedure, after using sp_configure to change the audit table, can use insert and select to copy data to the archive table in the archive database. The procedure can execute commands similar to these:
583
insert aud_db.sso_user.audit_data select * from sybsecurity.dbo.sysaudits_01 Example threshold procedure for audit segments
This sample threshold procedure assumes that three tables are configured for auditing:
declare @audit_table_number int /* ** Select the value of the current audit table */ select @audit_table_number = scc.value from master.dbo.syscurconfigs scc, master.dbo.sysconfigures sc where sc.config=scc.config and sc.name = current audit table /* ** Set the next audit table to be current. ** When the next audit table is specified as 0, ** the value is automatically set to the next one. */ exec sp_configure current audit table, 0, with truncate /* ** Copy the audit records from the audit table ** that became full into another table. */ if @audit_table_number = 1 begin insert aud_db.sso_user.sysaudits select * from sysaudits_01 truncate table sysaudits_01 end else if @audit_table_number = 2 begin insert aud_db.sso_user.sysaudits select * from sysaudits_02 truncate table sysaudits_02 end return(0) Attaching the threshold procedure to each audit segment
To attach the threshold procedure to each audit table segment, use the sp_addthreshold. Before executing sp_addthreshold:
584
CHAPTER 18
Auditing
Determine the number of audit tables configured for your installation and the names of their device segments Have the permissions and roles you need for sp_addthreshold for all the commands in the threshold procedure
Warning! sp_addthreshold and sp_modifythreshold check to ensure that only a user with sa_role directly granted can add or modify a threshold. All system-defined roles that are active when you add or modify a threshold are inserted as valid roles for your login in the systhresholds table. However, only directly granted roles are activated when the threshold procedure fires.
Audit tables and their segments
When you install auditing, auditinit displays the name of each audit table and its segment. The segment names are aud_seg1 for sysaudits_01, aud_seg2 for sysaudits_02, and so forth. You can find information about the segments in the sybsecurity database if you execute sp_helpsegment with sybsecurity as your current database. One way to find the number of audit tables for your installation is to execute the following SQL commands:
use sybsecurity go select count(*) from sysobjects where name like "sysaudit%" go
In addition, you can get information about the audit tables and the sybsecurity database by executing the following SQL commands:
sp_helpdb sybsecurity go use sybsecurity go sp_help sysaudits_01 go sp_help sysaudits_02 go ...
585
Required roles and permissions
To execute sp_addthreshold, you must be either the Database Owner or a System Administrator. A System Security Officer should be the owner of the sybsecurity database and, therefore, should be able to execute sp_addthreshold. In addition to being able to execute sp_addthreshold, you must have permission to execute all the commands in your threshold procedure. For example, to execute sp_configure for current audit table, the sso_role must be active. When the threshold procedure fires, Adaptive Server attempts to turn on all the roles and permissions that were in effect when you executed sp_addthreshold. To attach the threshold procedure audit_thresh to three device segments:
use sybsecurity go sp_addthreshold sybsecurity, aud_seg_01, 250, audit_thresh sp_addthreshold sybsecurity, aud_seg_02, 250, audit_thresh sp_addthreshold sybsecurity, aud_seg_03, 250, audit_thresh go
The sample threshold procedure audit_thresh receives control when fewer than 250 free pages remain in the current audit table. For more information about adding threshold procedures, see Chapter 15, Managing Free Space with Thresholds.
Auditing with the sample threshold procedure in place
After you enable auditing, Adaptive Server writes all audit data to the initial current audit table, sysaudits_01. When sysaudits_01 is within 250 pages of being full, the threshold procedure audit_thresh fires. The procedure switches the current audit table to sysaudits_02, and, immediately, Adaptive Server starts writing new audit records to sysaudits_02. The procedure also copies all audit data from sysaudits_01 to the audit_data archive table in the audit_db database. The rotation of the audit tables continues in this fashion without manual intervention.
Setting auditing configuration parameters

Set the following configuration parameters for your auditing installation:
audit queue size sets the number of records in the audit queue in memory. suspend audit when device full determines what Adaptive Server does if the
current audit table becomes completely full. The full condition occurs only if the threshold procedure attached to the current table segment is not functioning properly.
586
CHAPTER 18
Auditing
Setting the size of the audit queue
The memory requirement for a single audit record is 424 bytes. The default size for the audit queue is 100 records, which requires approximately 42K. To set the size of the audit queue, use sp_configure. The syntax is:
sp_configure "audit queue size", [value]
value is the number of records that the audit queue can hold. The minimum value is 1, and the maximum is 65,535. For example, to set the audit queue size to 300, execute:
sp_configure "audit queue size", 300
For more information about setting the audit queue size and other configuration parameters, see Chapter 5, Setting Configuration Parameters.
Suspending auditing if devices are full
If you have two or more audit tables, each on a separate device other than the master device, and have a threshold procedure for each audit table segment, the audit devices should never become full. Only if a threshold procedure is not functioning properly would the full condition occur. You can use sp_configure to set the suspend audit when device full parameter to determine what happens if the devices do become full. Choose one of these options: Suspend the auditing process and all user processes that cause an auditable event. Resume normal operation after a System Security Officer clears the current audit table. Truncate the next audit table and start using it. This allows normal operation to proceed without intervention from a System Security Officer.
To set this configuration parameter, use sp_configure. You must have the sso_role active. The syntax is:
sp_configure "suspend audit when device full", [0|1]
0 truncates the next audit table and starts using it as the current audit
table whenever the current audit table becomes full. If you set the parameter to 0, the audit process is never suspended; however, older audit records are lost if they have not been archived.
587
1 (the default value) suspends the audit process and all user processes
that cause an auditable event. To resume normal operation, the System Security Officer must log in and set up an empty table as the current audit table. During this period, the System Security Officer is exempt from normal auditing. If the System Security Officers actions would generate audit records under normal operation, Adaptive Server sends an error message and information about the event to the error log. If you have a threshold procedure attached to the audit table segments, set suspend audit when device full to 1 (on). If it is set to 0 (off), Adaptive Server may truncate the audit table that is full before your threshold procedure has a chance to archive your audit records.
Setting up transaction log management

This section describes guidelines for managing the transaction log in sybsecurity. If the trunc log on chkpt database option is active, Adaptive Server truncates syslogs every time it performs an automatic checkpoint. After auditing is installed, the value of trunc log on chkpt is on, but you can use sp_dboption to change its value.
Truncating the transaction log

If you enable the trunc log on chkpt option for the sybsecurity database, you do not need to worry about the transaction log becoming full. Adaptive Server truncates the log whenever it performs a checkpoint. With this option on, you cannot use dump transaction to dump the transaction log, but you can use dump database to dump the database. If you follow the procedures in Setting up threshold procedures on page 582, audit tables are automatically archived to tables in another database. You can use standard backup and recovery procedures for this archive database. If a crash occurs on the sybsecurity device, you can reload the database and resume auditing. At most, only the records in the in-memory audit queue and the current audit table are lost because the archive database contains all other audit data. After you reload the database, use sp_configure with truncate to set and truncate the current audit table.
588
CHAPTER 18
Auditing
If you have not changed server-wide auditing options since you dumped the database, all auditing options stored in sysauditoptions are automatically restored when you reload sybsecurity. If not, you can run a script to set the options prior to resuming auditing.
Managing the transaction log with no truncation

If you use db_option to turn the trunc log on chkpt off, the transaction log may fill up. Plan to attach a last-chance threshold procedure to the transaction log segment. This procedure gets control when the amount of space remaining on the segment is less than a threshold amount computed automatically by Adaptive Server. The threshold amount is an estimate of the number of free log pages that are required to back up the transaction log. The default name of the last-chance threshold procedure is sp_thresholdaction, but you can specify a different name with sp_modifythreshold, as long as you have the sa_role active.
Note sp_modifythreshold checks to ensure you have sa_role active. See
Attaching the threshold procedure to each audit segment on page 584 for more information. Adaptive Server does not supply a default procedure, but Chapter 15, Managing Free Space with Thresholds contains examples of last-chance threshold procedures. The procedure should execute the dump transaction command, which truncates the log. When the transaction log reaches the lastchance threshold point, any transaction that is running is suspended until space is available. The suspension occurs because the option abort xact when log is full is always set to false for the sybsecurity database. You cannot change this option. With the trunc log on chkpt option off, you can use standard backup and recovery procedures for the sybsecurity database, but be aware that the audit tables in the restored database may not be in sync with their status during a device failure.
Enabling and disabling auditing

To enable or disable auditing, use sp_configure with the auditing configuration parameter. The syntax is:
sp_configure "auditing", [0 | 1 ]
589
1 enables auditing. 0 disables auditing.
For example, to enable auditing, enter:

sp_configure "auditing", 1 Note When you enable or disable auditing, Adaptive Server automatically
generates an audit record. See event codes 73 and 74 in Table 18-5 on page 605.
Single-table auditing
Sybase strongly recommends that you not use single-device auditing for production systems. If you use only a single audit table, you create a window of time while you are archiving audit data and truncating the audit table during which incoming audit records are lost. There is no way to avoid this when using only a single audit table. If you use only a single audit table, your audit table is likely to fill up. The consequences of this depend on how you have set suspend audit when device full. If you have suspend audit when device full set to on, the audit process is suspended, as are all user processes that cause auditable events. If suspend audit when device full is off, the audit table is truncated, and you lose all the audit records that were in the audit table. For non-production systems, where the loss of a small number of audit records may be acceptable, you can use a single table for auditing, if you cannot spare the additional disk space for multiple audit tables, or you do not have additional devices to use. The procedure for using a single audit table is similar to using multiple audit tables, with these exceptions: During installation, you specify only one system table to use for auditing. During installation, you specify only one device for the audit system table. The threshold procedure you create for archiving audit records is different from the one you would create if you were using multiple audit tables.
Figure 18-2 shows how the auditing process works with a single audit table.
590
CHAPTER 18
Auditing
Figure 18-2: Auditing with a single audit table
User processes
Audit queue
Audit process
threshold procedure Archive audit table
database on another device (then normal dump and load)
Establishing and managing single-table auditing

The steps to configure for single-table auditing is the same as for multiple-table auditing. See Table 18-1 for more information.
Threshold procedure for single-table auditing

For single-table auditing, the threshold procedure should: Archive the almost-full audit table to another table, using the insert and select commands. Truncate the audit table to create space for new audit records, using the truncate table command.
591
Before you can archive your audit records, create an archive table that has the same columns as your audit table. After you have done this, your threshold procedure can use insert with select to copy the audit records into the archive table. Here is a sample threshold procedure for use with a single audit table:
create procedure audit_thresh as /* ** copy the audit records from the audit table to ** the archive table */ insert aud_db.sso_user.audit_data select * from sysaudits_01 return(0) go /* ** truncate the audit table to make room for new ** audit records */ truncate table sysaudits_01 go
After you have created your threshold procedure, you will need to attach the procedure to the audit table segment. For instructions, see Attaching the threshold procedure to each audit segment on page 584.
Warning! On a multiprocessor, the audit table may fill up even if you have a threshold procedure that triggers before the audit table is full. For example, if the threshold procedure is running on a heavily loaded CPU, and a user process performing auditable events is running on a less heavily loaded CPU, the audit table may fill up before the threshold procedure triggers. The configuration parameter suspend audit when device full determines what happens when the audit table fills up. For information about setting this parameter, see Suspending auditing if devices are full on page 587.
What happens when the current audit table is full?

When the current audit table is full: 1 The audit process attempts to insert the next audit record into the table. This fails, so the audit process terminates. An error message is writen to the error log.
592
CHAPTER 18
Auditing
When a user attempts to perform an auditable event, the event cannot be completed because auditing cannot proceed. The user process terminates. Users who do not attempt to perform an auditable event are unaffected. If you have login auditing enabled, no one can log in to the server except a System Security Officer. If you are auditing commands executed with the sso_role active, the System Security Officer cannot execute commands.
3 4
Recovering when the current audit table is full

If the current audit device and the audit queue becomes full, the System Security Officer becomes exempt from auditing. Every auditable event performed by a System Security Officer after this point sends a warning message to the error log file. The message states the date and time and a warning that an audit has been missed, as well as the login name, event code, and other information that would normally be stored in the extrainfo column of the audit table. When the current audit table is full, the System Security Officer can archive and truncate the audit table as described in Archiving the audit table on page 583. A System Administrator can execute shutdown to stop the server and then restart the server to reestablish auditing. If the audit system terminates abnormally, the System Security Officer can shut down the server after the current audit table has been archived and truncated. Normally, only the System Administrator can execute shutdown.
Restarting auditing
If the audit process is forced to terminate due to an error, sp_audit can be manually restarted by entering:
sp_audit restart
The audit process can be restarted provided that no audit was currently running, but that the audit process has been configured to run by entering sp_configure auditing 1.
593
Setting global auditing options

After you have installed auditing, you can use sp_audit to set auditing options. The syntax for sp_audit is:
sp_audit option, login_name, object_name [,setting]
If you run sp_audit with no parameters, it provides a complete list of the options. For details about sp_audit, see the Reference Manual.
Note Auditing does not occur until you activate auditing for the server. For
information on how to start auditing, see Enabling and disabling auditing on page 589.
Auditing options: types and requirements

The values you can specify for the login_name and object_name parameters to sp_audit depend on the type of auditing option you specify: Global options apply to commands that affect the entire server, such as booting the server, disk commands, and allowing ad hoc, user-defined audit records. Option settings for global events are stored in the sybsecurity..sysauditoptions system table. Database-specific options apply to a database. Examples include altering a database, bulk copy (bcp in) of data into a database, granting or revoking access to objects in a database, and creating objects in a database. Option settings for database-specific events are stored in the master..sysdatabases system table. Object-specific options apply to a specific object. Examples include selecting, inserting, updating, or deleting rows of a particular table or view and the execution of a particular trigger or procedure. Option settings for object-specific events are stored in the sysobjects system table in the relevant database. User-specific options apply to a specific user or system role. Examples include accesses by a particular user to any table or view or all actions performed when a particular system role, such as sa_role, is active. Option settings for individual users are stored in master..syslogins. The settings for system roles are stored in master..sysauditoptions.
Table 18-2 shows:
594
CHAPTER 18
Auditing
Valid values for the option and the type of each option global, databasespecific, object-specific, or user-specific Valid values for the login_name and object_name parameters for each option The database to be in when you set the auditing option The command or access that is audited when you set the option An example for each option
The default value for all options is off.

Table 18-2: Auditing options, requirements, and examples Option (option type)
adhoc
login_name
all
object_name
all
Database to be in to set the option Any
Command or access being audited Allows users to use sp_addauditrecord
(user-specific)
all
Example: sp_audit "adhoc", "all", "all", "on" (Enables ad hoc user-defined auditing records.) A login name all Any or role
Example
(user-specific)
All actions of a particular user or by users with a particular role active
sp_audit "all", "sa_role", "all", "on"
alter
(database-specific)
(Turns auditing on for all actions in which the sa_role is active.) all Database to be Any alter database, alter table audited
Example sp_audit @option = "alter", @login_name = "all", @object_name = "master", @setting = "on"
bcp
(database-specific)
(Turns auditing on for all executions of alter database and alter table in the master database.) all Database to be Any bcp in audited
Example sp_audit "bcp", "all", "pubs2"
bind
(database-specific)
(Returns the status of bcp auditing in the pubs2 database. If you do not specify a value for setting, Adaptive Server returns the status of auditing for the option you specify) all Database to be Any sp_bindefault, sp_bindmsg, sp_bindrule audited
Example sp_audit "bind", "all", "planning", "off"
(Turns bind auditing off for the planning database.)
595
Option (option type)

cmdtext
login_name A login name, role, or all for all users in the database
Example
object_name
all
Command or access being audited SQL text entered by a user. (Does not reflect whether or not the text in question passed permission checks or not. eventmod always has a value of 1.)
(user-specific)
sp_audit "cmdtext", "sa", "all", "off" create database, create table, create procedure, create trigger, create rule, create default, sp_addmessage, create view, create index, create function
create
(database-specific)
(Turns text auditing off for Database Owners.) all Database to be Any audited
Note Specify master for object_name to audit create database. You are also auditing the
creation of other objects in master.

Example sp_audit "create", "all", "planning", "pass"
(Turns on auditing of successful object creations in the planning database. The current status of auditing create database is not affected because you did not specify the master database.)
dbaccess all Example dbcc
(database-specific)
Database to be audited
Any
Any access to the database from another database
sp_audit "dbaccess", "all", "project", "on"
(global)
(Audits all external accesses to the project database.) all all Any All dbcc commands that require permissions
Example sp_audit "dbcc", "all", "all", "on" delete from a table, delete from a view
delete
(object-specific)
(Audits all executions of the dbcc command.) all Name of the The database of table or view to the table or be audited, or view (except default view or tempdb)
default table Example
sp_audit "delete", "all", "default table", "on"
disk
(global)
(Audits all delete actions for all future tables in the current database.) all all Any disk init, disk refit, disk reinit, disk mirror, disk unmirror, disk remirror, disk resize
Example sp_audit "disk", "all", "all", "on"
(Audits all disk actions for the server.)
596
CHAPTER 18
Auditing

drop
login_name
all
object_name Database to be audited
Command or access being audited

drop database, drop table, drop procedure, drop index, drop trigger, drop rule, drop default, sp_dropmessage, drop view, drop function
(database-specific)
Example dump
sp_audit "drop", "all", "financial", "fail"
(database-specific)
(Audits all drop commands in the financial database that fail permission checks.) all Database to be Any dump database, dump transaction audited
Example sp_audit "dump", "all", "pubs2", "on"
errors
(Audits dump commands in the pubs2 database.) all all Any

Example
Fatal error, non-fatal error
(global)
exec_procedure
sp_audit "errors", "all", "all", "on"
(object-specific)
(Audits errors throughout the server.) all Name of the The database of procedure to be the procedure audited or (except tempdb)
default procedure Example
execute
sp_audit "exec_procedure", "all", "default procedure", "off"
exec_trigger
(object-specific)
(Turns automatic auditing off for new procedures in the current database.) all Name of the The database of Any command that fires the trigger trigger to be the trigger audited or (except tempdb)
default trigger Example sp_audit "exec_trigger", "all", "trig_fix_plan", "fail"
func_dbaccess
(database-specific)
(Audits all failed executions of the trig_fix_plan trigger in the current database.) all Name of the Any Access to the database using the database you following functions: are auditing curunreserved_pgs, db_name, db_id, lct_admin, setdbrepstat, setrepstatus, setrepdefmode, is_repagent_enabled, rep_agent_config, rep_agent_admin
Example sp_audit @option="func_dbaccess", @login_name="all", @object_name = "strategy", @setting = "on"
(Audits accesses to the strategy database via built-in functions.)
597

func_obj_access
login_name
all
object_name Name of any object that has an entry in

sysobjects
Command or access being audited Access to an object using the following functions: schema_inc, col_length, col_name, data_pgs, index_col, object_id, object_name, reserved_pgs, rowcnt, used_pgs, has_subquery
(object-specific)
Example sp_audit @option="func_obj_access", @login_name="all", @object_name = "customer", @setting = "on"
grant
(database-specific)
(Audits accesses to the customer table via built-in functions.) all Name of the Any grant database to be audited
Example sp_audit @option="grant", @login_name="all", @object_name = "planning", @setting = "on"
insert
(object-specific)
(Audits all grants in the planning database.) all Name of the The database of view or table to the object which you are (except tempdb) inserting rows, or default view or default table
Example
insert into a table, insert into a view
sp_audit "insert", "all", "dpt_101_view", "on"
install
(database-specific)
(Audits all inserts into the dpt_101_view view in the current database.) all Database to be Any install java audited
Example sp_audit "install", "all", "planning", "on"
load
(database-specific)
(Audits the installation of java classes in database planning) all Database to be Any load database, load transaction audited
Example sp_audit "load", "all", "projects_db", "fail"
login
(Audits all failed executions of database and transaction loads in the projects_db database.) all all Any Any login to Adaptive Server
Example sp_audit "login", "all", "all", "fail"
(global)
logout
(Audits all failed attempts to log in to the server.) all all Any
Example
Any logout from Adaptive Server
sp_audit "logout", "all", "all", "off"
(Turns auditing off of logouts from the server.)
598
CHAPTER 18
Auditing

mount
login_name
all Example
object_name
all

mount database
(global)
quiesce
sp_audit "mount", "all", "all", "on"
(Audits all mount database commands issued.) all all Any

Example
quiesce database
(global)
reference
sp_audit "quiesce", "all", "all", "on"
(object-specific)
(Turns auditing on for quiesce database commands.) all Name of the Any create table, alter table view or table to which you are inserting rows, or default view or default table
Example sp_audit "reference", "all", "titles", "off"
remove
(database-specific)
revoke
(Turns off auditing of the creation of references to the titles table.) all all Any Audits the removal of Java classes Example sp_audit "remove", "all", "planning", "on" (Audits the removal of Java classes in the planning database.) all Database to be Any revoke audited
Example sp_audit "revoke", "all", "payments_db", "off"
(database-specific)
rpc
(global)
(Turns off auditing of the execution of revoke in the payments_db database.) all all Any Remote procedure calls (either in or out)
Example sp_audit "rpc", "all", "all", "on"
security
(global)
(Audits all remote procedure calls out of or into the server.) all all Any Server-wide security-relevant events. See the security option in Table 18-5.
Example sp_audit "security", "all", "all", "on"
select
(object-specific)
(Audits server-wide security-relevant events in the server.) all Name of the The database of select from a table, select from a view view or table to the object which you are (except tempdb) inserting rows, or default view or default table
Example sp_audit "select", "all", "customer", "fail"
(Audits all failed selects from the customer table in the current database.)
599

setuser
login_name
all Example
object_name
all

setuser
(database-specific)
table_access
sp_audit "setuser", "all", "projdb", "on"
(Audits all executions of setuser in the projdb database.) (user-specific) Name of the login to be audited, or all if all users are to be audited.
Example truncate all
Any
select, delete, update, or insert access in
a table
sp_audit "table_access", "smithson", "all", "on"
(database-specific)
(Audits all table accesses by the login named smithson.) all Database to be Any truncate table audited
Example sp_audit "truncate", "all", "customer", "on"
unbind
(database-specific)
(Audits all table truncations in the customer database.) all Database to be Any sp_unbindefault, sp_unbindrule, sp_unbindmsg audited
Example sp_audit "unbind", "all", "master", "fail"
unmount
(Audits all failed attempts of unbinding in the master database.) all all Any unmount database
Example sp_audit "unmount", "all", "all", "on" update to a table, update to a view
(global)
update
(object-specific)
(audits all attemps to unmout any database.) all Name The database of specifying the the object object to be (except tempdb) audited, default table or default
view Example
sp_audit "update", "all", "projects", "on"
view_access
(user-specific)
(Audits all attempts by users to update the projects table in the current database.) Login name all Any select, delete, insert, or update to a view of the user to be audited, or all to audit all users
Example sp_audit "view_access", "joe", "all", "off"
(Turns off view auditing of user joe.)
600
CHAPTER 18
Auditing
Examples of setting auditing options

Suppose you want to audit all failed deletions on the projects table in the company_operations database and for all new tables in the database. Use the object-specific delete option for the projects table and use default table for all future tables in the database. To set object-specific auditing options, you must be in the objects database before you execute sp_audit:
sp_audit "security", "all", "all", "fail"
For this example, execute:

use company_operations go sp_audit "delete", "all", "projects", "fail" go sp_audit "delete", "all", "default table", "fail" go
Determining current auditing settings

To determine the current auditing settings for a given option, use sp_displayaudit. The syntax is:
sp_displayaudit [procedure | object | login | database | global | default_object | default_procedure [, name]]
For more information, see sp_displayaudit in the Reference Manual.
Adding user-specified records to the audit trail

sp_addauditrecord allows users to enter comments into the audit trail. The
syntax is:
sp_addauditrecord [text] [, db_name] [, obj_name] [, owner_name] [, dbid] [, objid]
All the parameters are optional: text is the text of the message that you want to add to the extrainfo audit table. db_name is the name of the database referred to in the record, which is inserted into the dbname column of the current audit table.
601
obj_name is the name of the object referred to in the record, which is inserted into the objname column of the current audit table. owner_name is the owner of the object referred to in the record, which is inserted into the objowner column of the current audit table. dbid is an integer value representing the database ID number of db_name, which is inserted into the dbid column of the current audit table. Do not place it in quotes. objid is an integer value representing the object ID number of obj_name. Do not place it in quotes. objid is inserted into the objid column of the current audit table.
You can use sp_addauditrecord if: You have execute permission on sp_addauditrecord. The auditing configuration parameter was activated with sp_configure. The adhoc auditing option was enabled with sp_audit.
By default, only a System Security Officer and the Database Owner of sybsecurity can use sp_addauditrecord. Permission to execute it may be granted to other users.
Examples of adding user-defined audit records

The following example adds a record to the current audit table. The text portion is entered into the extrainfo column of the current audit table, corporate into the dbname column, payroll into the objname column, dbo into the objowner column, 10 into the dbid column, and 1004738270 into the objid column:
sp_addauditrecord "I gave A. Smith the payroll table in the corporate permission was in effect from 3:10 9/22/92.", "corporate", "payroll", 1004738270 permission to view database. This to 3:30 pm on "dbo", 10,
The following example inserts information only into the extrainfo and dbname columns of the current audit table:
sp_addauditrecord @text="I am disabling auditing briefly while we reconfigure the system", @db_name="corporate"
602
CHAPTER 18
Auditing
Querying the audit trail

To query the audit trail, use SQL to select and summarize the audit data. If you follow the procedures discussed in Setting up audit trail management on page 582, the audit data is automatically archived to one or more tables in another database. For example, assume that the audit data resides in a table called audit_data in the audit_db database. To select audit records for tasks performed by bob on July 5, 1993, execute:
use audit_db go select * from audit_data where loginname = "bob" and eventtime like "Jul 5% 93" go
This command requests audit records for commands performed in the pubs2 database by users with the System Security Officer role active:
select * from audit_data where extrainfo like "%sso_role%" and dbname = "pubs2" go
This command requests audit records for all table truncations (event 64):
select * from audit_data where event = 64 go
To query the audit trail using the name of an audit event, use the audit_event_name function. For example, to request the the audit records for all database creation events, enter:
select * from audit_data where audit_event_name(event) = Create Database go
Understanding the audit tables

The system audit tables can be accessed only by a System Security Officer, who can read the tables by executing SQL commands. The only commands that are allowed on the system audit tables are select and truncate. Table 18-3 describes the columns in all audit tables.
603
Table 18-3: Columns in each audit table Column name

event eventmod
Datatype
smallint smallint
Description Type of event being audited. See Table 18-5 on page 605. More information about the event being audited. Indicates whether or not the event in question passed permission checks. Possible values are: 0 = no modifier for this event. 1 = the event passed permission checking. 2 = the event failed permission checking.
spid eventtime sequence suid dbid objid xactid
smallint datetime smallint smallint int null int null binary(6) null
ID of the process that caused the audit record to be written. Date and time that the audited event occurred. Sequence number of the record within a single event. Some events require more than one audit record. Server login ID of the user who performed the audited event. Database ID in which the audited event occurred, or in which the object, stored procedure, or trigger resides, depending on the type of event. ID of the accessed object, stored procedure, or trigger. ID of the transaction containing the audited event. For a multi-database transaction, this is the transaction ID from the database where the transaction originated. Login name corresponding to the suid. Database name corresponding to the dbid. Object name corresponding to the objid. Name of the owner of objid. Additional information about the audited event. This column contains a sequence of items separated by semicolons. For details, see Reading the extrainfo column on page 604. Server nodeid in a cluster where the event occured.
loginname dbname objname objowner extrainfo
varchar(30) null varchar(30) null varchar(30) null varchar(30) null varchar(255) null
nodeid
tinyint
Reading the extrainfo column

The extrainfo column contains a sequence of data separated by semicolons. The data is organized in the following categories.
Table 18-4: Information in the extrainfo column Position 1 2 Category Roles Keywords or Options Description A list of active roles, separated by blanks. The name of the keyword or option that was used for the event. For example, for the alter table command, the add column or drop constraint options might have been used. If multiple keywords or options are listed, they are separated by commas.
604
CHAPTER 18
Auditing
Position 3 4 5 6 7
Category Previous value Current value Other information Proxy information Principal name
Description If the event resulted in the update of a value, this item contains the value prior to the update. If the event resulted in the update of a value, this item contains the new value. Additional security-relevant information that is recorded for the event. The original login name if the event occurred while a set proxy was in effect. The principal name from the underlying security mechanism if the users login is the secure default login, and the user logged in to Adaptive Server via unified login. The value of this item is NULL if the secure default login is not being used.
This example shows an extrainfo column entry for the event of changing an auditing configuration parameter.
sso_role;suspend audit when device full;1;0;;ralph;
This entry indicates that a System Security Officer changed suspend audit when device full from 1 to 0. There is no other information for this entry. The sixth category indicates that the user ralph was operating with a proxy login. No principal name is provided. The other fields in the audit record give other pertinent information. For example, the record contains the server user ID (suid) and the login name (loginname). Table 18-5 lists the values that appear in the event column, arranged by sp_audit option. The Information in extrainfo column describes information that might appear in the extrainfo column of an audit table, based on the categories described in Table 18-4.
Table 18-5: Values in event and extrainfo columns Audit option (Automatically audited event not controlled by an option) (Automatically audited event not controlled by an option) Unlocking Administrators account
adhoc
Command or access to be audited Enabling auditing with:

sp_configure auditing
event 73
Information in extrainfo
Disabling auditing with:

74
Disabling auditing with:

74
User-defined audit record
extrainfo is filled by the text parameter of sp_addauditrecord
605
Audit option
alter
Command or access to be audited

alter database
event 2
Information in extrainfo Keywords or options:

alter maxhold alter size
alter table
Keywords or options:
add/drop/modify columns add constraint drop constraint
bcp bind
bcp in sp_bindefault sp_bindmsg sp_bindrule
4 6 7 8 92 9 14 11 13 10 12 16 104 97 15 17
Other information: Name of the default Other information: Message ID Other information: Name of the rule Full text of command, as sent by the client Other information: Name of the index Other information: Message number Keywords or options:
use cmd outside reference
cmdtext create
All commands
create database create default create procedure create rule create table create trigger create view create index create function sp_addmessage
dbaccess
Any access to the database by any user

dbcc all keywords
dbcc
81
Keywords or options: Any of the dbcc keywords such as checkstorage and the options for that keyword. Keywords or options: delete Keywords or options: delete
delete
delete from a table delete from a view
18 19
606
CHAPTER 18
Auditing
Audit option
disk

disk init
event 20 23 21 22 87 25 24 100 26 31 28 27 29 30 33 105 98 32 34 35 36 37 38 39 86
Information in extrainfo Keywords or options: disk init Other information: Name of the disk Keywords or options: disk mirror Other information: Name of the disk Keywords or options: disk refit Other information: Name of the disk Keywords or options: disk reinit Other information: Name of the disk Keywords or options: disk release Other information: Name of the disk Keywords or options: disk remirror Other information: Name of the disk Keywords or options: disk unmirror Other information: Name of the disk Keywords or options: disk resize Other information: Name of the disk Other information: Index name Other information: Message number Other information: Error number.Severity.State Other information: Error number.Severity.State Other information: All input parameters
disk mirror
disk refit
disk reinit
disk release
disk remirror
disk unmirror
disk resize
drop
drop database drop default drop procedure drop table drop trigger drop rule drop view drop index drop function sp_dropmessage
dump errors
dump database dump transaction
Fatal error Non-fatal error
exec_procedure exec_trigger func_obj_access, func_dbaccess
Execution of a procedure Execution of a trigger Accesses to objects and databases via Transact-SQL functions
607
Audit option
grant insert

grant insert into a table
event 40 41
Information in extrainfo Keywords or options: If insert is used: insert If select into is used: insert into followed by the fully qualified object name Keywords or options: insert Other information: Host name and IP address of the machine from which the login was performed. Other information: Host name Keywords or options: reference Other information: Name of the referencing table
insert into a view install load login install load database load transaction
42 93 43 44 45
Any login to the server
logout mount quiesce reference
Any logouts from the server

mount database quiesce database
46 101 96 91
Creation of references to tables
remove revoke rpc
remove java revoke
94 47 48
Keywords or options: Name of client program Other information: Server name, host name of the machine from which the RPC was executed. Keywords or options: Procedure name Keywords or options: connect to Other information: Required roles Keywords or options: Setting SSO password Other information: Login name Previous value: on or off Current value: on or off Other information: Name of the role being set
Remote procedure call from another server
security
Remote procedure call to another server connect to (CIS only)

online database proc_role function (executed from
49 90 83 80 76 55
within a system procedure) Regeneration of a password by an SSO Role toggling
608
CHAPTER 18
Auditing
Audit option
Command or access to be audited Server start
event 50
Information in extrainfo Other information:

-dmasterdevicename -iinterfaces file path -Sservername -eerrorfilename
sp_webservices
111
sp_webservices
111
Server shutdown
set proxy or set session authorization sp_configure
51 88 82
Keywords or options: deploy if deploying a web service. deploy_all if deploying all web services Keywords or options: undeploy if undeploying a web service. undeploy_all if undeploying all web services Keywords or options: shutdown Previous value: Previous suid Current value: New suid Keywords or options: SETCONFIG Other information: If a parameter is being set: number of configuration parameter If a configuration file is being used to set parameters: name of the configuration file
sp_ssladmin administration
99 61 103 85 86 95
enabled Audit table access create login, drop login

create, drop, alter, grant, or revoke role
Keywords contains SSL_ADMIN addcert, if adding a certification. Keywords or options: create login, drop login Keywords or options: create, drop, alter, grant, or revoke role Keywords or options: Name of function Other information contains 'Unlocking admin account'
built-in functions Security command or access to be audited, specifically, starting Adaptive Server with -u option to unlock the administrators account..
609
Audit option
select
Command or access to be audited select from a table
event 62
Information in extrainfo Keywords or options:

select into select readtext
select from a view
63
setuser table_access
setuser delete insert select
84 18 41 62
Other information: Name of the user being set Keywords or options: delete Keywords or options: insert Keywords or options:
update
70
update writetext
truncate unbind
truncate table sp_unbindefault sp_unbindmsg sp_unbindrule
64 67 69 68 102 70
update writetext
unmount update
unmount database update to a table
update to a view
71
update writetext
view_access
delete insert select
19 42 63
Keywords or options: delete Keywords or options: insert Keywords or options:

update
71
update writetext
610
CHAPTER 18
Auditing
Table 18-6 lists the values that appear in the event column, arranged by the audit event..
Table 18-6: Audit event values Audit event ID Command name 1 ad hoc audit record 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33
alter database alter table bcp in
Audit event ID Command name 56 Reserved 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 Reserved Reserved Reserved Reserved access to audit table
select table select view truncate table
Reserved
bind default bind message bind rule create database create table create procedure create trigger create rule create default create message create view access to database delete table delete view disk init disk refit disk reinit disk mirror disk unmirror disk remirror drop database drop table drop procedure drop trigger drop rule drop default drop message drop view
Reserved Reserved
unbind default unbind rule unbind message update table update view
Reserved auditing enabled auditing disabled Reserved SSO changed password Reserved Reserved Reserved role check performed
dbcc
config
online database setuser command
UDR command built-in function Disk release set SSA command
611
Audit event ID Command name 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55

dump database dump transaction
Audit event ID Command name 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
kill or terminate command connect
Fatal error Non-fatal error execution of stored procedure Execution of trigger

grant insert table insert view load database load transaction login logout revoke rpc in rpc out
reference command text

JCS install command JCS remove command
Unlock admin account

quiesce database create SQLJ function drop SQLJ function
SSL administration
disk resize mount database unmount database login command create index drop index
server boot server shutdown Reserved Reserved Reserved role toggling
Reserved Reserved Reserved Reserved

deploy user-defined web services undeploy user defined web services
Auditing login failures

Although client applications may fail to login for many reasons, Adaptive Server does not provide them with any detailed information about the login failure. This is done to avoid giving information to malintentioned users attempting to crack passwords or otherwise breach Adaptive Servers authentication mechanisms. However, as a system administrator, detailed information is useful for diagnosing Adaptive Server administrative or configuration problems, and it is useful to security officers for investigating attempts to breach security.
612
CHAPTER 18
Auditing
This enables auditing for all login failures:

sp_audit "login", "all", "all", "fail"
In order to provide a barrier to inappropriate use of the information, only a user granted the SSO role can access the audit trail information containing this sensitive information. Adaptive Server audits login failures for the following conditions: For Adaptive Server started as a Windows Service, if the Sybase SQLServer service is paused (for example, by the Microsoft Management Console for Services). If a remote server attempts to establish a site handler for server-to-server RPCs, but insufficient resources (or any of the other conditions listed here) cause the site handler initialization to fail. Using Adaptive Server for Windows with the Trusted Login or Unified Login configuration, but the specified user is not a trusted administrator (that is, an authentication failure). Adaptive Server does not support the SQL interface requested by the client. A user is attempting to log into Adaptive Server when it is in single-user mode. In single-user mode, exactly one user with the sa_role is allowed to log in to Adaptive Server. Additional logins are prevented, even if they have the sa_role. The syslogins table in the master database fails to open, indicating the master database has an internal error. A client attempts a remote login, but sysremotelogins cannot be opened, or there is no entry for the specified user account and no guest account exists. A client attempts a remote login and, although it finds an entry referring to a local account for the specified user in sysremotelogins, the referenced local account does not exist. A client program requests a security session (for example, a Kerberos authentication), but the security session could not be established because: The Adaptive Server security subsystem was not initialized at startup. Insufficient memory resources for allocated structures. The authentication negotiation failed.
An authentication mechanism is not found for the specified user.
613
The specified password was not correct.

syslogins does not contain the required entry for the specified login.
The login account is locked. Adaptive Server has reached its limit for the number of user connections. The configuration parameter unified login required is set, but the login has not been authenticated by the appropriate security subsystem. Adaptive Servers network buffers are unavailable, or the requested packet size is invalid. A client application requests a host-based communication socket connection, but memory resources for the host-based communication buffers are not available. A shutdown is in progress, but the specified user does not have the SA role. Adaptive Server could not open the default database for a login, and this login does not have access to the master database. A client makes a high availability login failover request, but the high availability subsystem is does not have a high availability session for this login, or the login is unable to wait for the failover to complete. A client requests a high availability login setup, but the high availability subsystem is unable to create the session or is unable to complete the TDS protocol negotiations for the high availability session. Adaptive Server fails to setup tempdb for a login. TDS Login Protocol errors are detected.
614
CH A PTE R
1 9
Confidentiality of Data
This chapter describes how to configure Adaptive Server to ensure that all data is secure and confidential.
Topic Secure Sockets Layer (SSL) in Adaptive Server Kerberos confidentiality Dumping and loading databases with password protection Page 615 635 635
Secure Sockets Layer (SSL) in Adaptive Server

Adaptive Server Enterprise security services now support Secure Sockets Layer (SSL) session-based security. SSL is the standard for securing the transmission of sensitive information, such as credit card numbers, stock trades, and banking transactions, over the Internet. While a comprehensive discussion of public-key cryptography is beyond the scope of this document, the basics are worth describing so that you have an understanding of how SSL secures Internet communication channels. This document is not a comprehensive guide to public-key cryptography. The implementation of Adaptive Server SSL features assume that there is a knowledgeable System Security Officer who is familiar with the security policies and needs of your site, and who has general understanding of SSL and public-key cryptography.
615
Internet communications overview

TCP/IP is the primary transport protocol used in client/server computing, and is the protocol that governs the transmission of data over the Internet. TCP/IP uses intermediate computers to transport data from sender to recipient. The intermediate computers introduce weak links to the communication system where data may be subjected to tampering, theft, eavesdropping, and impersonation.
Public-key cryptography
Several mechanisms, known collectively as public-key cryptography, have been developed and implemented to protect sensitive data during transmission over the Internet. Public-key cryptography consists of encryption, key exchange, digital signatures, and digital certificates.
Encryption
Encryption is a process wherein a cryptographic algorithm is used to encode information to safeguard it from anyone except the intended recipient. There are two types of keys used for encryption: Symmetric-key encryption is where the same algorithm (key) is used to encrypt and decrypt the message. This form of encryption provides minimal security because the key is simple, and therefore easy to decipher. However, transfer of data that is encrypted with a symmetric key is fast because the computation required to encrypt and decrypt the message is minimal. Public/private key encryption also known as asymmetric-key, is a pair of keys that are made up of public and private components to encrypt and decrypt messages. Typically, the message is encrypted by the sender with a private key, and decrypted by the recipient with the senders public key, although this may vary. You can use a recipients public key to encrypt a message, who then uses his private key to decrypt the message. The algorithms used to create public and private keys are more complex, and therefore harder to decipher. However, public/private key encryption requires more computation, sends more data over the connection, and noticeably slows data transfer.
Key exchange
The solution for reducing computation overhead and speeding transactions without sacrificing security is to use a combination of both symmetric key and public/private key encryption in what is known as a key exchange.
616
CHAPTER 19
For large amounts of data, a symmetric key is used to encrypt the original message. The sender then uses either his private key or the recipients public key to encrypt the symmetric key. Both the encrypted message and the encrypted symmetric key are sent to the recipient. Depending on what key was used to encrypt the message (public or private) the recipient uses the opposite to decrypt the symmetric key. Once the key has been exchanged, the recipient uses the symmetric key to decrypt the message.
Digital signatures
Digital signatures are used for tamper detection and non-repudiation. Digital signatures are created with a mathematical algorithm that generates a unique, fixed-length string of numbers from a text message; the result is called a hash or message digest. To ensure message integrity, the message digest is encrypted by the signers private key, then sent to the recipient along with information about the hashing algorithm. The recipient decrypts the message with the signers public key. This process also regenerates the original message digest. If the digests match, the message proves to be intact and tamper free. If they do not match, the data has either been modified in transit, or the data was signed by an imposter. Further, the digital signature provides non-repudiationsenders cannot deny, or repudiate, that they sent a message, because their private key encrypted the message. Obviously, if the private key has been compromised (stolen or deciphered), the digital signature is worthless for non-repudiation.
Digital certificates
Digital Certificates are like passports: once you have been assigned one, the authorities have all your identification information in the system. Like a passport, the certificate is used to verify the identity of one entity (server, router, Web sites, and so on) to another. Adaptive Server uses two types of certificates: Server certificates a server certificate authenticates the server that holds it. Certificates are issued by a trusted third-party Certificate Authority (CA). The CA validates the holders identity, and embeds the holders public key and other identification information into the digital certificate. Certificates also contain the digital signature of the issuing CA, verifying the integrity of the data contained therein and validating its use. CA certificates (also known as trusted root certificates) is a list of trusted CAs loaded by the server at start-up. CA certificates are used by servers when they function as a client, such as during remote procedure calls (RPCs). Adaptive Server loads its CA trusted root certificate at start-up. When connecting to a remote server for RPCs, Adaptive Server verifies that the CA that signed the remote servers certificate is a trusted CA listed in its own CA trusted roots file. If it is not, the connection fails.
617
Certificates are valid for a period of time and can be revoked by the CA for various reasons, such as when a security breach has occurred. If a certificate is revoked during a session, the session connection continues. Subsequent attempts to login fail. Likewise, when a certificate expires, login attempts fail. The combination of these mechanisms protect data transmitted over the Internet from eavesdropping and tampering. These mechanisms also protect users from impersonation, where one entity pretends to be another (spoofing), or where a person or an organization says it is set up for a specific purpose when the real intent is to capture private information (misrepresentation).
SSL overview
SSL is an industry standard for sending wire- or socket-level encrypted data over secure network connections. Before the SSL connection is established, the server and the client exchange a series of I/O round trips to negotiate and agree upon a secure encrypted session. This is called the SSL handshake.
SSL handshake
When a client requests a connection, the SSL-enabled server presents its certificate to prove its identity before data is transmitted. Essentially, the handshake consists of the following steps: The client sends a connection request to the server. The request includes the SSL (or Transport Layer Security, TLS) options that the client supports. The server returns its certificate and a list of supported cipher suites, which includes SSL/TLS support options, algorithms used for key exchange, and digital signatures. A secure, encrypted session is established when both client and server have agreed upon a CipherSuite.
For more specific information about the SSL handshake and the SSL/TLS protocol, see the Internet Engineering Task Force Web site at http://www.ietf.org. For a list of cipher suites that Adaptive Server supports, see Cipher Suites on page 628.
SSL in Adaptive Server

Adaptive Servers implementation of SSL provides several levels of security.
618
CHAPTER 19
The server authenticates itselfproves that it is the server you intended to contactand an encrypted SSL session begins before any data is transmitted. Once the SSL session is established, the client requesting a connection can send his user name and password over the secure, encrypted connection. A comparison of the digital signature on the server certificate can determine whether the data received by the client was modified before reaching the intended recipient.
Adaptive Server uses the SSL Plus library API from Certicom Corp.
SSL filter
The Adaptive Server directory service, such as the interfaces file, NT Registry, or LDAP service, defines the server address and port numbers, and determines the security protocols that are enforced for client connections. Adaptive Server implements the SSL protocol as a filter that is appended to the master and query lines of the directory services. The addresses and port numbers on which Adaptive Server accepts connections are configurable, so you can enable multiple network and security protocols for a single server. Server connection attributes are specified with directory services, such as LDAP, or with the traditional Sybase interfaces file. See Creating server directory entries on page 625. All connection attempts to a master or query entry in the interfaces file with an SSL filter must support the SSL protocol. A server can be configured to accept SSL connections and have other connections that accept clear text (unencrypted data), or use other security mechanisms. For example, the interfaces file on UNIX that supports both SSL-based connections and clear-text connections looks like this:
SYBSRV1 master tcp ether myhostname myport1 ssl query tcp ether myhostname myport1 ssl master tcp ether myhostname myport2
The SSL filter is different from other security mechanisms, such as DCE and Kerberos, which are defined with SECMECH (security mechanism) lines in the interfaces file (sql.ini on Windows).
619
Authentication via the certificate

The SSL protocol requires server authentication via a server certificate to enable an encrypted session. Likewise, when Adaptive Server is functioning as a client during RPCs, there must be a repository of trusted CAs that a client connection can access to validate the server certificate.
The server certificate
Each Adaptive Server must have its own server certificate file that is loaded at start-up. The following is the default location for the certificates file, where servername is the name of the Adaptive Server as specified on the command line during start-up with the -s flag, or from the environment variable $DSLISTEN:
UNIX $SYBASE/$SYBASE_ASE/certificates/servername.crt NT
%SYBASE%\%SYBASE_ASE%\certificates\servername.crt
The server certificate file consists of encoded data, including the servers certificate and the encrypted private key for the server certificate. Alternatively, you can specify the location of the server certificate file when using sp_ssladmin.
Note To make a successful client connection, the common name in the
certificate must match the Adaptive Server name in the interfaces file.
The CA trusted roots certificate
The list of trusted CAs is loaded by Adaptive Server at start-up from the trusted roots file. The trusted roots file is similar in format to a certificate file, except that it contains certificates for CAs known to Adaptive Server. A trusted roots file is accessible by the local Adaptive Server in the following, where servername is the name of the server: UNIX $SYBASE/$SYBASE_ASE/certificates/servername.txt NT %SYBASE%\%SYBASE_ASE\certificates\servername.txt
The trusted roots file is only used by Adaptive Server when it is functioning as a client, such as when performing RPC calls or Component Integration Services (CIS) connections. The System Security Officer adds and deletes CAs that are to be accepted by Adaptive Server, using a standard ASCII-text editor.
Warning! Use the System Security Officer role (sso_role) within Adaptive Server to restrict access and execution on security-sensitive objects.
620
CHAPTER 19
Adaptive Server provides tools to generate a certificate request and to authorize certificates. See Using Adaptive Server tools to request and authorize certificates on page 624.
Connection types
This section describes various client-to-server and server-to-server connections.
Client login to Adaptive Server
Open Client applications establish a socket connection to Adaptive Server similarly to the way that existing client connections are established. Before any user data is transmitted, an SSL handshake occurs on the socket when the network transport-level connect call completes on the client side and the accept call completes on the server side. Adaptive Server establishes a socket connection to another server for RPCs in the same way that existing RPC connections are established. Before any user data is transmitted, an SSL handshake occurs on the socket when the network transport-level connect call completes. If the server-to-server socket connection has already been established, the existing socket connection and security context is reused. When functioning as a client during RPCs, Adaptive Server requests the remote servers certificate during connection. Adaptive Server then verifies that the CA that signed the remote servers certificate is trusted; that is to say, on its own list of trusted CAs in the trusted roots file. It also verifies that the common name in the server certificate matches the common name used when establishing the connection.
Server-to-server remote procedure calls
Companion server and SSL
You can use a companion server to configure Adaptive Server for failover. You must configure both the primary and secondary servers with the same SSL and RPC configuration. When connections fail over or fail back, security sessions are reestablished with the connections. Component Integration Services, RepAgent, Distributed Transaction Management, and other modules in Adaptive Server use Client-Library to establish connections to servers other than Adaptive Server. The remote server is authenticated by its certificate. The remote server authenticates the Adaptive Server client connection for RPCs with user name and password.
Open Client connections
621
Enabling SSL
Adaptive Server determines which security service it will use for a port based on the interface file (sql.ini on Windows).
Enabling SSL
1 2 3
Generate a certificate for the server. Create a trusted roots file. Use sp_configure to enable SSL. From a command prompt, enter:
sp_configure "enable ssl", 1
4 5 6
1 enables the SSL subsystem at start-up, allocates memory, and SSL performs wire-level encryption of data across the network. 0 (the default) disables SSL. This value is the default.
Add the SSL filter to the interfaces file. See Creating server directory entries on page 625. Use sp_ssladmin to add a certificate to the certificates file. See Administering certificates on page 625. Shut down and restart Adaptive Server.
Note To request, authorize, and convert third-party certificates, see the Utility Guide for information on the certauth, certreq, and certpk12 tools.
Unlike other security services, such as DCE, Kerberos, and NTLAN, SSL relies neither on the Security section of the Open Client/Open Server configuration file libtcl.cfg, nor on objects in objectid.dat. The System Administrator should consider memory use by SSL when planning for total physical memory. You need approximately 40K per connection (connections include user connections, remote servers, and network listeners) in Adaptive Server for SSL connections. The memory is reserved and preallocated within a memory pool and is used internally by Adaptive Server and SSL Plus libraries as requested.
Obtaining a certificate
The System Security Officer installs server certificates and private keys for Adaptive Server by:
622
CHAPTER 19
Using third-party tools provided with existing public-key infrastructure already deployed in the customer environment. Using the Adaptive Server certificate request tool in conjunction with a trusted third-party CA.
To obtain a certificate, you must request a certificate from a CA. If you request a certificate from a third party and that certificate is in PKCS #12 format, use the certpk12 utility to convert the certificate into a format that is understood by Adaptive Server. To test the Adaptive Server certificate request tool and to verify that the authentication methods are working on your server, Adaptive Server provides a tool, for testing purposes, that allows you to function as a CA and issue CA-signed certificate to yourself. The main steps to creating a certificate for use with Adaptive Server are: 1 2 3 4 5 6
Third-party tools to request certificates
Generate the public and private key pair. Securely store the private key. Generate the certificate request. Send the certificate request to the CA. After the CA signs and returns the certificate, store it in a file and append the private key to the certificate. Store the certificate in the Adaptive Server installation directory.
Most third-party PKI vendors and some browsers have utilities to generate certificates and private keys. These utilities are typically graphical wizards that prompt you through a series of questions to define a distinguished name and a common name for the certificate. Follow the instructions provided by the wizard to create certificate requests. Once you receive the signed PKCS #12-format certificate, use certpk12 to generate a certificate file and a private key file. Concatenate the two files into a servername.crt file, where servername is the name of the server, and place it in the certificates directory under $SYBASE/$SYBASE_ASE. See the Utility Guide.
623
Using Adaptive Server tools to request and authorize certificates
Adaptive Server provides two tools for requesting and authorizing certificates. certreq generates public and private key pairs and certificate requests. certauth converts a server certificate request to a CA-signed certificate.
Warning! Use certauth only for testing purposes. Sybase recommends that you use the services of a commercial CA because it provides protection for the integrity of the root certificate, and because a certificate that is signed by a widely accepted CA facilitates the migration to the use of client certificates for authentication.
Preparing the servers trusted root certificate is a five-step process. Perform the first two steps to create a test trusted root certificate so you can verify that you are able to create server certificates. Once you have a test CA certificate (trusted roots certificate) repeat steps three through five to sign server certificates. 1 2 3 4 5 Use certreq to request a certificate. Use certauth to convert the certificate request to a CA self-signed certificate (trusted root certificate). Use certreq to request a server certificate and private key. Use certauth to convert the certificate request to a CA-signed server certificate. Append the private key text to the server certificate and store the certificate in the servers installation directory.
For information about Sybase utilities, certauth, certreq, and certpk12 for requesting, authorizing and converting third-party certificates, see the Utility Guide.
Note certauth and certreq are dependent on RSA and DSA algorithms. These tools only work with crypto modules that use RSA and DSA algorithms to construct the certificate request.
Adaptive Server supports the Certicom Corp. cryptographic engine, Security Builder, which supports RSA and DSA algorithms to construct the certificate requests.
624
CHAPTER 19
Creating server directory entries

Adaptive Server accepts client logins and server-to-server RPCs. The address and port numbers where Adaptive Server accepts connections are configurable so you can specify multiple networks, different protocols, and alternate ports. In the interfaces file, SSL is specified as a filter on the master and query lines, whereas security mechanisms such as DCE or Kerberos are identified with a SECMECH line. The following example shows a TLI-based entry for an Adaptive Server using SSL in a UNIX environment: An entry for an Adaptive Server with SSL and DCE security mechanisms on UNIX might look like:
SYBSRV1 master tcp ether myhostname myport1 ssl query tcp ether myhostname myport1 ssl master tcp ether myhostname myport2 SECMECH 1.3.6.1.4.897.4.6.1
An entry for the server with SSL and Kerberos security mechanisms on NT might look like:
[SYBSRV2] query=nlwnsck, 18.52.86.120,2748,ssl master=nlwnsck 18.52.86.120,2748,ssl master=nlwnsck 18.52.86.120,2749 secmech=1.3.6.1.4.897.4.6.6
The SECMECH lines for SYBSRV1 and SYBSRV2 in the examples contain an object identifier (OID) that refers to security mechanisms DCE and Kerberos, respectively. The OID values are defined in: UNIX $SYBASE/$SYBASE_OCS/config/objectid.dat NT %SYBASE%\%SYBASE_OCS\ini\objectid.dat
In these examples, the SSL security service is specified on port number 2748(0x0abc).
Note The use of SSL concurrently with a SECMECH security mechanism is
intended to facilitate migration from SECMECHs to SSL security.
Administering certificates
To administer SSL and certificates in Adaptive Server, use sp_ssladmin. sso_role is required to execute the stored procedure.
625
sp_ssladmin is used to:
Add local server certificates. You can add certificates and specify the password used to encrypt private keys, or require input of the password at the command line during start-up. Delete local server certificates. List server certificates.
The syntax for sp_ssladmin is:

sp_ssladmin {[addcert, certificate_path [, password|NULL]] [dropcert, certificate_path] [lscert] [help]} [lsciphers] [setciphers, {"FIPS" | "Strong" | "Weak" | "All" | quoted_list_of_ciphersuites}]
For example:
sp_ssladmin addcert, "/sybase/ASE-12_5/certificates/Server1.crt", "mypassword"
This adds an entry for the local server, Server1.crt, in the certificates file in the absolute path to /sybase/ASE-12_5/certificates (x:\sybase\ASE-12_5\certificates on Windows). The private key is encrypted with the password mypassword. The password should be the one specified when you created the private key. Before accepting the certificate, sp_ssladmin verifies that: The private key can be decrypted using the provided password (except when NULL is specified). The private key and public key in the certificate match. The certificate chain, from root CA to the server certificate, is valid. The common name in the certificate matches the common name in the interfaces file.
626
CHAPTER 19
If the common names do not match, sp_ssladmin issues a warning. If the other criteria fails, the certificate is not added to the certificates file.
Warning! Adaptive Server limits passwords to 64 characters. In addition, certain platforms restrict the length of valid passwords when creating server certificates. Select a password within these limits:
Sun Solaris both 32- and 64-bit platforms, 256 characters. Linux 128 characters. IBM both 32- and 64-bit platforms, 32 characters. HP both 32- and 64-bit platforms, 8 characters. Windows NT 256 characters.
The use of NULL as the password is intended to protect passwords during the initial configuration of SSL, before the SSL-encrypted session begins. Since you have not yet configured SSL, the password travels unencrypted over the connection. You can avoid this by specifying the password as NULL during the first login. When NULL is the password, you must start dataserver with a -y flag, which prompts the administrator for the private-key password at the command line. After restarting Adaptive Server with an SSL connection established, use
sp_ssladmin again, this time using the actual password. The password is then
encrypted and stored by Adaptive Server. Any subsequent starts of Adaptive Server from the command line use the encrypted password; you do not have to specify the password on the command line during start-up. An alternative to using a NULL password during the first login is to avoid a remote connection to Adaptive Server via isql. You can specify localhost as the hostname in the interfaces file (sql.ini on Windows) to prevent clients from connecting remotely. Only a local connection can be established, and the password is never transmitted over a network connection.
Note Adaptive Server has sufficient memory in its network memory pool to allow sp_ssladmin addcert to set the certificate and private key password with
its default memory allocations. However, if another network memory consumer has already allocated the default network memory, sp_ssladmin may fail and display this error to the client:
Msg 12823, Level 16, State 1: Server 'servername', Procedure 'sp_ssladmin', Line 72:
627
Command 'addcert' failed to add certificate path /work/REL125/ASE-12_5/certificates/servername.crt, system error: ErrMemory. (return status = 1)
Or the following message may appear in the error log:

... ssl_alloc: Cannot allocate using ubfalloc(rnetmempool, 131072)
As a workaround, you can increase the additional network memory configuration parameter. Adaptive Server needs about 500K bytes of memory for sp_ssladmin addcert to succeed, so increasing additional network memory by this amount may allow it to succeed. This memory is reused by the network memory pool when needed, or you can return additional network memory to its previous value after sp_ssladmin has successfully completed.
Performance
There is additional overhead required to establish a secure session, because data increases in size when it is encrypted, and it requires additional computation to encrypt or decrypt information. The additional memory requirements for SSL increases the overhead by 50-60 percent for network throughput or for establishing a connection. You must have approximately 40K more memory for each user connection.
Cipher Suites
During the SSL handshake, the client and server negotiate a common security protocol via a CipherSuite. Cipher Suites are preferential lists of key-exchange algorithms, hashing methods, and encryption methods used by SSL-enabled applications. For a complete description of Cipher Suites, visit the Internet Engineering Task Force (IETF) organization at http://www.ietf.org/rfc/rfc2246.txt. By default, the strongest CipherSuite supported by both the client and the server is the CipherSuite that is used for the SSL-based session.
628
CHAPTER 19
Adaptive Server supports the Cipher Suites that are available with the SSL Plus library API and the cryptographic engine, Security Builder, both from Certicom Corp.
Note The Cipher Suites listed conform to the Transport Layer Specification
(TLS). TLS is an enhanced version of SSL 3.0, and is an alias for the SSL version 3.0 Cipher Suites.
@@ssl_ciphersuite
The Transact-SQL global variable @@ssl_ciphersuite allows users to know which cipher suite was chosen by the SSL handshake and verify that an SSL or a non-SSL connection was established. Adaptive Server sets @@ssl_ciphersuite when the SSL handshake completes. The value is either NULL, indicating a non-SSL connection, or a string containing the name of the cipher suite chosen by the SSL handshake. For example, an isql connection using SSL protocol displays the cipher suite chosen for it.
1> select @@ssl_ciphersuite 2> go
Output:
-----------------------------TLS_RSA_WITH_AES_128_CBC_SHA (1 row affected)
Setting SSL cipher suite preferences

In Adaptive Server, sp_ssladmin has two command options to display and set cipher suite preferences: lsciphers and setciphers. With these options, the set of cipher suites that Adaptive Server uses can be restricted, giving control to the System Security Officer over the kinds of encryption algorithms that may be used by client connections to the server or outbound connections from Adaptive Server. The default behavior for use of SSL cipher suites in Adaptive Server is the same as in earlier versions; it uses an internally defined set of preferences for cipher suites. To display the values for any set cipher suite preferences, enter:
629
sp_ssladmin lsciphers
To set a specific cipher suite preference, enter:

sp_ssladmin setciphers, {"FIPS" | "Strong" | "Weak" | "All" | quoted_list_of_ciphersuites }
where:
FIPS is the set of encryptions, hash, and key exchange algorithms that are FIPS-compliant. The algorithms included in this list are AES, 3DES, DES, and SHA1. Strong is the set of encryption algorithms using keys longer than 64
bits.
Weak is the set of encryption algorithms from the set of all supported cipher suites that are not included in the strong set. All is the set of default cipher suites. quoted_list_of_ciphersuites specifies a set of cipher suites as a comma-
separated list, ordered by preference. Use quotes () to mark the beginning and end of the list. The quoted list can include any of the predefined sets as well as individual cipher suite names. Unknown cipher suite names cause an error to be reported, and no changes are made to preferences. The detailed contents of the predefined sets are in Table 19-1 on page 631.
sp_ssladmin setciphers sets cipher suite preferences to the given ordered list. This restricts the available SSL cipher suites to the specified set of FIPS, Strong, Weak, All, or a quoted list of cipher suites. This takes effect on the next listener started, and requires that you restart Adaptive Server to ensure that all listeners use the new settings.
You can display any cipher suite preferences that have been set using sp_ssladmin lsciphers. If no preferences have been set, sp_ssladmin lsciphers returns 0 rows to indicate no preferences are set and Adaptive Server uses its default (internal) preferences.
630
CHAPTER 19
Table 19-1: Predefined cipher suites in Adaptive Server Set name FIPS Cipher suite names included in the set TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_RC4_128_MD5 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_DHE_DSS_WITH_RC4_128_SHA TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA Weak TLS_RSA_WITH_DES_CBC_SHA TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC4_56_SHA TLS_DHE_DSS_EXPORT1024_WITH_RC4_56_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_RC4_40_MD5 TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
Strong
631
Set name All
Cipher suite names included in the set TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_RC4_128_MD5 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_DHE_DSS_WITH_RC4_128_SHA TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC4_56_SHA TLS_DHE_DSS_EXPORT1024_WITH_RC4_56_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_RC4_40_MD5 TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
Table 19-2 describes Cipher suites no longer supported for Adaptive Server 15.0 and later. 15.0. Attempts to use use any dropped cipher suite results in an SSLHandshake failure and a failure to connect to Adaptive Server.
632
CHAPTER 19
Table 19-2: Dropped Cipher suites Set name FIPS Strong Weak Cipher suite names dropped from the set TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA None dropped TLS_RSA_EXPORT1024_WITH_RC4_56_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA Others TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA TLS_DH_anon_EXPORT_WITH_RC4_40_MD5 TLS_DH_anon_WITH_3DES_EDE_CBC_SHA TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_RC4_128_MD5 TLS_RSA_WITH_NULL_MD5 TLS_RSA_WITH_NULL_SHA
Examples sp_ssladmin
On initial startup, before any cipher suite preferences have been set, no preferences are shown by sp_ssladmin lscipher.
1> sp_ssladmin lscipher 2> go
Output:
Cipher Suite Name Preference -------------------------(0 rows affected) (return status = 0)
The following example specifies the set of cipher suites that use FIPS algorithms.
1> sp_ssladmin setcipher, 'FIPS' The following cipher suites and order of preference are set for SSL connections: Cipher Suite Name Preference ---------------------------------------------------------------- ----------TLS_RSA_WITH_AES_256_CBC_SHA 1 TLS_RSA_WITH_AES_128_CBC_SHA 2 TLS_RSA_WITH_3DES_EDE_CBC_SHA 3 TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA 4 TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA 5 TLS_RSA_WITH_DES_CBC_SHA 6 TLS_DHE_DSS_WITH_DES_CBC_SHA 7
633
TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA
8 9 10
A preference of 0 (zero) sp_ssladmin output indicates a cipher suite is not used by Adaptive Server. The other, non-zero numbers, indicate the preference order that Adaptive Server uses the algorithm during the SSL handshake. The client side of the SSL handshake chooses one of these cipher suites that matches its list of accepted cipher suites. This example uses a quoted list of cipher suites to set preferences in Adaptive Server:
1> sp_ssladmin setcipher, 'TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA' 2> go The following cipher suites and order of preference are set for SSL connections: Cipher Suite Name Preference ---------------------------------------------------------------- ----------TLS_RSA_WITH_AES_128_CBC_SHA 1 TLS_RSA_WITH_AES_256_CBC_SHA 2
Other considerations
When you upgrade to Adaptive Server version 12.5.3, the cipher suite preferences are the server defaults, and sp_ssladmin option lscipher displays no preferences. The server uses its default preferences, those defined by All. The System Security Officer should consider the security policies employed at his or her site and the available SSL cipher suites to decide whether to restrict cipher suites and which cipher suites are appropriate for the security policies. If you upgrade from Adaptive Server version 12.5.3 and have set cipher suite preferences, those preferences remain after upgrade. After the upgrade is complete, review your server's cipher suite preferences with current security policies and the lists of supported and unsupported cipher suites found in tables Table 19-1. Omit any cipher suites that are not supported. If tou have set SSL cipher suite preferences and want to remove all preferences from the server and use default preferences, delete the preferences from their storage location in system catalogs using the following commands:
1> sp_configure 'allow updates to system tables', 1 2> go 1> delete from master..sysattributes where class=24 2> go
634
CHAPTER 19
1> sp_configure 'allow updates to system tables', 0 2> go
These commands can be executed only by the System Security Officer or System Administrator.
Kerberos confidentiality
You can also ensure the confidentiality of all messages with Adaptive Server. To require all messages into and out of Adaptive Server to be encrypted, set the msg confidentiality reqd configuration parameter to 1. If this parameter is 0 (the default), message confidentiality is not required but may be established by the client. For example, to require that all messages be encrypted, execute:
sp_configure "msg confidentiality reqd", 1
For more information about using Message Confidentiality with Kerberos and other Security Services supported, see Administering network-based security on page 454.
Dumping and loading databases with password protection

You can protect your database dump from unauthorized loads using the password parameter of the dump database command. If you include the password parameter when you make a database dump, you must also include this password when you load the database. The partial syntax for the password-protected dump database and load database commands are:
dump database database_name to file_name [ with passwd = password ] load database database_name from file_name [ with passwd = password ]
where: database_name is the name of the database that is being dump or loaded.
635
Dumping and loading databases with password protection
file_name is the name of the dump file. password is the password you provide to protect the dump file from unauthorized users.
Your password must be between 6 and 30 characters long. If you provide a password that is less than 6 or greater than 30 characters, Adaptive server issues an error message. If you issue an incorrect password when you attempt to load the database, Adaptive Server issues an eror message and the command fails. For example, the following uses the password bluesky to protect the database dump of the pubs2 database:
dump database pubs2 to /Syb_backup/mydb.db with passwd = bluesky
The database dump must be loaded using the same password:

load database pubs2 from /Syb_backup/mydb.db with passwd = bluesky
Passwords and earlier versions of Adaptive Server

You can use the password-protected dump and load commands only with Adaptive Server version 12.5.2 and later. If you use the password parameter on a dump of a 12.5.2 version of Adaptive Server, the load fails if you try to load it on an earlier version of Adaptive Server.
Passwords and character sets

You can load the dump only to another server with the same character set. For example, if you attempt to load a dump from a server that uses an ASCII character set to a server that uses a non-ASCII character set, the load fails because the value of the ASCII password is different from the non-ASCII password. Passwords entered by users are converted to Adaptive Servers local character set. Because ASCII characters generally have the same value representation across character sets, if a users password is in an ASCII character set, the passwords for dump and load are recognized across all character sets.
636
Index
Symbols
& (ampersand) translated to underscore in login names 464 (apostrophe) converted to underscore in login names 464 * (asterisk) converted to pound sign in login names 465 select and 566 \ (backslash) translated to underscore in login names 464 ^ (caret) converted to dollar sign in login names 465 : (colon) converted to underscore in login names 464 , (comma) converted to underscore in login names 464 in SQL statements xxiii {} (curly braces) converted to dollar sign in login names 465 in SQL statements xxiv ... (ellipsis) in SQL statements xxv = (equals sign) converted to underscore in login names 464 ! (exclamation point) converted to dollar sign in login names 465 < (left angle bracket) converted to dollar sign in login names 465 (left quote), converted to underscore in login names 464 - (minus sign) converted to pound sign in login names 465 () (parentheses) converted to dollar sign in login names 465 % (percent sign) error message placeholder 327 translated to underscore in login names 464 . (period) converted to dollar sign in login names 465 | (pipe)
converted to pound sign in login names 465 + (plus) converted to pound sign in login names 465 ? (question mark) converted to dollar sign in login names 465 ?? (question marks) for suspect characters 321 (quotation marks) converted to pound sign in login names 465 enclosing parameter values 13 enclosing punctuation 379 enclosing values 377 > (right angle bracket) converted to underscore in login names 464 (right quote), converted to underscore in login names 464 ; (semicolon) converted to pound sign in login names 465 / (slash) converted to pound sign in login names 465 [ ] (square brackets) converted to pound sign in login names 465 in SQL statements xxiv ~ (tilde) converted to underscore in login names 464 $ISA 495 @@client_csexpansion global variable 310
Numerics
7-bit ASCII character data, character set conversion for 315
A
abort tran on log full database option 263 abstract plan cache configuration parameter abstract plan dump configuration parameter
79 80
637
Index
abstract plan load configuration parameter 80 abstract plan replace configuration parameter 81
access 528 restricting guest users 383 access control, row level 528 access permissions. See object access permissions access protection. See permissions; security functions access rules alter table command 534 bcp 534 creating 531 creating and binding 529 dropping 530 examples 532 extended 531 sample table 529 accounting, chargeback 431 accounts, server See logins;users ACF (Application Context Facility), problem-solving with 545 activating roles 399 adding comments to the audit trail 577 database devices 184, 246253 date strings 308 group to a database 380381 guest users 382 logins to server 377379 months of the year 308 remote logins 384, 442444 remote servers 436449 users to a database 184, 376 users to a group 381 additional network memory configuration parameter 81 address, server 16 administering security, getting started 363367 aggressive garbage collection 343 priority level 344 aggressive housekeeper 343 aliases server 438 aliases, user See also logins;users creating 408 database ownership transfer and 504
dropping 410, 511 help on 410 all keyword grant 509, 517 revoke 517 allocation pages 246 allocation units 246 See also size; space allocation allow backward scans configuration parameter 84 allow nested triggers configuration parameter 85 allow nulls by default database option 263 allow procedure grouping configuration parameter 85 allow remote access configuration parameter 86, 448 allow resource limits configuration parameter 86 allow sendmsg configuration parameter 87 allow sql server async i/o configuration parameter 87 allow updates configuration parameter (now called allow updates to system tables) 14 allow updates to system tables configuration parameter 14, 88 alter database command omitting database device and 254, 256 system tables and 243 alter role command 393, 421 alternate identity. See alias, user alternate languages. See languages, alternate and (&) translated to underscore in login names 464 ansi_permissions option, set permissions and 512 apostrophe converted to underscore in login names 464 Application Context Facility 538 granting and revoking privileges 539 setting permissions 538 valid users 539 application contexts built-in functions 540 using 540 application design 184 applications proxy authorization and 560 Arabic character set support 279 ASCII characters character set conversion and 315
638
Index
assigning login names 365 asterisk (*) converted to pound sign in login names 465 select and 566 asynchronous I/O limiting Server requests for 143 asynchronous prefetch configuring 127 @@char_convert global variable 310 @@client_csid global variable 310 @@client_csname global variable 310 @@langid global variable 312 @@language global variable 312 @@max_connections global variable 183 @@maxcharlen global variable 310 @@ncharsize global variable 310 audit options displaying 577 examples 595 setting 594 audit queue 576, 587 audit queue size configuration parameter 89, 576, 587 audit trail 31, 573, 603 adding comments 577, 601 changing current audit table 582 illustration with multiple audit tables 575 managing 582 querying 603 stacktrace of error messages 328 threshold procedure for 582 auditing 372, 573, 573603 See also audit options adding comments to the audit trail 577 configuration parameters 577 devices for 578 disabling 577 displaying options for 577 enabling 365, 577 enabling and disabling 589 installing 578 managing the audit trail 582 managing the transaction log 588 overview 573 queue, size of 89, 576 sybsecurity database 31, 574 sysaudits_01...sysaudits_08 tables 603 system procedures for 577 threshold procedure for 582 turning on and off 589 auditing configuration parameter 89, 589 authentication 452, 453 mutual 453 authorizations. See permissions auto identity database option 264 automatic operations character conversions in logins 464 primary and secondary database dumps 266
B
Backing up master database 54 backslash (\) translated to underscore in login names 464 backtracing errors. See error logs Backup Server error messages 337 shutting down 352 tape retention in days configuration parameter 226 backups 4245 hints 4245 Baltic character set support 279 base tables. See tables bcp (bulk copy utility) character set conversion and 322, 323 fast version 267 security services and 475 select into/bulkcopy/pllsort and 267 sort order changes and 300 with access rules 534 Big 5 similarities to CP 950 279 binary expressions xxv binary sort order of character sets character set changes and database dumps 300 brackets. See square brackets [ ] built-in functions security 479
639
Index
bytes character
320
C
CA certificates 617 location of 620 trusted root certificate 617 cache partitions configuring 127 cache, procedure 200 caches, data database integrity errors and 336 calls, remote procedure 435449 timeouts 439 cascade option, revoke 510 case sensitivity in SQL xxiv certificates administration of 625 authorizing 624 CA certificates 617 defined 617 obtaining 622 public-key cryptography 617 requesting 624 self-signed CA 624 server certificates 617 chains, ownership 568 changing See also updating configuration parameters 76, 447 database options 261270 Database Owners 503 default database 405 passwords for login accounts 404 server logins 405 system tables, dangers of 12, 14 user information 403407 users group 406 users identity 555 @@char_convert global variable 310 character expressions xxv character set conversions 313, 321322 character sets 100
See also Japanese character sets Arabic 279 Baltic 279 changing 298 conversion between client and file system 323 conversion between client and server 314316 conversion between client and terminal 323 conversion errors 320 conversion paths supported 314320 Cyrillic-script 279 default 284 definition 277 definition files 309 Eastern European 279 encoding in different 313 European currency symbol and 280 for language groups 279 Greek 279 Hebrew 279 ID number 100 Japanese 279 Korean 279 multibyte 306 multibyte, changing to 307 reindexing after configuring 304307 Russian 279 Simplified Chinese 279 Thai 279 Traditional Chinese 279 translation files, terminal-specific 309, 324 Turkish 279 Unicode 279 upgrading text values after changing 306 Vietnamese 279 Western European 279 character sets and password-protected dumps 636 characters disallowed in login names 464 that cannot be converted 320 chargeback accounting 431 charset.loc file 309 charsets directory 310 checking passwords for at least one character 423 checkpoint command setting database options and 270 checkpoint process 202
640
Index
no chkpt on recovery database option 266 recovery interval parameter and 203 trunc log on chkpt database option 202, 268
269
checktable option, dbcc
305
cipher suites defined 628 supported 628

cis bulk insert batch size configuration parameter
90, 91
cis connect timeout configuration parameter 91 cis cursor rows configuration parameter 91 cis packet size configuration parameter 92 cis rpc handling configuration parameter 93
@@client_csid global variable 310 @@client_csname global variable 310 clients assigning client name, host name, and application name 407 character set conversion 323 Closed Problem Reports 353 cntrltype option disk init 253 colon (:) converted to underscore in login names 464 column name unqualified 333 columns permissions on 509, 564 comma (,) converted to underscore in login names 464 in SQL statements xxiii command delete 343 disk resize 257260 reorg reclaim_space 344 comments adding to audit trail 577, 601 common.loc file 311 comparing values datatype problems 332 concrete identification 511 confidential data 452 configuration (server) character sets 298 message language 298303
network-based security 455 sort orders 298306 configuration file default name and location 62 specifying at start-up 67 storage of configured value 62 configuration file configuration parameter 115, 211, 212 configuration parameter max native threads per engine 147 rtm thread idle wait period 207 configuration parameters 79234 audit-related 577 changing 447 chargeback accounting 432 default settings of 61 dtm detach timeout period 343 help information on 64 housekeeper free write percent 343 listing values of 65 remote logins and 86, 447449 configuring Kerberos 481 conflicting permissions 524 See also permissions connecting to Adaptive Server 16 connections directory services 17 interfaces files 16 maximum user number 183 consistency checking databases 44 constants xxv context-sensitive protection 566 conventions Transact-SQL syntax xxiiixxv copying selected data See insert command; select command CP 1252 similarities to ISO 8859-1 279 CP 950 similarities to Big 5 279 cp437 character set 100 cp850 character set 100 CPR files 353
93, 111,
641
Index
cpu accounting flush interval configuration parameter
current audit table configuration parameter
95, 582
94, 432 cpu grace time configuration parameter 95 CPU usage per user 431 create database command default database size configuration parameter and 100 model database and 28 omitting database device and 254, 256 permission to use 503 system tables and 10 create index command 239, 244 create procedure command 14 create role command 393 create rule command, new functionality 528 create rule syntax 528 create rule , syntax 529 create table command 239 create trigger command 510 Creating databases 53 guest users 54 users 55 creating database objects 239 databases 503 groups 380381 guest users 382 master database 241 model database 241 segments 241 stored procedures 14 sybsecurity database 579 system procedures 14 system tables 10 tempdb database 241 triggers 510 user aliases 408 user-defined error messages 330 credential, security mechanism and 453 cs_connection command, number of user connections and 184 curly braces ({}) converted to dollar sign in login names 465 in SQL statements xxiv
current database 332 current usage statistics 432 current user set proxy and 559 cursors row count, setting 92 cyrillic character set support 279
D
DAC. See discretionary access control (DAC) data See also permissions confidentiality of 452 encryption 452 integrity of 452, 465 losing unlogged 268 packets 449 data caches configuring partitions 127 database integrity errors and 336 data dictionary. See system tables database administration 37 database device space See segments; space allocation database devices 245 See also disk mirroring; dump devices; master device adding 246253 default 256257 dropping 255 fragments 243 information about 254 initializing 245253 names of 241, 247 number of server-usable 165 placing objects on 240 database dumps password-protected 635 database object owners 6 See also database owners permissions 7, 502, 556 status not transferable 400 tasks of 6 database objects See also individual object names
642
Index
access permissions for 7, 508 assigning to devices 240 controlling user creation of 27 creating 27, 239, 506 dependent 569 dropping 506 dropping users who own 400 errors affecting 335 finding 331 maximum number of open 177 ownership 6, 400, 506 permissions on 506 triggers on 572 database options 261271 changing 270 listing 262 setting 263269 showing settings 263 Database Owners 6 changing 503 error responsibilities of 331, 333 login name 4, 6 name inside database 400, 409 objects not transferred between 400 password forgotten by 390 permissions granted by 517 permissions of 6, 502, 504 See also database object owners 501 setuser command and 555556 several users as same 408 tasks of 6 permissions database size configuration variable 54 Databases backing up 54 creating 53 guest users 54 databases See also database objects; user databases adding users 381384 auditing 579 backing up 28, 42 changing users default 378 creation permission 503 default 27, 378, 379, 405 default storage for 25, 256 dropping users from 399 dumping 42 errors affecting 335 integrity concerns 335 loading after character set change 301 loading after sort order change 301 new 28 number of open 173 options 261270 ownership of 503 sequence numbers for recovery 267 size 28 system 23 database-specific dbcc, master and 521 dataserver command using to unlock logins and roles 421 date parts alternate language 308 dates adding date parts 308 alternate language 308 display formats 311 format in error messages 329 days alternate language 308 dbcc and storage_admin_role command 521 dbcc (database consistency checker) 44 database damage and 331, 335 database-specific commands 520, 521 defined 520 described 520 discretionary access control 520 grant dbcc and roles 521 grant dbcc and users in databases 521 grant dbcc checkstorage command and 521 server-wide commands 520, 521 tune command and 520 when to use 335 DB-Library programs number of user connections and 184 dbo use only database option 264 dbo user name 4, 6 dbprocess command, number of user connections and 184 DCE (Distributed Computing Environment) security mechanism 461
643
Index
ddl in tran database option
264
deactivating roles
399
deadlock checking period configuration parameter 97 deadlock pipe active configuration parameter 97, 98 deadlock pipe max messages configuration parameter
98
deadlock retries configuration parameter
98 deadlocks 332 descending scans and 84 deckanji character set 100 default character set id configuration parameter 100 default database changing users 405 default database devices designating 256 default database size configuration parameter 100 default exp_row_size percent configuration parameter 101 default fill factor percent configuration parameter 102 default language id configuration parameter 102 default network packet size configuration parameter 103 default segment 241 default settings changing character set 298307 changing sort order 300306 character set ID number 100 configuration parameters 61 databases 27, 378, 379 language 102, 378 permissions 28 sort order 104 system databases at installation 241 default sortorder id configuration parameter 104 default XML sortorder configuration parameter 105 defaulton | defaultoff option, sp_diskdefault 256 defaults See also database objects defncopy utility command See also Utility Programs manual character set conversion and 322, 323 delete command 343 delete statistics syntax 513 deleting See also dropping files 255 users 55
denying access to a user 401, 402 descending scans deadlocks and 84 detached transactions 107 development server 36 device fragments 243 device shrinkage, disk resize 258 devices 245 See also database devices; dump devices; master device adding 246253 audit system 578 dropping 255 information listings on 254 initializing 245253 names for physical 247 number of user connections and 183, 184 using separate 240 digital signature defined 617 nonrepudiation 617 public-key cryptography 617 tamper detection 617 direct updates to system tables 88 directory drivers 456 example of entry in libtcl.cfg file 459 directory entries, creating 625 directory services in libtcl.cfg file 17, 457 directory structure character sets 310 internationalization files 310 localization files 312 *.loc files 312 dirty pages 202 disable character set conversions configuration parameter 105 disable disk mirroring configuration parameter 106 disabling auditing 577 discretionary access control (DAC) 501572 See also permissions granting and revoking permissions 507 of dbcc commands 520 overview 370 stored procedures and 567 System Administrators and 502
644
Index
user alias and 555 views for 565 disk controllers 253 disk devices See also database devices; dump devices; space allocation disk I/O configuration parameters for 167 database loads and 145, 164, 170 disk i/o structures configuration parameter 106 disk init command 238, 243, 246253 disk mirror command 239 disk mirroring disabling 106 enabling 106 recovery and 240 status in sysdevices table 255 disk reinit command See also disk init command disk resize 238, 257260 device shrinkage 258 insufficient disk space 258 minimum size 258 mirroring 258 specifying devive size 259 syntax 258 using 257 disks See database devices; devices; dump devices Distributed Transaction Management (DTM) 31 Distributed Transaction Processing (DTP) 31 drop logins option, sp_dropserver 442 drop role command 400 dropping database devices 255 dump devices 255 groups 400 guest users of master 383 logins from servers 402 master device from default space pool 256 remote logins 441, 442 servers 441 user aliases 410, 511 user from a database 399 user-defined roles 400 users from servers 402 users who own database objects 400
dscp utility for specifying security mechanism 461 dsedit utility for security services 461 dsync option disk init 255 dtm detach timeout period configuration parameter
107, 343
dtm lock timeout period configuration parameter dump database command disk init and 246
107
master database and 43 model database and 28 dump database syntax 635 dump devices dropping 255 information about 254 sysdevices table and 243 dump on conditions configuration parameter dump transaction command trunc log on chkpt and 268269 dump, database 42 dynamic configuration parameters 62
108
E
Eastern Europe character set support 279 editing. See changing; updating ellipsis (...) in SQL statements xxv empty pages, accumulating 344 enable cis configuration parameter 110, 111, 112, 118 enable DTM configuration parameter 110 enable housekeeper GC configuration parameter 113, 344 enable java configuration parameter 111, 114 enable metrics capture configuration parameter 116 enable monitoring configuration parameter 116 enable pam user auth configuration parameter 116 enable real time messaging configuration parameter 117 enable rep agent threads configuration parameter 117 enable row level access control configuration parameter 118 enable unicode conversions configuration parameter 318
645
Index
enable xact coordination configuration parameter
121 enabling auditing 365, 577 SSL 622 encoding characters 313 encryption data 452 key exchange 616 public/private key 616 public-key cryptography 616 symmetric key 616 engines identification numbers 329 number of 150 enivronment variable $ISA 495 error logs 46, 334 creation and ownership 328 format 329 location 15 purging 329 error messages 327336 altering server-provided 311, 330 character conversion 321 creating user-defined 330 for fatal errors 334336 numbering of 327 severity levels of 330336 user-defined 330 errorlog pipe active configuration parameter 122 errorlog pipe max messages configuration parameter 122 errors See also error logs; error messages character conversion 320 fatal 334336 logging 328 multiple 326 reporting of 336 server responses to 325336 state numbers 325 types of information logged 15 user 331, 331334 esp execution priority configuration parameter 123 esp execution stacksize configuration parameter 123 esp unload dll configuration parameter 124
eucjis character set 100 European currency symbol character sets 280 event buffers per engine configuration parameter 124 event log computer name configuration parameter 125 event logging configuration parameter 126 exclamation point (!) converted to dollar sign in login names 465 executable code size + overhead configuration parameter 126 execution ESPs and XP Server priority 123 expand_down parameter sp_activeroles 416 expiration interval for passwords 425 expiration of passwords 425 expired passwords 225 expressions types of xxv extended cache size configuration parameter 127 extended stored procedures configuration parameters 123236 extended UNIX character set 100
F
failures, media 336 fatal errors backtrace from kernel 328, 334 error messages for 334336 severity levels 19 and up 334336 file descriptors 183 maximum per-process configured for your operating system 186 files character set translation (.xlt) 309 Closed Problem Reports (CPRs) 353 deleting 255 error log 16, 328 interfaces 16 internationalization 309 libtcl.cfg file 17 localization 311 System Problem Reports (SPRs) 353
646
Index
fillfactor
default fill factor percent configuration parameter
102 finding database objects 331 user IDs 413 user names 413 users in a database 412 fix_text option, dbcc 306307 floating-point data xxv For load 54 formats date, time, and money 311 locale, unsupported 308309 formulas user requirements and 184 forwarded rows reducing with default exp_row_size configuration parameter 101 fragments, device space 243 french character set support 279 functions security 479
G
garbage collection aggressive test 343 lazy test 343 garbage collector configuring aggressive 344 housekeeper utility 343 German character set support 279 get_appcontext 540, 541 global async prefetch limit configuration parameter 127 global cache partition number configuration parameter 127 grant command 502, 507525 all keyword 517 public group and 509 roles and 526
grant dbcc
roles and 521 users in databases and 521 grant option sp_helprotect 562 grant option for option, revoke 510 granting access permissions 6 create trigger permission 510 object creation permissions 6 proxy authorization permission 519 roles to roles 395 roles with grant role 526 granting and revoking permissions for users and roles 513 granting default permissions on system tables 521 523 Greek character set support 279 groups See also public group changing 406 conflicting permissions and 524 creating 380381 dropping 400 grant and 512 naming 380 Public 55 revoke and 513 groups, language 279 Guest users creating 54 databases 54 guest users 505 adding 382 creating 382 permissions 383 sample databases and 32, 383 guidelines, security 364
H
Halloween problem avoiding with unique auto_identity index option 269 hardware
647
Index
errors 336 hash defined 617 message digest 617 hash buckets (lock) 140 heap memory per user configuration parameter 128 Hebrew character set support 279 hierarchy of permissions. See permissions hierarchy of roles. See role hierarchies high availability installhasvss script 112 insthasv script 112 setting enable HA 112 histogram tuning factor configuration parameter 129 housekeeper chores 343 configuration parameter license information 343 housekeeper free write percent configuration parameter 130, 343 housekeeper garbage collector 343 housekeeper task configuring 130 license use monitoring 430 space reclamation and 113 statistics flushing 131 housekeeper utility functionality 342 housekeeper wash, housekeeper garbage collection, housekeeper chores 342 three tasks 342 wash 343 wash task 130
I
I/O usage statistics 132, 433
i/o batch sizet configuration parameter 133 i/o polling process count configuration parameter
432
i/o accounting flush interval configuration parameter
133
IBM character set 100 Icons 50 identification and authentication See also logins
controls 368 identities alternate 408 proxies and 556 session authorizations and 556 identity burning set factor configuration parameter 134 IDENTITY columns automatic 264, 269 nonunique indexes 266 identity grab size configuration parameter 135 identity in nonunique index database option 266 identity of user. See aliases; logins; users IDs, user 388, 413 system procedures and 14 impersonating a user. See setuser command index descriptors maximum number open 175 indexes character set changes 306 character-based 304 default fill factor percent percentage for 102 IDENTITY columns in nonunique 266 object allocation maps of 173 rebuilding 305 sort order changes 305 suspect 305, 335 individual accountability 365 information (server) changing user 403407 configuration parameters 65 database devices 254 database options 262263 devices 254 dump devices 254 error messages 327336 locked logins 402 logins 412 permissions 560564 problems 328 remote server logins 447 remote servers 441 user aliases 410 users, database 411433 information messages (server). See error messages; severity levels
648
Index
initializing database devices 245253 installation, server audit system 578 establishing security after 364367 interfaces file 17 status after 241 installhasvss script 112 installing sample databases 32 insthasv script 112 insufficient disk space disk resize 258 insufficient permission 332 insufficient resource errors (Level 17) 333 integer data in SQL xxv interfaces file 16, 460 internal error, nonfatal 334 international language support. See character sets; languages internationalization a sample system 275 advantages 274 definition 273 directory structure for character sets 310 files 309 is_sec_service_on security function 479 ISO 8859-1 similarities to CP 1252 279 iso_1 character set 100 isolation levels level 0 reads 266 isql utility command character set conversion and 322, 323 number of user connections and 184 passwords and 446 security services and 475 status and informational messages 331 system administration and 7 support 279 See also languages, alternate Java configuration parameters ??212 job scheduler interval configuration parameter 136 job scheduler tasks configuration parameter 136 joins views and 566
K
kadmin 482 kanji. See Japanese character sets Kerberos 480 compatibility 480 configuring 481 CyberSafe Kerberos libraries 480 keytab file 482 licenses 480 MIT Kerberos libraries 480 Native libraries 480 kernel error messages 328, 334 key exchange encryption 616 public/private key 616 symmetric key 616 keys, table on system tables 11 keytab file specifying 466 specifying for utility programs 476 kill command 338342 kill command, changes 341 kill statusonly parameter 341 known problems 353 Korean character set support 279
L J
Japanese character sets 100 sjis (Shift-JIS) 100 LAN Manager security mechanism @@langid global variable 312 language defaults 102, 378 changing users 304 461
649
Index
us_english 102 @@language global variable 312 language groups 278, 279 languages on server 278 supported by a character set 278 languages, alternate 309 See also character sets; charset.loc file; Japanese character sets date formats in unsupported 308 localization files 294312 supported languages 274 Latin alphabet 280 lazy garbage collection 343 LDAP access restrictions 18 defined 18 multiple directory services 19 versus the interfaces file 20 levels, severity. See severity levels, error libtcl.cfg file 17 example of 459 preparing for network-based security 456 tools for editing 458 license information configuration parameter 137, 429 license information, configuration parameter 343 license use error log messages 430 monitoring 428 linkage, page See also pages, data linking users. See alias, user list_appcontext 540, 542 listing database options 262 load database syntax 635 load, database number of large i/o buffers configuration parameter 106, 145, 164, 170 local and remote servers. See remote servers local option, sp_addserver 438 local servers 438 locales directory 295 locales.dat file 311 localization 274
See also languages, alternate files for 311 lock address spinlock ratio configuration parameter 138 lock hash buckets 140 lock hash table configuring size of 138 lock hashtable size configuration parameter 138 lock promotion thresholds setting with sp_configure 190206 lock scheme default 139 lock scheme configuration parameter 139 lock shared memory configuration parameter 128, 139 lock spinlock ratio configuration parameter 140 lock table spinlock ratio configuration parameter 141 lock timeouts configuring server-wide 141 lock wait period configuration parameter 141 locking by dbcc commands 307 logins 401, 418 locking logins 55 locking scheme server-wide default 139 locks quantity of 171 log audit logon failure configuration parameter 142 log audit logon success configuration parameter 142 log file. See error logs log on option create database 243 logging login failures 142 successful logins 142 Windows NT event log in 125, 126 logical expressions xxv page sizes 35 login IDs, number of 385 login names. See logins login process authentication 453 login triggers configuring 547
650
Index
disabling execute privilege 555 displaying 549 dropping and changing 548 executing 549 issues 554 issues and information 554 output 549 restrictions 554 restrictions on 554 syntax for configuring 548 syntax for creating 547 understanding output 549 using 547 using for other applications 549 logins See also remote logins; users adding to servers 377379 alias 409, 511 assigning names for 365 database object owner 6 dbo user name 4, 6 displaying password information 422 dropping 402 finding 412 identification and authentication 368 information on 412 invalid names 464 locking 55, 401, 418, 421 maximum attempts, changing 419 maximum attempts, setting 418 sa 365 unlocking 401, 421 logsegment log storage 241 losing unlogged data 268 master database backing up 54 master database 9, 2527, 42 See also disk mirroring;system tables backing up 42 changing option settings 262 creating 241 as default database 378 dropping guest users of 383 guest user in 383 keys for system tables in 11 ownership of 504 sysdevices table 254 as user default database 378 master database, granting default permissions on system tables 522 master database, revoking default permissions on system tables 522 master device 24, 248, 254 See also database devices removing from default space pool 255, 256 sp_diskdefault and 256 max async i/os per engine configuration parameter 143 max async i/os per server configuration parameter 143 max cis remote connections configuration parameter 144 max concurrently recovered db configuration parameter 145, 164 max native threads per engine configuration parameter 147 max network packet size configuration parameter 147 max number network listeners configuration parameter 150 max online engines configuration parameter 150 max parallel degree configuration parameter 151 max repartition degree configuration parameter 152 max resource granularity configuration parameter 153 max roles enabled per user configuration parameter 160, 393 max scan parallel degree configuration parameter 153
M
Macintosh character set 100, 320 mail session, starting 220 management, space. See space allocation; storage management managing users. See users mapping device name to physical name 246 remote users 442446
651
Index
max SQL text monitored configuration parameter
154 @@max_connections global variable 183 @@maxcharlen global variable 310 maximum dump conditions configuration parameter 155 membership keyword, alter role 395 memory See also space allocation audit records 89, 587 freeing from XP Server 124 network-based security and 466 number of open databases and 174 memory alignment boundary configuration parameter 157 memory per worker process configuration parameter 157 message digest defined 617 hash 617 messages confidentiality 453, 465 error 15, 327336 fatal error 15 integrity 454, 465 language setting for 274 origin checks 454 protection services for 453 start-up 15 system 327336 user-defined 330 messaging memory configuration parameter 158 metadata caches configuration parameters 72188 Microsoft character set 100 minimum size, disk resize 258 minus sign (-) converted to pound sign in login names 465 miscellaneous user error 333 mistakes, user See errors; severity levels, error model database 54 model database 28 changing database options 268 changing options in 262 creating 241 keys for system tables in 11 size 100, 249 modifying
server logins 405 money local formats 311 monitoring spt_monitor table 14 SQL text 154 Windows NT Performance Monitor 213 monitoring tables configuration options 72 month values alternate language 308 MSDTC 110 msg confidentiality reqd configuration parameter 160 msg integrity reqd configuration parameter 160 multibyte character sets 306 changing to 307 default character set id configuration parameter 100 incompatible 320 multilingual character set 100 multiple directory services LDAP 19 mut_excl_roles system function 416 mutual authentication server option 471 mutual exclusivity of roles 371, 416
N
name of device 247 sysdevices listing 243 names See also information (server); logins alias 409, 511, 555 column, in commands 333 finding user 413 for logins 365 group 510 mapping remote user 443 original identity 556 partial, in option specification 270 remote server 437 remote user 443 server 438 system extended stored procedures 15
652
Index
system procedures 12 user 381, 413, 506, 510 naming groups 380 servers 438 user-defined roles 392 Navigating to objects 50 @@ncharsize global variable 310 nested trigger configuration parameter (now called allow nested triggers) 84 net password encryption option 440 network drivers 456 example of entry in libtcl.cfg file 459 syntax for in libtcl.cfg file 456 network-based security 451479 adding logins for unified login 467 configuring server for 462 connecting to server 475 getting information about 475, 478 identifying users and servers 461 memory requirements 466 overview 452 process for administering 454 rebooting server to activate 466 remote procedure calls 468 security mechanism 461 setting up configuration files 455 using 475 networks connections 16 directory services 17 interfaces files 16 software 38 no chkpt on recovery database option 266 no free space acctg database option 267 nonrepudiation, digital signature 617 nonstop recovery 240 NT LAN Manager security mechanism 461 null keyword in sp_addlogin 379 null passwords 405 number (quantity of) database devices 165 engines 150 locks 171 open databases on Server 173 open objects 177 remote sites 449 seconds for acquiring locks 141 user connections (@@max_connections) 183 number of alarms configuration parameter 161 number of aux scan descriptors configuration parameter 161 number of devices configuration parameter 165 number of dtx participants configuration parameter 165 number of histogram steps configuration parameter 168 number of index trips configuration parameter 169 number of large i/o buffers configuration parameter 170 number of locks configuration parameter 171 number of login IDs 385 number of mailboxes configuration parameter 172 number of messages configuration parameter 172 number of oam trips configuration parameter 173 number of open databases configuration parameter 173 number of open indexes configuration parameter 175 number of open objects configuration parameter 177 number of pre-allocated extents configuration parameter 180 number of remote connections configuration parameter 180, 449 number of remote logins configuration parameter 167, 181, 448 number of remote sites configuration parameter 181, 449 number of sort buffers configuration parameter 182 number of threads for memory dumps, determining 167 number of user connections configuration parameter 76, 182184 number of users 385 number of worker processes configuration parameter 185 numbers engine 329 error message 327 sort order 104
653
Index
status bit (sysdevices) 254 numeric expressions xxv
O
o/s file descriptors configuration parameter
overflow stack (stack guard size configuration parameter) 216 overriding user permissions 55 owners. See database object owners 517 ownership chains 568
186 object access permissions See permissions object lockwait timing configuration parameter 186 object owners. See database object owners object permissions grant all 509, 517 objectid.dat file 459 location of 625 objects icons 50 navigating to 50 See database objects on keyword grant 509 revoke 509 open index hash spinlock ratio configuration parameter 187 open index spinlock ratio configuration parameter 187 open object spinlock ratio configuration parameter 188 openVMS systems foreign device 247 operating system commands executing 15 operator role 5 permissions 390 optimization goals and configuration parameters 189 optimization timeout limit configuration parameter 190 options database 261271 remote logins 446 remote servers 439 server 439 unique string for 270 order of commands for database and log dumps 268 grant and revoke statements 507527 out-of-sequence checks 454 overflow errors server stack 218
P
packets, network pre-read 449 size, configuring 190
page lock promotion LWM configuration parameter
148149
page lock promotion HWM configuration parameter
191, 205
page lock promotion PCT configuration parameter
192 pages, data 246 dirty 202 parameters, procedure 379 parentheses ( ) converted to dollar sign in login names 465 partition groups configuration parameter 194 partition spinlock ratio configuration parameter partitions disk 247 password-protected database dumps 635 passwords 404 changing 404 checking for at least one character 423 choosing 377 choosing secure 377 date of last change 412 displaying information 422 encryption over network 440 expiration interval 425 expiration of 425 for roles 425 forgotten 390 minimum length 423 null 405 protecting 377 protection against guessing 418 remote users 440, 446 roles and 399
194
654
Index
rules for 377 object 7, 506 object access 507, 507513 object creation 517 operator 390 overriding 55 ownership chains and 568 proxy authorization 519 public group 506, 509, 525 remote users 446 revoking 507525 selective assignment of 523 stored procedures 446, 506, 509 summary of 501 System Administrator 502503 system procedures 505 system tables 521 tables 506, 509 tables compared to views 565 tempdb database 30 transfers and 504 triggers and 572 using setuser 555 views 565567 on views instead of columns 566 physical resources, managing. See storage management placeholders error message percent sign (%) 327 plan text pipe active configuration parameter 198 plan text pipe max messages configuration parameter 198 Pluggable Authentication Module (PAM) 493 $ISA 495 32- and 64-bit servers on the same machine 495 configuring Adaptive Server for PAM 496 determining which module to use 495 enable pam user auth 496 password management 496 RFC 86.0 495 unified logins 495 plus (+) converted to pound sign in login names 465 preferences, user name 381 preventing garbage collection accumulating empty pages 344
sp_password 404 per object statistics active configuration parameter
195
per opject statistics active configuration parameter
194 percent sign (%) error message placeholder 327 translated to underscore in login names 464 performance audit queue size 89 default fill factor percent effect on 102 disk mirroring and 240 ESPs and XP Server priority 123 space allocation and 240 speed and 240 performance monitoring option configuration parameter 197 period (.) converted to dollar sign in login names 465 permission cache entries configuration parameter 197 permissions See also discretionary access control (DAC) acquiring other users 555 aliases and 408 ansi_permissions option and 512 assigned by Database Owner 517 assigning 517 concrete identification 511 create database 503 database object owners 7 Database Owners 6, 502, 504 default 28 denying 332 disk init 253 for creating triggers 510 granting 507525 group versus user 55 groups and 380 guest users 382, 383 hierarchy of user 527 information on 560564 insufficient (Level 14) 332 master database 27 model database 28
655
Index
primary database
266 199 200
print deadlock information configuration parameter print recovery information configuration parameter
priority XP Server 123 proc_role system function stored procedures and 417, 568 procedure cache 200, 335 procedure calls. See remote procedure calls procedures. See stored procedures; system procedures process ID, status of 341 process wait events configuration parameter 201 processes (server tasks) 338, 342 See also servers administering Adaptive Server 363 current on server 411 information on 411 killing 338342 production server 36 protection mechanisms. See security functions; stored procedures; views protection system context-sensitive 566 hierarchy (ownership chains) 568 reports 560564 summary 501 proxy authorization 555564 executing 558 granting 518 granting permission for 519 how applications use it 560 how users use it 558 overview 556 using 556, 558 Public membership 55 public group 380 See also groups grant and 509, 518 guest user permissions and 383 permissions 506, 525 revoke and 509 sp_adduser and 381 sp_changegroup and 406 public keyword
grant 518 public/private key encryption public-key cryptography certificates 616 defined 616 digital signature 616 encryption 616 pubs2 database administering 32 image information in 33 pubs3 database administering 32
616
Q
queries conversion errors, preventing 321 question marks (??) for suspect characters 321 quotation marks ( ) converted to pound sign in login names
465
R
read committed with lock configuration parameter
201
read only database option
267, 270, 305 reads physical 240 rebooting the server 466 See restarts, server reconfigure command 75 record keeping 4648 configuration 47 contacts 46 maintenance 47 system 48 records, audit 576 recovery configuration parameters for 201203 loading databases 301 master database 42, 246 nonstop 240 planning backups for 28
656
Index
after reconfiguration 301 sort order changes and 301 space allocation and 240 up-to-date database copy method 266 recovery interval in minutes configuration parameter 201203 long-running transactions and 202 reestablishing original identity 556 remote logins adding 442444 configuration parameters for 86, 447449 dropping 441, 442 options for 446 timing out 439 trusted or untrusted mode 444 remote procedure calls 435449 configuration parameters for 447449 example of setting security 474 network-based security 468 overall process for security model B 472 security models for 471 setting security options 470 unified login and 470 remote server pre-read packets configuration parameter 204, 449 remote server users. See remote logins remote servers 436441 adding 436449 dropping 441 information on 441 names of 437 options for 439 remote users. See remote logins removing. See dropping reorg command running manually 345 reorg reclaim_space command 344 replay detection 454 reporting errors 331, 333, 336 reporting usage statistics 432 reports See also information (server) server usage 431 reset configuration. See configuration parameters;reconfigure command resource limits configuring 86 response time 228 restarts, server after reconfiguration 304 checkpoints and 267 reindexing after 304 from same directory 329 system tables and 304 temporary tables and 30 retaindays option dump database 226 dump transaction 226 return status system procedures 13 revoke command 502, 507525 public group and 509 revoking create trigger permission 510 role privileges using with override 401 roles with revoke role 527 revoking default permissions from system tables 522 revoking default permissions on master database system tables 522 RFC 86.0 495 rm_appcontext 540, 543 role hierarchies 371 creating 526 displaying 416 displaying with role_contain 416 displaying with sp_displayroles 416 role_contain system function 416 roles activating 399 configured for sa login 365 deactivating 399 in grant and revoke statements 510, 518 locking 418, 421 maximum login attempts, changing 420 maximum login attempts, setting 419 passwords for 425 permissions and 527 stored procedure permissions and 417 stored procedures and 526, 567 unlocking 421 roles, system
657
Index
Operator 5 System Administrator 4 System Security Officer 5 roles, user-defined planning 392 rolling back processes recovery interval and 202 server stack capacity and 219 roman8 character set 100 row lock promotion HWM configuration parameter 204 row lock promotion LWM configuration parameter 205 row lock promotion PCT configuration parameter 206 row lock promotion thresholds setting with sp_configure 204, 206 rowlevel access control 528 rows, table sysindexes 244 RPCs. See remote procedure calls rtm thread idle wait period configuration parameter 207 rules See also database objects protection hierarchy 571 runnable process search count configuration parameter 207 running out of space. See space running reorg command manually 345 russian character set support 279
S
sa login 365 changing password for 365 configured with System Administrator and System Security Officer roles 365 security recommendations for using 365 savepoints error (Level 13) 332 scan descriptors 161164 scripts 278 secmech specification 459 secondary database 266 secure default login 463 secure default login configuration parameter 209 security
auditing 372 discretionary access control 370 establishing after installation 364367 identification and authentication controls 368 Kerberos 480 login features 417 roles 371 security administration example of 366 getting started 363367 guidelines 364 security drivers example of entry in libtcl.cfg file 459 syntax for entries in libtcl.cfg file 457 security functions 479 security mechanism server option 471 security mechanisms 478 how the server determines which to support 467 security models 469 example of model B 474 for RPCs 470 model B 472 setting up model B for RPCs 471 security services example 452453 overview of 452 supported by Adaptive Server 453 segmap column, sysusages table procedures that change 243 segments 244 See also database devices; space allocation creating 241 default 241 logsegment 241 syssegments table 244 system segment 241 select * command error message 566 select into/bulkcopy/pllsort database option model database and 28 transaction log and 267 select on syscomments.text column configuration parameter 210 sensitive information, views of 565 separation of roles 371 sequence checks 454
658
Index
server aliases 438 server authentication server certificates 620 server certificates 617 location of 620 server authentication 620 server information options. See information (server) server user name and ID 413 server.loc file 311 server_name.cfg, default name of configuration file 62 servers See also processes (server tasks); remote servers adding new logins to 377379 adding users to 377379 connecting 16 dropping logins from 402 error message severity levels 330336 error messages 328 fatal errors and 334336 installing 37, 241 interfaces files 16 local 438 monitoring performance 76 names of 438 nonfatal internal errors 334 passwords on 440, 446 remote 437443 scheduler 228 shutting down 351 single-user mode 88, 268 sort order consistency among 300 stopping 351 syntax errors 332 unlocking logins or roles at startup 421 user connections to 184 user information 411433 values for configuration parameters 61 server-wide dbcc, master and 521 session authorization option, set 558 set command roles and 399 set_appcontext 540 setuser command show_role and 415 setuser, using 555 7-bit ASCII character data, character set conversion for 315 severity levels, error 325, 330 Backup Server 337 levels 10-18 (user errors) 331 levels 19-24 (fatal) 334 shared memory starting address configuration parameter 210 show_role system function 415 show_sec_services security function 479 shutdown command 351353 shutting down servers 351 simplified Chinese character set support 279 single user database option 268 single-user mode 88, 304 site handlers 449 sites, remote 449 size See also space dbcc fix_text transaction 306 error log 16 model database 100, 249 new database 28 tempdb database 29 transaction logs 268 size of auto identity column configuration parameter 211, 264 unique auto_identity index database option and 269 size of global fixed heap configuration parameter 211 size of process object fixed heap configuration parameter 211 size of shared class heap configuration parameter 212 size of unilib cache configuration parameter 213 sjis (Shift-JIS) character set. See Japanese character sets slash (/) converted to pound sign in login names 465 sort order changing 300304 consistency among servers 300 default sortorder id 104 default XML sortorder 105 definition files 309 installing new 310
659
Index
numbers 104 rebuilding indexes after changing 305 sp_activeroles system procedure 416 sp_addalias system procedure 409 sp_addauditrecord system procedure 601 sp_addgroup system procedure 380 sp_addlanguage system procedure 308 sp_addlogin system procedure 377379, 425, 427 sp_addremotelogin system procedure 442444 sp_addsegment system procedure sysusages and 243 sp_addserver system procedure 437439 sp_adduser system procedure 28, 381383 sp_audit system procedure setting options with 594 sp_changedbowner system procedure 503 sp_changegroup system procedure 380, 406 sp_column_privileges catalog stored procedure 564 sp_configure system procedure 65 See also individual configuration parameter names configuring server for security services 462 remote logins and 447 sp_countmetadata system procedure 174, 176, 177, 179 sp_dboption system procedure 261270 sp_deviceattr system procedure 238, 251 sp_diskdefault system procedure 238, 256257 sp_displaylogin system procedure 412 sp_displayroles system procedure 416 sp_dropalias system procedure 410, 511 sp_dropdevice system procedure 255 sp_dropgroup system procedure 399, 400 sp_droplogin system procedure 401, 402 sp_dropremotelogin system procedure 442 sp_dropsegment system procedure sysusages and 243 sp_dropserver system procedure 441 sp_dropuser system procedure 399, 400 sp_extendsegment system procedure sysusages and 243 sp_helpconfig system procedure 174, 175, 177 sp_helpdb system procedure 14 database option information 263 sp_helpdevice system procedure 14, 253 sp_helpindex system procedure 14 sp_helpjoins system procedure 11 sp_helpkey system procedure 11
sp_helpremotelogin system procedure 447 sp_helprotect system procedure 562563 sp_helpserver system procedure 441 sp_helptext system procedure 13 sp_helpuser system procedure 410 sp_indsuspect system procedure 305 sp_locklogin system procedure 401, 402 sp_modifylogin system procedure 304, 405, 425, 428
changing users default database with 378 changing users full name with 378 sp_monitorconfig system procedure configuring number of open databases and 174 configuring number of open indexes and 176 configuring number of open objects and 178, 179 sp_password system procedure 404 sp_remoteoption system procedure 446447 sp_reportstats system procedure 432 sp_serveroption system procedure 439, 470 sp_showplan system procedure 349 sp_showpsexe system command, housekeeper output 342 sp_table_privileges catalog stored procedure 563 sp_who system procedure 411, 561 sp_who, housekeeper output 342 space See also size; space allocation running out of 268, 333 space allocation See also database devices; segments; storage management commands summary 238 recovery/performance and 239 sysusages table 243 space reclamation enable housekeeper GC configuration parameter 113 Spanish character set support 279 #spdevtab temporary table 14 specifying device size, disk resize 259 speed (server) system performance and 240 #spindtab temporary table 14 spinlocks lock hash table 140 splitting
660
Index
tables across two disks 240 SPR files 353 spt_committab table 14 spt_monitor table 14 spt_values table 13 SQL batch capture configuration parameter 213 sql server clock tick length configuration parameter 214 sql text pipe active configuration parameter 215 sql text pipe max messages configuration parameter 215, 216 square brackets [ ] converted to pound sign in login names 465 in SQL statements xxiv .srt files 309 srvname column, sysservers table 439 srvnetname column, sysservers table 439 SSL defined 618 enabling SSL 622 filter, defined 619 handshake 618 SSL connections for companion servers 621 for RPCs 621 Open Client 621 stack guard size configuration parameter 216 stack size configuration parameter 219 standalone utilities and character sets 322 start mail session configuration parameter 220 starting servers Security Services and 466 statement pipe active configuration parameter 221 statement pipe max messages configuration parameter 221, 222 statement statistic active configuration parameter 222 statement statistics active configuration parameter 222 static configuration parameters 62 statistics housekeeper flushing and 131 I/O usage 431, 432 statistics, flushing with housekeeper task 131 status information messages (Level 10) 331 status bits in sysdevices 254 stem 520 steps administering security 363 stopping Backup Server 352 Servers 351 space allocation storage management 237 commands summary 238 database device initialization 245254 default database devices 256257 defaults at installation 241 issues 3941, 239 See also space 237 system tables and 242244 stored procedure triggers. See triggers stored procedures See also database objects; system procedures checking for roles in 417 creating 14 granting execution permission to roles 417 ownership chains 568 permissions granted 509 permissions on 446, 506, 509 procedure cache and 200 remote user access to 446 roles and 567 as security mechanisms 567 system tables changes and 14 strict dtm enforcement configuration parameter 222 structure internationalization files directory 310 localization files directory 311 suffix names, temporary table 30 suid (server user ID) 379 sun character set 100 superuser. See System Administrator suser_id system function 413414 suser_name system function 413414 suspend audit when device full configuration parameter 223, 587 syb_sendmsg port number configuration parameter 224 Sybase Central, using for system administration tasks 8
661
Index
syblicenseslog table 430 sybsecurity database 31, 574 sybsystemdb database 31 sybsystemprocs database 12, 15, 29 See also databases permissions and 505 symbols See also Symbols section of this index in SQL statements xxiii symmetric key encryption 616 syntax disk resize 258 dump database 635 errors in 332 load database 635 Transact-SQL conventions xxiiixxv sys_session application context table 544, 545 sysalternates table 409 See also sysusers table sysconfigures table 78 syscurconfigs table 78 sysdevices table 243, 253 disk init and 243 sp_dropdevice and 255 sp_helpdevice and 253 status bits 254 sysindexes table 244, 305 syslogins table sp_addlogin effect on 379 syslogs table modification of 12 syslogs transaction log for sybsecurity 588 sysmessages table 326, 327 sysobjects table 305 sysremotelogins table 444 syssegments table 244 sysservers table 435, 436, 437, 441 sp_helpserver and 441, 475 srvname column 439 srvnetname column 439 system administration tasks accomplishing with Sybase Central 8 System Administrator 37 error responsibilities of 331, 333336 permissions 502503 resolving system problems 331, 333
tasks for beginners 3548 system audit tables 603 system catalogs. See system tables system databases 2331 system extended stored procedures 15 system messages. See error messages 325 system problems See also errors Server responses to 325336 severity levels 10 to 18 331334 severity levels 19 to 24 334336 System Problem Reports (SPRs) 353 system procedure tables 13 system procedures 1214 See also information (server); stored procedures; individual procedure names for adding users 376 for changing user information 403407 creating 14 for dropping aliases 511 for managing remote servers 436441 permissions 505 on temporary tables 30 using 13 system roles activating 399 deactivating 399 granting with grant role 526 max_roles_enabled configuration parameter and 393 show_role and 415 System Security Officer 5 system segment 241 system tables 911 See also individual table names changes allowed to 522 changes dangerous to 14 corruption 336 create database and 10, 243 creation of 10 dbcc reindex and 306 keys for 11 permissions on 521 querying 10, 14 reindexing and 306 server restarts and 304
662
Index
storage management relationships 242244 stored procedures and 10, 14 updating 11, 14 for user databases 28 systemwide password expiration configuration parameter 225 sysusages table 243 corruption 336 sysusers table permissions and 505 sysalternates table and 409 terminals character set conversion for 323 installing new definitions 310 test servers 3637 text datatype changing character sets and 306 multibyte character sets and 306 text prefetch size configuration parameter 227 text values, dbcc fix_text upgrade of 306 Thai character set support 279 three housekeepers 343 threshold procedures audit trail 582 time for acquiring locks 141 time slice configuration parameter 228 time values display format 311 timeouts option, sp_serveroption 439 total data cache size configuration parameter 228 traditional Chinese character set support 279 transaction logs alter database and 243 create database and 243 device placement 240, 243 primary and secondary database 266 purging 307 select into/bulkcopy/pllsort database option 267 size 268 trunc log on chkpt option and 202, 268269 transactions error within 332 long-running 202 recovery and 202 two-phase commit 31 transferring ownership. See database objects, ownership translation. See character sets triggers See also database objects; stored procedures creating 510 nested 85 permissions and 572
T
Table editor 56 table owners. See database object owners tables See also database objects; system tables context-sensitive protection of 566 dbcc checktable and 305 integrity damage to 335 object allocation maps of 173 ownership chains for 568 permissions information on 563 permissions on 506, 509 permissions on, compared to views 565 read-only 305 splitting across two disks 240 system procedure 13 temporary 29 underlying 565 without indexes 306 tamper detection, digital signature 617 tape retention in days configuration parameter 226 tcp no delay configuration parameter 227 tempdb database 2930 See also databases auto identity database option and 264 creating 241 size of 29 unique auto_identity index database option and 269 temporary tables 29 select into/bulkcopy/pllsort database option and 268
663
Index
trunc log on chkpt database option 268269 recovery interval in minutes and 202 truncate table syntax 513
trusted mode remote logins and 446 trusted root certificate CA certificate 617 location of 620 tuning monitoring performance 76 turkish character set support 279 two-phase commit transactions 31 txn to pss ratio configuration parameter
230
U
underlying tables of views (base tables) 565 unichar datatype 280 Unicode 278, 280284 character sets 279 unichar datatype 280 univarchar datatype 280 UTF-16 281 unified login 453, 463 mapping login names 464 remote procedure security models 470 requiring 463 secure default login 463 unified login required 231 unique auto_identity index database option 269 univarchar datatype 280 UNIX platforms, raw disk partition 247 unlocking login accounts 421 roles 421 unlocking login accounts 401 unlocking roles 421 unlogged operations 268 untrusted mode, remote logins and 446 update statistics syntax 513 updating See also changing allow updates to system tables configuration
parameter and 14 system procedures and 567 text after character set change 306 upgrade version configuration parameter 232 us_english language 102 usage disk resize 257 statistics 432 use message confidentiality server option 471 use message integrity server option 471 use security services configuration parameter 232, 462 user connections memory allocated per 183184 user databases See also databases; permissions master database control of 25 system tables for 28 user-defined messages 330 user errors 331, 331334 user groups. See groups; public group user IDs 388 displaying 412 finding 413 number 1, Database Owner 14 user log cache size configuration parameter 233 user log cache spinlock ratio configuration parameter 234 user mistakes. See errors; severity levels, error user names 413, 506 changing 405 finding 413 preferences 381 user objects. See database objects user_id system function 414 user_name system function 414 user-defined roles activating 399 configuring 392 deactivating 399 dropping 400 granting with grant role 526 number of 393 planning 392 Users creating 55
664
Index
guest 54 users See also aliases; groups; logins; remote logins adding 376381 aliases 408 application name, setting 407 client host name, setting 407 client name, setting 407 currently on database 411 currently on server 411 deleting 55 dropping from databases 400 dropping from groups 407 dropping from servers 402 errors by 331, 331334 guest 382, 505 IDs 388, 413 information on 411433 license use monitoring 428 number of user connections and 184 number or 385 permissions to all or specific 523, 566 remote 442446 single-user mode 88, 268 views for specific 566 visiting 384 users, object.See database object owners using proxy authorization 556 UTF-16 281 utility commands See also Utility Programs manual character sets and 322 utility, housekeeper, aggressive 343 security and 565 virtual address 253 page numbers 250 visitor accounts 384 vstart option disk init 253
W
wait event timing configuration parameter
234 wash, housekeeper task 130 Western Europe character set support 279 window of vulnerability 88 Windows NT LAN Manager security mechanism 461 with grant option option, grant 510 with nowait option, shutdown 351, 352 with override option drop role 401 With override, database option 54 write operations physical 240 writetext command select into/bulkcopy/pllsort database option 267
X
X/Open XA 110 xact 235 .xlt files 309 XP Server freeing memory from 124 priority 123 xp_cmdshell context configuration parameter 236 xp_cmdshell system extended stored procedure 15
V
variables in error messages 327 verification, user-access 440, 444 Vietnamese character set support 279 views See also database objects dependent 569 ownership chains 568 permissions on 509, 565567
665
Index
666

Sybase

Uploaded by

Copyright:

Available Formats

Sybase

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sybase

Uploaded by

Copyright:

Available Formats

What is the document about?

What is the document about?

What are some of the main topics covered in the document?

What are some of the main topics covered in the document?

System Administration Guide: Volume 1 Adaptive Server Enterprise

About This Book .......................................................................................................................... xv

System Administration Guide: Volume 1

Adaptive Server Enterprise

System Administration Guide: Volume 1

Adaptive Server Enterprise

System Administration Guide: Volume 1

Adaptive Server Enterprise

System Administration Guide: Volume 1

Adaptive Server Enterprise

System Administration Guide: Volume 1

Controlling number of preread packets.................................. 449

Adaptive Server Enterprise

System Administration Guide: Volume 1

Adaptive Server Enterprise

About This Book

System Administration Guide: Volume 1

Adaptive Server Enterprise

About This Book

System Administration Guide: Volume 1

Adaptive Server Enterprise

About This Book

System Administration Guide: Volume 1

Other sources of information

Adaptive Server Enterprise

About This Book

Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on component certifications

System Administration Guide: Volume 1

Adaptive Server Enterprise

About This Book

Formatting SQL statements

SQL syntax conventions

or, for a command with more options:

System Administration Guide: Volume 1

pub_id ------0736 0877 1389

Examples of output from the computer are printed like this:

pub_name ------------------New Age Books Binnet & Hardley Algodata Infosystems

Obligatory options {you must choose at least one}

Square brackets and vertical bars: Choose none or only one.

Adaptive Server Enterprise

About This Book

[extra_cheese, avocados, sour_cream]

System Administration Guide: Volume 1

Adaptive Server Enterprise

Basics of System Administration

Overview of System Administration

Adaptive Server administration tasks

System Administration Guide: Volume 1

Adaptive Server administration tasks

Roles required for system administration tasks

Adaptive Server Enterprise

Overview of System Administration

System Administration Guide: Volume 1