| Greg Fenton 2005-07-19, 11:24 am |
| Kevin Dunn wrote:
> 1. Create the new tables and mobilink scripts on the consolidated database
> 2. Drop the synchronization definition on the remote database
> 3. Create the new tables on the remote database
> 4. Recreate the synchronization definition with the new tables.
>
Step 2a. Disallow any new connections to the database
Step 2b. Successfully synchronize the remote
Step 2c. Drop the synchronization definition on the remote database
> My question is that data entered after their last successful
> synchronization session will it be contained in the next synchronization
> session or will the synch session only contain data that was entered
> after the time when the new synchronization definition was created?
As the database engine performs any DML actions, it logs to the
transaction log which publications (if any) that particular action
affects. When dbmlsync runs, it scans the *transaction log* to find out
which actions need to be synchronized.
So if changes are made to the database when no publication exists or if
they don't match a publication's WHERE clause, those changes will not be
synchronized. If a publication is added (or modified), previous data
changes will not be synchronized as they would not have been logged with
this new publication.
Does this help?
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|