Archives of the TeradataForum
Message Posted: Mon, 08 Jan 2001 @ 22:11:46 GMT
I have to agree with Andy Blevins. When I first read your email, I thought perhaps you had inadvertently transposed 'Teradata' and 'DB2' because every Teradata cusmomer with which I have worked has taken the normalised approach.
I think a normalized design is most appropriate to start. However, I would also very strongly suggest that you develop a Data Access model, which would identify common and probable business questions and decomposes these questions into technical data requirements that could then be used to determine the possible data access paths required to answer the business questions. This should identify likely join strategies and will guide you in selecting indices and also should help in making decisions about the super-type/sub-type relationship. Data Access modeling is a natural extension of the Business Discovery process, if you've gone through that exercise.
Thomas F. Stanek
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|