Comments
Sort by recent activity
Hi Mulmad,
If you select an object, a list of linked objects will be displayed in the Dependencies pane in the bottom right of the screen. If you double click one of these, the viewer will select and scroll to the selected objects.
Regards,
Dan / comments
Hi Mulmad,
If you select an object, a list of linked objects will be displayed in the Dependencies pane in the bottom right of the screen. If you double click one of these, the viewer will select a...
ThePonderer,
You're quite right, this is a bug in SQL Dependency Tracker v2.0 and v2.1.
The fix has been made to our dependency engine itself, and is being tested internally. The next release of Dependency Tracker should fix this issue; I'm afraid I can't give you a date for that at this time.
All the best,
Dan / comments
ThePonderer,
You're quite right, this is a bug in SQL Dependency Tracker v2.0 and v2.1.
The fix has been made to our dependency engine itself, and is being tested internally. The next release of De...
Hi ubu,
We don't currently track dependencies at the column/field level, so reliably pointing out errors in the schema at the current level is not supported.
However, a future version of Dependency Tracker may well support column level dependency tracking, and then this sort of information should be available.
All the best,
Dan / comments
Hi ubu,
We don't currently track dependencies at the column/field level, so reliably pointing out errors in the schema at the current level is not supported.
However, a future version of Dependency...
Hey Glyn,
Under the circumstances, if you send me a private message I'll see about getting your trial extended if you'd like to continue evaluating the product.
Regards,
Dan / comments
Hey Glyn,
Under the circumstances, if you send me a private message I'll see about getting your trial extended if you'd like to continue evaluating the product.
Regards,
Dan
Hi Steve,
Thanks for the feedback. Yep, that's a small bugette in the 2.0 release. It's fixed for our forthcoming 2.1 maintainance release, which'll be free to existing customers.
We did consider making the panel dockable. I'll pass your comment on to the team. In the meantime, you can still leave the script window open whilst you click around - admittedly this is easier on a high resolution or multi monitor system.
Thanks again,
Dan / comments
Hi Steve,
Thanks for the feedback. Yep, that's a small bugette in the 2.0 release. It's fixed for our forthcoming 2.1 maintainance release, which'll be free to existing customers.
We did consider m...
Hi Eric,
You're most welcome, glad to be of service. Apologies for the slight labour involved here - with a fixed time budget for development we did agonise over which features were vital and which less so. Generally we opted for providing functionality which wasn't available through other means; this does mean that a few tasks like this are a bit more involved. Thanks for persevering!
Cheers,
Dan / comments
Hi Eric,
You're most welcome, glad to be of service. Apologies for the slight labour involved here - with a fixed time budget for development we did agonise over which features were vital and whic...
Hi Eric,
Thanks for the feedback. There wasn't time in the development schedule for v2.0 to include the features you're talking about, but there are a few ways to achieve these goals:
You can copy either the whole diagram, the current selection or the currently visible area onto the clipboard: select Copy from the toolbar or from the Edit menu. You can then Paste this into a graphics-compatible application with print capabilities. During the beta, it was recommended by one of our users that Excel is an excellent choice for this task, since it handles printing of such large areas very well.
To chose the print area, you could arrange the display so that the visible area contains only that which you wish to print, just by panning and zooming around the diagram, and temporarily hiding any objects you wish to omit. After pasting into an application such as Excel you can resize the image to the size you want - since it's a vector based image it should scale well in applications which support the vector format we export (EMF or enhanced metafile format).
To export to PDF, repeat the same process but chose as your destination an application which directly supports PDF export. There are a number of them out there (such as popular third party office applications). Alternatively, export the diagram as EMF and use a third party EMF to PDF converter; again there are a number of them available over the net.
Apologies for the fact that this feature isn't in Dependency Tracker. It will be considered as and when we're planning the next major release. / comments
Hi Eric,
Thanks for the feedback. There wasn't time in the development schedule for v2.0 to include the features you're talking about, but there are a few ways to achieve these goals:
You can copy ...
Hi tsoren,
Thanks for the feedback.
1. To achieve this you can select an object, pull down the Edit menu (or right click the object) and choose Select, then Same Type. This will select all objects of that type. Then right click, select Properties, and change the colour. All selected objects will change colour.
(There is an issue in the 2.0 release if your selection is very large; this is fixed in our 2.1 release, which is upcoming will be free to existing customers.)
2. Duly noted. The best you can do is to right click, select View SQL Script, and inspect the script visually for the reference. This gives you more detail than an indicator as to the type of dependency - of course it may be too much detail for you.
All the best,
Dan / comments
Hi tsoren,
Thanks for the feedback.
1. To achieve this you can select an object, pull down the Edit menu (or right click the object) and choose Select, then Same Type. This will select all objects ...
Thanks Fernando,
That's a very good workaround. If this works, I'd recommend others with this issue follow your lead for the moment.
The warning you're seeing is a standard one; Dependency Tracker flags any unresolved reference, whether it ultimately can be resolved by right clicking and Resolving External References or not.
All the best,
Dan / comments
Thanks Fernando,
That's a very good workaround. If this works, I'd recommend others with this issue follow your lead for the moment.
The warning you're seeing is a standard one; Dependency Tracker ...
Thanks for the report.
We're looking into this - it looks like our parser doesn't fully support linked servers.
It tries to translate that four part name such that LinkServer is a literal SQL Server instance name.
I'll pass this on to the appropriate development team. We may be able to add this support for a future release, provided that the server on the other end of the link is a SQL Server 2000 or 2005 instance. Meantime, you should still be able to use a literal server name, assuming that server is a SQL Server 2000 or 2005 instance.
Thanks,
Dan / comments
Thanks for the report.
We're looking into this - it looks like our parser doesn't fully support linked servers.
It tries to translate that four part name such that LinkServer is a literal SQL Serve...