August 3, 2008 at 1:58 pm
has anyone out there got the deletion of maintenace plan text reports working?
Version 9.00.3054
doesn't work when I cut and paste the xp_delete_file into query window either. Reports success but does nothing.
---------------------------------------------------------------------
August 4, 2008 at 9:11 am
It is a known bug with that version. You need to upgrade to 9.00.3175 (Cumulative update package 2 for SQL Server 2005 Service Pack 2).
August 4, 2008 at 3:15 pm
thanks, you are right, I have a 9.00.3200 (CU4) server and it turns out it is working there.
still leaves the history cleanup task though. maintenance plan history delete seems to be correct, but backup history doesn't look right, and jobhistory is definitely wrong, I have no history older than current day, which is annoying when you try and check on a job.
Another maintenance plan bug fixed in a later CU?
---------------------------------------------------------------------
August 5, 2008 at 6:51 am
I have not run into that problem. I can see job history for all of my jobs. Not sure what that one is.:unsure:
August 8, 2008 at 6:23 pm
We use 9.00.3186 specifically to correct this problem. This is cumm update 3.
August 10, 2008 at 1:10 pm
juliembarr (8/8/2008)
We use 9.00.3186 specifically to correct this problem. This is cumm update 3.
julie(?) this resolves backup history and jobhistory problems? Because I am at 9.00.3200 (CU4), so maybe problem reintroduced!
---------------------------------------------------------------------
August 13, 2008 at 5:28 pm
We originally encountered problems with txt file deletion when running Build 3159 [9.00.3159]. We applied 3159 to address an issue with Check Integrity. After some research and contact with Microsoft, they acknowledged a problem with .txt files not being deleted on our system and we determined that 9.00.3186 [Cumm Upd 3] addressed the problem. We have not applied any maintenance since then so I cannot speak for any maintenance level above 3186. I have not noticed any problems with jobhistory, but I haven't specifically looked into that issue one way or the other.
August 14, 2008 at 7:37 am
We've been having this problem on several servers. I ended up sticking this batch code into a schedued task.
@echo off
echo.
echo Removing old emrRun log files
forfiles /p C:\MSSQL.1\MSSQL\LOG /s /m MaintenancePlan*.txt /d -7 /c "cmd /c del @path"
echo.
echo Removing old emrRun log files
forfiles /p C:\MSSQL.1\MSSQL\LOG /s /m Rebuild*.txt /d -7 /c "cmd /c del @path"
The -7 is number of days to retain. The MaintenancePlan*.txt and Rebulid*.txt are used to specify which maintenance plan .TXT files you want to delete.
October 16, 2008 at 7:11 am
george sibbald (8/4/2008)
thanks, you are right, I have a 9.00.3200 (CU4) server and it turns out it is working there.still leaves the history cleanup task though. maintenance plan history delete seems to be correct, but backup history doesn't look right, and jobhistory is definitely wrong, I have no history older than current day, which is annoying when you try and check on a job.
Another maintenance plan bug fixed in a later CU?
lack of job history was due to the fact that the default no. of rows kept in msdb..sysjobhistory is 1000. I have so many jobs on this server which run frequently that 1000 rows is quickly used up. fix is to go to properties on sql server agent and under history increase maximum job history log size (in rows) value
---------------------------------------------------------------------
October 16, 2008 at 7:20 am
Thanks for the update. That's good to know.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply