It would be nice if I could distinguish the types of dependancies when evaluating connected objects - for example, there are times when I'm only interested in evaluating queries that write to a particular table, and it would be helpful to ignore table read references (SELECT).

It would be great if DT could evaluate dependancies within SSIS packages - I've not seen a tool yet that could do that.

It would be nice in the graphing if I could see more of a workflow layout - if I could pick one object and define it as a central point, and have all related objects flow to/from it, or as a top level point and have all related objects cascade down from it... So, for example, if I have a particular table and I want to see how data flows in and out of it, I would set that as my central point... all queries that write to it appear on the left side, and all queries that read from it appear on the right side; queries that both read and write are clustered beneath. (...and, if I'm ignoring read references in queries, both write and read/write queries are diagrammed on the left side.)

Last edited by rreitz on Wed Jan 20, 2010 5:12 pm, edited 1 time in total.

I start with a query that writes to a table...
That table gets replicated to another server...
A view exists on the replicated table...
A job step selects data from the view into a different table...
An SSIS package exports the new table to a text file...

...and Dependancy Tracker is able to follow the original data point through all of these transitions, and diagram it as a data workflow.