Comments
Sort by recent activity
FYI - this happened to me once before with an earlier version of SDT. Then, I exited and restarted the append everything worked. That is not the case now. / comments
FYI - this happened to me once before with an earlier version of SDT. Then, I exited and restarted the append everything worked. That is not the case now.
To clarify - they are shown in the diagram, but no listed in the Dependencies window. (The diagram does not help me much, since it is almost unreadable for my VERY complex vendor database.) / comments
To clarify - they are shown in the diagram, but no listed in the Dependencies window. (The diagram does not help me much, since it is almost unreadable for my VERY complex vendor database.)
Very strange. Re-started Dependency Tracker, now works as it has before. Weird. / comments
Very strange. Re-started Dependency Tracker, now works as it has before. Weird.
Does the new version (2.5) address the problem of exporting and/or printing the list of dependencies retrieved by the tracker software? This is an urgent need. I was told a few months ago that it might be included in sqlserver 2008 release.
thanks - chuck / comments
Does the new version (2.5) address the problem of exporting and/or printing the list of dependencies retrieved by the tracker software? This is an urgent need. I was told a few months ago that it m...
I cannot believe that you and I are the only two users of the dependency tracker who need this capability. Although my case may be extreme - 3000 procs spread across multiple databases - I would think finding dependencies would only be the first step in some extended process.
Doesn't anybody else have this basic need? / comments
I cannot believe that you and I are the only two users of the dependency tracker who need this capability. Although my case may be extreme - 3000 procs spread across multiple databases - I would t...
I would like to add my support to the previous posting.
I work with a sql server installation with about six databases made up of about 3000 procs and an equal number of tables, plus all the assorted "accessories" that go with them.
Once we have a list of proc-to-proc dependencies on the screen, we usually want to DO SOMETHING with them, the first requirement usually being to e-mail them to someone else. Jumping back and forth from the sdt screen to the window where we are "working" is just not a good work process.
I currently generate a pdf file, then cut and paste from there, but this is slow and very inconvenient.
We need either a "cut & paste" from the screen or the option to "print" the information in the current dependency list. / comments
I would like to add my support to the previous posting.
I work with a sql server installation with about six databases made up of about 3000 procs and an equal number of tables, plus all the assort...