no history on SQL Agent jobs - SQL Server 2000

[jpotucek]

SQL Server 2000 Ent

A couple of weeks ago, a password got changed on a SQL login that 'broke' a couple of scheduled jobs. They were DTS packages that used this SQL Account that were scheduled and set up as scheduled jobs using the SQL agent.

Basically what I did was change the password in the DTS password to match the new password, reschedule the DTS package which created a new Scheduled Job under the SQL Agent and then I dropped the old (original) job that was failing because of the pasword change.

I thought I was good to go. the newly scheduled DTS packages are running fine but i cannot view the job history on any of these new jobs. When use EM and drill down to JOBS under Sql Agent and right click on any of these new jobs, it just says NO HISTORY AVAILABLE.....


Can anyone tell me what is going on with this and possibly how I can rectify it???

 

[mrdenny]

In addition to my other post, make sure to refresh the Job list page (may require that you close EM and reopen it). EM is known for caching data when it shouldn't. You may be passing in the wrong SPID for the SQL Job which is why you are getting no history.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[jpotucek]

passing the wrong SPID? The SQL Jobs are created by the system when you scheduled the DTS package. How do I check or fix if it's passing the wrong SPID?

 

[mrdenny]

The only way to see if your client is passing the wrong spid would be to use SQL Profiler to see what spid is being passed and then see if that GUID actually exists in the sysjobs table.

The only way to fix it is to close EM and reopen it.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[jpotucek]

I guess there is alot to learn about all of this but if you fix it by closing and reopening enterprise Manager - this is done everyday when I take my laptop home.