Hi there,

I can't think of a quick way which you can implement to find the name of the stored procedure that is causing the trigger to fire but you can...

Hi,

You could also try using the extended stored procedure xp_FileExists. See http://www.sqlservercentral.com/scripts/contributions/424.asp

Cheers,

Sameer

Hi,

You can use the xp_cmdshell stored procedure to achieve this. For example:

Declare

 @sExecSQL   NVARCHAR(4000),

 @sFileLocation_Source  NVARCHAR(255),

 @sFileLocation_Target NVARCHAR(255)

SET @sFileLocation_Source = 'C:\Download\XXXXX.txt'

SET @sFileLocation_Target = 'C:\Archive\YYYYY.txt'

--Copy File

SET @sExecSQL = 'Copy ' + LTRIM(RTRIM(@sFileLocation_Source)) + '...