These pages relate to SQL Dependency Tracker versions 2.0 to 2.8. Help for older versions is also available.

Skip to end of metadata
Go to start of metadata

When you add objects to your project, SQL Dependency Tracker automatically adds the dependent objects to your diagram. If a dependent object belongs to a different database and you have not previously added an object from that database to the project, the object is displayed as an unresolved external reference.

SQL Dependency Tracker knows very little about unresolved external references. For example, the object type cannot be determined, and SQL Dependency Tracker can only detect uses dependencies.

You can resolve the external reference so that the object details can be shown.

Icon
You can't resolve unresolved internal references; unresolved internal references are references to objects that could not be found within the database schema, for example a reference from a stored procedure to a column in a table that has been subsequently dropped.

By default, objects from different databases are displayed in different colors. You can change the color objects are displayed in if required.

To resolve all unresolved external references:

  1. On the toolbar, click Resolve All External References.
    A progress message box is displayed. If you select the Close message box on completion check box, SQL Dependency Tracker closes this message box automatically next time you resolve external references. Alternatively, you can set your project options to close all message boxes when operations are complete.
  2. If necessary, click OK to close the message box.

To resolve unresolved external references for selected objects:

  1. Select the objects.
  2. Right-click a selected object, click Add to Project, and then click Resolve External References.
  • No labels