affecting a certain table (we use SQL 2000)... is there anyway to check
this?
and have the features for such dependency analysis been added for SQL
2005?I've never tried this, but you might be able to trap it using Profiler;
set up a log and filter on object_id.
http://www.microsoft.com/technet/ar...9.mspx?mfr=true
Post back and let us know if that works for you.
Stu
metaperl wrote:
> hi, we were doing something and began to wonder which jobs/dts were
> affecting a certain table (we use SQL 2000)... is there anyway to check
> this?
> and have the features for such dependency analysis been added for SQL
> 2005?sql
No comments:
Post a Comment