Jacob Wilkins (12/16/2016)I'm sure this will just fall in line with all the other numbers, but since I don't see it posted in the thread yet, when you run DBCC...

Jacob Wilkins (12/16/2016)

So those results show just under 11 GB reserved, 5ish GB data, 5ish GB index with only 192 MB unused.

Could you post the results of this query...

sgmunson (12/16/2016)

It's a given that the following might be a serious PITA, but it might be worth it if the space recovery is critical.

1.) Script the database and ALL of...

Jeffrey Williams 3188 (12/16/2016)

---

How did you determine that only 11GB of space is in use? I have seen this kind of issue with one or more tables where LOB...

ADDITIONIAL INFORMATION:

Thought I'd put this in the initial post, but it's not there.

I watched the DBCC SHRINKFILE process running (via sp_who), and noted this:

The first time I run it (after...

Steve Jones - SSC Editor (12/16/2016)

---

Weird. I'd think that you should be able. No matter what the spacing of the objects in the file.

Maybe try a reindex that might...

Unfortunately, example B on the DBCC SHRINKFILE man page won't help much, since that shrinks the transaction log, and my problem is shrinking the data file.

Recovery setting is FULL (it's still production data for a couple of weeks).

Lowell (7/1/2014)

---

a bit of research on my side seems to tell me this DMV can help: sys.database_recovery_status :

if the database in question is in this resultset, it does not have...

Michael L John (6/30/2014)

---

Uh, no. Setting the recovery from full to simple and doing a log backup are not related.

The point of performing a log backup is to...

So, an update. We did get the server restarted over the weekend. In fact, we also got a disk drive replaced and the OS rebuilt. One supposes...

I'm pretty sure that I've already got any fix from SQL 2005 SP2 CU6 (released on 2008-02-18) in my SQL 2008 SP2 (released 2010-09-24). Thanks anyway...

Our regular job recycled the error log last night; the output in the previous message was generated 5 minutes ago.

The SQL Server log just shows this:

[font="Courier New"]DBCC CHECKDB (master) WITH...

The full and complete output of [font="Courier New"]DBCC CHECKDB('master') WITH all_errormsgs, no_infomsgs[/font] is, excitingly enough:

Msg 0, Level 11, State 0, Line 0

A severe error occurred on the current command. ...

Several things:

1) Confirm the recovery model and backup scheme for you database is appropriate. Are...