﻿<?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 .Net, Performance Tuning</title><link>http://www.sqlservercentral.com/</link><description>Content tagged .Net, Performance Tuning posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>Gathering Metrics with SMO</title><description>Keeping track of the performance of your SQL Servers requires metrics. There are many methods for doing this, but some type of automated process is essential these days with DBAs managing many servers. New author Allen White brings us a technique for doing this using SMO, the replacement for DMO in SQL Server 2005.
</description><guid>http://www.sqlservercentral.com/articles/Performance+Tuning/2692/</guid><pubDate>2006/11/22</pubDate><link>http://www.sqlservercentral.com/articles/Performance+Tuning/2692/</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>