﻿<?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 T-SQL, .Net, Strategies</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, .Net, Strategies posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><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>