Archives of the TeradataForum
Message Posted: Tue, 26 Mar 2002 @ 15:28:14 GMT
has anyone of you made performance experiences with partitioning of a large table into several smaller ones.
a table which holds call detail records for a telecommunication's company has stored 6 months of data in a 600 GB table if we would partition it into 6 separate tables - one for each month - they would have 100 GB each.
if we only query days within one month the response time should of course be faster when we direct it to the right monthly table but if we query days spanned over several month we would have to do it via a view which combines all separate tables with a UNION ALL
the execution plan says it queries all separate tables in parallel is this in your opinion faster than querying the big table?
thanks for any helpful response...
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|