DBCC Updateusage

DBCC Updateusage

Post by Bill Brag » Tue, 05 May 1998 04:00:00



I'm running a DBCC Updateusage on a database with the count_rows option
set.  It starts just fine looking through indexes but when it get's to
INDID = 1 of one of my large tables, it just stops after about 50 minutes.
No error, no more tables, it just stops as if it had completed.  When I run
DBCC newalloc on this database, it comes back clean.  Any ideas?

 
 
 

DBCC Updateusage

Post by Tibor Karasz » Wed, 06 May 1998 04:00:00


Bill,

Haven't seen that... What about DBCC CHECKDB?

--

MCSE, MCSD, MCT, SQL Server MVP
Cornerstone Sweden AB


>I'm running a DBCC Updateusage on a database with the count_rows option
>set.  It starts just fine looking through indexes but when it get's to
>INDID = 1 of one of my large tables, it just stops after about 50 minutes.
>No error, no more tables, it just stops as if it had completed.  When I run
>DBCC newalloc on this database, it comes back clean.  Any ideas?


 
 
 

DBCC Updateusage

Post by Neil Pik » Wed, 06 May 1998 04:00:00


Bill,

 Weird - does it run ok without the countrows?

 Neil Pike MVP/MCSE
 Protech Computing Ltd

 
 
 

1. dbcc updateusage question

Shawn,

This all depends on the activity of your database.

I run the following :

1.   dbcc updateusage once a week.  This reports and checks the sysindexes
table.  Updating space usage counters used by the sp_spaceused system
stored procedure. This command corrects any clustered indexes on user and
system tables
If you are running this against syslogs then you will have to place the
database in single user mode.
2.  dbcc checkcatalog once a week to check the consistency of my system
tables
3.  dbcc newalloc once a week to check the consistency of my data and index
pages against the extents
4.  dbcc checkdb once a night to check all my table and index pages are
correct and in the right sort order.
5.  dbcc dbreindex once a night on all indexes as they become fragmented
quite badly due to the number of transactions and the current index setup
(will be looking at this though)
6.  sp_recompile on tables that have just had the dbreindex so that all
procs and triggers are recopiled the next timer they are run (to take
advantage of the possible index changes)

I hope this was of use to you

--
Steve Robinson MCP (SQL /NT)


2. in852.com - 4

3. dbcc updateusage vrs update stats ?

4. Isql for X?

5. Difference between UPDATE STATISTICS and DBCC UPDATEUSAGE

6. SQL Server Evaluation Problem

7. DBCC UPDATEUSAGE Failing

8. FPD2.6 under WIN95 - print to file

9. DBCC Updateusage(0) reports failure in log?

10. dbcc updateusage vrs update stats ?

11. dbcc updateusage fails

12. DBREINDEX & UPDATEUSAGE Hangs up