I have one table, address points, in my enterprise geodatabase that when queried non the points geometry have an STSrid. Its all 0s. The featureclass behaves normally in maps but its distressing to know something is wrong with the geometry on the back end. I'm using SQL native geometry for storage in a 2008R2 SQL Server. The GDB is 10.3.1. Any ideas? I can do an update on the geometry objects and set Shape.STSrid = 2238 but I dont want to break the geodatabase. I expect this could be a bottleneck with speed. Only this table returns 0 for all the records. Every other feature class is 2238.