Re: [GENERAL] Staging Database

2013-08-07 Thread Steve Crawford
On 08/07/2013 03:38 AM, BladeOfLight16 wrote: On Wed, Aug 7, 2013 at 4:43 AM, Luca Ferrari > wrote: ... I wasn't very careful with my wording. Sorry about that. There will be updates and possibly deletions as well as additions. Furthermore, the public versio

Re: [GENERAL] Staging Database

2013-08-07 Thread David Johnston
BladeOfLight16 wrote > The company I work for has a client who has expressed interest in having a > staging database for their data. Staging as in they add data, do some > QCing, then push to a database with an identical schema to make it public. > Fortunately, we're not doing that right now, but i

Re: [GENERAL] Staging Database

2013-08-07 Thread BladeOfLight16
On Wed, Aug 7, 2013 at 4:43 AM, Luca Ferrari wrote: > Not really helpful, but here are my considerations. > The low frequency and the preference for a single server suggest me a > dump and restore cycle on two databases, assuming this is possible due > to not high volume data. > I would also cons

Re: [GENERAL] Staging Database

2013-08-07 Thread Luca Ferrari
On Wed, Aug 7, 2013 at 6:00 AM, BladeOfLight16 wrote: > The company I work for has a client who has expressed interest in having a > staging database for their data. Staging as in they add data, do some QCing, > then push to a database with an identical schema to make it public. > Fortunately, we'

[GENERAL] Staging Database

2013-08-06 Thread BladeOfLight16
The company I work for has a client who has expressed interest in having a staging database for their data. Staging as in they add data, do some QCing, then push to a database with an identical schema to make it public. Fortunately, we're not doing that right now, but it's something they may want l