| Greg Fenton 2005-08-15, 3:24 am |
| MJN wrote:
> I have 3 remotes where I need to make some schema changes.
> Before I do these changes I will make sure all db's a fully synced up to
> date then will turn off the sync and the actual db servers.
>
> My question is should I make all the changes to each db or just to one and
> then redistribute that one to all remotes and consolidated?
> In theory this should be fine but want to take the safest but also the
> quickest approach..
This depends on what you are willing to do as well as how frequently you
need to do it.
If you can make the schema changes to your consolidated and still
support the current version of your synchronization scripts, then you
can create a new ScriptVersion and have both the new and the old
versions of your application/remotes synchronizing to one consolidated.
This is likely the smoothest approach as it can be done without having
any downtime.
> Once these changes have been made I assume each remote will go thru an
> initial sync as if none has been made before..is that correct?
This isn't necessary depending on the nature of your schema changes.
You can actually send out the schema changes as part of a
synchronization (if you set this up ahead of time) by downloading the
required DDL to your remote and applying it during the
sp_hook_dbmlsync_sch
ema_upgrade event on the client side.
Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|