﻿<?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 2008 / SQL Server 2008 Administration  / Discrepancy Between sys.dm_os_performance_counters and DBCC SQLPERF(logspace) / 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>Wed, 19 Jun 2013 07:36:45 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Discrepancy Between sys.dm_os_performance_counters and DBCC SQLPERF(logspace)</title><link>http://www.sqlservercentral.com/Forums/Topic1394687-1550-1.aspx</link><description>[quote][b]Perry Whittle (12/11/2012)[/b][hr]have you run a log backup since removing the extra log file?[/quote]Yup - we run them every 10 minutes, for log shipping.</description><pubDate>Tue, 11 Dec 2012 07:11:21 GMT</pubDate><dc:creator>tim_harkin</dc:creator></item><item><title>RE: Discrepancy Between sys.dm_os_performance_counters and DBCC SQLPERF(logspace)</title><link>http://www.sqlservercentral.com/Forums/Topic1394687-1550-1.aspx</link><description>have you run a log backup since removing the extra log file?</description><pubDate>Tue, 11 Dec 2012 06:41:03 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Discrepancy Between sys.dm_os_performance_counters and DBCC SQLPERF(logspace)</title><link>http://www.sqlservercentral.com/Forums/Topic1394687-1550-1.aspx</link><description>Not 100%, but some sys views only refresh on a SQL restart - could be that the extraneous counter will vanish then.</description><pubDate>Tue, 11 Dec 2012 04:44:47 GMT</pubDate><dc:creator>Gazareth</dc:creator></item><item><title>Discrepancy Between sys.dm_os_performance_counters and DBCC SQLPERF(logspace)</title><link>http://www.sqlservercentral.com/Forums/Topic1394687-1550-1.aspx</link><description>Background - A deployment gone bad.  Deployment caused the transaction log to grow to the point where I needed to add a 2nd one.  Deployment is done, and now I am cleaning up.  I am getting alerts that my TLog is over it's threshold, but it is not.  When I run DBCC SQLPERF(loginfo), it shows my log as ~8.5 GB.  When I look at the actual file on disk, it also shows 8.5 GB.  This is what I expect.The issue is that the alert is being generated from: [code="sql"]select * from sys.dm_os_performance_counters where object_name = 'SQLServer:Databases'and instance_name = ...and counter_name = 'Log File(s) Size (KB)'[/code]This tells me that the log file is 18.5 GB.  When I run system monitor I see the same result.The log file that I added, and deleted after the fact was 10 GB.  PerMon thinks it is still there.  I have verified from the file system that there is no file there anymore.Has anyone seen a similar discrepancy, or can anyone explain to me why I might be seeing this?  Thanks in advance.</description><pubDate>Mon, 10 Dec 2012 09:44:22 GMT</pubDate><dc:creator>tim_harkin</dc:creator></item></channel></rss>