Comments
Sort by recent activity
alphadog wrote:
Well, depending on how you did it, grepping on <object> tags could over-inflate the numbers, given that the tag <object> is used as a child of <uses> and of <used by>, which are children of <object> again.
Grepping on <object> in general would actually give, I think, a general count of the number of links or dependencies.
That makes complete sense. But I don't know how else to determine the number of objects in my diagram.
I can easily report back the number of Tables, Procedures, etc, in the database. But I'm not clear on which objects SDT currently tracks.
Running this query:
select type, count(*) as [Count]
from sysobjects
group by type
Gives these results:
type Count
---- -----------
TR 23
U 161
F 281
C 79
S 19
K 201
D 468
FN 4
TF 2
V 51
P 147
/ comments
alphadog wrote:
Well, depending on how you did it, grepping on <object> tags could over-inflate the numbers, given that the tag <object> is used as a child of <uses> and of <used by>, which are ...
Bart Read wrote:
I'd be interested in knowing roughly how many objects are on your diagram if you could give me that information please? Then I can test SQL Dependency Tracker on a comparably sized database here and see how it performs, and if there are any other improvements we can make.
Since that information is useful to you, it would be nice if the GUI had an easy way for me to determine how many objects are in the diagram. If it does, I can't find it.
I exported to XML and grepped the number of <Object> occurrances. 4,223 objects, according to this method.
I uploaded an exported PNG of my diagram to http://www.jonrobertson.net/DependencyTracker.png. I don't know about you, but that's just not very useful to me. Particularly when trying to navigate around is very slow (even using the diagram list, it isn't fast enough to be useful to me).
By the way, it took my machine over half an hour to generate that diagram (Orthogonal). I wish I'd actually timed it. But it was definitely over 30 minutes.
I'll echo other posts that I've read: When looking for a Dependency Tracker, I'm not looking for a fancy diagraming tool that'll let me bounce from one object to another. I'm looking for something that will let me easily and quickly determine what the dependencies are, and what affect removing a single constraint/column/table/stored proc/func/etc will have on the rest of the schema. / comments
Bart Read wrote:
I'd be interested in knowing roughly how many objects are on your diagram if you could give me that information please? Then I can test SQL Dependency Tracker on a comparably si...
Dan J Archer wrote:
Is change impact analysis one of the main reasons you'd use dependency viewer?
Yes
Dan J Archer wrote:
Could you (would you want to) work in the way we invisaged for this task, or do you think we're off base on this one?
Yes. I never considered trying to work that way. Perhaps some "Best Practices" documentation or tutorials would be beneficial to new users (like me!). / comments
Dan J Archer wrote:
Is change impact analysis one of the main reasons you'd use dependency viewer?
Yes
Dan J Archer wrote:
Could you (would you want to) work in the way we invisaged for this ...