September 28, 2010 at 3:23 am
Hi all,
On a particular server I keep getting timed out when I try to access a job's history, everything else in MS Studio refreshes ok, and thhe problem is isolated to a particular server, any idea what the cause is?
Cheers,
Jim
September 28, 2010 at 4:53 am
Hi, I had a similar issue when there was no Service Packs installed for MS SQL 2005 and when I had an issue installing SP3 on the same server and it failed on database services part of the install ...
MCITP: Database Administrator 2005
MCTS SQL Server 2008
MCP SQL 2012/2014
MCSA SQL Server 2012/2014
MCSE Data Management and Analytics
September 28, 2010 at 7:54 am
Possible, but there are òther servers still on SP2 that don't exhibit the issue.
September 28, 2010 at 8:50 am
Check for excessive locks on MSDB database
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 28, 2010 at 9:00 am
You might try checking also how many records are in the table holding the job history. I've seen the GUI timeout just cause there were so many records to return from the table. I believe the table is sysdbmaintplan_history.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply