﻿<?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, Performance Tuning, Performance Tuning and Scaling</title><link>http://www.sqlservercentral.com/</link><description>Content tagged T-SQL, Visual Basic 6, Performance Tuning, Performance Tuning and Scaling posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><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><item><title>Reducing Round Trips - Part 2</title><description>Last week Andy started a discussion of the various ways you can reduce the number of round trips to the server. This week he continues by looking at a method he used recently to do client side caching of data to eliminate the round trip altogether. Gotta read it!
</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/</guid><pubDate>2002/02/06</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning/reducingroundtripspart2/588/</link></item></channel></rss>