Tag Info

New answers tagged

0

Try running this first, and selecting it into a temp table: INSERT INTO #TempProbChild Select * FROM ProblemChild WITH (INDEX(IDX_geog)) WHERE Geog.Filter(@geog) = 1) Then on that subset, run your .STIntersects. Select count(*) FROM #TempProbChild WHERE Geog.STIntersects(@geog) = 1) I've found that on very large datasets (hundreds of millions of rows ...


1

You are correct in your interpretation of a SRID. It identifies the projection used to locate the Geometry or Geography. Even if the database in question (I'm assuming SQL Server) doesn't make use of the SRID directly, the point of it is to identify how to work with the coordinates in relationship to others. I suppose you could look at it like having a ...



Top 50 recent answers are included