Archives of the TeradataForum
Message Posted: Wed, 13 Feb 2008 @ 20:45:41 GMT
TD has embedded in their documentation a UDF named "tdat" that they propose, suggest and claim provides direct connectivity between two stand alone TD servers. The purpose proposed was to allow real-time comparisons of DBC environment metrics for two systems. However, when I contacted TD about this UDF, which they reference, no one seems to be aware of it and the person who wrote the documentation no longer works for TD.
So, if one of the TD major meisters is reading this thread, who can tell me the source of the UDF "tdat"? P.s., I can proved the documentation cite, if requested.
P.s., the named pipes approach is an interesting concept, as there is essentially no storage required, since the data is read from the pipe, as soon as it is written to the pipe. So if a fast export would write on the pipe on Server A, a server A ftp job could read the pipe and ftp the content to a named pipe at the other end at Server B, which would feed a server B fastload, then very little Unix node storage would be required at either end.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|