Trace Mode

DOC xPress ›› Features ›› Lineage Analysis ››
Parent Previous Next

Trace Mode


Trace mode allows users the ability to set a source and target object and then run a trace that builds a step by step path from the starting object to the target object. Users can begin trace mode using three different techniques.


1.   Within the solution explorer, users can right-click on an object to launch a context menu. Clicking on either the "set as trace source" or "set as trace target" buttons will enable the trace bar and set the respected item as either the source or target item


2.  Within visual view, users can right-click on a node to launch a context menu. Clicking on either the "set as trace source" or "set as trace target" buttons will enable the trace bar and set the respected item as either the source or target item


3.   Enabling the trace bar will allow users to left-click on objects within the solution explorer or text view and drag-and-drop them into either the source or target text box.



Once both the source and target have been set, users can click the trace switch button to switch the source object with the target object.


After the user is content with the source object and target object, click the start trace button to allow DOC xPress begin calculating all possible paths between the source and target objects.


Trace Operation


Traces will only follow similar types of link - so, for example, a route from object A to object B would not be reported if it was comprised of Column and Object links. The links that can be combined to form a trace route are:


  Column and Data Flow links

  Foreign Key and Foreign Key Column links

  Object links


Some links may be reported as 'Link Set' or 'Aggregate' - this happens when multiple types of link follow the same path.


Note that the trace operation respects the 'Refinements' set in lineage. So, if you only want to trace data lineage, then deselect the 'Object' and 'Key' refinements before starting the trace. This can significantly improve the performance of a trace as it reduces the size of the search graph.


Trace will also operate from target to source, tracing backwards. This is because often a key table within a database will be read by many entities, but only updated by a few. By tracing in reverse, we cut down on the number of paths we must follow because only those links that update the table need to be traced in order to find that route.


Important Note:

The process of calculating all possible paths between a source and target object may take several minutes depending on the complexity of the solution. If at any time a user wishes to terminate the process, click the cancel button.


Results


Once trace calculations are completed, the first trace path will be displayed.


Users can move between each of the trace paths by clicking left and right on the trace results page numbers. The number of routes returned is limited by the "Trace Mode Route Limit" preference and the shorter routes will be displayed first before the longer ones.


Each path result contains a series of objects each connected by a route dependency. The first object in the trace result will be located at the top of the trace result view and will always be the source object. Likewise, the last object in the trace result will be located at the bottom and will always be the target object.



Each route dependency contains a link set. When clicked, the user will be shown a list of the route information that created the dependency.