I'm building a view which uses a spatial intersect (STIntersect in MSSQL 2012) between points (student addresses with address information) and polygons (school boundary polygons with school numbers by grade).
The idea is another team will build a stored procedure that will take an address and get the schools and district of that location based on the school boundaries.
The question is: both the points and the polygons have a spatial index. Can or should I use the indices on both tables, or would using one be beneficial over the other?
UPDATE: Running the query twice testing the speed of using either index proved that the spatial index on the point layer was much faster... perhaps this answers my question?