﻿<?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 Newbies  / DBCC UPDATEUSAGE / 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>Sat, 25 May 2013 10:52:52 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: DBCC UPDATEUSAGE</title><link>http://www.sqlservercentral.com/Forums/Topic1403724-1292-1.aspx</link><description>I ran the DBCC UPDATEUSAGE command without incident.  The DBCC CheckDB runs fine.  I don't have any experience dropping and recreating an index.  What I've done is take a backup of the database (with the corruption) and will attempt this in a test environment.  Learning process continues...  Thank you both for responding.</description><pubDate>Tue, 08 Jan 2013 08:36:11 GMT</pubDate><dc:creator>jralston88</dc:creator></item><item><title>RE: DBCC UPDATEUSAGE</title><link>http://www.sqlservercentral.com/Forums/Topic1403724-1292-1.aspx</link><description>[quote][b]WolfgangE (1/7/2013)[/b][hr]Maybe - and I really mean MAYBE - you can solve the problem by rebuilding the indexe mentioned in the error message.[/quote]Dropping and recreating should solve this particular corruption.</description><pubDate>Mon, 07 Jan 2013 12:44:21 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: DBCC UPDATEUSAGE</title><link>http://www.sqlservercentral.com/Forums/Topic1403724-1292-1.aspx</link><description>"take long" is quite relative. In the enviroment I know we lose data if a table is locked for more than 30 seconds. As far as I have seen the UPDATE-USAGE-command places a lot of locks and on tables with some million records the command runs much longer than 30 seconds.Maybe - and I really mean MAYBE - you can solve the problem by rebuilding the indexe mentioned in the error message. Depending on the SQLServer-version you use you can do an online rebuild which should hold only minimal locks. I don't believe an index reorg will work but it would be another try.</description><pubDate>Mon, 07 Jan 2013 12:32:46 GMT</pubDate><dc:creator>WolfgangE</dc:creator></item><item><title>RE: DBCC UPDATEUSAGE</title><link>http://www.sqlservercentral.com/Forums/Topic1403724-1292-1.aspx</link><description>Just run exactly what the error says - DBCC UPDATEUSAGE. Doesn't usually take that long</description><pubDate>Mon, 07 Jan 2013 10:33:04 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>DBCC UPDATEUSAGE</title><link>http://www.sqlservercentral.com/Forums/Topic1403724-1292-1.aspx</link><description>DBCC CheckDB job failed last night.  This is SQL Server 2005 Enterprise Edition 64 bit environment.  The message / solution indicated running "DBCC UPDATEUSAGE".This is a first for me, should the command be run against the database?  Or against the table listed?  I'm assuming this should be run during a maintenance &amp;#119;indow.  Error message is as follows: Progress: 2013-01-06 12:00:05.17     Source: Execute T-SQL Statement Task      Executing query "USE [xxx]  ".: 50% complete  End Progress  Error: 2013-01-06 12:01:21.03     Code: 0xC002F210  Source: Execute T-SQL Statement Task Execute SQL Task Description: Executing the query "DBCC CHECKDB WITH ALL_ERRORMSGS" failed with the following error: "The In-row data USED page count for object "Project_SubFees", index ID 9, partition ID 2544946730696704, alloc unit ID 2544946730696704 (type In-row data) is incorrect. [b]Run DBCC UPDATEUSAGE[/b].  The In-row data RSVD page count for object "Project_SubFees", index ID 9, partition...The package execution fa...  The step failed.Any comments would be appreciated - thank you.</description><pubDate>Mon, 07 Jan 2013 09:59:30 GMT</pubDate><dc:creator>jralston88</dc:creator></item></channel></rss>