Go to content Go to navigation and search


Current SQL Server Blog Articles

    SQL Server Spatial: STFlipVectors
    SQL Server Spatial: Extract LineStrings in GeometryCollection to create LineString
    SQL Server Spatial: Converting a LineString to COGO XML
    SQL Server Spatial: Creating (Multi)LineStrings geometries from COGO XML instructions
    New Version of Package of TSQL Spatial Functions
    Vectorize/Segmentize SQL Server 2012
    Coordinate Editing Functions for SQL Server Spatial
    Function to Scale a geometry object for SQL Server Spatial
    TSQL String Tokenizer Function for SQL Server
    geography/geometry to MBR helper functions
    generate_series for SQL Server 2008
    Extract Polygons from result of STIntersection in SQL Server Spatial
    Function to round ordinates of a SQL Server Spatial geometry object
    Extract elements of SQL Server Spatial geometry object
    Counting number of polygon rings SQL Server Spatial
    Filtering Polygon Rings in SQL Server Spatial
    Function to Move a geometry object in SQL Server Spatial
    Alternate Centroid Functions for SQL Server Spatial
    Function to Rotate geometry objects in SQL Server Spatial
    A GetVertices wrapper for DumpPoints in SQL Server 2008 Spatial
    Creating a Morton number Space Key generator for SQL Server
    Gridding a geometry or geography object (SQL Server Denali)
    On hinting spatial indexes
    Random Search Procedure (SQL Server 2008 Spatial)
    COGO: Converting (Google Earth) Formatted Longitude/Latitude points to decimal degrees (SQL Server)
    COGO: Convert Degrees, Minutes and Seconds values to Decimal Degrees
    COGO: DD2DMS Formatting a latitude/longitude decimal degree value
    COGO: Create point from bearing and distance
    COGO: Compute number of vertices required to stroke circle or circular arc
    COGO: Calculating the bearing between two points (SQL Server 2008 Spatial)
    COGO: Compute arc length subtended by angle centre of circle
    COGO: Compute chord length of segment of a circle (arc)
    COGO: Computing Arc To Chord (Arc2Chord) Separation
    COGO: Creating a stroked polygon from a circle's centre x,y and radius
    COGO: Finding centre and radius of a curve defined by three points: FindCircle function
    Identifying Tight Radius Curves sections within LineString geometry data
    Generating random point data for SQL Server 2008 Spatial
    New Presentation on Active (Searchable) Spatial Metadata for SQL Server 2008 Spatial and FreeText
    Checking is a column in a table or a view is of type geometry or geography
    Extracting geometry type string values from geometry/geography objects in SQL Server 2008 Spatial
    Vectorising geometry objects in SQL Server 2008
    MBR to geography/geometry helper functions
    Extracting geometry types from geometry/geography objects in SQL Server 2008
    Getting the number of coordinate dimensions of a geometry/geography object in SQL Server 2008
    A Dump Points Function for SQL Server 2008 Spatial
    toGeography and toGeography Conversion Functions for SQL Server 2008 Spatial
    Write text file with spatial data from SQL Server 2008
    Loading Shapefiles into Geography type column in SQL Server 2008
    Tip #6: Correcting invalid geometries
    Tip #5: Where or where has my little column gone
    Tip #4: What Coordinate System is that?
    Tip #3: What object is that?
    Tip #2: Spatial Indexing and Primary Keys
    Tip #1: SQL Server 2008 "Katmai" - Setting SRIDs



RSS / Atom

Email me


Creative Commons License
All Blog Articles, Data Models and Free Source Code by Simon Greener, The SpatialDB Advisor is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

Tip #2: Spatial Indexing and Primary Keys

Saturday November 24 2007 at 03:54

For fast and efficient search and retrieval all columns containing spatial data should have a spatial index created on them.

For Oracle an index can be created on any SDO_GEOMETRY column regardless as to whether the table has a primary key or not. This is because Oracle uses an internal, unique, ROWID pseudo-column in its indexes: the ROWID links a leaf in the spatial index to the table’s actual row on disk (in the table’s tablespace).

However, SQL Server 2008 “Katmai” requires that all tables must have a primary key before a spatial index can be constructed. The primary key can be based on one or more columns in the table with those columns being of any data type.

The table I loaded for Tip #1, TAS_LGA, can have its primary key constructed as follows:

1. Make the column that will become the primary key “NOT NULL”

alter table dbo.tas_lga alter column lga_pid char(15) not null;

2. Declaratively define the primary key on our not null column lga_pid as follows:

alter table dbo.tas_lga add constraint tas_lga_pk  primary key (lga_pid);

We are now in a position to create our spatial index. Microsoft’s spatial index requires you define the bounding box of the spatial index. For our TAS_LGA table this will be the complete extent of the data. This can be discovered as follows:

select min( a.geog.STEnvelope().STPointN(1).STX) as minx,
       min( a.geog.STEnvelope().STPointN(1).STY) as miny,
       max( a.geog.STEnvelope().STPointN(3).STX) as maxx,
       max( a.geog.STEnvelope().STPointN(3).STY) as maxy
  from gisdb.dbo.tas_lga a;
minx miny maxx maxy
143.813480017165 -43.8603741008445 148.503628803775 -39.1918359319521

Now that we know the extent of our data we can create a spatial index as follows:

CREATE SPATIAL INDEX tas_lga_geog_idx
  ON tas_lga (geog)
  WITH (
BOUNDING_BOX = ( 143, -44, 149, -39),

Creative Commons License

post this at del.icio.uspost this at Diggpost this at Technoratipost this at Redditpost this at Farkpost this at Yahoo! my webpost this at Windows Livepost this at Google Bookmarkspost this to Twitter