Circling back to this. Sure, it's years later, but this may help someone.

This was caused by inconsistent SQL drivers. Because of a minor OS difference, I had to use different drivers, and they had inconsistent behavior on calculated, unnamed columns. Updating the driver fixed it.