Appendix C. Implementing Spatial Search Using SQL Server

The MapPoint Web Service provides a comprehensive set of find nearby (proximity search) APIs and custom data storage hosted in a secure environment on Microsoft servers. This setting works seamlessly for most business needs. However, while the MapPoint Web Service proximity search solution is effective for most scenarios, in some circumstances, implementing proximity searches independent of MapPoint Web Service may be necessary. There are three scenarios that might lead you to want to store and query your points of interest data locally within your enterprise network:

Sensitive or confidential information

If your data is sensitive, such as information about crimes, for example, you may not want to upload the data to MapPoint Web Service.

Frequent changes

If your data changes frequently, such as sales information that is updated in real-time, it may not be practical to upload your data to MapPoint Web Service continually.

Large datasets

If you have a database containing millions of locations, you must store and manage it in a local Microsoft SQL Server database. MapPoint Web Service allows you to upload up to approximately 100,000 points of interest.

This section describes how to implement simple proximity searches locally within your enterprise using a SQL Server.

Tip

This appendix assumes that you have a basic understanding of SQL Server, Stored Procedures, and ADO.NET.

Understanding Proximity Search

Proximity search works by applying ...

Get Programming MapPoint in .NET now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.