﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Content tagged Monitoring, Miscellaneous</title><link>http://www.sqlservercentral.com/</link><description>Content tagged Monitoring, Miscellaneous posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Alert! Alert! Backup and Restore Baby!</title><description>Are you using alerts to help you keep track of things? Are you using as many alerts as you should be? Jeremy has a great list of alerts that he considers so important they are on his &amp;#39;best practice&amp;#39; list. Definitely worth reading.

</description><guid>http://www.sqlservercentral.com/articles/Administering/alertalertbackupandrestorebaby/1253/</guid><pubDate>2004/01/08</pubDate><link>http://www.sqlservercentral.com/articles/Administering/alertalertbackupandrestorebaby/1253/</link></item><item><title>Create Maintenance Job with a Click without using a Wizard</title><description>Don&amp;#39;t like the blackbox approach of maintenance plans? Like the maintenance plans but need a tweak to suit your needs? New author Robin Back has put together a monster script to allow you to build your own quickly and easily.


</description><guid>http://www.sqlservercentral.com/articles/Administering/createmaintenancejobwithaclickwithoutusingawizard/1102/</guid><pubDate>2003/08/20</pubDate><link>http://www.sqlservercentral.com/articles/Administering/createmaintenancejobwithaclickwithoutusingawizard/1102/</link></item><item><title>Auto Close and Auto Shrink - Just Don't</title><description>New author! Mike Pearson discusses how auto close was at the root of a performance problem he was troubleshooting, how you can check your servers easily, and discusses why both auto close and auto shrink are bad ideas in a production environment.

</description><guid>http://www.sqlservercentral.com/articles/Administering/autocloseandautoshrinkjustdont/984/</guid><pubDate>2003/05/05</pubDate><link>http://www.sqlservercentral.com/articles/Administering/autocloseandautoshrinkjustdont/984/</link></item><item><title>Review of SQL 2000 Fast Answers</title><description>A monster book at 980 pages, it&amp;#39;s written in &amp;#39;how-to&amp;#39; format and has a ton of good material. Andy gave it the once over for us and reports back - see what he thinks!

</description><guid>http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/</guid><pubDate>2003/04/18</pubDate><link>http://www.sqlservercentral.com/articles/Installation/reviewofsql2000fastanswers/959/</link></item><item><title>Managing Jobs Using TSQL</title><description>We&amp;#39;ve had a good run of jobs about job management lately, Randy sent us another one that looks at the job of job management and shows us how he tackled the problem.



</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobsusingtsql/945/</guid><pubDate>2003/04/02</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobsusingtsql/945/</link></item><item><title>Managing Jobs - Part 2</title><description>Jobs are pretty basic aren&amp;#39;t they? They are until you get a couple hundred, or a thousand. Andy continues talking about managing jobs by standardizing how you handle notifications and failures, and talks about an interesting idea to monitor jobs separately from SQL Agent. Worth reading!
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/</guid><pubDate>2003/02/14</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart2/919/</link></item><item><title>Managing Jobs - Part 1</title><description>How many jobs do you have? 10? 100? 1000? Andy makes the point that what works to manage for a small number of jobs doesn&amp;#39;t work when that number doubles or triples (well, unless you only had 1 job to start with!). In part one of two, this article looks at ideas for using categories and naming conventions to get things under control.
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/</guid><pubDate>2003/01/31</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart1/906/</link></item><item><title>The Case for SQL Logins - Part 1</title><description>Andy says Windows Authentication &amp;#34;is bad&amp;#34;. What? That&amp;#39;s not what Microsoft says! Heck, that&amp;#39;s not even what we say! Everyone knows NT authentication is the way to go. Then again, when was the last time Andy wrote an article that wasn&amp;#39;t worth reading?! Read the article, rate it and add a comment - and automatically be entered in a drawing for a copy of SQL Server 2000 Performance Tuning donated by Microsoft Press.

</description><guid>http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginspart1/714/</guid><pubDate>2002/06/25</pubDate><link>http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginspart1/714/</link></item><item><title>Review of SQL Server 2000 Performance Tuning</title><description>This book from Microsoft Press has a lot of good information that will help you do capacity planning and performance tuning. Is it worth buying though? Andy just finishing reading it and writing the review, see what he thinks!
</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/reviewofsqlserver2000performancetuning/673/</guid><pubDate>2002/05/03</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/reviewofsqlserver2000performancetuning/673/</link></item></channel></rss>