While it doesn't help you track down the specific machine, that particular message means that someone/thing tried to authenticate to SQL Server with Windows authentication but wasn't on the same...

Adriadne, you've got it right. The xp_restore_verifyonly sproc takes as many @filename parameters as you need, so you'd have something like this:

EXEC master.dbo.xp_restore_verifyonly

@filename = 'Q:\subdirectory1\File1.mdf',

@filename = 'Q:\Subdirectory1\File2.mdf',

@filename = 'Q:\Subdirectory1\File3.mdf'

Hi Stephen,

This script http://www.chriskempster.com/scripts/listtriggers.sql, which appears to be originally from sqlservercentral.com, will do the trick. It's just a text file, so do a "view source" in your browser...

Actually mine will be a little simpler. I have a trigger maintaining the lineage and depth of each node (http://www.sqlteam.com/item.asp?ItemID=8866) so that we don't ever have to do...

Andy -- I can't use cascade deletes because the parent points to a row in the same table; SQL Server considers this to be a circular reference and won't allow...