Great, glad that resolved it.  Autoclose on or taking the db offline were the only things I could think of that would cause that to happen.

I believe heaps do show up, just under index_id 0 rather than 1.

OK, I finally found notes on the sys view I was trying to remember:

sys.dm_db_file_space_usage

This time, that should (actually) help you determine what you need to know (you would likely need...

So sorry, obviously I didn't look closely enough.

I can't imagine the db has autoclose on or that the db is taken offline, so, yeah, that is really weird.

Take a look at sys.dm_db_index_usage_stats, it should give you what you want.

With the exception of random but evenly distributed indexes, I wouldn't use logical fragmentation to determine if an index needs to be rebuilt.  In the case mentioned, you actually...

Wrap the value in a: FLOOR, CEILING or ROUND(,0) function, depending on how you want to handle the decimal part of the value.

There's not a lot of data left in the file, so I'm rather surprised it would take that long to shrink it, since SQL wouldn't need to move that much...

The first command might not shrink the file at all, because of the "TRUNCATEONLY" option.

The second command should work, but shrinks can take a long time.

For best performance, you want to stop using NULL so you don't have to do ISNULL() as part of the WHERE.  Yes, you will have to go back...

Once you get rid of the LOWER on the vehicle type, then the clustering key could be ( VehicleType, ValidFrom, ValidUntil ).

For best performance, you want to stop using NULL so you don't have to do ISNULL() as part of the WHERE.  Yes, you will have to go back and change...

SELECT LEFT(devicename, month_in_date - 2) AS device, MAX(CAST(devicedate AS datetime)) AS max_device_date
FROM #test1
CROSS APPLY (
    SELECT PATINDEX('%[0-9]/%', devicename) AS month_in_date_prelim
) AS ca1
CROSS APPLY (
...

I think CHARINDEXes might be somewhat more efficient here:

;WITH data AS (
    SELECT rl_event_id = 'AB123456_BlahBlah_BESTSELLER_blahBlah'
)
SELECT rl_event_id, SUBSTRING(rl_event_id, pos_of_second_underscore + 1, pos_of_third_underscore - pos_of_second_underscore...

The db that table was in already had space allocated but that had not been used yet.  Therefore, SQL can allocate that space to a table without having to get...