By creating the table using SYNCHRONIZE OFF, you control when to exclude the entire table from the upload operation. You can use these non-synchronizing tables for client-specific persistent data that is not required in the consolidated database. Other than being excluded from synchronization, you can use these tables in exactly the same way as other tables in the UltraLite database.
The synchronization type for a table can only be changed if it does not have any unsynchronized changes that need to be uploaded.
If you create a table with a _nosync suffix, you can only rename that table so it retains the _nosync suffix. For example, the following ALTER TABLE statement with a rename clause is not allowed because the new name no longer ends in nosync:
ALTER TABLE purchase_comments_nosync RENAME comments; |
To correct this, the statement must be rewritten to include this suffix:
ALTER TABLE purchase_comments_nosync RENAME comments_nosync; |
You can alternatively use publications to achieve the same effect.
As an alternative to creating or altering a table with the SYNCHRONIZE OFF clause, you can append the phrase _nosync to the table name to turn it into a non-synchronizing table.
See also |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |