The solution turned out to be adding this to the query:

SET ANSI_DEFAULTS ON;

Apparently the gem does not account for that.

My apologies. I'm trying to execute the query using a ruby gem called tiny_tds. I've used this many times before and I haven't seen this behavior, so I assumed that...

The stats I ran against the table are in a screen shot I have available here:

The table is about 10GB and the fragmentation to me looks significant enough unless I'm...