﻿<?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, .Net, Programming</title><link>http://www.sqlservercentral.com/</link><description>Articles tagged Administering, Strategies, .Net, 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 4</title><description>Andy has been busy lately on a project you&amp;#39;ll be hearing more about soon (!), but he did manage to get part four of his managing jobs series done. This article discusses ideas for patterns to follow when building jobs, including writing to the console, setting errorlevels, and how to get them installed on the server. DBA&amp;#39;s, if you&amp;#39;re not developers, look at this article - this is stuff you can take to your development team and get better/more manageable jobs.
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart4/1037/</guid><pubDate>2003/06/25</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart4/1037/</link></item><item><title>Managing Jobs Part 3</title><description>This week Andy looks at where, when, and how jobs should be run and why you need to think about those items before you build the job. Part of this is deciding what runs on production servers and what doesn&amp;#39;t.
</description><guid>http://www.sqlservercentral.com/articles/Administering/managingjobspart3/936/</guid><pubDate>2003/03/11</pubDate><link>http://www.sqlservercentral.com/articles/Administering/managingjobspart3/936/</link></item></channel></rss>