You can't use extended stored procedures in an ExecuteSQL task like normal stored procedures. This is because the meta-data about the parameters is not available at design time.

You can work...

If you want to show the information as a summary across the different servers, then you'll need to bring the data together somehow. You could use a summary table, or...

Just do the same as you have done for the month and day.

eg: Right("0" & Hour(Now), 2)

Michelle, Try this,

REPLACE("[A-MSG]", '''','')

You could try something like the following in query Analyzer. Despite appearences, only single quotes are used. Also, make sure you have an alert setup for the severity level, or change...

I think it stores it in memory somewhere, unless it calculates it based on the job duration prior to writing to sysjobhistory.

Job execution status has always been one of those...

Ok, are you able to extract the SQL statement from the package and run it in Query Analyzer? Then you'll be able to play around a bit more freely to...

Yes, but couldn't you link the information you've already got from sysprocesses to the information from the xp?

Instead of using NOT IN, try using a left join like this,

update sup 
set sup.Del_Status='YES' 
from supplier sup
  left join Items_Master mas
  on sup.supp_ID = mas.supp_ID
where sup.Supp_ID='S01'...

What do Idera say about the problem?

I don't think there is anything specific you can check for when the reindex/defrag occurred. You can run DBCC SHOW_CONTIG to check on the table fragmentation.

There is an extended stored procedure that is called to return the currently running jobs. I think it's xp_enum_sqlagentjobs, not sure about that though and I don't have access to...

Came across this one myself. What you'll need to do is assign the [A-MSG] token to a variable and then replace the quotes.

EG: From memory you end up with something...

... or even easier, turn on package logging to SQL Server. Then you have the same as sysjobhistory but without the limit on the history.

Once turned on, DTS logs information...

Sorry, this is a bit confusing. What "parameters and other details" are you changing and how are you executing the customer.bas file?