Archives of the TeradataForum

Message Posted: Fri, 18 Sep 2009 @ 21:13:37 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

One other thing to consider - if you run the delete as an insert to a new table, you'll have to collect stats and make sure you have a system in place to manage granting rights on the new table. The stats thing may or may not be an issue, since depending on the volume of deletes you might want to recollect on the original table anyway. The grants can be automated (bteq script with SQL that generates grants from dbc.AllUserRights and dbc.AllRoleRights then runs the results), but it's still something you might have to set up.

A question for the list: leaving aside deletion by PPI (where you'd always want to at least collect on PARTITION), would a reasonable rule of thumb be that the row change threshold for collecting stats after a delete is the same for running a delete as insert into a new table?

Dave

	<Prev	Next>		<<First	<Prev	Next>	Last>>