Archives of the TeradataForum
Message Posted: Sat, 23 Feb 2013 @ 10:57:27 GMT
There isn't always a direct relationship between the size/growth of the journal db and etl db, it really depends on what type of maintenance commands are being executed.
To take some 'extreme' cases:
- if you update the same row multiple times then each update writes a new row to the journal db but the etl db doesn't change size
- if you delete 100 rows and then insert 100 rows (whether they're the same rows or not) there will be 200 entries in the journal db but the etl db won't have changed row count.
So what is the mix of insert / update and delete in your etl work?
Like you , I wouldn't immediately associate "high cpu skew" with the jurnal db filling up. I think for now you have to treat that as a separate issue.
Ward Analytics Ltd: Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|