Archives of the TeradataForum
Message Posted: Fri, 05 Jan 2007 @ 09:07:38 GMT
Please give us your opinion on this.
Due to the way the present project team are using Datastage Enterprise Edition to generate the ETL process, they require a full unique primary index(tables having 50 to 90% of columns as unique primary index) on the tables (as per FSLDM logical model). However, My concerned is this may cause long-term performance problems. (In the new Datastage architecture, they are not using Teradata mload).
For our POC, we were using mloads to enforce uniqueness for ensuring data quality, and primary key was not required to enforce uniqueness.
Would this cause any long-term performance problems or other issues, if we are creating tables 50 to 90% of columns as unique primary index?.
Thank you for your help.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|