		A Look at the SERVER Directory for PB 12.5
			Last Updated: 11/23/2010


Overview
---------
The Server directory is a repository for scripts that do not get compiled
during normal build processing of the PowerBuilder and InfoMaker products.
Moreover, files in this directory are not downloaded from the CD during a
PowerBuilder or InfoMaker installation. 

Scripts stored in the Server directory are typically run by a database
administrator at the customer site. Procedures for installing these scripts
on server databases are thoroughly documented in "Connecting to Your Database". 


Contents of the Server Directory
---------------------------------
PBSYC.SQL - Transact SQL that creates stored procedures used by PBSYC125.DLL. 
pbsyc.sql includes stored procedures used to provide superior performance in the
PowerBuilder development environment when connected to a database using 
PBSYC125.DLL. Running pbsyc.sql before using PBSYC125.DLL is recommended but
not required. 

PBSYC2.SQL - Transact SQL that creates an optional replacement for the 
sp_pb125table procedure. If the DBA at a customer site should decide to implement
this variant of sp_pb125table, s/he should run pbsyc2.sql after first running
pbsyc.sql. 

PBASE.SQL - Transact SQL that creates stored procedures used by PBASE125.DLL. 
pbase.sql includes stored procedures used to provide superior performance in the
PowerBuilder development environment when connected to a database using 
PBASE125.DLL. Running pbase.sql before using PBASE125.DLL is recommended but
not required. This script can only be run on a database server running ASE 15.0 
or a higher version.

PBASE2.SQL - Transact SQL that creates an optional replacement for the 
sp_pb125table procedure. If the DBA at a customer site should decide to implement
this variant of sp_pb125table, s/he should run pbase2.sql after first running
pbase.sql. This script can only be run on a database server running ASE 15.0 
or a higher version.

DB2SYSPB.SQL - Since the DBA at most DB2/MVS sites creates all tables, chooses
which tablespace to put them in, and restricts access to specific groups of users,
this script provides template DDL for creating the PowerBuilder extended catalog
tables for DB2/MVS. The definition of the PowerBuilder extended catalog has not 
changed since PowerBuilder 5.0, so db2syspb.sql does not need to be rerun by 
existing PowerBuilder customers. 

IQPB.SQL - This script should be run against Sybase Adaptive Server IQ v.12.0.0
using the provided Adaptive Server Anywhere ODBC driver. Doing so will create
the PowerBuilder extended catalog information in a Sybase IQ (SAINT) database.
 
