You can append either _allsync or _nosync to a table name to control data restriction for synchronization. You can use these suffixes as an alternative to using publications to control data restrictions. To control data priority, define one or more publications.
If you create a table with a name ending in _allsync, all rows of that table are synchronized at each synchronization—even if they have not changed since the last synchronization.
You can store user-specific or client-specific data in allsync tables. If you upload the data in the table to a temporary table in the consolidated database on synchronization, you can use the data to control synchronization by your other scripts without having to maintain that data in the consolidated database.
If you create a table with a name ending in _nosync, all rows of that table are excluded from synchronization. You can use these tables for persistent data that is not required in the consolidated database's table.
In the CustDB.udb sample database, you can see one table was declared a nosync table because the table name is defined as ULIdentifyEmployee_nosync. Therefore, no matter how data changes in this table, it is never synchronized with MobiLink and information will not appear in the CustDB.db consolidated database.