Sybase to DB2 Migration

Comparison White Paper

IBM Software Migration Project Office

DB2 Migration Team
www.ibm.com/solutions/softwaremigration
Sybase to DB2 Migration - Comparison White Paper IBM

Table of Contents
INTRODUCTION......................................................................................................................................................................1

WHY MIGRATE TO DB2 UDB ? ...........................................................................................................................................2

INTEGRATED SUPPORT FOR WINDOWS NT ................................................................................................................................2
INTEGRATED SYSTEM MANAGEMENT TOOLS............................................................................................................................2
DATA REPLICATION ..................................................................................................................................................................3
INTEGRATED WEB ACCESS .......................................................................................................................................................4
INTEGRATED SUPPORT FOR COMPLEX DATA ............................................................................................................................4
INTEGRATED SUPPORT FOR DEVELOPMENT ENVIRONMENTS ....................................................................................................5
IBM SOLUTION DEVELOPER PROGRAM ....................................................................................................................................5
DB2 UNIVERSAL DATABASE PRODUCT FAMILY .........................................................................................................6
DB2 UNIVERSAL DATABASE PERSONAL EDITION .....................................................................................................................7
DB2 UNIVERSAL DATABASE WORKGROUP EDITION ................................................................................................................7
DB2 UNIVERSAL DATABASE ENTERPRISE EDITION ..................................................................................................................7
DB2 UNIVERSAL DATABASE EXTENDED ENTERPRISE EDITION ................................................................................................7
DB2 SOFTWARE DEVELOPER'S KIT (DB2 SDK).......................................................................................................................7
DATA TYPES CONVERSION.................................................................................................................................................9

ADMINISTRATION ISSUES.................................................................................................................................................11
ENVIRONMENTS ......................................................................................................................................................................11
DATABASE DEVICES ...............................................................................................................................................................11
LOG FILES ...............................................................................................................................................................................12
DATABASE SECURITY .............................................................................................................................................................12
DUMP/LOAD ...........................................................................................................................................................................13
JOBS........................................................................................................................................................................................14
SYSTEM STORED PROCEDURES ...............................................................................................................................................14
IMPLEMENTATION DIFFERENCES.................................................................................................................................14
ISOLATION LEVELS .................................................................................................................................................................15
LOCKING MECHANISMS ..........................................................................................................................................................15
SYSTEM DATABASES ..............................................................................................................................................................15
SQL........................................................................................................................................................................................16
TABLES ...................................................................................................................................................................................16
TEMPORARY TABLES ..............................................................................................................................................................17
INDEXES .................................................................................................................................................................................17
IDENTITY COLUMNS ............................................................................................................................................................17
CONSTRAINTS .........................................................................................................................................................................17
SCROLLABLE CURSORS ...........................................................................................................................................................18
ANSI JOIN OPERATORS ..........................................................................................................................................................18
TRANSACTIONS .......................................................................................................................................................................18
TRIGGERS ...............................................................................................................................................................................18
STORED PROCEDURES.............................................................................................................................................................19
GLOBAL VARIABLES ...............................................................................................................................................................19
PROGRAMMING INTERFACES.........................................................................................................................................20
EMBEDDED SQL.....................................................................................................................................................................21
OPEN CLIENT AND OPEN SERVER LIBRARIES ..........................................................................................................................21
TERMINOLOGY MAP ..........................................................................................................................................................22

© IBM Corporation Page i

Sybase to DB2 Migration - Comparison White Paper IBM

CONVERSION TOOLS..........................................................................................................................................................23
SQL CONVERSION WORKBENCH (SQL-CW) .........................................................................................................................23
DATA JUNCTION......................................................................................................................................................................23
PLATINUM ERWIN...............................................................................................................................................................24
RESOURCES AND REFERENCES ......................................................................................................................................25

TRADEMARKS.......................................................................................................................................................................26

© IBM Corporation Page ii

Sybase to DB2 Migration - Comparison White Paper IBM

Introduction
DB2® Universal Database (DB2 UDB) can help improve the performance of database applications. Many
solution developers have already chosen DB2 UDB as their primary development database environment,
and have ported and continue to enable applications to it to take advantage of its unique features.

DB2 UDB is a true cross-platform DBMS, running on a wide variety of systems including Windows NT and
95, Solaris, HP-UX, AIX®, SCO UnixWare and OS/2®. It scales from single-processor workstations or
servers, to symmetrical multiprocessor (SMP) servers, and on up to massively parallel processing (MPP)
computers.

A real database leader in several technologies, it provides integrated support for complex data such as
text documents; images; video and audio clips; integrated Web access through native support for Java,
JDBC, SQLJ and Net.Data; integrated system management tools; and data replication service.

This paper introduces DB2 Universal products and their capabilities, discusses porting databases and
applications and describes the most important aspects of porting applications from Sybase Adaptive
Server to DB2 UDB. It also describes the differences in database options, data definition language (DDL),
data model, SQL considerations, data conversion and application conversion.

Note: All information contained in this document is based on publicly available information as of October 5,
1998 and is subject to change. IBM® disclaims all warranties as to the accuracy, completeness, or
adequacy of such information. IBM shall have no liability for errors, omissions or inadequacies in the
information contained herein or for interpretations thereof.

© IBM Corporation Page: 1

Sybase to DB2 Migration - Comparison White Paper IBM

Why Migrate to DB2 UDB ?

DB2 UDB is a database leader in several technologies, and offers true multi-platform support and
scalability. The same database is able to mix workloads on a single server. The DB2 UDB design handles
workloads from high-volume online transaction processing (OLTP) to complex multi-user queries while
maintaining excellent performance.

On December 1, 1998, the IBM Personal Systems Group and the IBM Software Group published a 100GB
TPC-D benchmark (Transaction Processing Performance Council Benchmark D) using DB2 UDB 5.2.0
under Windows NT on an IBM Netfinity 7000 M10 server with four Pentium II Xeon 400 MHz processors.
This benchmark achieved a multi-user throughput result of 831.2 QthD@100GB, a price/performance
result of $130/QphD@100GB, and a power result of 3450 QppD@100GB. It has also since been
published by TPC (For more details, see the section “Resources and References” on page 25).

In addition to affordability and performance, DB2 UDB offers the following advantages:

• Integrated support for Windows NT

• Integrated system management tools
• Data replication service
• Integrated Web access
• Integrated support for complex data
• Integrated support for development environments
• IBM solution developer program

Each of these is described in detail below.

Integrated support for Windows NT

DB2 UDB conforms to Windows NT standards. It maps closely onto Windows NT internals for
performance, and scales across all Windows NT hardware. It uses native Windows NT threads, and its
architecture relies on Windows NT for task dispatching and other internal operating system functions. All
these considerations make it more reliable and more tightly integrated to the operating system.

Integrated System Management Tools

DB2 administration tools allow users to perform database administration tasks for DB2 UDB servers that
are available locally or remotely. The Control Center (Figure 1) is a graphical interface that can be used to
perform server administrative tasks such as configuring, backing up and recovering data, managing
directories, scheduling jobs and managing media, as well as accessing and manipulating databases. This
tool can be installed on OS/2, Windows NT, or Windows 95/98 workstations.
The Control Center provides the following additional facilities to manage DB2 UDB servers:
• Command Center, to enter DB2 commands and SQL statements in an interactive window and
see the execution output in a result window.
• Script Center, to create scripts, which can be stored and invoked at a later time. These scripts
can contain DB2 commands, SQL statements and operating system commands. Scripts can be
scheduled to run unattended, in which case they are called jobs. Jobs can be scheduled to run
once only, at a later date or at regular intervals (for tasks such as backups).

© IBM Corporation Page: 2

Sybase to DB2 Migration - Comparison White Paper IBM

• Journal, to view all available information in the history and alter a message in the log files about
jobs that are pending, being executed or completed. It can also be used to review the results of
unattended jobs.
• Alert Center, to monitor the system for early warnings of potential problems or to automate
actions to correct problems that are discovered.
• DB2 Performance Monitor, to monitor the performance of a DB2 system and to create
snapshots of data over a period of time or data for a particular event, which can be used to
monitor activities.
• Visual Explain, to graphically analyze and tune SQL statements, as well as analyze query access
plans.
• SmartGuides, to help perform administration tasks. For example, a SmartGuide is available to
help tune the performance of the database server.
• The Web Control Center, the Java version of the DB2 UDB Control Center. The Web Control
Center is implemented as a Java applet that uses DB2 JDBC support. Currently, the Web Control
Center requires Netscape Navigator 4.04 for Windows 95 or Windows NT, and the JDK 1.1.4
patch for Navigator 4.04.

Figure 1 Control Center Main Window

Data Replication
DB2 UDB includes a complete data replication solution by supporting sources and targets that include the
DB2 family, IMS, VSAM, Oracle, Sybase, Microsoft, Lotus Notes, and others to ensure timely, reliable, and
consistent data across an enterprise. IBM offers the following data replication tools:

© IBM Corporation Page: 3

Sybase to DB2 Migration - Comparison White Paper IBM

• IBM Replication – the DataPropagator® Relational Version 1 (DPROPR V1) products have been
updated for Version 5 (V5) of the DB2 database.

• DB2 Universal Database V5 replication tools – the Control Center replication administration
features and the Capture and Apply programs.
• IBM Capture and Apply for MVS V5.1
• Capture for VSE and VM V5.1 – integrated with IBM DB2 Server for VSE and VM V5.1.
• DPROPR V1 for support of DataJoiner
• DataPropagator Relational Capture and Apply for OS/400 V3.1
• IBM DataPropagator NonRelational
• IBM DataJoiner®

• Lotus NotesPump

Integrated Web Access

DB2 UDB provides web access to enterprise data on DB2 databases through native support for Java,
Java Database Connectivity (JDBC), Embedded SQL for Java (SQLJ) and Net.Data®.

JDBC can be used to create applications or applets that access data in DB2 databases. These applets
can be run inside HTML web pages on any system with a Java-enabled browser, independent of the
client’s platform. The processing of JDBC applets is shared between the client and the server.

DB2 SQLJ support facilitates the creation, building and running of SQLJ programs against DB2 UDB
databases.

DB2 Net.Data enables application developers to create Internet applications that access data from DB2
databases, are stored on a web server and are viewable from any web browser. While viewing these
documents, users can either select automated queries or define new ones that retrieve the specified
information directly from a DB2 UDB database.

Integrated Support for Complex Data

DB2 Universal Database Extenders allow storage and manipulation in the database of nontraditional data
such as images, video, voice, complex documents, spatial objects and more. All these data types can be
brought together in one SQL query and can then be manipulated with powerful built-in functions.

Each extender defines a new type of data in DB2 UDB by using built-in support for user-defined types and
user-defined functions. Each extender also exploits DB2 Version 5 support for large objects of up to 2
gigabytes, and uses DB2 triggers to ensure referential integrity of image data.

The DB2 Extenders exploit the DB2 client/server model. Supported platforms are AIX, OS/2, Windows
NT, HP-UX and Solaris Operating Environment.

© IBM Corporation Page: 4

Sybase to DB2 Migration - Comparison White Paper IBM

Integrated Support for Development Environments

DB2 provides a Software Developer's Kit (SDK) that contains a collection of tools specially designed for
database application developers. The DB2 SDK includes libraries, header files, documented Application
Programming Interfaces (APIs) and sample programs to build database applications.

IBM Solution Developer Program

The IBM Solution Developer Program provides business, technical and marketing services to partners to
help them develop and market applications. The strategic focuses of this program are network computing
and e-business.

Benefits offered by this program include the following:

• Hardware and software discounts, equipment lease and loaner programs and business discounts
to reduce development costs
• On-site and remote access to fully equipped testing and porting facilities at full-service IBM
Solution Partnership Center (SPC) locations around the world
• Exclusive, focused development support
• Examples of how to interface with and exploit the newest technologies
• Technical information based on actual development experience in the form of “Frequently Asked
Questions” and “Hints And Tips”
• The IBM Developer Connection, which is loaded with development tools, software and late-
breaking news from IBM
• The Global Software Solutions Guide, an online catalog providing worldwide exposure to new
customers for partners' solutions
• In-depth technical seminars and hands-on workshops
• Partners In Development specialty areas, with specialized technical, business, marketing and
information services for areas of expertise
• A technical library, complete with the latest white papers, road maps and a calendar of upcoming
events
• The IBM Solution Developer Program worldwide web site, http://www.developer.ibm.com/, which
is a dynamic, 24-hour, 7-day-a-week service that provides information about all services.

© IBM Corporation Page: 5

Sybase to DB2 Migration - Comparison White Paper IBM

DB2 Universal Database Product Family

The DB2 product family scales through a variety of platforms: AS/400® systems, RISC System/6000®
hardware, IBM S390 systems, Intel systems and non-IBM machines from Hewlett-Packard and Sun
Microsystems. Figure 2 provides a pictorial representation of the DB2 UDB connectivity.

DB2 UDB version 5.2 database software servers run on the following software environments: AIX, HP-UX,
OS/2, SCO UnixWare, SINIX, Linux, Sun Solaris, Windows NT, Windows 98 and Windows 95.

Client access is provided for all these platforms, as well as for DOS, Apple MacOS, and Silicon Graphics
IRIX. In addition, web access is provided with popular browsers and Java applications using DB2's native
Java/JDBC support and Net.Data.

Figure 2 DB2 UDB Connectivity

The DB2 UDB products and components include:

• DB2 Personal Edition

• DB2 Workgroup Edition
• DB2 Enterprise Edition
• DB2 Extended Enterprise Edition
• DB2 Software Developer’s Kit

© IBM Corporation Page: 6

Sybase to DB2 Migration - Comparison White Paper IBM

DB2 Universal Database Personal Edition

DB2 Universal Database Personal Edition allows for the creation and use of local databases. It also allows
access to remote relational databases when they are available. This product is available for the OS/2,
Windows NT, and Windows 95 operating systems.

DB2 Universal Database Workgroup Edition

The DB2 Universal Database Workgroup Edition server enables local clients, remote clients and
applications to create, update, control and manage relational databases using Structured Query Language
(SQL), ODBC, or CLI. It contains all the latest DB2® Client Application Enablers, which enable client
workstations to access the DB2 UDB server and all supported DB2 Net.Data products.

DB2 Universal Database Enterprise Edition

The DB2 Enterprise Edition includes all functions provided in the DB2 Workgroup Edition, plus DB2®
Connect Enterprise Edition to allow support for host connectivity. This provides multi-user access to DB2
databases residing on host systems such as MVS/ESA, OS/390, AS/400, VM, and VSE. The DB2
Enterprise Edition supports unlimited LAN database access.

DB2 Universal Database Extended Enterprise Edition

DB2 Universal Database Extended Enterprise Edition (formerly known as DB2 Parallel Edition) enables a
database to be partitioned across multiple independent computers of a common platform. SQL operations
and utilities can operate in parallel on the individual database partitions. Performance is enhanced by
speeding up the execution time of a single query or utility.

DB2 Software Developer's Kit (DB2 SDK)

DB2 SDK is a collection of tools that enable database application developers to build character-based,
multimedia or object-oriented applications. It includes libraries, header files, documented APIs and sample
programs.

The DB2 SDK can be used to develop applications that use the following interfaces:

• Embedded SQL, both static and dynamic

• Call Level Interface (CLI) development environment (compatible with ODBC from Microsoft)
• Java Database Connectivity (JDBC)
• Application programming interfaces to access database utilities

DB2 SDK supports several programming languages (including COBOL, FORTRAN, Java, C, and C++) for
application development, and provides precompilers for the supported languages. It is available on all DB2
UDB-supported platforms. The same application does not require any source changes to run against DB2
UDB on any Intel or UNIX platform; therefore, only one base code allows support for several platforms.

DB2 SDK also supports SQLJ. Along with DB2 JDBC support provided by the DB2 Client Application
Enabler (DB2 CAE), DB2 SQLJ support allows for the creation, build, and run of embedded SQL for Java
applications, applets, stored procedures and user-defined functions (UDFs). These contain static SQL and
use embedded SQL statements that are bound to a DB2 database.

© IBM Corporation Page: 7

Sybase to DB2 Migration - Comparison White Paper IBM

Other important DB2 products are:

• DB2® Connect Personal Edition, which provides access from a single workstation to DB2
databases residing on host systems such as MVS/ESA, OS/390, OS/400, VM and VSE, as well
as access to DB2 Universal Databases. This product is available for the OS/2, Windows 3.1x,
Windows NT, and Windows 95 operating systems. DB2 Connect Enterprise Edition provides
similar capabilities in a multi-user environment including UNIX systems, OS/2, and Windows NT.
• DB2® OLAP (online analytical processing) Server, which is designed for multidimensional
planning, analysis, and reporting applications.
• DB2 for Domino, which extends the capabilities of DB2 Universal Database to Lotus Notes and
Domino users.
• DB2 DataJoiner 2.1.1, which provides a single interface to heterogeneous databases. It provides
global query optimization, and supports most relational and non-relational database systems.

© IBM Corporation Page: 8

Sybase to DB2 Migration - Comparison White Paper IBM

Data Types Conversion

Most of the Sybase data types can be mapped to DB2 UDB. The following table compares all data types:
Sybase Data Range of Values Bytes of DB2 UDB Data Range of Values Bytes of
Type Name Storage Type Name Storage
tinyint 0 to 255 1 smallint -32768 to 32767. 2

smallint -32768 to 32,767 2 smallint -32768 to 32767. 2

int -231 ( -2,147,483,648) to 231 - 4 integer -231 to 231 - 1 4
integer 1 (2,147483,647) int
bigint 9223372036854775808 to 8
+9223372036854775807
numeric(p,s) -1038 to 1038 -1 2-17 num[eric](p,s) -1031+1 to 1031-1 (p/2) + 1
dec[imal](p,s) dec[imal](p,s) ( p+s <=31)
float(p) h/w dependent 4 or 8 1 float(p) 4 or 8

real h/w dependent 4 real 0 or from -3.402E+38 to - 4

1.175E-37, or from 1.175E-37
to 3.402E+38 ( 8 digits)
double h/w dependent 8 double precision 0 or from -1.79769E+308 to - 8
precision 2.225E-307, or from 2.225E-
307 to 1.79769E+308
(16 digits)
smallmoney -214,748.3648 to 4 numeric(10,4) 6
214,748.3647
money -922,337,203,685,477.5808 8 numeric(19,4) 11
to 922,337,203,685,477.5807
2 7
smalldatetime January 1, 1900 to June 6, 4 timestamp January 1, 0001 to December 10 internal,
2079 31, 9999 26 external
datetime January 1, 1753 to December 83 timestamp January 1, 0001 to December 10 internal,
31, 9999 31, 9999 26 external
timestamp4 January 1, 1753 to December 8 timestamp January 1, 0001 to December 10 internal,
31, 9999 31, 9999 26 external
date8 year: 0001 to 9999, 4 internal,
month: 1 to 12, day: 1 to 31 10 external
time9 hour: 0 to 24. 3 internal, 8
minutes/seconds: 0 to 59 external
char[acter](n) 0 to 255 n char[acter](n) 1 to 254 n
varchar(n) 0 to 255 entry length varchar(n) 1 to 4000 entry length
char[acter] character varying
varying
long varchar(n)10 1 to 32,700 entry length

nchar(n) 0 to 255 n * char size graphic(n) 1 to 127 2*n

5

nvarchar(n) 0 to 255 n * char size vargraphic(n) 1 to 2000 2 * entry

5
nchar varying length
long vargraphic(n)10 1 to 16,350 2 * entry
length
DBCLOB(n) 1 to 1 073 741 823 2 * entry
length
binary(n) 0 to 255 n character(n) FOR 1 to 254 n
BIT DATA
varbinary(n) 0 to 255 entry length varchar(n) FOR BIT 1 to 4000 entry length
DATA
bit 0 or 1 1 character(1) FOR 0 or 1 1
BITDATA11
text(n) 231 - 1 (2,147,483,647) multiples of CLOB(n) 1 to 231 entry length
a page 6
image 231 - 1 (2,147,483,647) multiples of a BLOB(n) 1 to 231 entry length
page 6

© IBM Corporation Page: 9

Sybase to DB2 Migration - Comparison White Paper IBM

Note: Some DB2 UDB datatypes not available in Sybase have been included on the table.
1
float(p) storage is 4 bytes if p < 8; 8 bytes if 8 < p < 16.
2
datetime values are accurate to 1/300 of a second on platforms that support this level of granularity. Storage size is 8
bytes: 4 bytes for the number of days since the base date of January 1, 1900 and 4 bytes for the time of day.
3
smalldatetime values are accurate to the minute. Storage size is 4 bytes: 2 bytes for the number of days since January 1,
1900 and 2 bytes for the number of minutes since midnight
4
timestamp is a Sybase SQL Server-supplied, user-defined datatype that is defined as varbinary(8) NULL. Used in tables
that are to be browsed in Client-Library applications (see "Browse Mode" for more information). SQL Server automatically
updates the timestamp column each time its row is modified. A table can have only one column of timestamp datatype.
5
allows national character set, where 1 character uses > 1 byte
6
0 until initialized, a page is 2K.
7
DB2 UDB time stamp format is YYYY-MM-DD-HH-MM-SS-NNNNNN (year-month-day-hour-minutes-seconds-
microseconds).
8
date is a three-part value, YYYY-MM-DD (year, month, and day), where year = 0001 to 9999, month = 1 to 12, and day =
1 to 31.
9
time is a three-part value, HH:MM:SS (hour, minute, and second), designating a time of day under a 24-hour clock.
10
Special restrictions apply to an expression resulting in a varying-length string data type whose maximum length is greater
than 254 bytes. Such expressions are not permitted in: a SELECT DISTINCT statement's SELECT list, a GROUP BY
clause, an ORDER BY clause, a column function with DISTINCT and a subselect of a set operator other than UNION
ALL.
11
FOR BIT DATA specifies that the contents of the column are to be treated as bit (binary) data. During data transfer with
other systems, code page conversions are not performed. Comparisons are done in binary, irrespective of the database
collating sequence.

© IBM Corporation Page: 10

Sybase to DB2 Migration - Comparison White Paper IBM

Administration Issues
This section compares the administrative features available in Sybase Adaptive Server version 11.5 and
DB2 UDB version 5.2.

Environments
In Sybase, several SQL servers can be created to define different environments. Sybase has a separate
server process for Backup.

DB2 UDB uses instances to provide separate environments within the same machine. Other instances
can also be used to restrict access to sensitive information or to limit the impact of instance unavailability.
However, multiple instances require additional system resources (memory and disk space) and more
administration. Backups are performed by a special instance called the administration server instance.

Database Devices
Sybase SQL Server uses database devices to store data for a Database. DB2 UDB stores data on table
spaces (Figure 3). A table space can be either a system managed space (SMS) or a database managed
space (DMS). For an SMS tablespace, each container is a directory within the operating system, and the
operating system's file manager controls the allocation of storage space. For a DMS tablespace, each
container is either a fixed-size pre-allocated file or a physical device such as a disk, and DB2 UDB
controls the storage space. A container is a physical storage device (directory, file, or device).

Figure 3 DB2 UDB Tablespaces

DB2 UDB has three table space types: regular, temporary and long. Regular table spaces are used for
tables, indexes, and system catalog tables. Temporary table spaces are used during SQL operations that

© IBM Corporation Page: 11

Sybase to DB2 Migration - Comparison White Paper IBM

required disk space, such as sorting or reorganizing tables, creating indexes and joining tables. Long table
spaces are used to store Large Object Data (LOB).

A single table space may consist of several containers. A database can use different table spaces for
indexes, tables and LOBs. The create table command is used to associate a table to a tablespace. It is
recommended that users allocate a container for each physical disk to enable I/O parallelism.

Log Files
Sybase log data is recorded on the database device or on a separate log device. DB2 UDB databases
have log files (devices) associated with them; table spaces are not used for log data. These logs record all
database changes. Active logs are used during crash recovery to prevent a failure (such as a system
power failure or an application error) from leaving a database in an inconsistent state. After a failure, the
following actions are taken to ensure the integrity of the database: changes already made but
uncommitted are removed from the database (rolled back), and all committed units of work, which may
not have been physically written to disk, are redone.

Circular and archive logging are two recovery methods available in DB2 UDB. Circular logging is the
default. It uses a number of online logs for crash recovery. Only full database off-line backups are valid for
recovery, and roll forward from the last backup is not allowed. The other type of recovery, archive logging,
enables forward recovery using active and archived logs to any point in time before the failure. A database
can be rolled forward after a full database backup has been restored up to the last completed transaction.
Once archive logging is enabled, online database backups can be performed.

Database Security
Sybase authentication is controlled by users, logins and groups, which are objects defined in the SQL
Server. DB2 UDB authentication of a user is completed using an external security facility such as the
native operating system security or distributed computing environment (DCE). A user must have a valid
login system name in order to gain access to a database.

Sybase authorization is defined by means of roles and privileges. The roles are as follows: SA, SSO and
OPER. Additionally, each database has a special user called database owner (dbo).

DB2 UDB authorization (Figure 4) is defined by means of a system of authorities and privileges. Each
authority has a group name assigned that can be managed using the operating system facility. Four
authorities are available: system administration, system control, system maintenance and database
administration. Sybase roles can be mapped to DB2 authorities, and assigned to users by becoming a
member of the group with the proper authority.

© IBM Corporation Page: 12

Sybase to DB2 Migration - Comparison White Paper IBM

Figure 4 DB2 UDB Authorization

Sybase uses permissions to restrict access to objects and commands based on a user's identity or group
membership. The commands grant and revoke are used to give users permission to create databases
and objects within a database, as well as access specified tables, views and columns.

In DB2 UDB, privileges enable users to create or access database resources. The following types of
object privileges exist: database, schema, table, view, package, and index. Most of Sybase permissions
can be mapped to privileges such as create table, create database, create view, and all object
permissions. DB2 UDB has privileges not available in Sybase, such as package and schema privileges.
Sybase stored procedure privileges can be mapped to DB2 UDB package privileges.

Sybase has a special system administrator user (SA) who is responsible for administrative tasks to setup
and maintain the Server. In DB2, the System Administration (SYSADM) authority is the highest level of
authority within the database manager, and controls all database objects. This parameter defines the
group name with SYSADM authority for the database. In UNIX, the initial value is null and defaults to the
primary group of the instance owner. In Windows NT, the value defaults to the Administrator Group.
Following installation, a different group name can be assigned to SYSADM within DB2 UDB.

Dump/Load
The dump/load commands on Sybase are limited to databases and transaction logs only. The dump
command can be executed while the database is active. It does not reflect any data changes made to the
database after the command begins. It supports point-in-time recovery and maintains a history of
database backups.

DB2 UDB backup/restore procedures can be performed on databases and tablespaces. Online backups
can be performed when archived logging is enabled. Point-in-time recovery is available. When recovering
from a system failure, the time specified should a time prior to the system failure.

© IBM Corporation Page: 13

Sybase to DB2 Migration - Comparison White Paper IBM

Jobs
Sybase allows suspended execution through the waitfor command in stored procedures and triggers. DB2
UDB offers a graphical user interface called Script Center to schedule a script to run at a later date or at a
regular interval. This is particularly useful for scheduling administrative tasks such as making backups.

System Stored Procedures

Sybase supplies system procedures used for getting reports from and updating system tables. These
procedures are located in a separate database sybsystemprocs and are owned by the System
Administrator.

DB2 UDB provides APIs for performing administration tasks such as creating, activating, backing up or
restoring a database. These APIs can also be invoked from DB2 SQL applications.

Sybase Central is the new graphical user interface (available on version 11.5) for managing Sybase
products. Sybase Central runs on Windows 95 or Windows NT 4.0.

DB2 UDB provides the Control Center, which is a graphical interface for OS/2, Windows 95, or Windows
NT, to manage a local database server or multiple remote database servers and the database objects
within.

From the Control Center, the following tasks can be performed on database objects:

• Create and drop a database

• Create, alter, and drop a table-space or table
• Create, alter, and drop an index
• Back up and recover a database or table space
• Define the replication sources and subscriptions to replicate data between systems
• Set database manager configuration values that affect performance
• Configure database manager communications parameters
• Generate database information in a profile that can be used to configure clients

DB2 UDB SmartGuides are also available on OS/2, Windows 95 or Windows NT as an aid to performing
common administration tasks. SmartGuides are available for adding or creating a database, creating
tables, creating tablespaces, backing up and restoring databases, configuring performance and tuning
parameters.

Implementation Differences
This section compares implementation features available in Sybase Adaptive Server version 11.5 and
DB2 UDB version 5.2.

© IBM Corporation Page: 14

Sybase to DB2 Migration - Comparison White Paper IBM

Isolation Levels
Sybase supports four isolation levels that are defined by numbers. Level 0 prevents other transactions
from changing data already modified, while other transactions can still read the uncommitted data ("dirty
reads"). Level 1, the default level, prevents dirty reads. Level 2 prevents non-repeatable reads and Level 3
prevents phantoms.

DB2 isolation levels refer to locking data in row units (occurs at the base table row). The DB2 UDB
supports four isolation levels: Read Stability, Repeatable Read, Cursor Stability, and Uncommitted Read.
Regardless of the isolation level, the database manager places exclusive locks on every row that is
inserted, updated, or deleted. Thus, all isolation levels ensure that any row that is changed by this
application process during a unit of work is not changed by any other application processes until the unit of
work is complete.
Sybase DB2 UDB
0 Uncommitted Read
1 (default) Cursor Stability (default)
2 Read Stability
3 Repeatable Read

Locking Mechanisms
Sybase has two levels of locking: page locks and table locks (row level locking is an option only in version
11.9). Lock promotion is controlled by the configuration parameter lock promotion and the system-stored
procedure sp_setpglockpromote to define the number of page locks that SQL Server acquires on a table
before it attempts to escalate to a table lock on a server-wide, per database and per table basis. In
previous versions, the number of page locks setting is 200 and could not be configured.

DB2 UDB employs row-level locking by default (page-level locking is not an option). The database
manager, however, can escalate a lock to the table level. DB2 UDB lock escalation can be influenced by
modifying the value of the maxlocks and/or the locklist parameters in the database configuration file.

System Databases
The master database controls the operation of the SQL Server as a whole and stores information about all
user databases and their associated database devices. DB2 UDB has a catalog table space
SYSCATSPACE, which contains all the system catalog tables for a single database. All other aspects of
database configuration can be controlled by the DB2 command interface or the Control Center. The
operating system security facility should be used to manage user accounts.

Sybase system procedures are stored in the database sybsystemprocs. The tasks automated by these
procedures can be performed using the DB2 UDB graphical interface Control Center to administer local
and remote databases or DB2 API’s (See section “System Stored Procedures” on page 14).

Sybase model database provides a template, or prototype, for new user databases. Typically, changes
made to the model database are adding user-defined datatypes, rules or defaults; adding users who
should have access to all databases; and granting default privileges, particularly for guest accounts. DB2
UDB does not require a model database: a script can be written to create a database, define datatypes
and grant privileges. Users that are already created can have access to all databases by use of group
membership or trusted connections.

Sybase temporary database tempdb provides a storage area for temporary tables and other temporary
working storage needs such as intermediate results of group by and order by. In DB2 UDB, each

© IBM Corporation Page: 15

Sybase to DB2 Migration - Comparison White Paper IBM

database has one or more temporary table spaces for such purposes. Having a table space instead of a
database provides the following advantages: applications running on different databases use different
table spaces (storage areas) and system managed space (SMS) table spaces need very little
administration (limited by file system free space).

Sybase provides sample databases pubs2 and pubs3, which can be optionally installed. DB2 UDB
provides a sample database called Sample, along with the API db2sampl to create this database. It also
provides First Steps, a graphic tool for Intel platforms that helps with creating and manipulating the
Sample database. The product documentation and sample programs refer to this database.

SQL
Sybase is compliant with the SQL92 Entry level. This complaint behavior is set by default for embedded
applications. The command set in Transact-SQL can be used to change it. Also to be compliant with the
entry-level SQL92, identifiers must not exceed 18 characters, begin with a pound sign (#) or contain
lowercase letters. Sybase Transact-SQL extensions allows ‘#’, lower case letters and 30-character
identifiers.

DB2 UDB is also compliant with the SQL92 Entry level, but includes features from the Intermediate and
Full levels, as well as the future SQL3. Identifiers cannot exceed 18 characters in length; however, the
SQL3 standard for allowing identifiers with 128 characters length is not yet implemented.

Tables
The following table summarizes the different limitations for tables between Sybase and DB2 UDB:

Description Sybase DB2 UDB

Table space Page Size 2K 4K or 8K
1
Maximum length of a row 1,962 bytes 4,005 or 8,101 bytes
1
Maximum columns in a table 250 500 or 1012
Maximum indexes in a table 249 32 767 or storage
Maximum tables in a database 2 billion 65 534
Maximum number of constraints 192 storage
on a table
1
Maximum columns in a view 250 500 or 1012
1
Maximum elements in a select 250 500 or 1012
Maximum tables referenced in a 16 storage
select or view
1
Maximum number of columns in 16 500 or 1012
an ORDER BY clause
1
Maximum total length of columns 2014 bytes 4,005 or 8,101 bytes
in an ORDER BY clause
1 These values depend on the table space page size 4K or 8K.

© IBM Corporation Page: 16

Sybase to DB2 Migration - Comparison White Paper IBM

Temporary Tables
Sybase supports local and global temporary tables. DB2 UDB does not currently support temporary
tables, but they can be implemented with DB2 UDB common table expressions or with the not logged
initially clause on the create table and alter table commands to provide temporary table characteristics.

Indexes
In Sybase, indexes are all created in ascending order: no clause exists in the command create index to
specify ordering. In version 11.9, the create index command has been modified to allow ordering
specification. In DB2 UDB, indexes can be defined in ascending or descending order. Bi-directional
indexes are not currently supported. The ordering property can be useful in executing queries with order
by and group by clauses.

Sybase uses a B-tree model to represent the cluster index in a sparse index (not every row has an index
entry). DB2 UDB creates indexes on a separate structure that replicate the key values. The cluster factor
of a clustering index is maintained or improved dynamically as data is inserted into the associated table by
attempting to insert new rows physically close to the rows for which the key values of this index are in the
same range. In both databases, only one clustered index per table is permitted.

Sybase has a fillfactor clause on create index to specify a percentage value as to how full SQL Server will
make each page when it is creating a new index on existing data. The default is 0 which completely fills
the pages. DB2 UDB has a pctfree clause on the create index command to specify the percentage of free
space. The default is 10%. This clause is for performance only since the index will continue to work with
slightly degraded performance.

IDENTITY Columns
Sybase SQL Server supports the IDENTITY constraint on numeric columns with a scale of 0. IDENTITY
columns start with 1 and increment by 1. DB2 UDB does not currently support this type of constraint, but
allows it to be implemented by using a combination of triggers and user-defined functions (UDFs), or by
using the generate_unique() function.

Constraints
Sybase allows the creation of defaults and rules for columns in a database to define default and check
constraints. Rules cannot be defined for an SQL Server-supplied datatype or to a column of type text,
image, or timestamp. In DB2 UDB, check and default constraints are defined only in the commands create
table and alter table at the column or table level. There are no restriction on data types.

Sybase integrity constraint definitions can indicate whether the index to be created is nonclustered
(default) or clustered. DB2 UDB creates a unique index, using ascending order for every column in the
key; if a cluster index is required, the command reorganize table, specifies an index, then uses that index
to physically reorder the records in the table.

Sybase referential constraints cannot cascade changes through related tables in the database. Triggers
must be used for this purpose. DB2 UDB referential constraint definitions have a rule clause to specify
what action to take on dependent tables. The delete rule has four possible actions : NO ACTION (default),
RESTRICT, CASCADE, and SET NULL. If RESTRICT or NO ACTION is specified, an error occurs and no
rows are affected. If CASCADE is specified, the operation is propagated to all the dependents rows. If

© IBM Corporation Page: 17

Sybase to DB2 Migration - Comparison White Paper IBM

SET NULL is specified, each nullable column of the foreign key of each dependent row is set to null. NO
ACTION and RESTRICT are the only possible actions on update.

Scrollable Cursors
Sybase does not support scrollable cursors. DB2 Call Level Interface (CLI) supports read-only scrollable
cursors to navigate forward, backward, or to an absolute position within the result set. This feature can be
very useful in GUI applications for displaying information in scroll boxes.

ANSI Join Operators

Sybase SQL Server has a specific syntax for right and left outer joins of *= and =*; however, full outer joins
are not supported. DB2 syntax for joins is ANSI-style, with the operators {INNER | LEFT [OUTER] | RIGHT
[OUTER] | FULL [OUTER]}. The ANSI join operators also follow the ANSI definitions for join behavior.

Transactions
Sybase defines a transaction by enclosing SQL statements and/or system procedures within the phrases
begin transaction, savepoint and commit. Savepoint provides a mechanism for selectively rolling back
portions of a batch. If chained transaction mode is enabled, SQL Server implicitly invokes a begin
transaction before the following statements: delete, insert, open, fetch, select, and update. A commit must
still explicitly close the transaction.

DB2 UDB Compound SQL (begin compound) allows you to group several SQL statements into a single
executable block. No savepoint mechanism is provided. Two types of compound SQL are available:

• Atomic – returns a response when all sub-statements have been executed successfully or when
one of them ends in an error. When an error occurs, the entire block is rolled back.
• Not Atomic – returns a response when all sub-statements have been executed, regardless of
whether or not a preceding sub-statement failed. The entire block is rolled back only when the unit
of work that contains it is rolled back.

Compound SQL is supported through embedded static SQL and the DB2 Call Level Interface.

Triggers
Sybase Triggers are coded using Transact-SQL and stored in the database. SQL Server allows nested
triggers by default.

DB2 UDB triggers are also stored in the database, and are compiled at runtime with the SQL statement
associated with the trigger. Multiple triggers can be created for the same event, activation time and subject
tables. The first trigger that is created is the first to be executed. A triggered action is composed of one or
more SQL statements or by an optional condition for the execution of the SQL statements. The maximum
depth of cascaded triggers is 16. Adding a trigger to a table that already has rows in it will not cause any
triggered actions to be activated.

DB2 UDB triggers provide referencing: correlation names are specified for the transition variables, and
table names for the transition tables. Correlation names identify a specific row in the set of rows affected

© IBM Corporation Page: 18

Sybase to DB2 Migration - Comparison White Paper IBM

by the triggering SQL operation, while table names identify the complete set of affected rows. Each row or
set of rows affected by the triggering SQL operation is available to the triggered action by qualifying
columns with correlation names and table names. The MS SQL Server if update (column) can be
converted to WHEN (old.column != new.column). DB2 UDB triggers cannot call stored procedures: if this
is required, it can be implemented by invoking UDFs from the trigger.

Stored Procedures
Sybase stored procedures are coded using Transact-SQL and stored in the database. The maximum
number of parameters in a stored procedure is 255.

DB2 UDB stored procedures (Figure 5) are compiled code libraries. DB2 does not provide a proprietary
4GL to program storedprocedures. 3GL languages, including C, C++, COBOL and Java, can be used to
code stored procedures using embedded static or dynamic SQL, CLI, or JDBC. Procedural logic can be
easily implemented in any of the programming languages to match Transact-SQL logic. The maximum
number of parameters is 32,767. Nested stored procedures are not currently supported.

Figure 5 DB2 UDB Stored Procedures

Global Variables
Sybase provides global variables to report system or connection information. DB2 UDB uses special
registers such as CURRENT SERVER, CURRENT DATE, CURRENT TIME, and USER for that purpose.

© IBM Corporation Page: 19

Sybase to DB2 Migration - Comparison White Paper IBM

Programming Interfaces
DB2 UDB provides the following programming interfaces to develop applications:

Embedded SQL
Embedded SQL uses SQL statements that are precompiled before a program is compiled. The SQL
statements can be static or dynamic.

DB2 Application Programming Interfaces (APIs)

Some database administration tasks, such as creating, activating, backing up, or restoring a database,
can be performed using DB2 APIs from an application, including embedded SQL and DB2 CLI
applications.

Java Development Kit

The JAVA Development Kit provides the tools and environment to develop Java applications and applets.
The kit includes the DB2 JDBC driver that supports Sun Microsystem's Java Database Connectivity
(JDBC) Application Programming Interface (API). This provides a standard way to access databases from
Java code.

DB2 Call Level Interface (CLI)

DB2 CLI is a callable SQL interface based on the X/Open CLI specification. It is compatible with the
Microsoft Corporation's Open Database Connectivity (ODBC). DB2 CLI is also a programming interface
that allows applications to access DB2 databases using dynamic SQL. These applications can be written
in C and C++. As such, DB2 CLI is an alternative to embedded dynamic SQL.

In addition to dynamic SQL, DB2 CLI offers the following advantages:

Portability - DB2 CLI applications use a standard set of functions to pass SQL statements to the
database. It is only necessary to compile and link DB2 CLI applications before execution: no precompile or
bind is needed.

No binding - There is no need to bind individual DB2 CLI applications to each database they access; only
one binding is needed to the bind files that are shipped with DB2 CLI, for all DB2 CLI applications.

Array fetching and input - DB2 CLI functions can retrieve multiple rows in the database into an array
with a single call. An SQL statement can be executed many times, using an array of input variables.

Consistent interface to catalog - DB2 CLI provides a consistent interface among systems to query
catalog information about tables, columns, foreign and primary keys, and user privileges.

Extended data conversion - DB2 CLI automatically converts data between SQL and C data types.

No global data areas - DB2 CLI eliminates the need for application-controlled global data areas, such as
SQLDA and SQLCA. Instead, it automatically allocates and controls the necessary data structures, and
provides a handle to let an application reference them.

Retrieve result sets from stored procedures - DB2 CLI applications can retrieve multiple rows and
result sets generated from a stored procedure residing on the server.

Scrollable cursors - DB2 CLI supports server-side scrollable cursors that can be used in conjunction with
array output. Only read-only scrollable cursors can be declared.

© IBM Corporation Page: 20

Sybase to DB2 Migration - Comparison White Paper IBM

Embedded SQL
Sybase provides precompilers for C and COBOL. DB2 UDB supports the C, C++, COBOL and FORTRAN
programming languages through its precompilers. It also supports the REXX language through a dynamic
interpreter, as well as the Java language.

Sybase uses the variables SQLCODE, SQLCA, and SQLSTATE to communicate between the SQL
Server and the application. When using DB2 UDB, the LANGLEVEL precompile option should be set to
SQL92E to declare SQLSTATE and SQLCODE fields explicitly as variables:

EXEC SQL BEGIN DECLARE SECTION;

char SQLSTATE[6]
long SQLCODE;
.
EXEC SQL END DECLARE SECTION;

With a few exceptions, Sybase allows the use of all Transact-SQL statements, functions and control-of-
flow language in Embedded SQL. DB2 UDB SQL and Transact-SQL extensions are different; therefore,
some Transact-SQL statements are not valid in DB2 UDB.

In Sybase, statements can be used to associate the descriptor with a SQL statement and with the
appropriate cursor associated with the SQL statement (allocate descriptor, get descriptor, set descriptor).
The DB2 UDB describe command obtains information about a prepared SQL statement.

In Sybase, the connect statement is used to establish a connection between an application program and
SQL Server. The connect statement is also available in DB2 UDB, but the syntax is slightly different: a
database name specification is mandatory, but the user specification is optional.

Sybase offers two ways to group statements: ANSI/ISO SQL and Transact-SQL transaction mode.
Transact-SQL transaction mode provides a save transaction or begin transaction statement. DB2 UDB
employs the ANSI/ISO SQL transaction mode for all programming APIs. A transaction begins implicitly
with the first executable SQL statement and ends with either a commit or a rollback statement, or ends
when the program ends.

Open Client and Open Server Libraries

Sybase Open Client provides the following several core programming interfaces to write client
applications: Client-Library and DB-Library. Sybase Open Server provides Server-Library for creating
server applications. These libraries offer different features and data structures for communication
(CS_CONNECTION, DBPROCESS).

DB2 UDB CLI is a callable SQL interface that can be used to program client applications as well as server
applications. The same application does not require any source changes to run against DB2 UDB on any
Intel or UNIX platform; therefore, only one base code allows support for several platforms.

These programming interfaces are very different, but the effort of porting applications to DB2 can be
significantly reduced by using conversion tools (see “Conversion Tools” on page 23).

© IBM Corporation Page: 21

Sybase to DB2 Migration - Comparison White Paper IBM

Terminology Map
The following table provides a list of basic DB2 UDB administration-related terms that are equivalent to
terms used by Sybase:

DB2 Universal Database Sybase

Physical Layer
Tablespace Segment
SMS tablespace n/a
DMS tablespace n/a
Container (raw or file) Database device (raw or file)
Logical Layer
Server Server
Instance (one or more. Each instance manages one or SQL Server
more databases.)
Database Database
Database directories (created by DB2) Interfaces file
Node directory (created by DB2) Interfaces file
Database Manager Configuration File Server configuration file
Database Configuration File Database options and server configuration file
Catalog tables System tables (master database and database)
Database Objects
Schema Schema
Table Table
Table constraint Rule and table constraint
View View
Index Index
Recovery log Transaction log
Archive log Transaction log dump
Users and user groups (operating system) Database users, groups and roles
Package n/a
Sample database (called sample) Sample database (called pubs2)
Administration / Usage
Control Center SQL Central
Tables assigned to tablespaces, containers assigned to Database devices assigned to databases, segments
tablespaces assigned to devices, tables assigned to segments
Administration commands and statements System stored procedures
Binding (a DB2 utility or a program so you can use it) n/a
Backup database Dump database
Archive online log files Dump transaction
Restore from backup Load database
Roll-forward recovery Load transaction
Crash recovery Automatic recovery
Run statistics Update statistics
Load, Import, Export bcp
Command Processor ISQL

© IBM Corporation Page: 22

Sybase to DB2 Migration - Comparison White Paper IBM

Conversion Tools
The most common approaches to converting a database applications are manual conversion, dynamic
call translation, and automated conversion. In general, conversion tools take in source code and translate
data management calls to an equivalent SQL call. Information from the source and target databases, as
well as program code, is used to build the new SQL statements. Some tools use an “expert” system to
make decisions over the generated SQL statements by cross-referencing the original and the new
databases.

SQL Conversion Workbench (SQL-CW)

One of the automated tools available today is the SQL Conversion Workbench. This PC-based tool kit
from Mantech Systems Solutions Corporation (MSSC) facilitates the conversion of various databases and
the associated applications to any database in the DB2 UDB family on any supported platform. MS SQL
Server is one of the database management systems supported.

The SQL-CW tool does the following:

• Provides metrics for the source database in order to estimate cost and effort
• Allows modifications to the design and data definition of the target database
• Generates DDL for the target database
• Unloads database data and creates load scripts
• Allows code re-engineering
• Generates procedural code for stored procedures and triggers
• Generates application code for DB-Lib, Client-Lib, and E-SQL applications

For more information, contact MSSC ( http://www.mantech.com/).

Data Junction
Data Junction offers a transformation tool for DB2 UDB data migration and application integration. It is a
visual design tool for building and testing data transformations that work between DB2 and other data
formats such as Microsoft SQL Server. Microsoft SQL Server is supported via a native API, a Massive
Insert API and the bcp command.

Projects and transformations designed with Data Junction can be executed by the DJEngine. This tool is
an engine that executes data transformations on demand or as scheduled. The graphic interface allows
the definition of source-to-target mapping and transformation rules. It accounts for data type differences,
and can set various filters to dynamically modify target columns during the conversion process.

For additional information, contact Data Junction Corporation (http://www.datajunction.com).

© IBM Corporation Page: 23

Sybase to DB2 Migration - Comparison White Paper IBM

PLATINUM ERwin
ERwin is a database design tool that aids in designing and maintaining database applications. A logical
model, along with business rules, defines the database, and a physical model represents the target
database. ERwin allows visualization of the structure, key elements and design of a database. It
automatically generates tables, stored procedures and trigger code for leading databases such as DB2
UDB and Microsoft SQL Server.

ERwin can also be used to reverse-engineer database objects using a DDL script or existing database.
The physical model allows users to select different target databases and generate DDL script for every
target. Using this feature, DDL scripts for different databases and versions can be easily supported.
For more information, contact PLATINUM Technologies Inc.
(http://www.platinum.com/products/ap_dev.htm).

© IBM Corporation Page: 24

Sybase to DB2 Migration - Comparison White Paper IBM

Resources and References

DB2 Universal Database Documentation
Quick Beginnings for Windows NT
Administration Guide
SQL Reference
Road Map to DB2 Programming
DB2 Universal Database Certification Guide, 2nd Edition
by Calene Janacek and Dwaine Snow.
Published by Prentice Hall, 1997. ISBN 0-13-079661-1.
A Complete Guide to DB2 Universal Database
by Don Chamberlin.
Published by Morgan Kaufmann, 1998. ISBN 1-55860-482-0
Sybooks , Sybase documentation online
Reference Manual
Transact-SQL User’s Guide
System Administration Guide
What’s New in Sybase Adaptive Server version 11.5 ?
New Functionality in Adaptive Server Enterprise 11.9.2
Sybase SQL Server 11
by John Kirkwood
Published by International Thomson Computer Press.
SQL Conversion Workbench User's Guide
by Allyson Hart Benavides
Published by Mantech System Solutions Corporation, 1998. No. 986ASQL-CW
100GB TPC-D Benchmark published on December 1st., 1998
http://www.software.ibm.com/data/db2/benchmarks/netfinity100_120198.html
http://www.tpc.org/results/FDR/TPCD/ibm.7000m10.98120101.fdr.pdf (Full Disclosure
Report)
DB2 Family Benchmarks
http http://www.software.ibm.com/data/db2/benchmarks/
Sun Microsystems: News and Events Press Releases
http://www.sun.com/smi/Press/sunflash/9711/sunflash.971119.3.html
For more information ...
DB2 Family
http://www.software.ibm.com/data/db2
DB2 Product and Service Technical Library
http://www.software.ibm.com/data/db2/library
DB2 Maintenance
http://www.software.ibm.com/data/db2/db2tech/indexsvc.html
ftp://ftp.software.ibm.com/ps/products/db2/fixes/<language>/<platform>/<FixPak#>
IBM Solution Developer Program
http://www.developer.ibm.com/
Internet Newsgroup
news://comp.database.ibm-db2
CompuServe
GO IBMDB2

© IBM Corporation Page: 25

Sybase to DB2 Migration - Comparison White Paper IBM

Trademarks
The following terms are trademarks or registered trademarks of the IBM Corporation in the United States
and/or other countries:
AIX IMS
AIXwindows MVS/ESA
AS/400 MVS/XA
C Set++ OS/400
C/370 OS/390
DATABASE 2 OS/2
DataJoiner RISC System/6000
DataPropagator SQL/DS
DataRefresher SQL/400
DB2 S/370
DB2 Connect System/370
DB2 Universal Database System/390
DB2 OLAP Server VisualAge
Distributed Relational Database Architecture VM/ESA
DRDA VSE/ESA
IBM VTAM
WIN-OS/2

The following terms are trademarks or registered trademarks of the companies listed:

HP-UX is a trademark of Hewlett-Packard.

Java and HotJava are trademarks of Sun Microsystems, Inc.

Microsoft, Windows, Windows NT, Windows 95 and the Windows 98 are trademarks or registered
trademarks of Microsoft Corporation.

SQL Conversion Workbench is a trademark of Mantech Systems Solutions Corporation.

Solaris is a trademark of Sun Microsystems, Inc.

Sybase, Adaptive Server, SQL Server, Transact-SQL, Open Client, and Open Server are trademarks of
Sybase, Inc. or its subsidiaries.

UNIX is a registered trademark in the United States and other countries licensed exclusively through
X/Open Company Limited.

TPC Benchmark, TPC-D, QppD, QthD, and QphD are trademarks of the Transaction Processing
Performance Council.

Other trademarks and trade names mentioned herein are the property of their respective owners.

© IBM Corporation Page: 26