Need to move SQL Server 2005 Table storing Lat;Lng as varchar to Spatial ?
I have read some articles about using spatial optimized tables. Actually I use stored latitude and longitude as varchar comma-separated (lat;lng). Could you suggest the best way to perform this change and enumerate the advantages. It's really necessary for a large project or only move to SQL Server 2008? thanks. ...