Does column order matter?
No! Never!
What indexes are useful?
That's a question with a long answer. Check out the Type-1 and Type-2 pages.
Can the same source table be used for multiple targets?
Yes. However, you should make sure that the
Can multiple sources be used to load the same target table?
No
Can a source table be loaded if it has no update-date column?
Yes. Just leave the SourceUpdateDateColumn column in SyncConfig null for the relevant sync/diff.
Can you use a view as the source?
Sure.
Can you use a view as the target
Sure.
What types of processing are supported?
Currently there is support for Type-1 (non-deleting) and Type-2 tables.
Can a table be sync'd if it doesn't have a primary key?
Sort of. You don't need a primary key index defined in the source, but you must configure one in the SyncConfig table.
What happens if there are duplicates?
If there are duplicate entries for a single PK and source update-date value, then the sync will fail for that table.
If no source update-column is specified, the sync will fail if there are any duplicates for a single PK.
What about case sensitivity in data?
Right now case-sensitive changes in the data are ignored, so if you change 'this is sparta' to 'THIS IS SPARTA', the diff code will ignore the change. It's on the roadmap of things to change
What about case sensitive SQL instances?
This is not supported at all yet. Feel free to contribute if this is something you want to add.