The error says that the minimum level to repair is repair_allow_data_loss, so why are you wasting your time trying other options? (btw, repair_fast does nothing at all in SQL 2005+)

Considering...

No

Other than that an index rebuild will update statistics, they're completely unrelated.

Fragmentation is related to the physical and logical ordering of the pages of an index within the data file

Statistics...

Don't use sysprocesses, it's deprecated, included only for backward comparability and will be removed in a future version.

Use sys.dm_exec_requests and/or sys_dm_tran_locks.

The way to 'unlock' a table is to kill the...

I can't answer the "does Dense_Rank and partition clause, will they create any time out problems" question, as you've given virtually no information.

If you're concerned about performance, please post the...

Assuming that there are values such as 1st, 2nd, 3rd, 4th and so on in there as well as the ones you've listed.

Use REPLACE to get rid of the suffixes,...

http://www.sqlservercentral.com/blogs/glennberry/archive/2009/10/29/suggested-max-memory-settings-for-sql-server-2005_2F00_2008.aspx

Once you've prevented SQL from starving the OS (which is is very capability of doing), then you can go and...

Two-year-old-thread alert.

Please run the following and post the full and complete output:

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

What's the exact version of SQL that you're running?

SELECT @@Version

Please don't cross post. It just wastes peoples time and fragments replies.

No replies to this thread please. Direct replies to: http://www.sqlservercentral.com/Forums/Topic933059-1633-1.aspx

Just be aware that the above query will perform absolutely terribly on larger row counts (and by larger I mean maybe thousands not tens of millions), as a result of...

mike mcneer (6/4/2010)

---

I thought that was my undertstanding as well. but looking at the dbcc ind command shows shared PAGEPID.

From the command DBCC IND('dbname',PCKWRK,-1)

3502852460876770817808117.20576E+16In-row data1035028533502851

From the command DBCC IND('dbname',POLDAT,-1)

5502851614949222623836117.20576E+16In-row data1055028526489528

5502852614949222623836117.20576E+16In-row...

Ack, part of the where clause was filtered out, hence that was useless. Sorry.

SELECT cp.plan_handle, cp.cacheobjtype, cp.refcounts, cp.usecounts,

...

Obviously you think that we're willing to spend hours solving your problem instead of doing...

After a purge, rebuild the clustered index of the table purged. Leave the free space within the database, SQL can and will reuse the available space in the data file

Query sys.dm_db_index_physical_stats