Hi
Thank you for the link, but I am afraid that's not the solution I am looking for. What I am trying to do is add logging as part of an audit process to several hundreds of DTS Packages in order to find out which ones are actually running. I could write a SQL Task inside a package, which would...
I see. Unfortunately I have no control over those batch processes.
I was hoping to find a way to handle it at the trigger level. It's part of an audit to find out which db objects are actually being used prior to migration to SQL Server 2005. Running a trace in production is not an option.
Thank...
ok. But I am not sure I understand. How can I rewrite my trigger so that it does not do one record insert at a time? Below is my trigger that fires for each insert, update, and delete
CREATE TRIGGER MyTriger
on MyTableName
FOR INSERT UPDATE DELETE
INSERT MYAUDITTABLE(OBjectName...
Hi George
I actually have no control over those stored procedures that run through scheduled jobs, and some them are run manually on a weekly basis. They do a batch inserts and updates. The assumption is that the trigger fires every time a record gets inserted into the tables. So if we have...
I am trying to find a way to set a trigger on sys tables to log a record in my audit table every time a DTS package executes whether manually or through a job scheduler. I have been looking at these sys tables, but could not find which fields actually record the DTS package execution info...
I am doing some auditing to find out which tables are actually being used/referenced in SQL Server 2000 Database. I have an audit table with the following fields:
ID PK
OBjectName. The name of the table
OBjectType. The Object Type. Table
AuditDate. GetDate()
Initiator. SYS_USER
The Trigger I...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.