I'm not 100% sure, but I would guess that you need to (if you're the DBA) take action. I don't see SQL doing it automatically.

From BOL: "Maximum file size, in 8-KB pages"

100 MB * 1024 (KB) / 8

Hope that makes sense

Hi Steve,

You can try "select * from sys.database_files"

adoniadelavigne, for the Implementation & Maintenance exam, it's about 10 full days (according to Microsoft anyway) for the course & usually about twice that much if you're doing it part...

Thanks. The log is fine.

I have re-biult the indexes, but the filesize (of the primary file - MDF) doesn't change after shrinking.

Thanks again Cliff.

No rows returned. I don't think any objects(tables) are orphaned as I only truncate & delete data, not dropping tables. I'll pray this weekend & start afresh on...

Thanks Cliff.

Still no joy. I'm really stumped. Funny thing is this happens every time I restore this db...

No errors with DBCC Checkcatalog.

Thanks for the script Michael. It's a nice to have, but unfortunately didn't shrink it...

Appreciate the help though.

It returns the following:

DbID: 18

FileID: 1

CurrentSize: 13887128

MinimumSize: 152

UsedPages: 234824

EstimatedPages: 234528

Even though the current size reflects what it should be, the size of the file on the OS is still 110GB

Thanks, I appreciate the input. But as previously stated, truncating/shrinking the log file is not a problem. 😉

It's getting that MDF down to size...

sp_spaceused & OS correlate.

The log file is under control & is currently sitting on 100MB.

The problem is that the MDF file is sitting on 105GB, but I'd like it to...

Thanks Bessem,

There's also a report you can run from Management Studio for this info.

Unused space in my tables only add up to about 750MB (Againt a total of nearly 95GB...

Thanks for the pointers. Unfortunately it's producing the same results...

Is there anything else I can/should look at?

Thanks Mohan, will give it...