Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Working Around 2005 Maintenance Plans Expand / Collapse
Author
Message
Posted Wednesday, February 8, 2006 4:56 PM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, January 17, 2014 11:05 AM
Points: 779, Visits: 222
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/aingold/workingaround2005maintenanceplans.asp
Post #256915
Posted Monday, March 6, 2006 5:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, December 5, 2013 4:35 AM
Points: 31, Visits: 79
Hi,
I might have missd something, but couldn't you just use a Maintenance Cleanup Task to delete old backups? That's how we have it set up here, and it seems to do the trick. As I recall, you aren't offered one of these in the wizard, but you can drag them into your maintenance plan from the toolbox.



Post #263409
Posted Monday, March 6, 2006 10:13 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, January 17, 2014 11:05 AM
Points: 779, Visits: 222
That is a very good point which I had neglected to mention! You read an article a thousand times thinking you've addressed everything...

In our situation we wanted to stick with an existing departmental guideline which puts each backup into its own subdirectory. While it seems inconsequential there are certain rules and precedents on the server which rely upon this setup. In my experimentation I couldn't get the maintenance cleanup task to traverse subdirectories properly by pointing to the parent directory (unless I was willing to create a new task for each subdirectory).
Post #263552
Posted Monday, March 6, 2006 10:32 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, December 5, 2013 4:35 AM
Points: 31, Visits: 79
Ain't it always the way

Yes, the lack of support for cleaning a directory tree is a strange omission. I believe we ended up writing a tool to generate the package automatically. There are a few questionable aspects of the interface, as I recall.

Very slightly off topic, but what is the point of naming schedules for the maintenance tasks? Now if I could selected an already created schedule for a different task,... Doubtless I've missed something obvious though!



Post #263556
Posted Monday, March 6, 2006 11:30 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, January 17, 2014 11:05 AM
Points: 779, Visits: 222
Yes, I originally was playing around with using vb or perl to clean up the backup files, however I ended up wanting to try to keep everything inside SQL. The other thing was that if the traditional maintenance plans failed the logs were woefully inadequate. With this type of framework you can use more standard error trapping and log those using RAISERROR or offload them to a table if you so desire.

I don't know if I understand your last question. If you're asking about re-using schedules for different jobs you can do so via the GUI by clicking the "Pick..." button on the Schedules page in your job or by using msdb.dbo.sp_attach_schedule if you're scripting things out. Schedules can be found listed in msdb.dbo.sysschedules.
Post #263575
Posted Tuesday, March 7, 2006 2:54 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, December 5, 2013 4:35 AM
Points: 31, Visits: 79
Ah, I'd not noticed it there - I'd been looking at it from the maintenance plan editor, where you don't appear to be able to select, only create




Post #263765
Posted Tuesday, March 7, 2006 4:10 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, August 29, 2006 12:07 AM
Points: 4, Visits: 1

We came across several postings in Forums about Maintenaceplan cleanup task not deleting the backup files if backups of databases were created under separate folders. This helped us take immediate action to address it in our service pack(SP).

This issue is now addressed in Service Pack 1. The private beta of SP1 is released and public beta release of SP1 is expected to be sometime this month.

Thanks for all your feedback and we hear and value every feedback we get!

Gops Dwarak, Program Manager, SQL Server Tools Team, Microsoft

Post #264001
Posted Wednesday, March 8, 2006 11:34 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, January 17, 2014 11:05 AM
Points: 779, Visits: 222
That's great news to hear! Thank you very much for being so responsive to the community. I knew that there would be an official solution from MS dwn the line, but I didn't know it would come so quickly.
Post #264255
Posted Tuesday, March 6, 2007 6:55 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, May 7, 2007 3:16 PM
Points: 32, Visits: 1

My particular backup problem is that when I do a full backup on some transaction-heavy databases that have their recovery models set to Full, the first hourly transaction log - .trn file - after the full backup is almost the same size as the .bak file. 

Subsequent hourly .trn files are nice and small.

I wanted all the .trn files to be small, to conserve drive space, so I tried setting the recovery models to bulk_logged, then do the .trn backup, then setting the recovery models back to Full, but this three-step approach seems to either take forever, or fail.

Any ideas would be appreciated.

 Thanks, Mike

 

 

Post #349346
Posted Wednesday, January 30, 2008 3:57 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 3:32 AM
Points: 99, Visits: 670
I cannot download the code:
"
Search for any content tagged Administration & workingaround2005maintenanceplans & 2282 & bch_article_work_v2.txt
Sorry, nothing found for this search
"
Post #449253
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse