For some reason I had to break this down into small pieces or it never completed. The table had 7M records. It could handle a selection of 2M at a time but somewhere above 2.5M it would choke.
Is it creating a giant transaction and running out of buffer?
UPDATE dbo.location
SET geoPoint
=
geography::Point(RooftopLatitude,RooftopLongitude,
4326)
WHERE geoPoint
is
null
The following also never returns. Is there any way to break the creation of an index down into bite sized chunks SQL Azure can handle?
CREATE
SPATIAL
INDEX idxGeometryIndex
ON dbo.location
( geoPoint )
USING GEOGRAPHY_GRID
WITH (GRIDS =(LEVEL_1 = MEDIUM,LEVEL_2 = MEDIUM,LEVEL_3 = MEDIUM,LEVEL_4 = MEDIUM), CELLS_PER_OBJECT = 16,
DROP_EXISTING =
OFF)