 |
 |
Archives of the TeradataForum
Message Posted: Thu, 19 Jul 2012 @ 12:42:57 GMT
| Subj: | | Re: Insert statement starts OK but then slows down |
| |
| From: | | Bodla, Sravan Kumar |
Hi,
Sugesh iyyani wrote:
| | As you are trying to load to a SET table, insert will run slower and slower as record count in table increases. | |
| | This is because, as SET table won't allow entire row duplicate, as you insert new rows to the table | |
| | TD system should check whether particular row is already present or not. | |
| | And if row is already present, it won't insert particular row. It won't give any error message also. | |
| | As this is an automatic process, lot of resources and processor time required to do the same. | |
| | Initially it work faster and as record count reach millions, it becomes slow. | |
I understand, the above is True only in case of a SET table with Unique Primary Index as it(SET and Unique) double checks for each record that
is getting inserted.
Thanks,
Sravan.
| |
