I have a database which contains two primary sets of data:
1) A large (~150GB) dataset. This data set is mainly static. It is
updated, but not by the users (it is updated by our company, which provides
the data to users). There are some deletions, but it is safe to consider
this an "add-only" d
On 03/29/12 9:43 AM, Jonathan Bartlett wrote:
1) A large (~150GB) dataset. This data set is mainly static. It is
updated, but not by the users (it is updated by our company, which
provides the data to users). There are some deletions, but it is safe
to consider this an "add-only" database, w
>
>
> by 'dataset' do you mean table, aka relation ?'
>
It's a group of tables.
> by 'not using any referential integrity', do you mean, you're NOT using
> foreign keys ('REFERENCES table(field)' in your table declaration ?
Correct.
Also, many queries cross the datasets together.
>>
>>
> by '
Hi Jonathan,
On 29/03/12 19:01, Jonathan Bartlett wrote:
Now, my issue is that right now when we do updates to the
dataset, we have to make them to the live database. I would
prefer to manage data releases the way we manage software
releases - have a staging are
Tom -
Your suggestion gives me an idea, and I'd like your opinion since I haven't
done much with schemas.
(1) Separate the datasets into different schemas
(2) Use different schema names for different static data releases
(3) For the *company*, we can use a schema search path that includes the
nex
On Thu, Mar 29, 2012 at 2:39 PM, Jonathan Bartlett
wrote:
> Tom -
>
> Your suggestion gives me an idea, and I'd like your opinion since I haven't
> done much with schemas.
>
> (1) Separate the datasets into different schemas
> (2) Use different schema names for different static data releases
> (3)
Jonathan Bartlett wrote on 29.03.2012 22:39:
Your suggestion gives me an idea, and I'd like your opinion since I haven't
done much with schemas.
(1) Separate the datasets into different schemas
(2) Use different schema names for different static data releases
(3) For the *company*, we can use a
On 03/29/12 2:16 PM, Thomas Kellerer wrote:
Jonathan Bartlett wrote on 29.03.2012 22:39:
Your suggestion gives me an idea, and I'd like your opinion since I
haven't done much with schemas.
(1) Separate the datasets into different schemas
(2) Use different schema names for different static data
