CREATE PUBLICATION [ IF NOT EXISTS ] [ owner. ]  publication-name
( article-definition, ... )

article-definition :
  TABLE table-name [ ( column-name, ... ) ]
[ WHERE search-condition ]

CREATE PUBLICATION  [ IF NOT EXISTS ] [ owner.]
WITH SCRIPTED UPLOAD 
( article-definition, ... )

article-definition :
  TABLE table-name [ ( column-name, ... ) ] 
[ USING ( [ PROCEDURE ] [ owner.][procedure-name ] 
   FOR UPLOAD { INSERT | DELETE | UPDATE }, ... ) ]

CREATE PUBLICATION [ IF NOT EXISTS ] [ owner.] publication-name
FOR DOWNLOAD ONLY
( article-definition, ... )

article-definition :  TABLE table-name [ ( column-name, ... ) ]

CREATE PUBLICATION [ IF NOT EXISTS ] [ owner.] publication-name
( article-definition, ... )

article-definition :
  TABLE table-name [ ( column-name, ... ) ]
[ WHERE search-condition ]
[ SUBSCRIBE BY expression ]

The CREATE PUBLICATION statement creates a publication in the database. A publication can be created for another user by specifying an owner name.

In MobiLink, publications are required in SQL Anywhere remote databases, and are optional in UltraLite databases. These publications and the subscriptions to them determine which data is uploaded to the MobiLink server.

You set options for a MobiLink publication with the ADD OPTION clause in the CREATE SYNCHRONIZATION SUBSCRIPTION statement or ALTER SYNCHRONIZATION SUBSCRIPTION statement.

Syntax 2 creates a publication for scripted uploads. Use the USING clause to register the stored procedures that you want to use to define the upload. For each table, you can use up to three stored procedures: one each for inserts, deletes, and updates.

Syntax 3 creates a download-only publication that can be synchronized with no transaction log file. When download-only publications are synchronized, downloaded rows may overwrite changes that were made to those rows in the remote database.

In SQL Remote, publishing is a two-way operation, as data can be entered at both consolidated and remote databases. In a SQL Remote installation, any consolidated database and all remote databases must have the same publication defined. Running the SQL Remote extraction utility from a consolidated database automatically executes the correct CREATE PUBLICATION statement in the remote database.

DBA authority and exclusive access to all tables referred to in the statement.

Automatic commit.

• ALTER PUBLICATION statement [MobiLink] [SQL Remote]
• DROP PUBLICATION statement [MobiLink] [SQL Remote]
• CREATE SYNCHRONIZATION SUBSCRIPTION statement [MobiLink]
• ALTER SYNCHRONIZATION SUBSCRIPTION statement [MobiLink]
• SQL Anywhere MobiLink clients: Publishing data
• UltraLite MobiLink clients: CREATE PUBLICATION statement [UltraLite] [UltraLiteJ]
• SQL Remote: Publications and articles
• Scripted upload
• Download-only publications
• ISYSSYNC system table

The following statement publishes all columns and rows of two tables.

CREATE PUBLICATION pub_contact (
   TABLE Contacts,
   TABLE Company
);

The following statement publishes only some columns of one table.

CREATE PUBLICATION pub_customer (
   TABLE Customers ( ID, CompanyName, City )
);

The following statement publishes only the active customer rows by including a WHERE clause that tests the Status column of the Customers table.

CREATE PUBLICATION pub_customer (
   TABLE Customers ( ID, CompanyName, City, State, Status )
   WHERE Status = 'active'
);

The following statement publishes only some rows by providing a subscribe-by value. This method can be used only with SQL Remote.

CREATE PUBLICATION pub_customer (
   TABLE Customers ( ID, CompanyName, City, State )
   SUBSCRIBE BY State
);

The subscribe-by value is used as follows when you create a SQL Remote subscription.

CREATE SUBSCRIPTION TO pub_customer ( 'NY' )
   FOR jsmith;

The following example creates a MobiLink publication that uses scripted uploads:

CREATE PUBLICATION pub WITH SCRIPTED UPLOAD (
      TABLE t1 (a, b, c) USING (
         PROCEDURE my.t1_ui FOR UPLOAD INSERT,
         PROCEDURE my.t1_ud FOR UPLOAD DELETE,
         PROCEDURE my.t1_uu FOR UPLOAD UPDATE
      ),
      TABLE t2 AS my_t2 USING (
         PROCEDURE my.t2_ui FOR UPLOAD INSERT
      )
   );

The following example creates a download-only publication:

CREATE PUBLICATION p1 FOR DOWNLOAD ONLY (
   TABLE t1
);