On the Download Subset tab, you can specify whether downloads contain the same rows for all remote databases or if different remote databases receive different subsets of the rows. This tab does not apply if you chose Custom for the download type on the Download Type tab.
Download Subset Choose one of the following options from the dropdown list to subset data:
None Download the same data to each remote database.
User The rows in the download are determined based on the synchronization user (also known as a MobiLink user) that is synchronizing.
Remote The rows in the download are determined based on the remote ID of the remote database synchronizing. It is usually better to partition by user or by authentication parameter than by remote ID, because the remote ID can change if the remote computer is reset or replaced.
Custom The rows in the download are determined by a SQL WHERE clause that you write. This option is useful when you need multiple joins or particular business logic in your download cursor WHERE clause.
For subset by user, the Download Subset tab shows the following information for the selected table mapping:
Use a column in the consolidated table Select this option if the table contains a column that holds the MobiLink user name that should receive the row. Rows are included in the download if the value of the column matches the name of the MobiLink user that is synchronizing.
Column name Specify the name of the column that holds the MobiLink user name.
Use a column in a joined relationship table Select this option if the table can be joined to another table, and that other table contains a column, such as ID, that identifies the MobiLink user that should receive the row. Rows are included in the download if there exists a row in T1 join T2 where ID matches the name of the remote ID of the client that is synchronizing.
You can specify:
Table to join Select the table to join to.
Column to match Select the column from the joined table (specified in the Table to join field) that contains the remote ID.
Join condition Create a join condition by choosing a column from the table chosen in the Table Mappings pane and choosing a column from the table specified in the Table to Join field above.
For subset by remote ID, the Download Subset tab shows the following information for the selected table mapping:
Use a column in the consolidated table Select this option if the table contains a column that holds the MobiLink user name that should receive the row. Rows are included in the download if the value of the column matches the name of the MobiLink user that is synchronizing.
Column name Specify the name of the column the holds the MobiLink user name.
Use a column in a joined relationship table Select this option if the table can be joined to another table, and that other table contains a column, such as ID, that identifies the MobiLink user that should receive the row. Rows are included in the download if there exists a row T1 join T2 where ID matches the name of the ML user that is synchronizing.
You can specify:
Table to join Select the table to join to.
Column to match Select the column from the joined table (specified in the Table to join field) that contains the MobiLink user name.
Join condition Create a join condition by choosing a column from the table chosen in the Table Mappings pane and choosing a column from the table specified in the Table to Join field above.
Custom For a custom download subset, the Download Subset tab shows the following.
Tables to add to the download cursor's FROM clause Type the table name(s) if your download_cursor requires a join to other tables. If the join requires multiple tables, separate them with commas.
SQL Expression to use in the download cursor's WHERE clause
Type the SQL expression. You may use MobiLink named parameters in your expression. For example, col1 = {ml s.username}. See Named script parameters.
By default the same expression and joined tables are used for the download delete subset. If you are using a shadow table for deletes and want to use the same expression, avoid using the base table name in the expression. If that is not possible, use a custom download delete subset.
See also |
Discuss this page in DocCommentXchange.
|
Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0 |