downloaded developer addition.

registration key: QEDDE-C888A-6N000-24190-11131

database is now running

dba | [password]
10.168.11.58:2630
database: demo

From Ivan :

=================================================================================
New SQL Anywhere TYPE-2 JDBC driver   A new TYPE-2 JDBC driver is now available for JDBC applications to use when
connecting to SQL Anywhere.  Unlike the iAnywhere JDBC driver, which sits on top of ODBC and can be used to connect
to a variety of servers via ODBC, the SQL Anywhere JDBC
driver connects to SQL Anywhere only and does not require the SQL Anywhere ODBC driver to be installed or registered.
The SQL Anywhere JDBC driver comes with a JDBC 3.0 driver and a JDBC 4.0 driver.
Note
If you currently use the iAnywhere JDBC driver, it is strongly recommended that you change to the new SQL Anywhere
JDBC driver.
The JDBC 4.0 driver automatically loads and registers itself.
To use the version 3.0 SQL Anywhere JDBC driver, you must load the sybase.jdbc.sqlanywhere.IDriver class that
implements the java.sql.Driver interface and registers the SQL
Anywhere JDBC driver with the JDBC driver manager. Once loaded, connections using the SQL Anywhere JDBC driver
can be made by using the URL jdbc:sqlanywhere:connection-string-parameters.
The connection-string-parameters are the standard connection parameters required to connect to SQL Anywhere.
Note that the application no longer needs to specify DRIVER= or DSN= in
connection-string-parameters when using the SQL Anywhere JDBC driver. See JDBC support.


New support for JDBC Statement class methods   Previously, the JDBC drivers only supported the addBatch and executeBatch
methods of the PreparedStatement class. The JDBC drivers now also
support the addBatch, clearBatch, and executeBatch methods of the Statement class. Due to the fact that the JDBC
specification is unclear on the behavior of the executeBatch method of the
Statement class, the following notes should be considered when using this method with the SQL Anywhere JDBC drivers:
   1. Processing of the batch stops immediately upon encountering a SQL exception or result set. If processing of the batch
stops, then a BatchUpdateException will be thrown by the
        executeBatch method. Calling the getUpdateCounts method on the BatchUpdateException will return an integer array
of row counts where the set of counts prior to the batch failure
        will contain a valid non-negative update count; while all counts at the point of the batch failure and beyond will contain
a -1 value. Casting the BatchUpdateCount to a SQLException
        provides additional details as to why batch processing was stopped.
   2. The batch is only cleared when the clearBatch method is explicitly called. As a result, calling the executeBatch method
repeatedly will re-execute the batch over and over again. In
        addition, calling execute( sql_query ) or executeQuery( sql_query ) correctly executes the specified SQL query, but
does not clear the underlying batch. Hence, calling the executeBatch
        method followed by execute( sql_query ) followed by the executeBatch method again will execute the set of batched
statements, then execute the specified SQL query, and then execute
        the set of batched statements again.
===================================================================================
CREATE SPATIAL REFERENCE SYSTEM statement           -- object.  create/drop/alter.  ST_SPATIAL_REFERENCE_SYSTEMS
CREATE SPATIAL UNIT OF MEASURE statement            -- object.  create/drop.  ST_UNITS_OF_MEASURE
there are many new system procedures to work with the top two objects.
couple new catalog tables for the above objects have been added.


Database mirroring enhancements: You can now set up a database mirroring system using SQL statements
instead of specifying mirroring settings on the database server command line. You must upgrade or
rebuild existing databases to use this feature.
CREATE MIRROR SERVER statement                      -- object. create/alter/drop/set. COMMENT statement.
SYSMIRRORSERVER / SYSMIRRORSERVEROPTION / SYSMIRROROPTION
new procedures to support above object.

CREATE SEQUENCE statement                           -- object. create/alter/drop. COMMENT, GRANT, REVOKE statements. 
SYSSEQUENCE / SYSSEQUENCEPERM

*CREATE MATERIALIZED VIEW statement `               -- THIS IS NOT NEW TO 12 BUT ITS SUPPORTED AND
WE AREN'T SUPPORTING IT ? there are some new features added to matvies in 12.


CREATE SYNCHRONIZATION PROFILE statement            -- object. create/atler/drop. SYSSYNCPROFILE

CREATE INDEX statement -- New WITH NULLS NOT DISTINCT clause

=======================================================================================
New IF NOT EXISTS clause   With the new IF NOT EXISTS clause, no changes are made and an error is not returned if the
named object already exists. See:

    * CREATE INDEX statement
    * CREATE PUBLICATION statement [MobiLink] [SQL Remote]
    * CREATE SPATIAL REFERENCE SYSTEM statement
    * CREATE TABLE statement
    * CREATE TEXT INDEX statement

New IF EXISTS clause   The new IF EXISTS clause allows you to specify that you do not want an error returned when the DROP
statement attempts to remove a database object that does not exist. See:

    * DROP EVENT statement
    * DROP FUNCTION statement
    * DROP INDEX statement
    * DROP MATERIALIZED VIEW statement
    * DROP PROCEDURE statement
    * DROP PUBLICATION statement [MobiLink] [SQL Remote]
    * DROP SPATIAL REFERENCE SYSTEM statement
    * DROP SPATIAL UNIT OF MEASURE statement
    * DROP SYNCHRONIZATION PROFILE statement [MobiLink]
    * DROP TABLE statement
    * DROP TRIGGER statement
    * DROP VARIABLE statement
    * DROP VIEW statement

New OR REPLACE clause   The new OR REPLACE clause allows you to create or replace a profile or variable of the same name. See:

    * CREATE FUNCTION statement (external procedures)
    * CREATE FUNCTION statement (web clients)
    * CREATE FUNCTION statement
    * CREATE MIRROR SERVER statement
    * CREATE PROCEDURE statement (external procedures)
    * CREATE PROCEDURE statement (web clients)
    * CREATE PROCEDURE statement [T-SQL]
    * CREATE PROCEDURE statement
    * CREATE SEQUENCE statement
    * CREATE SPATIAL REFERENCE SYSTEM statement
    * CREATE SYNCHRONIZATION PROFILE statement [MobiLink]
    * CREATE TRIGGER statement
    * CREATE VARIABLE statement
    * CREATE VIEW statement


===============================================================================================
New START SERVER statement   The START SERVER statement has been added. It should be used instead of the START ENGINE statement,
which is now deprecated. See START SERVER statement [Interactive SQL].
New STOP SERVER statement   The STOP SERVER statement has been added. It should be used instead of the STOP ENGINE statement,
which is now deprecated. See STOP SERVER statement.
===============================================================================================

===============================================================================================
DATATYPES:
TIMESTAMP WITH TIME ZONE data type: Stores a point in time with a time zone offset. See TIMESTAMP WITH TIME ZONE data type.
The alias DATETIMEOFFSET is also supported. See DATETIMEOFFSET data type.

*CHAR, NCHAR, NVARCHAR, and VARCHAR data types support 32767 character length

*Data types for spatial data type: [I THINK THESE WILL RETURN AS (ST_Geometry)]
ST_CircularString
ST_CompoundCurve
ST_Curve
ST_CurvePolygon
ST_GeomCollection
ST_Geometry
ST_LineString
ST_MultiCurve
ST_MultiLineString
ST_MultiPoint
ST_MultiPolygon
ST_MultiSurface
ST_Point
ST_Polygon
ST_SpatialRefSys
ST_Surface
==============================================================================================
Reserved words   The following is a list of reserved words added to the database in SQL Anywhere version 12.0.0:
      datetimeoffset
      inner
      openxml
      spatial
      treat
The following is a list of reserved words removed from the database in SQL Anywhere version 12.0.0:
      index_lparen
      lock
      with_cube
      with_lparen
      syntax_error
      with_rollup