Home

	Expand Search

Installing Adaptive Server Enterprise on Windows NT

Chapter 1: Installation Overview

Chapter 1

This chapter covers the following topics:

• Installation Definitions
• User Roles
• Product Descriptions
• Installation and Setup Utilities
• Environment Variables
• Sybase Installation Directory
• Windows NT Registry
• Client/Server Communication (sql.ini)
• Adaptive Server Devices and System Databases
• What's Next?

Installation Definitions

These terms are used in the installation and upgrade process:

• Downloading - is the process of transferring programs and files from CD to a target computer.
• Installing - describes the tasks required to enable software functionality once programs and files are downloaded to the target computer. Tasks vary for first-time installations and upgrades.
• Upgrading - describes the tasks required to install a new software release for an existing software product. Upgrading requires new programs be downloaded and installed. Additional steps might be required to enable previous programs and databases to utilize the new software's functionality.
• Server - provides a service in client/server computing. Examples include Adaptive Server, Backup Server(TM), Historical Server, Monitor Server, and XP Server(TM).
• Client - requests a service in client/server computing. Sybase Central, PowerDynamo, PowerDesigner SQL Modeler(TM), and end-user applications are clients.
• Client plug-in - is the software component that enables a client to access a service. For example, Sybase Central uses plug-ins to the Sybase Central framework. The Adaptive Server plug-in accesses an Adaptive Server.

User Roles

The Adaptive Server installation and setup process defines various user roles. Different user roles have different responsibilities and privileges. These user roles clarify the way Adaptive Server is integrated into your system:

• Operating System Administrator

  The individual who maintains the operating system. This individual has "administrator" privileges.

• Sybase System Administrator

  The individual in charge of Adaptive Server system administration, creating user accounts, assigning permissions on databases, and creating new databases. At installation time, the System Administrator's login name is "sa". The "sa" login is not a Windows NT login. The "sa" login is specific to Adaptive Server and is used to log in to Adaptive Server using the isql command.

• Sybase Login

  The "sybase" login is a Windows NT login which owns all the Sybase installation directories and files, sets permissions on these directories and files, and performs the installation and upgrading of Adaptive Server.

Product Descriptions

This installation guide describes how to install Sybase products. Table 1-1 lists Sybase products for this version.

Table 1-1: Sybase products

Product Name	Contents
Adaptive Server Enterprise	Adaptive Server Language Modules - English, German, French, Spanish, Chinese (simplified), Japanese, Korean, Brazilian Portuguese Component Integration Services Adaptive Server Enterprise Monitor Server Adaptive Server Enterprise Monitor Client Library Adaptive Server Enterprise Monitor Historical Server
Clients and client plug-ins	Sybase Central, with the following plug-ins: - Adaptive Server Enterprise - PowerDynamo PowerDynamo InfoMaker(TM) SQL Advantage Open Client(TM) Language Modules - English, German, French, Japanese
OmniConnect	Same as Adaptive Server, but does not include PowerDynamo and InfoMaker

For complete product descriptions, see Appendix A, "Product Descriptions and Platforms."

Installation and Setup Utilities

This section describes installation and setup tools and utilities. Table 1-2 describes the tools that are used:

Table 1-2: Installation tools

Tool or Process	Name	Description
Setup executable program	setup	The executable program used to initiate the sybsetup utility. Also configures servers after downloading, if you choose to do so; automatically configures Historical Server.
Installation program or sybsetup utility	sybsetup	The installation program that downloads programs and files from media, such as CD, to the target computer.
Server Config utility	syconfig	An installation tool used to configure Adaptive Server, Monitor Server, Backup Server, and XP Server. When running syconfig in a language other than English, all user input must be in a character set supported by U.S. English (no diacritical marks).
Server batch utility	sybatch	A command-line utility used to create Adaptive Server, Monitor Server, and Backup Server, based on a resource file.
Editor program	dsedit	A program used to edit the sql.ini file and configure directory services.

The installation program, sybsetup, is a flexible tool that enables you to install Sybase products. For example, the installation program enables you to:

• Install all products on one properly equipped computer
• Install a subset of products initially and install additional products at a future date
• Perform a "quick start" installation for practice or experimentation, use the Uninstall option of sybsetup to remove all Sybase products, and then use the installation program to reinstall the products
• View online help during installation or without performing an installation

Environment Variables

The installation program creates default environment variables if values are not defined. If you are maintaining multiple installations on one machine, you must set the environment variables to point to the correct installation.

• DSLISTEN - This environment variable defines the name Adaptive Server uses to listen for client connections if no name is given during the Adaptive Server start-up. If DSLISTEN is not set, and no name is given during the Adaptive Server start-up, the Adaptive Server name defaults to the server name given at installation.
• DSQUERY - This environment variable defines the Adaptive Server name that client programs try to connect to if no Adaptive Server is specified with a command line option.
• PATH - This environment variable specifies which directory paths to search for executables and dynamic link libraries (DLLs). The Sybase executables are in the bin directory in the Sybase release directory; the Sybase DLLs are in the dll directory. The installation program appends these paths to the current PATH environment variable.

  WARNING! Keep all Sybase DLLs in the directories in which they were installed. To avoid possible confusion about current DLLs, do not keep multiple versions of Sybase DLLs on your machine.

• SYBASE - This environment variable defines the path of the Sybase release directory. The installation program sets up the variable SYBASE to point to the release directory specified during installation. The installation program uses the default directory, C:\sybase, if it does not find an existing Sybase environment variable value.
• TEMP - This environment variable defines the location used by the installation program to write files temporarily during the installation process. The installation process frees the disk space after installation is completed.
• CLASSPATH - This environment variable defines the Adaptive Server plug-in location. The default location value is:

  c:\sybase\asep\monclass.zip; c:\sybase\asep\3pclass.zip

Sybase Installation Directory

This section describes the Sybase installation directory structure. The installation program creates the directories shown in Figure 1-1 if all products are installed.

Figure 1-1: Installation directory structure

The Adaptive Server installation program installs Powersoft(R) products and some Sybase tools in the other directories, as in the following list.

WARNING! The InfoMaker installation program lets you change its directory. For consistency and ease of management, you should not change the default location when you install InfoMaker.

• c:\Program Files\Sybase\
  • Sybase Central for Adaptive Server Enterprise (viewer plug-in)
• d:\sybase (your Sybase installation directory)
  • Adaptive Server Plug-in for Sybase Central
  • Plug-in for PowerDynamo
• d:\sybtools (where d: is your Sybase installation drive)
  • ODBC (Open Database Connection)
  • PowerDynamo
• d:\pwrs (where d: is your Sybase installation drive)
  • InfoMaker, including the development tool and deployment kit
  • PowerDesigner SQL Modeler

For descriptions of these products, see Appendix A, "Product Descriptions and Platforms."

Windows NT Registry

The installation program creates Registry entries for Adaptive Server. The Registry identifies the locations of the application and system objects and services.

The installation program creates the following Registry entries, among others:

\\HKEY_LOCAL_MACHINE\SOFTWARE\SYBASE\Server\server_name

\\HKEY_LOCAL_MACHINE\SOFTWARE\SYBASE\SQLServer\server_name\
Parameter

\\HKEY_LOCAL_MACHINE\SOFTWARE\SYBASE\SQLServer

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
SessionManager\Environment

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
SYBSQL_server_name

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
SYBBCK_server_name_BS

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
SYBMON_server_name_MS

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
SYBHIS_server_name_HS

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
SYBXPS_server_name_XP

Client/Server Communication (sql.ini)

For Sybase products to interact with one another, each product needs to know where the others reside on the network. This information is stored in an interfaces file, named sql.ini, which is located in the d:\sybase\ini directory. Adaptive Server or client software can connect with any server on the network whose information is included in the interfaces file.

The interfaces file is like an address book that lists the name and address of servers to which clients can connect. When you are using a client program and you want to connect with a particular server, the client program looks up the server name in the interfaces file and connects to that server (see Figure 1-2). You can supply the name of the server by using the DSQUERY environment variable.

On TCP/IP networks, the port number gives clients a way to identify the Adaptive Server to which they want to connect. The port number also tells Adaptive Server where to listen for incoming connection attempts from clients. Adaptive Server uses a single port for these two services, referred to as query service and listener service.

Figure 1-2: Communicating with a server

During installation, sybsetup adds entries to the sql.ini file for the new Adaptive Server, Backup Server, Monitor Server, Historical Server, or XP Server.

For instructions on using dsedit to modify existing interfaces file entries or create new interfaces file entries for existing servers, see Configuring Adaptive Server Enterprise for Windows NT.

Note: You can use Windows NT Directory Replication to replicate sql.ini in multiple locations. See Microsoft documentation for information. You can also use directory services, which are stored in the Registry.

Adaptive Server Devices and System Databases

Devices are files or portions of a disk that are used to store databases and database objects. Adaptive Server requires the following devices:

• Master device - to store system databases
• System procedures device - to store system procedures

The master and system procedures devices are created when you install Adaptive Server.

Master Device

The master device contains the following databases:

• master - Controls the operation of Adaptive Server as a whole and stores information about all users, user databases, devices, objects, and system table entries. The master database is contained entirely on the master device and cannot be expanded onto any other device.
• model - Provides a template for new user databases. The model database contains required system tables, which are copied into a new user database with the create database command.
• tempdb - The work area for Adaptive Server. Each time Adaptive Server is started the tempdb database is cleared and rebuilt from the model database.

The sample databases are stored on the master device at installation, but should be moved to a user-defined device after installation. For more information on the sample databases, see "Sample Databases".

Note: For recovery purposes, it is recommended that you do not create other system or user databases or user objects on the master device.

System Procedures Device

The system procedures device stores the sybsystemprocs database, which contains the Sybase-supplied system procedures. System procedures are a collection of SQL statements and flow-of-control statements that perform system tasks; for example, sp_configure. System procedure names begin with "sp_".

The system procedures that are needed during difficult recovery situations are stored in the master database.

Optional Functionality Devices and Databases

The devices and databases in this section are needed only to configure Adaptive Server for optional functionality, like two-phase commit transactions, or to provide syntax information.

Security Device and sybsecurity Database

The security device stores the sybsecurity database and the auditing system procedures with which you can configure auditing for your system. The auditing system records system security information in an Adaptive Server audit trail, which is useful for monitoring Adaptive Server or system resource use.

For information about auditing, see Chapter 6, "Adding Optional Functionality to Adaptive Server."

System Database Device and sybsystemdb Database

The system database device stores the sybsystemdb database, which stores information about two-phase commit transactions.

For information about two-phase commit, see Chapter 6, "Adding Optional Functionality to Adaptive Server."

Sample Databases

The pubs2 and pubs3 databases are sample databases provided as a learning tool for Adaptive Server. The pubs2 sample database is used for most of the examples in the Adaptive Server documentation; other examples use the pubs3 database. Both are available in U.S. English versions of Adaptive Server.

The interpubs database contain French and German data. jpubs contains Japanese data.

For information about installing the sample databases, see Chapter 6, "Adding Optional Functionality to Adaptive Server."

sybsyntax Database

The syntax database, sybsyntax, contains syntax help for Transact-SQL commands, Sybase system procedures, Adaptive Server utilities, and Open Client DB-Library(TM) routines.

For information about the syntax database, see Chapter 6, "Adding Optional Functionality to Adaptive Server."

dbccdb Database

The Database Consistency Checker (dbcc) provides commands for checking the logical and physical consistency of a database. The dbccdb database stores the results of dbcc when the dbcc checkstorage command is used.

dbcc checkstorage records configuration information for the target database (the database that you are checking with dbcc), 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 information on installing dbccdb, see the System Administration Guide.

What's Next?

Decide what to do next:

• To install version 11.9.2, see Chapter 3, "Installing Sybase Servers."
• To upgrade from a previous version to version 11.9.2, see Chapter 5, "Upgrading Sybase Servers."