why would you create a table with a single column? And name that column like sequence_number? Seems a bit dumb; I'd probably just create a freakin' sequence if that's what I wanted. smfh.
@jadarnel27 no. They wanted to know if there is a way to have SQL Server identify missing indexes. Of course, I'm pointing them at sys.dm_db_missing_indexes DMVs, but I wasn't expecting there to be a missing freaking CX like that. It's very slightly possible that they intended to do that, but if that's the case, I'm going to be absolutely amazed.
we've got about 2500 databases, and I can probably count on one hand the number of multi-column indexes with an include statement.
I just ran the query from my blog post against a single SQL Server instance that shows over 500 heaps across multiple databases. A great many have non-clustered primary keys; something stinks in Denmark.
I mean, I do get that sometimes it helps to not have a clustered primary key, but jeez, that looks like a lot.