In Enterprise Manager: Right-click on table, All tasks, Display dependencies

In Query Analyzer: Expand database, User Tables, table, Dependencies

Also see sp_fkeys in master db.

Greg

Here's how I'd do this, though I'm not a fan of developers maintaining databases.

1. Create a DTS package with steps that disable or drop foreign keys, delete from the destination tables (if...

Is the database using the Simple recovery model?  If so, there's no way you can retrieve transactions that occurred over the past year because everytime a checkpoint occurred, the entries...

Also, though you can't write a trace directly to a table when using the stored procedures to create a trace, you can programatically copy the trace file to a table. ...

Audit for event number 118.  See 'sp_trace_setevent' in BooksOnLine. 

Greg

I suppose you could make the trace output file read-only, otherwise sure, the contents of the files could be changed.  Who you gonna trust?

Greg

Glad to help.  There are some really cool tools posted here if you search for the right terms. 

Greg

Check out this script: http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1350

I found it while researching a way to import Windows log info to a central computer for a daily health check.  I have tested it...

Does the stored procedure use a linked server?  There are lots of posts about this error being generated in that situation.  Search this site for "NT AUTHORITY\ANONYMOUS LOGIN".

Greg

Hi Greg,

If you're interested in named instances because the server name is long, you'll probably be disappointed to know that a named instance is identified by a name with the...

The log backup will fail because the disk file is in use by the tape copy process.  To avoid that, schedule log backups so they don't occur during the window...

Chethan,

I don't think you can use a Transform Data task to import into a view, but you can use an Execute SQL task using your current stored procedures.  I'm not sure...

We create and start the trace using T-SQL and the sp_trace stored procedures.  This runs the trace without having the Profiler client running and allows us to customize the events...

Unless you were auditing for DROP DATABASE, I don't think there's a way to know who dropped it.

Auditing requirements on our data warehouse server require us to run a Profiler trace...

I don't know about the trigger but, since you posted in the DTS forum, I assume you're interested in a DTS solution also. 

I've used the method in this article...