Archives of the TeradataForum
Message Posted: Mon, 11 Apr 2005 @ 19:26:48 GMT
Have any of you had success in v2r5 by taking a big table and splitting it into 5 or 6 tables (retaining identical metadata except for the table names). Each table has it own view (for insert, update, delete). One overarching
view is created that UNION ALLs the tables together for end user access for reporting purposes.
Such a setup would facilitate archiving of smaller blocks of data.
What does this approach do to normal multi table joins that select data?
In the past, one of our teams tried this under v2.r3 and ran into lousy performance during testing and abandoned the idea.
Do any of you have anything different to report?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|