DSXchange

Just bring the date column across and let column analysis worry about whether the value is null or not.

You haven't really solved it, you've just swept it under the carpet.

IF you have been diligent with handling your metadata, only ever loading table definitions from the Repository, then you can quite simply perform a usage analysis on the table definition and learn from that when jobs have loaded it (and therefore, presumably, are using it).

Data Set Management is also available from the Designer client's menu.

If they insist on WAS 7.x, why not have "them" sponsor your upgrade to Information Server 8.7 so you can benefit from all the new functionality, such as the Operations Console?

You could check out [url=mailto://andy.sorrell@sbcglobal.net]Andy Sorrell[/url] who is based in Texas and posts on DSXchange from time to time.

Another possibility is PR3 Systems headquartered in Aurora, IL.

In particular, Information Server 8.1 will not work with WAS 7.x.

Disable the display of Categories in Director.

SecondsSinceFromTimestamp() function.

Do you have separate links for inserts, updates and deletes? If so you can capture those link row counts separately. If not, there is no solution.

Download ETLstats from Kim Duke's website - this package does all that and more. (And it's free.)

How about you show us what you tried?

And maybe start by getting the routine names correct. For example, it's DSGetJobInfo(), not DSJobGetInfo().

I typically use the method described by James Wiles earlier.

Perhaps you could post the PMR number, so anyone else can research the solution when it comes.

Something like the following query should do it for you: