It seems that the Microsoft SQL Server Geography data type is better suited for lat/lon because Geography "stores ellipsoidal (round-earth) data, such as GPS latitude and longitude coordinates."
While the Geometry data type "represents data in a Euclidean (flat) coordinate system."
I have data stored in SQL Server Geometry data type column, and it is lat/lon coordinates - the SRID is EPSG:4326.
The reason being, is the data is used by Geoserver, and Geoserver only recognizes Geometry data types for SQL Server. But the data is 4326.
Is there anything wrong with doing this? Will there be accuracy or performance issue? Should/could the data be converted?