Red Gate forums: SQL Dependency Tracker 2

RE: Can i select only items that are dependent based on columns?

merk — Mon, 10 Jun 2013 17:31:39 GMT

Thanks - is there a link to view all pending feature requests?

RE: Can i select only items that are dependent based on columns?

chriskelly — Mon, 10 Jun 2013 13:54:59 GMT

This isn't possible at the moment, unfortunately. I have added your details to an existing request, DT-451 for the development to review.

Can i select only items that are dependent based on columns?

merk — Fri, 07 Jun 2013 00:02:35 GMT

Is it possible using dependency tracker to select only related items if they read or update a specific column?

e.g. I have Table A and I only want to see other tables/sprocs/functions etc that do anything with Column 1 in Table A. So if i have some sproc which is doing a 'select column 2 from table A' i don't want to see it.

RE: dependencies for a table created within a stored procedure

POTOOLE — Thu, 09 May 2013 08:24:02 GMT

Hi Pete

Can you confirm if this has been added as a feature request?

Thanks

Paul

peter.peart wrote:

We use a separate dependency checking mechanism than SQL Server, however to the best of my knowledge, this isn't supported in the tool which is why it wouldn't be working for you.

I'm also very sorry to say that I'm not aware of any workaround at all. I'll raise it as a feature request for you though to see if we can support this.

Pete

RE: Add cross-database dependencies?

Anu Deshpande — Thu, 25 Apr 2013 13:38:52 GMT

Many thanks for your post.

I have logged a support call for you call reference for which is F0072188.

Add cross-database dependencies?

alicorn2 — Tue, 23 Apr 2013 21:24:32 GMT

I have approximately 50 databases, spread across 4 SQL Server instances.

I know I can find out which external objects things inside my current database rely on - but I want to do the reverse. I want to find out what all is pointing AT my current database, so that I know what will break when I try to move this database.

Is there a way to do this?

I tried adding all objects in each database, one database at a time. I eventually hung the application when I tried to get it to resolve external references, it encountered a reference to a database that doesn't exist anymore.

Feature Request: Stop reuse of "Object" in XML Export

PCurd — Fri, 15 Mar 2013 22:03:12 GMT

The XML export feature of Dependency tracker is really nice since I can write my own analysis functions - except I can't autoload the XML into .Net because the XSD tool won't let you have nested relations. The Object type exists at three levels, in the root of Database, inside Uses, and inside UsedBy.

Can you use a different name at each level (like Object, UsesObject, UsedByObject) so they can be parsed by XSD?

Thanks

RE: How to get rid of the pins

JColton — Mon, 11 Mar 2013 21:05:33 GMT

whenriksen wrote:

I'd like the option to remove the pins. They do not serve any purpose when the diagram is printed.

I second this request, all they do is make it look like the object beside it is somehow related

RE: Error Messages while using Dependency Tracker

chriskelly — Tue, 19 Feb 2013 11:30:16 GMT

Thank you for your post.
Have you activated the installed tools?

RE: Error Messages while using Dependency Tracker

romiltcs — Mon, 18 Feb 2013 13:29:51 GMT

Any replies would be much help!!!

Error Messages while using Dependency Tracker

romiltcs — Mon, 18 Feb 2013 10:38:45 GMT

Hi,

When I'm using Dependency tracker through SSMS (Right Click the SQL Object) I am getting notification of 5 error messages. http://imageshack.us/photo/my-images/339/dtracererror.png/

It shows that I dont have a valid license for SQL Comparison SDK but I have installed the SDK, SQL Compare Pro 9 and SQL Data Compare 9 also.

Can you still let me know why it is failing yet???[/img]

Exporting or quickly gathering Dependency Errors

robwarner46106 — Thu, 10 Jan 2013 21:07:15 GMT

Before and after I do database changes in our production environment I run the RedGate Dependency tracker and look at the errors that are generated to see if a developer has not included objects I need to migrate for the entire database. Is there a quick or efficient way to export or copy that error log out rather than looking at the error message individually?

I inherited this database and am cleaning up the mess.

Rob Warner

SQL Dependency Tracker 2

software — Thu, 13 Dec 2012 16:01:21 GMT

I've been playing around with SQL dependency tracker for my business and we will probably need 3-5 licenses. I can't find information on the following:

Can I Automate SQL Dependency Tracker 2? I.E. Batchscripts?

Can i Find dependencies across servers?

Can I find dependencies across multiple aliases?

Thanks.

RE: Can I exclude hidden objects from dependency list export?

Manfred.Castro — Wed, 14 Nov 2012 17:59:24 GMT

Sorry you are experiencing this.
This appears to be a known issue under the internal reference number of DT-514
Unfortunaltely I do not have an ETA for a fix.

Can I exclude hidden objects from dependency list export?

isme — Tue, 13 Nov 2012 15:33:00 GMT

My dependency tracker version is 2.7.4.1.

How do I export a dependency list for only the visible objects in the project?

The dependency export feature seems only to export a dependency list for all the objects in the project, visible or hidden.

The exported document contains a message like this:

Quote:

This report include visible dependencies for all objects in the project.
Objects and dependencies that are not visible are not included.

Based on the behavior of the export function, it would appear 'visible' in this context means 'added to the project' rather than 'not hidden from view'.

Is this the intended behavior?

How to reproduce

Create an example database on your development instance using the following script:

Code:

CREATE DATABASE DependencyTracker_isme_20121113;
GO

USE DependencyTracker_isme_20121113;
GO

CREATE TABLE a (
b INT PRIMARY KEY,
c INT
);

CREATE TABLE d (
e INT PRIMARY KEY FOREIGN KEY REFERENCES a(b),
f INT
);

CREATE TABLE g (
h INT PRIMARY KEY FOREIGN KEY REFERENCES d(e),
i INT
);
GO

Create a new project in SQL Dependency tracker. Add all the tables from database DependencyTracker_isme_20121113 but nothing else.

The main view of SQL Dependency Tracker looks like this:

Export a PDF dependency list.

The PDF should look like this:

The export contains all the same information as the Dependency Tracker main view. So far, so good.

Hide table g.

The main view looks like this:

Export the PDF dependency list again.

The dependency list looks exactly the same:

The table g is not visible in the Dependency Tracker main view, so I would expect to see no reference to it in the exported dependency list.