All cloud-hosted EasyTerritory instances, and nearly all on-premises instances, use SQL Server to store spatial data for display. Cloud-hosted instances use SQL Azure. On-premises instances can use any version from SQL Server 2008 forward.
EasyTerritory can display point data (street addresses or latitude/longitude) directly from CRM or from spreadsheets, but any line or polygon shapes must be stored as SQL Server geometries. Point data can also be stored in SQL Server to facilitate detecting relationships between point data and area shapes such as territory polygons.
The data layers such as county and zip code boundaries which we provide to all cloud-hosted EasyTerritory instances are stored in SQL Azure.
Every EasyTerritory Enterprise edition cloud-hosted customer gets their own 1 GB SQL Azure database. This database is for storing spatial information related to your CRM records as well as your territory boundaries. EasyTerritory.com offers segregated databases to maximize security and performance for each customer.
IMPORTANT NOTE: One security measure Microsoft uses for SQL Azure is to only allow configured IP addresses to access a SQL Azure instance. In order for you to have access to your SQL Azure database with MapDotNet UX Studio, SQL Server Management Studio or the Azure Portal, you’ll need to provide your EasyTerritory.com support person an IP address or address range so they may configure it for you.
Enterprise customers, cloud-hosted or on-premises, may also wish to integrate with Microsoft Dynamics CRM. EasyTerritory has several useful features for this, including:
- View CRM Advanced Find results in an EasyTerritory map
- Export data from CRM into SQL Server
- Sync changes in CRM to a related SQL Server table
- Push territories from EasyTerritory to both SQL and CRM while detecting contained point features
Next Step: Read the following article on Connecting to SQL Server with MapDotNet UX Studio to learn how to use Studio to map a SQL Server layer to export point data from CRM into SQL Server.