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/SQ...acker/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/SQ...acker/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:
>
>
>
> - 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?
Showing posts with label project. Show all posts
Showing posts with label project. Show all posts
Monday, March 19, 2012
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.
Thanks
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
>
|||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:
>
>
> - 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?
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
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
>
|||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:
>
>
> - 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?
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?
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?
maintaining a 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.
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.
ThanksObviously you could run traces while the db is running-- although this could
cause some resource descrease.
You could also do direct searches in all the sys tables for instances of the
keywords you are using
--
Jack Vamvas
___________________________________
The latest IT jobs - www.ITjobfeed.com
<a href="http://links.10026.com/?link=http://www.itjobfeed.com">UK IT Jobs</a>
<oraustin@.hotmail.comwrote in message
news:1172498745.473644.252660@.t69g2000cwt.googlegr oups.com...
Quote:
Originally Posted by
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
>
Monday, February 20, 2012
Lumigent Entegra
Hi there I was looking for people who use this product or something
similiar.
I'm doing an evaluation for a project where we need a strong
monitoring of DB activities on SQL 2000. After some research I saw the
Entegra, however the process to get price information already turns me
a bit away from the company.
So my question would be, how is the peoples experience with this
product, and second what alternatives are available ?
best regards
Andreas Palm
HP C&I .NET Development
8902 Urdorf, SwitzerlandIn my opinion it is worth every penny if you need that sort of information.
The UI is very good and the details you get are unmatched. If you really
need that type of a toll then they should be your first choice and in some
cases they are your only choice. Don't know what troubles your having with
the pricing but you really should give them a call or at least an email.
--
Andrew J. Kelly
SQL Server MVP
"Andreas Palm" <apa57@.hotmail.com> wrote in message
news:d0e0a20b.0307110312.45aa89a4@.posting.google.com...
> Hi there I was looking for people who use this product or something
> similiar.
> I'm doing an evaluation for a project where we need a strong
> monitoring of DB activities on SQL 2000. After some research I saw the
> Entegra, however the process to get price information already turns me
> a bit away from the company.
> So my question would be, how is the peoples experience with this
> product, and second what alternatives are available ?
>
> best regards
> Andreas Palm
> HP C&I .NET Development
> 8902 Urdorf, Switzerland
similiar.
I'm doing an evaluation for a project where we need a strong
monitoring of DB activities on SQL 2000. After some research I saw the
Entegra, however the process to get price information already turns me
a bit away from the company.
So my question would be, how is the peoples experience with this
product, and second what alternatives are available ?
best regards
Andreas Palm
HP C&I .NET Development
8902 Urdorf, SwitzerlandIn my opinion it is worth every penny if you need that sort of information.
The UI is very good and the details you get are unmatched. If you really
need that type of a toll then they should be your first choice and in some
cases they are your only choice. Don't know what troubles your having with
the pricing but you really should give them a call or at least an email.
--
Andrew J. Kelly
SQL Server MVP
"Andreas Palm" <apa57@.hotmail.com> wrote in message
news:d0e0a20b.0307110312.45aa89a4@.posting.google.com...
> Hi there I was looking for people who use this product or something
> similiar.
> I'm doing an evaluation for a project where we need a strong
> monitoring of DB activities on SQL 2000. After some research I saw the
> Entegra, however the process to get price information already turns me
> a bit away from the company.
> So my question would be, how is the peoples experience with this
> product, and second what alternatives are available ?
>
> best regards
> Andreas Palm
> HP C&I .NET Development
> 8902 Urdorf, Switzerland
Subscribe to:
Posts (Atom)