Kevin Remde's IT Pro Weblog
IT Pro Resources
TechNet EventsMicrosoft Security Response CenterTechNet IT Manager Community HubMicrosoft Virtual AcademyKevin’s Evaluation Download Center
IT Pro Evangelist Blogs
Blain Barton Blain Barton's Blog@BlainBar
Brian LewisMy Thoughts on IT...@BrianLewis_
Dan Stolts IT Pro Guru Blog@ITProGuru
Jennelle Crothers TechBunny@jkc137
Keith MayerIT Pros ROCK!@KeithMayer
Kevin Remde Full of I.T.@KevinRemde
Matt Hester Matthew Hester's WebLog@MatthewHester
Tommy PattersonVirtually Cloud 9@Tommy_Patterson
Yung Chou Yung Chou on Hybrid Cloud@YungChou
SQL Server 2005 Tidbit 025
This tidbit comes as an answer to a really good question asked at a recent TechNet Event:
“What if a Maintenance Plan fails at some point? Do I have the ability to restart the plan at a particular step?”
The answer to this is similar to the answer to the one in tidbit 28 – You really should consider plans as full sets of work. If the plan fails at some point, you would probably want to launch the task separately, or create a job just to tackle what wasn’t otherwise completed.
Got an IT question? Give me a comment, or contact me.
Maintenance Plans in SQL Server 2005 are SSIS packages. With an SSIS package you can use "checkpoints" to restart your package and it will pick up where the package failed. This is a better way to finish the Maintenance Plan than creating a package just for the last few tasks. I've done plenty of DTS development and its a pain to copy and paste a few tasks from a package that failed into a new package just so you can finish the process. In my last job we call them "Hack-a-Pack(age)s"
Information on Checkpoints can be found in the following TechNet doc at http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx