SYBASE PRODUCTS:

    ASE.  Base DB, formerly "SQL Server".  (what we have)
    ASA:  For embedded stuff
    REP:  Replication server

Current version 12.5.3.

infotech02 Sybase instance:

    Currently running ASE 11.5.1, 03/14/1998 (don't know if that's the ASE
    release date or the install date).

    Init script on infotech02 SUCKS.  It just runs
        su - sybase -c '/sybase/bin/sybstart'
    for "start".

    You can start up Sybase with a -psa switch to generate and echo a new
    sa password:
    http://www.isug.com/Sybase_FAQ/ASE/section1.1.html#1.1.14
    (N.b.: That page is for v. 1..02.)

    http://www.sybase.com/detail?id=1017357
    Use the "sqlupgrade" utility.

Shutdown

    Just kill -TERM all of the processes "databasever", "backupserver",
     "sybmultbuf".  Kill -KILL those that remain.

Startup

    ... well, the DBNAME is apparently just an identifier, because the
    "DB name" is "master"!
    install/startserver -f RUN_<DBNAME>
    where RUN_<DBNAME> is a shell script that runs ".../bin/dataserver" or
    ".../bin/backupserver".  dataserver/backupserver are the programs that
    take the "-psa" reset password arg.

usage: isql [-b] [-e] [-F] [-p] [-n] [-v] [-X] [-Y]
        [-a display_charset] [-A packet_size] [-c cmdend] [-D database]
        [-E editor [-h header [-H hostname [-i inputfile]
        [-I interfaces_file] [-J client_charset] [-K keytab_file]
        [-l login_timeout] [-m errorlevel] [-M labelname labelvalue]
        [-o outputfile] [-P password] [-R remote_server_principal]
        [-s col_separator] [-S server_name] [-t timeout] [-U username]
        [-V [security_options]] [-w column_width] [-z localename]
        [-Z security_mechanism]
isql -D database -P password -S server_name -U username
isql -P pasword -U blaine -S infotech03  # (no -D switch!)
WORKS:
    export SYBASE=/sybase
    isql -P blaine -U blaine -D master -S infotech02
    sp_help
    go
Looks like you always run "user mydb\ngo\nsomething\go", (but they never
give the db name).
sp_who and dbcc seem to be important commands.
Execute commands with "go" on its own line, not ";".

Some "interfaces file" tells the ports, etc.  /sybase/interfaces.
I think a TLI string is kept in this file.  Script tliToAddr.pl converts
from a TLI hex string to an IP addr:port.
INFOTECH02 ADDR/PORTS:
    infotech02 - master on port 4100, host 199.223.18.19
    infotech02 - query on port 4100, host 199.223.18.19
    infotech02_back - master on port 4200, host 199.223.18.19
    infotech02_back - query on port 4200, host 199.223.18.19


Theres a Java interface: jisql.  Like a thin driver, you must know
the ports, not just DB name.

ADMIN
    Use "sa" account, or enable and use "sa_role".


New SSO password for sa: tmfyrkdwpibung


JDBC
Must install some Metadata before can use JDBC.
Documented in the jConnect documentation.
Ignore the error messages when you execute their sql file.
JDBC_HOME variable is entirely unnecessary.
Can run sp_* commands over JDBC.

Driver lib is jconn3.jar.
jdbc:sybase:Tds:<HOST>:<PORT>[/databasename]
com.sybase.jdbc3.jdbc.SybDriver

CREATE NEW ACCOUNT
    sp_addlogin username, password
    (This appears to silently fail if user exists)

CHANGE PASSWORD:
(N.b., passwords are supplied without quotes, but the string 'null' is magical).
To change your own:
    sp_password oldpassword, newpassword
Use "null" to mean blank password.
I don't know how to change somebody else's, but can use sp_blank_password script
to blank it then user the sp_password script. N.b. you must run
"set chained off" before sp_blank_password will work.
    sp_blank_password username
Looks like the real user table is "syslogins" not "sysusers".

Role table is syssrvroles

Grant the role sa_role to make a user into an Admin.


DISK USAGE:  1.2G all in files in /sybdata.


DATABASES
    Databases seem more similar to SQL Server databases than Oracle or
    HSQLDB database instances.
    "master" has all 44 system tables; others have only 21, such as
     sysusers, but are significantly missing syslogins and sysdevices.
    "master" has 11 non-system tables, 1 jdbc_* + 10 spt_* (probably
     "support" tables for features.

Some useful info re. checking versions, and paching:
http://scn.sap.com/thread/3430629

ESD installation video:  https://www.youtube.com/watch?v=fGqfrogatIA
They call this ESD Upgrade, not Patch.
For graphical install, run "setup.bin" from ESD distro dir like "ebf20373".
Then use isql to execute some (depending on your features) scripts from a
  scripts (I think under the ASE home).

One way to get version:  In isql run:
    select @@version
    go
Or:  $SYBASE/$SYBASE_ASE/bin/dataserver -v