Re: Best Practices   

wrote in message 
news:1186599651.675557.148810@b79g2000hse.googlegroups.com...
>I am new to replication, so some of my choices are flawed, but I'd
> like to know the best way to configure the replica set.
>
> 1/ I am still in design mode, so I am using the design master for
> development as well as for processing data; once the database is
> stable, I plan to create a replica to do the file processing.
>
> 2/ There are 2 replicas, one in NY and one in London; the desgn master
> is also in NY.  I (or the eventual DBA), synchronizes prior day
> updates to the central DB, then processes new files in the AM, then
> resynchronizes, allowing London to work until early afternoon - the
> database has code to shut itself down at a specific time, as well as
> provide a time window - whence the data is synched again from London
> to the master, then from the master to NY.  At a time during the
> afternoon in NY, the datbase shutsdown, and all the data is synched
> between the master and NY.  Round and round it goes.
>
> 3/ The database is one, and not setup as a front-end and back-end.
>
> 4/ I used the TSI synchronizaer to reduce the RetentionPeriod to 14
> days, to reduce bloat.
>
> What do I need to do to make this the best configuration I can, from
> both a starting-from-scrath perspective, as well as from trudge-on-
> with-current-config?
>
> Although I have a separate question on the upgrade path to SQL server,
> I will ask that separately.
>

date: Thu, 25 Oct 2007 14:16:37 -0400   author:   shaquille combs