maintaining/altering database

Our database(s) are all over the place - no documentation - lot's of
rubbish and unused stuff.
I'm managing a project focusing on data quality that covers code
changes, alterations to DTS packages, schema changes etc etc.
What I'd like to do is see where the bit I want to change is being
used.
that might mean what stored procs use a field and what sprocs use that
sproc.
maybe it's which dts packages use a sproc (and again up the
hieararchy)
The list is a long one but basically I need to know what the effects
are of changes.
Is there a tool out there that lets me navigate a database to that
level of detail - I understand something along the same lines is
available for MS Access but I can't find it for SQL Server.
ThanksRed-Gate has a pretty cool tool called SQL Dependency Tracker that you
should check out:
http://www.red-gate.com/products/SQL_Dependency_Tracker/index.htm
There's also a stored proc in SQL Server called sp_depends which queries
an internal view called sysdepends. You can also check that out if you
want to spend $0 on new software. A warning: sysdepends is not that
reliable, or at least it hasn't been for me in the past. I don't really
know if SQL Server 2005 makes it more useful than it was in 2000. Does
anyone on the group know if there have been any significant enhancements
to sysdepends in 2005?
oliver wrote:
> Our database(s) are all over the place - no documentation - lot's of
> rubbish and unused stuff.
> I'm managing a project focusing on data quality that covers code
> changes, alterations to DTS packages, schema changes etc etc.
> What I'd like to do is see where the bit I want to change is being
> used.
> that might mean what stored procs use a field and what sprocs use that
> sproc.
> maybe it's which dts packages use a sproc (and again up the
> hieararchy)
> The list is a long one but basically I need to know what the effects
> are of changes.
> Is there a tool out there that lets me navigate a database to that
> level of detail - I understand something along the same lines is
> available for MS Access but I can't find it for SQL Server.
> Thanks
>|||On 26 Feb, 22:54, David Markle <new...@.markleconsulting.c0m> wrote:
> Red-Gate has a pretty cool tool called SQL Dependency Tracker that you
> should check out:
> http://www.red-gate.com/products/SQL_Dependency_Tracker/index.htm
> There's also a stored proc in SQL Server called sp_depends which queries
> an internal view called sysdepends. You can also check that out if you
> want to spend $0 on new software. A warning: sysdepends is not that
> reliable, or at least it hasn't been for me in the past. I don't really
> know if SQL Server 2005 makes it more useful than it was in 2000. Does
> anyone on the group know if there have been any significant enhancements
> to sysdepends in 2005?
>
> oliver wrote:
> > Our database(s) are all over the place - no documentation - lot's of
> > rubbish and unused stuff.
> > I'm managing a project focusing on data quality that covers code
> > changes, alterations to DTS packages, schema changes etc etc.
> > What I'd like to do is see where the bit I want to change is being
> > used.
> > that might mean what stored procs use a field and what sprocs use that
> > sproc.
> > maybe it's which dts packages use a sproc (and again up the
> > hieararchy)
> > The list is a long one but basically I need to know what the effects
> > are of changes.
> > Is there a tool out there that lets me navigate a database to that
> > level of detail - I understand something along the same lines is
> > available for MS Access but I can't find it for SQL Server.
> > Thanks- Hide quoted text -
> - Show quoted text -
it's not really fully featured enough I don' think - money's not
really too much of an issue - surely there something a bit more meaty?