﻿<?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, Visual Basic 6, .Net</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, Visual Basic 6, .Net 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><item><title>Performance Comparison: Data Access Techniques</title><description>Architectural choices for data access affect performance, scalability, maintainability, and usability. This article focuses on the performance aspects of these choices by comparing relative performance of various data access techniques, including Microsoft® ADO.NET Command, DataReader, DataSet, and XML Reader in common application scenarios with a Microsoft SQL Server™ 2000 database.</description><guid>http://www.sqlservercentral.com/redirect/articles/620/</guid><pubDate>2002/03/01</pubDate><link>http://www.sqlservercentral.com/redirect/articles/620/</link></item></channel></rss>