﻿<?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 Articles tagged Administering, Strategies, Configuring, Programming</title><link>http://www.sqlservercentral.com/</link><description>Articles tagged Administering, Strategies, Configuring, Programming posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><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>Another Disaster (Almost)</title><description>Andy had a semi-disaster similar to the one he wrote about last year. Interesting to see the kinds of problems that happen to other people. This article raises some interesting points that are outside the scope of basic disaster recovery, looking at how/when to move databases to a different server and how to reduce the server load dynamically.
</description><guid>http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/</guid><pubDate>2003/01/14</pubDate><link>http://www.sqlservercentral.com/articles/Administering/anotherdisasteralmost/881/</link></item><item><title>The Case for SQL Logins - Part Two</title><description>In this follow up to one of our most popular articles, Andy responds to comments posted by readers and discusses how to manage SQL logins effectively in your applications.

</description><guid>http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginsparttwo/780/</guid><pubDate>2002/08/19</pubDate><link>http://www.sqlservercentral.com/articles/Administering/thecaseforsqlloginsparttwo/780/</link></item><item><title>Version Control for Stored Procedures</title><description>Version control for stored procedures isn&amp;#39;t always popular and certainly isn&amp;#39;t easy. Or can it be? Andy discusses a technique he used on a recent project that you might find interesting.
</description><guid>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</guid><pubDate>2002/05/10</pubDate><link>http://www.sqlservercentral.com/articles/Administering/versioncontrolforstoredprocedures/681/</link></item></channel></rss>