﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 Performance Tuning  / Measuring "workload" in SQLServer / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 20 May 2013 08:32:33 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Measuring "workload" in SQLServer</title><link>http://www.sqlservercentral.com/Forums/Topic955718-360-1.aspx</link><description>Thanks Tara, and there just happens to be an article on using powershell to capture perfmon statistics in one of my emails this morning: http://www.simple-talk.com/sql/database-administration/gathering-perfmon-data-with-powershell/?utm_source=simpletalk&amp;utm_medium=email-main&amp;utm_content=Perfmon-20100712&amp;utm_campaign=SQL</description><pubDate>Wed, 21 Jul 2010 07:25:46 GMT</pubDate><dc:creator>jrc172</dc:creator></item><item><title>RE: Measuring "workload" in SQLServer</title><link>http://www.sqlservercentral.com/Forums/Topic955718-360-1.aspx</link><description>I totally agree.  I should have said this is an OLTP system, not OLAP. Queue length and system waits are great performance metrics, but I'm looking for workload metrics.  Different but not totaly opposite.</description><pubDate>Wed, 21 Jul 2010 07:24:30 GMT</pubDate><dc:creator>jrc172</dc:creator></item><item><title>RE: Measuring "workload" in SQLServer</title><link>http://www.sqlservercentral.com/Forums/Topic955718-360-1.aspx</link><description>It really kind of depends on your business and your systems. For example, I work for an insurance company. We don't do umpty-gazillion transactions per/second, so measuring just transactions per second wouldn't supply us with much information. Instead, more often than not, we look at query execution time. But even that is not enough of a measure. Instead of finding a single number and deciding that's your point of entry, I'd suggest just a few measures. Base everything on waits and queues. Disk Queue Length, Processor Queue Length and various system waits. Gather those metrics and you'll have a good idea of the performance of the system. Anything else is just a symptom. Transactions/sec went down... why? We have an increased disk queue length. Uh, oh, IO issues. See what I mean?</description><pubDate>Tue, 20 Jul 2010 11:10:56 GMT</pubDate><dc:creator>Grant Fritchey</dc:creator></item><item><title>RE: Measuring "workload" in SQLServer</title><link>http://www.sqlservercentral.com/Forums/Topic955718-360-1.aspx</link><description>We use batch requests per second in PerfMon.  On our busiest system, we have 1500-3000 batches per second occurring 24/7.</description><pubDate>Tue, 20 Jul 2010 11:03:57 GMT</pubDate><dc:creator>Tara Kizer</dc:creator></item><item><title>Measuring "workload" in SQLServer</title><link>http://www.sqlservercentral.com/Forums/Topic955718-360-1.aspx</link><description>I'm trying to get a handle on what constitutes a measure of work (to calculate comparative "workloads") in the SQLServer environment.  The answer "all of them" is probably neither usable nor correct.  How about transactions/sec (from dmv  sys.dm_os_performance_counters)?Others ... ?</description><pubDate>Tue, 20 Jul 2010 09:56:11 GMT</pubDate><dc:creator>jrc172</dc:creator></item></channel></rss>