Why would a SQL Server 2008 R2 database disable a table index when upgraded to SQL Server 2012
This has to do with any table which contains a geospatial field. I'm not sure why yet (is it a bug or a feature lol), but that's the cause.

Update: the problem only appears when there is a geospatial field and a PERSISTED column that uses it.