dure to put the affected database in single-user mode: 1> use master 2> go 1> sp_dboption database_name, single, true 2> go 1> use database_name 2> go 1> checkpoint 2> go 2.Check the value of the "indid on extent" in the error message to determine whether it is a table (value is 0) or an index (value is greater than 0). 3.Run dbcc tablealloc or dbcc indexalloc, depending on whether the object named in the 2540 error message is a table or an index. Then execute the appropriate command. Before you run the appropriate command, keep the following in mind: - dbcc tablealloc corrects either a table or an index, but if the problem is on an index, you can avoid affecting the entire table by using dbcc indexalloc. If you need to minimize the amount of time the table is unavailable, it may be most practical to use dbcc indexalloc. - These commands correct the error only when run in the full or optimized mode, with the fix option specified, because the default value is nofix on system tables. - You can use the "object name" or "object id on extent" in the commands above where the argument object_name appears.Use the command appropriate for your situation: For Tables (index id in extent = 0) For Indexes (0 < index id in extent < 255) 1> dbcc tablealloc (object_name, 2> full, fix) 3> go 1> dbcc indexalloc (object_name, 2> indid_on_extent, full, fix) 3> go 4.Turn off single-user mode in the database: - If the database is master, refer to "Returning SQL Server to Multiuser Mode". - If the database is not master, use the following procedure: 1> use master 2> go 1> sp_dboption database_name, single, false 2> go 1> use database_name 2> go 1> checkpoint 2> go Refer to "dbcc" in the SQL Server Reference Manual and "Checking Database Consistency" in the System Administration Guide for information about dbcc tablealloc and dbcc indexalloc. Releases in Which This Error Is Raised 11.0 and later