<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Maintenance plans love story</title><link>http://sqlblog.com/blogs/maria_zakourdaev/archive/2012/04/05/maintenance-plans-love-story.aspx</link><description>There are about 200 QA and DEV SQL Servers out there. There is a maintenance plan on many of them that performs a backup of all databases and removes the backup history files. First of all, I must admit that I’m no big fan of maintenance plans in particular</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Maintenance plans love story</title><link>http://sqlblog.com/blogs/maria_zakourdaev/archive/2012/04/05/maintenance-plans-love-story.aspx#42724</link><pubDate>Fri, 06 Apr 2012 09:11:44 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:42724</guid><dc:creator>Ian Yates</dc:creator><description>&lt;p&gt;Great script. &amp;nbsp;We're an ISV and tend to have a mix of Express &amp;amp; Standard edition around the place at our various clients. &amp;nbsp;For those with standard edition I configure a maintenance plan but the customer's IT support company rarely knows more than how to spell SQL, and tend to like to see things in the Windows task scheduler. &amp;nbsp;I had a very simple version of the above script, but yours is is a bit more elegant.&lt;/p&gt;
&lt;p&gt;What sort of approaches do you tend to recommend for monitoring of success/failure of backups? &amp;nbsp;Reindexing, etc? &amp;nbsp;I tend to just script things in SQLCMD and dump the output to a file, but that needs someone to know what a 100% success looks like vs a 90% success or complete failure.&lt;/p&gt;
</description></item><item><title>re: Maintenance plans love story</title><link>http://sqlblog.com/blogs/maria_zakourdaev/archive/2012/04/05/maintenance-plans-love-story.aspx#42725</link><pubDate>Fri, 06 Apr 2012 12:48:44 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:42725</guid><dc:creator>Jon Harn</dc:creator><description>&lt;p&gt;Thanks for sharing your info. I really appreciate your efforts and I will be waiting for your further write ups thanks once again.&lt;/p&gt;</description></item><item><title>re: Maintenance plans love story</title><link>http://sqlblog.com/blogs/maria_zakourdaev/archive/2012/04/05/maintenance-plans-love-story.aspx#42739</link><pubDate>Sun, 08 Apr 2012 20:32:32 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:42739</guid><dc:creator>Wiseman82</dc:creator><description>&lt;p&gt;I've never been a big fan of maintenance plans. &amp;nbsp;They have probably got better with newer versions of SQL server, but certainly in SQL 2005 they were buggy. &amp;nbsp;Also, in a dev environment you might have certain databases you want to exclude from backup but you might also want to ensure that any new databases created are included in the backup automatically. &amp;nbsp;Scripts work well and they offer additional flexibility.&lt;/p&gt;
&lt;p&gt;Thanks for sharing your solution. &amp;nbsp;My own solution is posted here if it helps anyone:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.wisesoft.co.uk/scripts/t-sql_backup_databases_script.aspx"&gt;http://www.wisesoft.co.uk/scripts/t-sql_backup_databases_script.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Ideally you would receive an alert to inform you that the backup job has failed but I also like to check manually that the backup has completed without any issues. &amp;nbsp;I use this SP to have each server send me a status email on a daily basis:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.wisesoft.co.uk/articles/dba_daily_checks_email_report.aspx"&gt;http://www.wisesoft.co.uk/articles/dba_daily_checks_email_report.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It's also a good idea to test backups on a regular basis - particularly for production systems.&lt;/p&gt;
&lt;p&gt;As Ian mentioned reindexing, here is my script based solution to re-indexing:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.wisesoft.co.uk/scripts/t-sql_defrag_indexes_for_database.aspx"&gt;http://www.wisesoft.co.uk/scripts/t-sql_defrag_indexes_for_database.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I find that it allows me to take a more targeted approach to index maintenance compared to index maintenance plans. &amp;nbsp;I use a SSRS report based on the two tables created in the script for monitoring (plus a failure notification on the agent job).&lt;/p&gt;
&lt;p&gt;I'm work with a much smaller number of servers and the links I've posted are solutions I've developed based on my own specific requirements. &amp;nbsp;If they are useful to anyone else, great!&lt;/p&gt;
</description></item><item><title>re: Maintenance plans love story</title><link>http://sqlblog.com/blogs/maria_zakourdaev/archive/2012/04/05/maintenance-plans-love-story.aspx#42745</link><pubDate>Mon, 09 Apr 2012 14:08:22 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:42745</guid><dc:creator>Steve</dc:creator><description>&lt;p&gt;I'd recommend looking at Ola Hallengren's solution which can be found here. &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://ola.hallengren.com"&gt;http://ola.hallengren.com&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>