was googling for ways to find the duration of a db restore and found this OLD post...

if you have your errorlog from the time the db was last restored...

I did a quick comparison against a few other databases (of varying sizes) with the same table/index definitions and found similar results..

short term, I'll just exclude this from the...

Final update of the day from me... my brain hurts and im going home...

I just did a Alter Index ALL on this table to see what came of it...

Index_id...

The highlighted index is the one we're dealing with...

and I'm not above making stupid mistakes... in fact, I usually dont recognize them as such untill I post here or ask...

I added 20gb to the data file, and immediately ran the rebuild.

same, 94.1932% avg_fragmentation_in_percent...

might this have anything to do with the datatypes of the index columns?

also, my first post had...

Doh, there we go... attachments!

scroll bar is my friend :w00t:

There was 10gb free in the data file. I was thinking in that direction myself.

219k pages @ 8k/page = 1,752,000 kb = 1.7gb... I just added a few...

its a link to my dropbox, but understand your hesitation. dont have another place handy to stick that image at the moment, so sorry...

I DO NOT have auto-shrink enabled....

for giggles, I rebuilt with a 50% fill factor:

avg_fragmentation_in_percent changed to 94.691...

Fragment_count up to 380190

avg_fragment_size_in_pages a touch over 1.03

and page_count is up (as expected) to 394577

DECLARE @db_id SMALLINT;

DECLARE @object_id INT;

SET @db_id = DB_ID(N'dbName');

SET @object_id = OBJECT_ID(N'tableName');

IF @object_id IS NULL

BEGIN;

PRINT N'Invalid object';

END;

ELSE

BEGIN;

SELECT * FROM sys.dm_db_index_physical_stats(@db_id, @object_id, 11,...

over 218k

thanks for confirming what I thought I knew but was questioning 😉

kd11 (1/16/2013)

---

We currently have a job which backs up the database daily using sqlcmd (along with some parm i.e. @databases, @backuptype, @directory etc). Is it possible where...

silly possibility, make sure the user SQL Agent runs under has access to the database it queries.

that was my problem, found it using the @append output option.

my Sysadmin colleague in the next desk over said "just reboot it" in (sorta) jest.

I insisted this couldnt possibly be something a reboot would fix, and fought/googled/profiled, and screwed with...