I've set myself a project of getting some geo data into SQL Server but before I get started doing any of the big jobs I wanted to see if I was on the right track.
All of my data is for the UK and is therefore based on Easting & Northing coordinates (OSGB36), not Latitude & Longitude (WGS84).
My understanding is that I cannot create a geography field based on Eastings & Northings in SQL Server without first re-projecting in a GIS package (I have QGIS).
I can however convert Easting & Northings based data into a geometry field with no problems.
I have managed to re-project some point data to WGS84 in QGIS and create a geography field from this, however when I use the QGIS MSSQL link to bring the resulting point data into QGIS, it really doesn't seem to be able to marry it with layers in OSGB36 (despite having on-the-fly re-projection activated).
So my question is: Following the path of least resistance (and maximising compatibility with other UK datasets), is it acceptable to store OSGB36 data as geometry in SQL Server, despite actually being geography?