Here's another. I was just using DT to see if anything was dependant on a certain UDF.

How about a quick-and-simple text report that lists all obejcts for which nothing depends on it downstream? We could use this report to manually clean out objects that have been deprecated-and-dissociated or are dangling in development.

I imagine there are many more reports that users could suggest. Maybe this functionality could be opened to users to query out? I'm sure you have some sort of internal representation that could be exposed to users for querying. Build and save your own reports? Maybe in an exportable format such that they can be shared in a newsgroup like this?

- alphadog
alphadog
0

Comments

12 comments

  • alphadog
    Here's another example query I would love to ask the underlying data: which views out of 200+ involve tables A, B and X?

    That would allow me to possibly reuse a view rather than end up re-inventing the wheel.

    - alphadog

    PS: I am available for consultantion for a small fee... :wink:
    alphadog
    0
  • Dominick Reed
    Whilst the functionality isn't availble by constructing a query, it is possible to do what you want with Dependency Tracker... I think.

    For example, your second scenario, you could selectively add just those three tables and all views. On the diagram, if there's any relationship they'll be shown.

    Hope I've understood what you are tyring to do, but I do ocassionally drink lead paint so I may have got the wrong end of the stick...

    :)

    Dom
    Dominick Reed
    0
  • alphadog
    Yes, it is possible already. But, the result would be visual/graphical, which is great for top-level viewing. Then, let's say I want to then work on changing things correctly. I'd rather have a textual print-out, maybe to check off as I do my work for example.

    I hear 1998 was a good year for lead paint. :D

    - alphadog
    alphadog
    0
  • Bart Read
    Hi Alphadog,


    We don't support text output as such, but you can generate an XML report of the dependencies in your database by going to File > Export > XML. You can then do whatever post-processing on the data you like.

    Hope that helps.


    Many thanks,
    Bart Read
    0
  • alex.weatherall
    Hi,

    I think Alphadog's points are key here. Whilst the dependency viewer is a powerful tool, with the powerful graphical interface, the real point is that the power is in the behind the scenes dependancy logic which is I believe Redgate's proprietory algorithm. Its more complete, acurate and reliable than the sysdepends data.

    As a database developer I would far rather have this information in a queryable (the XML is great) format and be able to add that into our build process, and automated documentation. I wouldn't necessarily buy the product for the fancy interface, but for the more reliable dependency data.

    I would want a command line option that would give me the XML output for a particular database that I could then query.

    Even better, can you not add that functionality into SQL Compare, so where you can save a snap shot, beable to save the dependancy data. (Am I right in thinking this is used internally in SQLCompare, so it should be possible to do.) I'm not trying to get something for nothing ;-) but having played with the new version today, the only thing I would use regularly is the XML output, and the list and tree view in the toolbar. The diagram, while clever and impressive, is too slow and complicated for databases with many (100's - 1000s) of schema and interface objects.

    I say keep it simple. Still a very impressive product, (not sure about the odd menu interface :? )

    Thanks

    Alex Weatherall
    TeleWare.com
    alex.weatherall
    0
  • Bart Read
    Hi Alex,


    I think you raise some valid points there: in a lot of situations you're not really concerned with a nice diagram necessarily, but just want an accurate impression of the dependencies that exist within a database.

    The XML reporting will do this, and perhaps at some point we might add a command line to SQL Dependency Tracker to allow automation. As for integrating this function with SQL Compare, it would be difficult since SQL Compare does not handle the cross-database and cross-server dependencies that SQL Dependency Tracker does. However, I think there's definitely a compelling argument for possibly introducing automation support for the product sometime in the future.


    Thanks,
    Bart Read
    0
  • alex.weatherall
    Hi,

    Just written a really long addendum to my post but login timed out and I lost it!! Doh! :oops:

    I was just commenting that the other area that DT handles, that has been a bugbear of mine for ages, is Deferred Name Resolution. It's hit and miss (seems to only work with 2 part names - a habit I try to stick to but why not a one part name? :?: ) But at least it does report missing tables, views and table functions that are referenced by stored procedures.

    If DNR references were tightened up. I'd definitely consider getting DT. But again, I would not want the diagrams. Is it possible to add a "fast mode" where you just load the objects in and are able to traverse the object tree in the toolbars without waiting for the diagrammer to catch up. I did select all on one of my databases and it took over a minute to select the objects in the diagram. I just don't see it being responsive enough. :(

    Thanks,

    Alex Weatherall
    TeleWare.com
    alex.weatherall
    0
  • alphadog
    Alex:

    Here's what I do. First, save your project. Then, close and re-open it. Don't select a diagram type, that way nothing is diplayed graphically. You can navigate dependencies without the redraw slowing things down.

    I'd definitely want a "Hide Diagram" option. I guess you could "Select All" and then "Hide" with the buttons above the diagram, but with large databases, "Select All" is very slow. A single button "Hide All", or just being able to close/open both diagram windows would be better.

    - alphadog
    alphadog
    0
  • Bart Read
    Hi there,


    Quite true: we are aware of the Select All/None etc issues, and I'm pleased to say they've already been fixed so you'll find this a lot more satisfactory in the final release.


    Thanks,
    Bart Read
    0
  • Bart Read
    alphadog wrote:
    Alex:

    Here's what I do. First, save your project. Then, close and re-open it. Don't select a diagram type, that way nothing is diplayed graphically. You can navigate dependencies without the redraw slowing things down.

    I'd definitely want a "Hide Diagram" option. I guess you could "Select All" and then "Hide" with the buttons above the diagram, but with large databases, "Select All" is very slow. A single button "Hide All", or just being able to close/open both diagram windows would be better.

    - alphadog

    Hi alphadog,


    Do you see this every time you open a project? I assume you mean a big grey square where the diagram would normally appear? This has just happened to me (it's definitely not supposed to BTW) but I can't reproduce it again.

    Can you let me know a bit more about the spec of your PC please? E.g. processor type, speed, dual core, hyperthreading or anything like that would be most helpful.


    Many thanks,
    Bart Read
    0
  • alphadog
    Bart:

    If I open a saved project, the visual diagram window shows "You have no objects in your project", until you "Reapply Layout" with the button at the top of that window, or select a new graph type.

    My machine is a Dell Optiplex GX280, P4 540, i915G chipset, 2GB RAM running WinXP SP2, Hyperthreading is off. If you need more, I can get you a full export...
    alphadog
    0
  • Bart Read
    OK, thanks very much for this alphadog. I've added this to the bug report I filed yesterday about seeing a big grey square instead of the graph and it'll be fixed by the final release. I suspect it's some slightly odd threading issue, in that I only see it intermittently (but manifesting itself slightly differently), but have hyperthreading enabled. I don't think Dan's seen it at all: he has faster HT-enabled processor.
    Thanks,
    Bart Read
    0

Add comment

Please sign in to leave a comment.