User profile for Dan J Archer

Hi nigwil, In the Add Objects to Project dialog, if you select Windows Authentication then the application will try and connect using that authentication; if it can't connect, it will display a '!' warning triangle and switch back to SQL Server Authentication. Hope that's of help, Regards, Dan / comments

Hi nigwil, In the Add Objects to Project dialog, if you select Windows Authentication then the application will try and connect using that authentication; if it can't connect, it will display a '!'...

0 votes

Dear nigwil, Thanks for that, we'll look into it. Regards, Dan / comments

Dear nigwil, Thanks for that, we'll look into it. Regards, Dan

0 votes

Hi alphadog, Thanks for that, it would be a good plan, and aim to allow this easily for the final release. Regards, Dan / comments

Hi alphadog, Thanks for that, it would be a good plan, and aim to allow this easily for the final release. Regards, Dan

0 votes

Hi Gary, I'm afraid there will only be one round of beta testing. On the plus side, it's because our release date is all the closer as a result! All the best, Dan / comments

Hi Gary, I'm afraid there will only be one round of beta testing. On the plus side, it's because our release date is all the closer as a result! All the best, Dan

0 votes

Hi Gary, You're quite right, there's no help file at this time - apologies. In the final release you shold indeed be able to see more details about dependencies from an object. Some of the self-referencing circular dependencies you see are caused by the fact that, by default, we hide constraints (such as foreign keys, indexes, and check constraints) and instead show them as dependency lines rather than separate objects. If you'd like to see these as objects rather than dependency lines, you can click the button near the far right of the bottom toolbar to uncheck it: "Show Constraints as Dependencies". This option is also available from the View menu's Options dialog. Hope this is of some help, Regards, Dan / comments

Hi Gary, You're quite right, there's no help file at this time - apologies. In the final release you shold indeed be able to see more details about dependencies from an object. Some of the self-ref...

0 votes

Thanks Dwaine, A good point duly noted. Cheers, Dan ==================== Dan J Archer SQL Dependency Tracker Project Lead Red Gate Software / comments

Thanks Dwaine, A good point duly noted. Cheers, Dan ==================== Dan J Archer SQL Dependency Tracker Project Lead Red Gate Software

0 votes

Chaps, There's some great feedback here, and many thanks for it. We're still digesting it all, and as you've no doubt surmised a lot of this is beyond the scope of our 2.0 release. That said, there's some very good food for thought here and we're most grateful for it. Your words are not falling on deaf ears. Cheers, Dan Dan J Archer SQL Dependency Tracker Project Lead / comments

Chaps, There's some great feedback here, and many thanks for it. We're still digesting it all, and as you've no doubt surmised a lot of this is beyond the scope of our 2.0 release. That said, there...

0 votes

Hi all, This is a very interesting thread to read, and I'm still mulling it over. Hence my late reply to this thread; apologies for that. A key use case we are aiming to support with SQL Dependency Tracker is impact analysis. For example, say as a developer/DBA you've got to change X, Y and Z tables. You want to know what other objects are going to be affected by this. Now the way to do this as we designed it in Dependency Tracker is to go to Add Objects to Project, pick just the objects you intend to change (so in this example tables X, Y and Z), and hit "Add to Project". Dependency Tracker will add all those to a diagram, but will also automatically add all objects which tables X, Y and Z are used by; and all the objects those are used by; and so on. So your initial diagram should answer that high level question pretty immediately. Where the objects that have been added have dependencies which aren't on the diagram, there'll be little stalks (a la "O----", if I may use brief ASCII art) sticking out of the objects on the diagram. You can mouse over those objects for a list of dependencies which aren't shown, and then right click to add those objects to the diagram. So the drilling down process would start with a few objects on the diagram, and more are added as you drill down to what you're interested in. We were anticipating that people would use the tool in an incremental way, adding objects to the diagram as needed. Interestingly it seems a lot of people are using the beta by adding everything to the diagram and then going from there. Now if your database is complex this is going to give you a bit of a headache, as you're trying to visualise the whole thing at once, and you've got many, many inter-depencies. If the original task was impact analysis, that's a lot to navigate, as people have discovered. So a few questions: Is change impact analysis one of the main reasons you'd use dependency viewer? If not, what's the biggest reason you'd use it? 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? Thanks for your feedback, and all the best, Dan Dan J Archer SQL Dependency Tracker Project Lead Red Gate Software / comments

Hi all, This is a very interesting thread to read, and I'm still mulling it over. Hence my late reply to this thread; apologies for that. A key use case we are aiming to support with SQL Dependency...

0 votes

Hi all, Since we track at the table level, one way in the final release will be to drop the table whose field/column is of interest onto the graph (which will bring in all objects which that table is used by). We're aiming to show source SQL for the dependency objects, which should allow you to determine which references apply to the table and which to particular columns. We're still considering colour coding dependency types, although given the large number of ways in which references can occur, we figured that showing the source SQL would let the user get right to the meat of the problem more easily. Do let us know what you think though. Hoping that's of help, Regards, Dan. / comments

Hi all, Since we track at the table level, one way in the final release will be to drop the table whose field/column is of interest onto the graph (which will bring in all objects which that table ...

0 votes

Hi jvance, We do track dependencies down to the field level, but we don't display them as such; on the diagram and in the Object Dependencies list, the dependencies will go to/from the table in question. All the best, Dan / comments

Hi jvance, We do track dependencies down to the field level, but we don't display them as such; on the diagram and in the Object Dependencies list, the dependencies will go to/from the table in que...

0 votes

How can we help you today?

Dan J Archer

Comments