The DB2 development team has compiled a set of best practices for DB2
for LUW which can be found here:
http://www.ibm.com/developerworks/db2/bestpractices/

Feedback (completeness, too much, too little, consumability, ...) much
appreciated.

Enjoy
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Serge,

thanks for your message. First I think, it is good to have a set of
best practices easily accessible as offered here.

However I am surprised to see in "Physical database design", p. 9 the
one-true-lookup-table advocated. There has just been a nice thread in
comp.databases on this and there are a lot of good arguments to be
made against.

http://groups.google.com/group/comp....fe0fd7343dae93

Indeed it is not much fun for a front-end coder to issue edit forms
for all those lookup tables, however if one form pattern is created,
it could be easily copied and pasted and slightly amended to match the
respective lookup table.

Personally, the cons against the OTLT design convince me more than the
pros.

brgds

Philipp Post

Philipp Post wrote:
> Serge,
>
> thanks for your message. First I think, it is good to have a set of
> best practices easily accessible as offered here.
>
> However I am surprised to see in "Physical database design", p. 9 the
> one-true-lookup-table advocated. There has just been a nice thread in
> comp.databases on this and there are a lot of good arguments to be
> made against.
>
> http://groups.google.com/group/comp....fe0fd7343dae93
>
> Indeed it is not much fun for a front-end coder to issue edit forms
> for all those lookup tables, however if one form pattern is created,
> it could be easily copied and pasted and slightly amended to match the
> respective lookup table.
>
> Personally, the cons against the OTLT design convince me more than the
> pros.
Interesting. I think the truth is neither black nor white.
Presumably the intent of the authors was not to merge "dimension tables"
at large. I have passed your information on and we'll see what the
authors have to say in their defense :-)

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

On Jun 25, 3:58 pm, Serge Rielau <srie...@ca.ibm.com> wrote:
> Philipp Post wrote:
> > Serge,
>
> > thanks for your message. First I think, it is good to have a set of
> > best practices easily accessible as offered here.
>
> > However I am surprised to see in "Physical database design", p. 9 the
> > one-true-lookup-table advocated. There has just been a nice thread in
> > comp.databases on this and there are a lot of good arguments to be
> > made against.
>
> >http://groups.google.com/group/comp....read/thread/3b...
>
> > Indeed it is not much fun for a front-end coder to issue edit forms
> > for all those lookup tables, however if one form pattern is created,
> > it could be easily copied and pasted and slightly amended to match the
> > respective lookup table.
>
> > Personally, the cons against the OTLT design convince me more than the
> > pros.
>
> Interesting. I think the truth is neither black nor white.
> Presumably the intent of the authors was not to merge "dimension tables"
> at large. I have passed your information on and we'll see what the
> authors have to say in their defense :-)
>

Can anyone repost the link from Serges first post, the first msg in
this thread is not visible in google news :-(




> Cheers
> Serge
>
> --
> Serge Rielau
> DB2 Solutions Development
> IBM Toronto Lab

On Jun 25, 6:07 pm, Lennart <Erik.Lennart.Jons...@gmail.com> wrote:
> On Jun 25, 3:58 pm, Serge Rielau <srie...@ca.ibm.com> wrote:
>
>
>
> > Philipp Post wrote:
> > > Serge,
>
> > > thanks for your message. First I think, it is good to have a set of
> > > best practices easily accessible as offered here.
>
> > > However I am surprised to see in "Physical database design", p. 9 the
> > > one-true-lookup-table advocated. There has just been a nice thread in
> > > comp.databases on this and there are a lot of good arguments to be
> > > made against.
>
> > >http://groups.google.com/group/comp....read/thread/3b...
>
> > > Indeed it is not much fun for a front-end coder to issue edit forms
> > > for all those lookup tables, however if one form pattern is created,
> > > it could be easily copied and pasted and slightly amended to match the
> > > respective lookup table.
>
> > > Personally, the cons against the OTLT design convince me more than the
> > > pros.
>
> > Interesting. I think the truth is neither black nor white.
> > Presumably the intent of the authors was not to merge "dimension tables"
> > at large. I have passed your information on and we'll see what the
> > authors have to say in their defense :-)
>
> Can anyone repost the link from Serges first post, the first msg in
> this thread is not visible in google news :-(
>

Never mind, now it is


/Lennart

Serge Rielau wrote:
> The DB2 development team has compiled a set of best practices for DB2
> for LUW which can be found here:
> http://www.ibm.com/developerworks/db2/bestpractices/
>
> Feedback (completeness, too much, too little, consumability, ...) much
> appreciated.
>
> Enjoy
> Serge
>

Have only read the Storage best practice, but found this to be an excellent
introduction and have urged my colleagues to bookmark the site. Thanks, Chris