On 03/06/2014 03:52 PM, Merlin Moncure wrote:
On Tue, Mar 4, 2014 at 3:08 PM, Rob Sargent wrote:
Do you make a distinction between a key and an index? I'm not picking up on
design-by-natural-key and what that entails. Especially the notion that the
natural key of a given item might be mutable.
On Tue, Mar 4, 2014 at 3:08 PM, Rob Sargent wrote:
> Do you make a distinction between a key and an index? I'm not picking up on
> design-by-natural-key and what that entails. Especially the notion that the
> natural key of a given item might be mutable. What stops it from colliding
> with the ne
On 03/04/2014 01:40 PM, Merlin Moncure wrote:
On Tue, Mar 4, 2014 at 2:15 PM, Kevin Grittner wrote:
Roy Anderson wrote:
We have an OLTP database and no data warehouse. We are currently
planning out a build for a data warehouse however (possibly using
Hadoop). "X" is recommending that we conv
On Tue, Mar 4, 2014 at 2:15 PM, Kevin Grittner wrote:
> Roy Anderson wrote:
>
>> We have an OLTP database and no data warehouse. We are currently
>> planning out a build for a data warehouse however (possibly using
>> Hadoop). "X" is recommending that we convert our current,
>> normalized OLTP da
Roy Anderson wrote:
> We have an OLTP database and no data warehouse. We are currently
> planning out a build for a data warehouse however (possibly using
> Hadoop). "X" is recommending that we convert our current,
> normalized OLTP database into a flattened Star Schema.
I'm not going to repeat
On 2/4/2014 10:06 PM, Roy Anderson wrote:
We have an OLTP database and no data warehouse. We are currently
planning out a build for a data warehouse however (possibly using
Hadoop). "X" is recommending that we convert our current, normalized
OLTP database into a flattened Star Schema.
The primar
On Feb 6, 2014, at 12:44 PM, Scott Marlowe wrote:
> Merlin, this reminds me of the quote from Mencken: For every complex
> problem there is an answer that is clear, simple, and wrong.
Or as Niklaus Wirth said.
... complexity has and will maintain a strong fascination for many people. It
is t
On Thu, Feb 6, 2014 at 12:44 PM, Scott Marlowe wrote:
> On Thu, Feb 6, 2014 at 7:51 AM, Merlin Moncure wrote:
>
>> *) Do not consider any advice to implement exotic storage backend from
>> someone that has not previously implemented that same technology on a
>> similar scale on a previous project
On Thu, Feb 6, 2014 at 7:51 AM, Merlin Moncure wrote:
> *) Do not consider any advice to implement exotic storage backend from
> someone that has not previously implemented that same technology on a
> similar scale on a previous project, ever. Data of large scale is
> hard. Installing magical t
On Tue, Feb 4, 2014 at 10:06 PM, Roy Anderson wrote:
> We have an OLTP database and no data warehouse. We are currently
> planning out a build for a data warehouse however (possibly using
> Hadoop). "X" is recommending that we convert our current, normalized
> OLTP database into a flattened Star S
We have an OLTP database and no data warehouse. We are currently
planning out a build for a data warehouse however (possibly using
Hadoop). "X" is recommending that we convert our current, normalized
OLTP database into a flattened Star Schema.
The primary rationale for this OLTP flattening is that
11 matches
Mail list logo
