# Geocoding from SQL Server Data

**URL:** <https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225>\
**Category:** Geocoding\
**Created:** [August 5, 2010, 6:02am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225 "2010-08-05T06:02:22Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [August 5, 2010, 6:02am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/1 "2010-08-05T06:02:22Z")

</div>

I&nbsp;am&nbsp;researching&nbsp;the&nbsp;use&nbsp;of&nbsp;Map&nbsp;Suite&nbsp;Geocoder&nbsp;for&nbsp;the&nbsp;new&nbsp;version&nbsp;of&nbsp;our&nbsp;application.&nbsp;&nbsp;The&nbsp;old&nbsp;version&nbsp;used&nbsp;ESRI's&nbsp;Map&nbsp;Objects,&nbsp;which&nbsp;has&nbsp;been&nbsp;unsupported&nbsp;for&nbsp;some&nbsp;time.

Our&nbsp;application&nbsp;will&nbsp;have&nbsp;all&nbsp;of&nbsp;its&nbsp;data&nbsp;in&nbsp;SQL&nbsp;Server.&nbsp;&nbsp;I&nbsp;haven't&nbsp;seen&nbsp;any&nbsp;mention&nbsp;in&nbsp;the&nbsp;documentation&nbsp;or&nbsp;forums&nbsp;about&nbsp;using&nbsp;SQL&nbsp;Server&nbsp;data&nbsp;for&nbsp;geocoding.&nbsp;We&nbsp;have&nbsp;had&nbsp;issues&nbsp;with&nbsp;people&nbsp;opening&nbsp;and&nbsp;possibly&nbsp;modifying&nbsp;standalone&nbsp;files,&nbsp;so&nbsp;we're&nbsp;working&nbsp;to&nbsp;keep&nbsp;everything&nbsp;possible&nbsp;inside&nbsp;a&nbsp;password-protected&nbsp;SQL&nbsp;Server&nbsp;database.

Can&nbsp;we&nbsp;use&nbsp;SQL&nbsp;Server&nbsp;with&nbsp;this&nbsp;product?

Thanks,

Allen&nbsp;Huber

---

<div class="post-metadata">

**Author:** ![David](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/aeb1de/32.png) [@David](https://community.thinkgeo.com/u/David)\
**Post date:** [August 5, 2010, 6:13am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/2 "2010-08-05T06:13:59Z")

</div>

Allen,&nbsp;  
&nbsp;&nbsp;  
&nbsp;&nbsp;&nbsp;At&nbsp;the&nbsp;moment&nbsp;we&nbsp;do&nbsp;not&nbsp;support&nbsp;SQL&nbsp;Server&nbsp;with&nbsp;our&nbsp;Geocoder&nbsp;4.0&nbsp;as&nbsp;we&nbsp;have&nbsp;our&nbsp;custom,&nbsp;high&nbsp;performance,&nbsp;file&nbsp;format.&nbsp;&nbsp;We&nbsp;could&nbsp;however&nbsp;possibly&nbsp;support&nbsp;encryption&nbsp;of&nbsp;the&nbsp;files&nbsp;if&nbsp;you&nbsp;are&nbsp;concerned&nbsp;about&nbsp;user&nbsp;tampering.&nbsp;&nbsp;We&nbsp;could&nbsp;also&nbsp;do&nbsp;some&nbsp;research&nbsp;about&nbsp;supporting&nbsp;SQL&nbsp;Server,&nbsp;do&nbsp;you&nbsp;have&nbsp;a&nbsp;layout&nbsp;of&nbsp;your&nbsp;data,&nbsp;would&nbsp;it&nbsp;be&nbsp;possible&nbsp;to&nbsp;post&nbsp;the&nbsp;schema&nbsp;of&nbsp;it?&nbsp;&nbsp;What&nbsp;makes&nbsp;me&nbsp;curious&nbsp;is&nbsp;that&nbsp;we&nbsp;did&nbsp;have&nbsp;a&nbsp;SQL&nbsp;based&nbsp;version&nbsp;with&nbsp;our&nbsp;Map&nbsp;Suite&nbsp;2.0&nbsp;platform&nbsp;and&nbsp;we&nbsp;may&nbsp;be&nbsp;able&nbsp;to&nbsp;bring&nbsp;that&nbsp;forward&nbsp;with&nbsp;some&nbsp;tweaks.&nbsp;&nbsp;The&nbsp;class&nbsp;structure&nbsp;for&nbsp;our&nbsp;4.0&nbsp;Geocoder&nbsp;is&nbsp;well&nbsp;designed&nbsp;and&nbsp;very&nbsp;flexible.&nbsp;&nbsp;We&nbsp;could&nbsp;leverage&nbsp;most&nbsp;of&nbsp;the&nbsp;core&nbsp;classes&nbsp;and&nbsp;just&nbsp;plug&nbsp;in&nbsp;the&nbsp;SQL&nbsp;part.&nbsp;&nbsp;If&nbsp;you&nbsp;are&nbsp;interested&nbsp;in&nbsp;any&nbsp;of&nbsp;this&nbsp;please&nbsp;let&nbsp;me&nbsp;know.&nbsp;  
&nbsp;&nbsp;  
&nbsp;David

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [August 6, 2010, 7:34am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/3 "2010-08-06T07:34:42Z")

</div>

David,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;for&nbsp;the&nbsp;response.&nbsp;&nbsp;I&nbsp;discussed&nbsp;this&nbsp;with&nbsp;my&nbsp;manager&nbsp;yesterday,&nbsp;and&nbsp;he&nbsp;said&nbsp;that&nbsp;if&nbsp;there&nbsp;was&nbsp;interest&nbsp;in&nbsp;supporting&nbsp;SQL&nbsp;Server&nbsp;on&nbsp;Think&nbsp;Geo’s&nbsp;part&nbsp;that&nbsp;we&nbsp;would&nbsp;be&nbsp;willing&nbsp;to&nbsp;get&nbsp;involved.&nbsp;He’s&nbsp;on&nbsp;vacation&nbsp;next&nbsp;week,&nbsp;so&nbsp;I&nbsp;can&nbsp;more&nbsp;or&nbsp;less&nbsp;go&nbsp;in&nbsp;whatever&nbsp;direction&nbsp;things&nbsp;take&nbsp;me&nbsp;if&nbsp;we&nbsp;want&nbsp;to&nbsp;discuss&nbsp;this&nbsp;further.&nbsp;&nbsp;At&nbsp;the&nbsp;moment&nbsp;we&nbsp;have&nbsp;a&nbsp;SQL&nbsp;Server&nbsp;table&nbsp;(“roads”)&nbsp;which&nbsp;I&nbsp;believe&nbsp;has&nbsp;all&nbsp;of&nbsp;the&nbsp;stuff&nbsp;needed&nbsp;for&nbsp;the&nbsp;geocoding,&nbsp;since&nbsp;this&nbsp;is&nbsp;the&nbsp;same&nbsp;data&nbsp;we&nbsp;use&nbsp;in&nbsp;the&nbsp;current&nbsp;version&nbsp;of&nbsp;our&nbsp;product&nbsp;using&nbsp;Map&nbsp;Objects&nbsp;to&nbsp;geocode.&nbsp;&nbsp;It&nbsp;has&nbsp;the&nbsp;prefix,&nbsp;name,&nbsp;type,&nbsp;left/right&nbsp;from/&nbsp;to&nbsp;fields,&nbsp;etc.&nbsp;&nbsp;The&nbsp;only&nbsp;big&nbsp;difference&nbsp;is&nbsp;that&nbsp;the&nbsp;actual&nbsp;shape&nbsp;is&nbsp;now&nbsp;stored&nbsp;in&nbsp;a&nbsp;SQL&nbsp;Server&nbsp;geometry&nbsp;field;&nbsp;everything&nbsp;that&nbsp;is&nbsp;in&nbsp;shapefiles&nbsp;in&nbsp;our&nbsp;current&nbsp;application&nbsp;will&nbsp;be&nbsp;in&nbsp;SQL&nbsp;Server&nbsp;Express&nbsp;in&nbsp;the&nbsp;new&nbsp;version&nbsp;using&nbsp;the&nbsp;geometry&nbsp;data&nbsp;type.&nbsp;&nbsp;(Our&nbsp;application&nbsp;has&nbsp;a&nbsp;map&nbsp;and&nbsp;the&nbsp;roads&nbsp;in&nbsp;this&nbsp;table&nbsp;are&nbsp;displayed&nbsp;on&nbsp;it,&nbsp;and&nbsp;the&nbsp;data&nbsp;is&nbsp;used&nbsp;for&nbsp;address&nbsp;lookup&nbsp;functions&nbsp;as&nbsp;well.)&nbsp;&nbsp;&nbsp;I&nbsp;think&nbsp;it&nbsp;would&nbsp;be&nbsp;great&nbsp;to&nbsp;have&nbsp;whatever&nbsp;data&nbsp;your&nbsp;geocoder&nbsp;requires&nbsp;to&nbsp;be&nbsp;right&nbsp;in&nbsp;SQL&nbsp;Server&nbsp;under&nbsp;SQL&nbsp;login&nbsp;authority,&nbsp;and&nbsp;with&nbsp;the&nbsp;performance&nbsp;that&nbsp;can&nbsp;be&nbsp;obtained&nbsp;from&nbsp;a&nbsp;high-performance&nbsp;DB&nbsp;such&nbsp;as&nbsp;this,&nbsp;I&nbsp;would&nbsp;imagine&nbsp;with&nbsp;the&nbsp;proper&nbsp;use&nbsp;of&nbsp;indexing,&nbsp;etc.,&nbsp;it&nbsp;should&nbsp;perform&nbsp;acceptably.&nbsp;&nbsp;I&nbsp;look&nbsp;forward&nbsp;to&nbsp;hear&nbsp;what&nbsp;you&nbsp;think&nbsp;about&nbsp;all&nbsp;of&nbsp;this.&nbsp;&nbsp;If&nbsp;the&nbsp;desire&nbsp;is&nbsp;there&nbsp;to&nbsp;pursue&nbsp;this,&nbsp;I’m&nbsp;here&nbsp;to&nbsp;help.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![David](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/aeb1de/32.png) [@David](https://community.thinkgeo.com/u/David)\
**Post date:** [August 13, 2010, 1:19am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/4 "2010-08-13T01:19:24Z")

</div>

Allen,&nbsp;  
&nbsp;&nbsp;  
&nbsp;&nbsp;&nbsp;We&nbsp;are&nbsp;still&nbsp;looking&nbsp;into&nbsp;this.&nbsp;&nbsp;I&nbsp;should&nbsp;know&nbsp;more&nbsp;early&nbsp;next&nbsp;week.&nbsp;&nbsp;Sorry&nbsp;for&nbsp;the&nbsp;delays&nbsp;but&nbsp;things&nbsp;are&nbsp;busy&nbsp;here.&nbsp;  
&nbsp;&nbsp;  
&nbsp;David

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [August 14, 2010, 8:31pm UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/5 "2010-08-14T20:31:37Z")

</div>

David,&nbsp;  
&nbsp;&nbsp;  
&nbsp;No&nbsp;problem…I’ve&nbsp;been&nbsp;keeping&nbsp;busy&nbsp;with&nbsp;some&nbsp;production&nbsp;coding,&nbsp;a&nbsp;bunch&nbsp;of&nbsp;research,&nbsp;and&nbsp;some&nbsp;experimenting&nbsp;on&nbsp;what&nbsp;I&nbsp;found&nbsp;after&nbsp;doing&nbsp;that&nbsp;research.&nbsp;&nbsp;I&nbsp;look&nbsp;forward&nbsp;to&nbsp;hearing&nbsp;from&nbsp;you&nbsp;sometime&nbsp;next&nbsp;week.&nbsp;&nbsp;I&nbsp;don’t&nbsp;know&nbsp;if&nbsp;anyone&nbsp;else&nbsp;is&nbsp;interested&nbsp;in&nbsp;this&nbsp;and&nbsp;would&nbsp;like&nbsp;to&nbsp;follow&nbsp;it,&nbsp;but&nbsp;if&nbsp;you&nbsp;ever&nbsp;feel&nbsp;it’s&nbsp;time&nbsp;to&nbsp;move&nbsp;this&nbsp;off&nbsp;the&nbsp;forum,&nbsp;just&nbsp;let&nbsp;me&nbsp;know.&nbsp;&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![David](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/aeb1de/32.png) [@David](https://community.thinkgeo.com/u/David)\
**Post date:** [August 16, 2010, 11:43pm UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/6 "2010-08-16T23:43:35Z")

</div>

Allen,&nbsp;  
&nbsp;&nbsp;  
&nbsp;&nbsp;&nbsp;Sounds&nbsp;good.&nbsp;  
&nbsp;&nbsp;  
&nbsp;David

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [August 31, 2010, 9:07am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/7 "2010-08-31T09:07:27Z")

</div>

Anything&nbsp;new&nbsp;on&nbsp;this,&nbsp;David?&nbsp;&nbsp;We’re&nbsp;actually&nbsp;discussing&nbsp;a&nbsp;need&nbsp;for&nbsp;this&nbsp;sometime&nbsp;in&nbsp;the&nbsp;not-so-distant&nbsp;future.&nbsp;&nbsp;It&nbsp;would&nbsp;be&nbsp;a&nbsp;shame&nbsp;to&nbsp;have&nbsp;to&nbsp;look&nbsp;somewhere&nbsp;else.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![Ben](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/ben/32/25720_2.png) [@Ben](https://community.thinkgeo.com/u/Ben)\
**Post date:** [September 6, 2010, 8:18am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/8 "2010-09-06T08:18:31Z")

</div>

Allen,&nbsp;  
&nbsp;&nbsp;  
&nbsp;We&nbsp;are&nbsp;working&nbsp;on&nbsp;this.&nbsp;I&nbsp;think&nbsp;we&nbsp;can&nbsp;give&nbsp;you&nbsp;something&nbsp;tomorrow&nbsp;and&nbsp;please&nbsp;have&nbsp;a&nbsp;try&nbsp;then.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Ben

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [September 6, 2010, 3:06pm UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/9 "2010-09-06T15:06:42Z")

</div>

OK,&nbsp;Ben…I’ll&nbsp;try&nbsp;to&nbsp;keep&nbsp;a&nbsp;closer&nbsp;watch&nbsp;here&nbsp;on&nbsp;the&nbsp;forum&nbsp;to&nbsp;see&nbsp;what’s&nbsp;happening.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![Ben](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/ben/32/25720_2.png) [@Ben](https://community.thinkgeo.com/u/Ben)\
**Post date:** [September 7, 2010, 3:28am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/10 "2010-09-07T03:28:38Z")

</div>

Allen,

We&nbsp;have&nbsp;integrated&nbsp;StreetSQLServerMatchingPlugin&nbsp;to&nbsp;the&nbsp;latest&nbsp;Geocoder&nbsp;(4.0.126),&nbsp;the&nbsp;autobuild&nbsp;process&nbsp;is&nbsp;running&nbsp;and&nbsp;it&nbsp;might&nbsp;be&nbsp;available&nbsp;to&nbsp;download&nbsp;in&nbsp;a&nbsp;couple&nbsp;hours,&nbsp;please&nbsp;have&nbsp;a&nbsp;try&nbsp;then&nbsp;with&nbsp;the&nbsp;attached&nbsp;test&nbsp;sample.&nbsp;From&nbsp;the&nbsp;sample&nbsp;code&nbsp;you&nbsp;can&nbsp;find&nbsp;it&nbsp;very&nbsp;straightforward,&nbsp;you&nbsp;need&nbsp;to&nbsp;input&nbsp;3&nbsp;parts&nbsp;of&nbsp;data,&nbsp;1st,&nbsp;the&nbsp;connection&nbsp;string&nbsp;and&nbsp;table&nbsp;name&nbsp;for&nbsp;initialization;&nbsp;2nd&nbsp;the&nbsp;column&nbsp;names&nbsp;for&nbsp;searching&nbsp;within,&nbsp;(streetColumnName,&nbsp;LeftFromAddressColumnName,&nbsp;etc)&nbsp;and&nbsp;3rd,&nbsp;the&nbsp;addresses&nbsp;for&nbsp;searching.&nbsp;Let&nbsp;us&nbsp;know&nbsp;if&nbsp;you&nbsp;have&nbsp;any&nbsp;issues&nbsp;about&nbsp;it.

 ![](https://community.thinkgeo.com/uploads/default/original/2X/e/ed57358245eddfabf4e047a4f0c8cea6dc217df1.png)  
Thanks,  
Ben  
  
[SQLQueryMatchingPluginSample.zip](https://community.thinkgeo.com/uploads/default/original/2X/5/56907434e8fa30d6a3a6cca5844198e37d1b118f.zip) (15.4 KB)

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [September 7, 2010, 1:13pm UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/11 "2010-09-07T13:13:54Z")

</div>

That’s&nbsp;great&nbsp;news,&nbsp;Ben…I’m&nbsp;wrapping&nbsp;things&nbsp;up&nbsp;for&nbsp;the&nbsp;day&nbsp;but&nbsp;I’ll&nbsp;be&nbsp;sure&nbsp;to&nbsp;check&nbsp;first&nbsp;thing&nbsp;tomorrow&nbsp;(Wednesday)&nbsp;morning.&nbsp;&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![Ben](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/ben/32/25720_2.png) [@Ben](https://community.thinkgeo.com/u/Ben)\
**Post date:** [September 8, 2010, 3:10am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/12 "2010-09-08T03:10:12Z")

</div>

No&nbsp;problem.&nbsp;Just&nbsp;let&nbsp;us&nbsp;know&nbsp;what&nbsp;you&nbsp;find&nbsp;out.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Ben

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [September 15, 2010, 5:36am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/13 "2010-09-15T05:36:36Z")

</div>

Ben,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Sorry…I’ve&nbsp;been&nbsp;swamped&nbsp;with&nbsp;things&nbsp;to&nbsp;do&nbsp;for&nbsp;about&nbsp;a&nbsp;week&nbsp;and&nbsp;didn’t&nbsp;get&nbsp;to&nbsp;this&nbsp;yet,&nbsp;but&nbsp;it&nbsp;is&nbsp;slowly&nbsp;rising&nbsp;closer&nbsp;to&nbsp;the&nbsp;top&nbsp;of&nbsp;my&nbsp;list.&nbsp;&nbsp;We’re&nbsp;all&nbsp;anxious&nbsp;here&nbsp;to&nbsp;give&nbsp;it&nbsp;a&nbsp;try.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![Ben](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/ben/32/25720_2.png) [@Ben](https://community.thinkgeo.com/u/Ben)\
**Post date:** [September 16, 2010, 12:50am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/14 "2010-09-16T00:50:48Z")

</div>

Allen,&nbsp;that’s&nbsp;fine.&nbsp;In&nbsp;fact,&nbsp;we&nbsp;did&nbsp;some&nbsp;updates&nbsp;even&nbsp;after&nbsp;that.&nbsp;Now&nbsp;please&nbsp;try&nbsp;the&nbsp;attached&nbsp;new&nbsp;sample&nbsp;which&nbsp;works&nbsp;with&nbsp;4.0.135&nbsp;or&nbsp;later.&nbsp;It&nbsp;is&nbsp;easier&nbsp;to&nbsp;use.

.

 ![](https://community.thinkgeo.com/uploads/default/original/2X/e/e775062f2b99aef6fac5fb93adc9c9cbf31a60d1.png)

Ben

[SQLQueryMatchingPluginSampleUpdated.zip](https://community.thinkgeo.com/uploads/default/original/2X/3/3b982100b1c766910bce454da4ed1d0bbe9438bc.zip) (14.6 KB)

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [September 21, 2010, 9:46am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/15 "2010-09-21T09:46:09Z")

</div>

Ben,&nbsp;  
  
  
  
I&nbsp;just&nbsp;wanted&nbsp;to&nbsp;let&nbsp;you&nbsp;(and&nbsp;anyone&nbsp;else&nbsp;watching)&nbsp;that&nbsp;I&nbsp;finally&nbsp;got&nbsp;around&nbsp;to&nbsp;downloading&nbsp;this&nbsp;stuff.&nbsp;Initially&nbsp;it&nbsp;didn't&nbsp;work,&nbsp;but&nbsp;then&nbsp;I&nbsp;realized&nbsp;the&nbsp;version&nbsp;of&nbsp;the&nbsp;actual&nbsp;geocoder&nbsp;release&nbsp;was&nbsp;BEFORE&nbsp;we&nbsp;started&nbsp;talking&nbsp;about&nbsp;adding&nbsp;SQL&nbsp;Server.&nbsp;So&nbsp;I&nbsp;snagged&nbsp;the&nbsp;latest&nbsp;nightly&nbsp;build's&nbsp;DLL&nbsp;and&nbsp;it's&nbsp;working.&nbsp;I'm&nbsp;modifying&nbsp;the&nbsp;sample&nbsp;a&nbsp;little&nbsp;to&nbsp;make&nbsp;it&nbsp;easier&nbsp;for&nbsp;someone&nbsp;to&nbsp;do&nbsp;testing,&nbsp;but&nbsp;I&nbsp;pointed&nbsp;it&nbsp;to&nbsp;a&nbsp;table&nbsp;of&nbsp;ours&nbsp;and&nbsp;it's&nbsp;working.&nbsp;We&nbsp;generally&nbsp;geocode&nbsp;by&nbsp;municipality&nbsp;code&nbsp;rather&nbsp;than&nbsp;zip&nbsp;code,&nbsp;so&nbsp;I&nbsp;had&nbsp;to&nbsp;change&nbsp;a&nbsp;few&nbsp;of&nbsp;the&nbsp;column&nbsp;names&nbsp;from&nbsp;"ZIP"&nbsp;to&nbsp;our&nbsp;more&nbsp;generic&nbsp;"ZONE"&nbsp;but&nbsp;other&nbsp;than&nbsp;that&nbsp;and&nbsp;changing&nbsp;the&nbsp;connection&nbsp;string&nbsp;(it&nbsp;appears&nbsp;Windows&nbsp;authority&nbsp;doesn't&nbsp;work,&nbsp;but&nbsp;we&nbsp;have&nbsp;a&nbsp;SQL&nbsp;login&nbsp;in&nbsp;the&nbsp;database&nbsp;already&nbsp;anyway)&nbsp;but&nbsp;beyond&nbsp;those&nbsp;little&nbsp;tweaks,&nbsp;the&nbsp;demo&nbsp;was&nbsp;working&nbsp;AOK.&nbsp;  
  
  
  
Here's&nbsp;a&nbsp;question&nbsp;for&nbsp;you.&nbsp;For&nbsp;our&nbsp;immediate&nbsp;need,&nbsp;we&nbsp;know&nbsp;ahead&nbsp;of&nbsp;time&nbsp;what&nbsp;muni&nbsp;(or&nbsp;munis)&nbsp;we&nbsp;are&nbsp;looking&nbsp;for.&nbsp;Is&nbsp;there&nbsp;a&nbsp;way&nbsp;to&nbsp;tell&nbsp;it&nbsp;only&nbsp;to&nbsp;look&nbsp;for&nbsp;certain&nbsp;codes?&nbsp;I&nbsp;think&nbsp;MapObjects&nbsp;used&nbsp;to&nbsp;allow&nbsp;defining&nbsp;a&nbsp;specific&nbsp;code&nbsp;rather&nbsp;than&nbsp;pointing&nbsp;to&nbsp;the&nbsp;columns&nbsp;in&nbsp;the&nbsp;data.&nbsp;Right&nbsp;now&nbsp;I&nbsp;modified&nbsp;the&nbsp;example&nbsp;to&nbsp;filter&nbsp;out&nbsp;unwanted&nbsp;matches,&nbsp;but&nbsp;it&nbsp;would&nbsp;probably&nbsp;be&nbsp;more&nbsp;efficient&nbsp;not&nbsp;to&nbsp;even&nbsp;look&nbsp;at&nbsp;those&nbsp;records&nbsp;right&nbsp;from&nbsp;the&nbsp;start.&nbsp;(In&nbsp;reality&nbsp;we&nbsp;could&nbsp;probably&nbsp;implement&nbsp;a&nbsp;view&nbsp;or&nbsp;something&nbsp;like&nbsp;that.)&nbsp;  
  
  
  
Hopefully&nbsp;I&nbsp;can&nbsp;get&nbsp;someone&nbsp;from&nbsp;the&nbsp;office&nbsp;who&nbsp;is&nbsp;more&nbsp;familiar&nbsp;with&nbsp;the&nbsp;address&nbsp;input&nbsp;formatting&nbsp;to&nbsp;do&nbsp;some&nbsp;in-depth&nbsp;testing.&nbsp;I'll&nbsp;continue&nbsp;to&nbsp;report&nbsp;back.&nbsp;  
  
  
  
Thanks!&nbsp;  
  
Allen

---

<div class="post-metadata">

**Author:** ![Ben](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/ben/32/25720_2.png) [@Ben](https://community.thinkgeo.com/u/Ben)\
**Post date:** [September 27, 2010, 3:42am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/16 "2010-09-27T03:42:03Z")

</div>

Allen,&nbsp;  
&nbsp;&nbsp;  
&nbsp;That’s&nbsp;great&nbsp;finally&nbsp;the&nbsp;sample&nbsp;works&nbsp;on&nbsp;your&nbsp;machine.&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;Just&nbsp;want&nbsp;to&nbsp;make&nbsp;things&nbsp;clear.&nbsp;So&nbsp;there&nbsp;are&nbsp;some&nbsp;ColumnNames&nbsp;in&nbsp;streetSqlMatchingPlugin,&nbsp;only&nbsp;StreetColumnName&nbsp;is&nbsp;required&nbsp;and&nbsp;the&nbsp;others&nbsp;are&nbsp;optional,&nbsp;which&nbsp;means&nbsp;just&nbsp;setting&nbsp;them&nbsp;to&nbsp;null&nbsp;or&nbsp;string.Empty,&nbsp;those&nbsp;columns&nbsp;will&nbsp;then&nbsp;be&nbsp;skipped&nbsp;internally&nbsp;while&nbsp;searching&nbsp;and&nbsp;it&nbsp;will&nbsp;not&nbsp;bring&nbsp;any&nbsp;performance&nbsp;penalty&nbsp;in&nbsp;this&nbsp;part.&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;The&nbsp;searching&nbsp;result&nbsp;includes&nbsp;all&nbsp;the&nbsp;columns&nbsp;of&nbsp;the&nbsp;hit&nbsp;record,&nbsp;is&nbsp;that&nbsp;where&nbsp;you&nbsp;were&nbsp;concerning&nbsp;that&nbsp;we&nbsp;only&nbsp;need&nbsp;to&nbsp;return&nbsp;the&nbsp;columns&nbsp;we&nbsp;want&nbsp;instead&nbsp;of&nbsp;all&nbsp;the&nbsp;columns&nbsp;in&nbsp;the&nbsp;database?&nbsp;I&nbsp;think&nbsp;that&nbsp;makes&nbsp;sense&nbsp;and&nbsp;I&nbsp;will&nbsp;talk&nbsp;with&nbsp;our&nbsp;Tech&nbsp;Director&nbsp;about&nbsp;this&nbsp;and&nbsp;see&nbsp;if/when&nbsp;we&nbsp;can&nbsp;implement&nbsp;this&nbsp;feature.&nbsp;&nbsp;Thanks&nbsp;for&nbsp;the&nbsp;suggestion.&nbsp;As&nbsp;you&nbsp;said,&nbsp;for&nbsp;the&nbsp;current&nbsp;version&nbsp;you&nbsp;can&nbsp;use&nbsp;a&nbsp;view&nbsp;or&nbsp;something&nbsp;like&nbsp;that.&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Ben&nbsp;

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [September 29, 2010, 9:32am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/17 "2010-09-29T09:32:26Z")

</div>

Hi&nbsp;Ben,&nbsp;  
&nbsp;&nbsp;  
&nbsp;I’ve&nbsp;done&nbsp;a&nbsp;little&nbsp;more&nbsp;testing&nbsp;and&nbsp;for&nbsp;certain&nbsp;addresses&nbsp;I’m&nbsp;not&nbsp;getting&nbsp;the&nbsp;correct&nbsp;result&nbsp;or&nbsp;I’m&nbsp;doing&nbsp;something&nbsp;wrong&nbsp;in&nbsp;the&nbsp;plugin&nbsp;setup.&nbsp;&nbsp;Our&nbsp;address&nbsp;here&nbsp;is&nbsp;313&nbsp;W&nbsp;Liberty&nbsp;St.&nbsp;&nbsp;There&nbsp;are&nbsp;two&nbsp;results&nbsp;for&nbsp;Liberty&nbsp;St.,&nbsp;but&nbsp;not&nbsp;the&nbsp;right&nbsp;ones:&nbsp;the&nbsp;results&nbsp;are&nbsp;in&nbsp;a&nbsp;different&nbsp;part&nbsp;of&nbsp;the&nbsp;county.&nbsp;&nbsp;The&nbsp;address&nbsp;313&nbsp;&nbsp;matches&nbsp;the&nbsp;range,&nbsp;but&nbsp;the&nbsp;results&nbsp;are&nbsp;for&nbsp;Liberty&nbsp;St.,&nbsp;not&nbsp;W&nbsp;Liberty&nbsp;St.&nbsp;&nbsp;It&nbsp;appears&nbsp;to&nbsp;be&nbsp;ignoring&nbsp;the&nbsp;“W”&nbsp;part.&nbsp;&nbsp;We&nbsp;have&nbsp;the&nbsp;direction&nbsp;in&nbsp;STREET\_DIR,&nbsp;but&nbsp;I&nbsp;don’t&nbsp;see&nbsp;a&nbsp;place&nbsp;to&nbsp;assign&nbsp;this&nbsp;to&nbsp;the&nbsp;plugin.&nbsp;&nbsp;I&nbsp;tried&nbsp;the&nbsp;prefix&nbsp;column&nbsp;and&nbsp;it&nbsp;didn’t&nbsp;seem&nbsp;to&nbsp;change&nbsp;anything.&nbsp;&nbsp;When&nbsp;I&nbsp;use&nbsp;my&nbsp;home&nbsp;address,&nbsp;which&nbsp;doesn’t&nbsp;have&nbsp;a&nbsp;direction,&nbsp;it’s&nbsp;the&nbsp;first&nbsp;match&nbsp;that&nbsp;comes&nbsp;up.&nbsp;&nbsp;This&nbsp;is&nbsp;important&nbsp;of&nbsp;course,&nbsp;since&nbsp;there&nbsp;is&nbsp;data&nbsp;with&nbsp;address&nbsp;313&nbsp;for&nbsp;both&nbsp;E.&nbsp;Liberty&nbsp;and&nbsp;W.&nbsp;Liberty&nbsp;street.&nbsp;&nbsp;Any&nbsp;thoughts&nbsp;as&nbsp;to&nbsp;what&nbsp;could&nbsp;be&nbsp;causing&nbsp;this?&nbsp;  
&nbsp;&nbsp;  
&nbsp;Also,&nbsp;I&nbsp;noticed&nbsp;when&nbsp;I&nbsp;put&nbsp;in&nbsp;my&nbsp;home&nbsp;address,&nbsp;401&nbsp;Eden&nbsp;Rd,&nbsp;it&nbsp;works,&nbsp;but&nbsp;when&nbsp;I&nbsp;put&nbsp;in&nbsp;401&nbsp;Eden&nbsp;Road,&nbsp;it&nbsp;finds&nbsp;no&nbsp;matches.&nbsp;&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;To&nbsp;answer&nbsp;your&nbsp;question…no,&nbsp;that&nbsp;isn’t&nbsp;what&nbsp;I&nbsp;was&nbsp;asking&nbsp;about.&nbsp;&nbsp;The&nbsp;data&nbsp;I’m&nbsp;using&nbsp;at&nbsp;the&nbsp;moment&nbsp;(and&nbsp;this&nbsp;is&nbsp;typical&nbsp;for&nbsp;our&nbsp;application)&nbsp;is&nbsp;for&nbsp;all&nbsp;of&nbsp;Lancaster&nbsp;County,&nbsp;PA,&nbsp;because&nbsp;this&nbsp;is&nbsp;what&nbsp;the&nbsp;application&nbsp;map&nbsp;shows.&nbsp;&nbsp;But&nbsp;when&nbsp;we&nbsp;try&nbsp;to&nbsp;geocode&nbsp;an&nbsp;address,&nbsp;we&nbsp;know&nbsp;it’s&nbsp;for&nbsp;a&nbsp;certain&nbsp;municipality–in&nbsp;the&nbsp;application&nbsp;the&nbsp;user&nbsp;selects&nbsp;the&nbsp;municipality&nbsp;of&nbsp;interest–say&nbsp;the&nbsp;city&nbsp;of&nbsp;Lancaster,&nbsp;as&nbsp;opposed&nbsp;to&nbsp;something&nbsp;like&nbsp;East&nbsp;Earl&nbsp;Township&nbsp;which&nbsp;is&nbsp;on&nbsp;the&nbsp;east&nbsp;side&nbsp;of&nbsp;the&nbsp;county.&nbsp;&nbsp;It&nbsp;think&nbsp;it&nbsp;would&nbsp;be&nbsp;nice&nbsp;to&nbsp;tell&nbsp;the&nbsp;geocoder&nbsp;up&nbsp;front&nbsp;which&nbsp;municipalities&nbsp;to&nbsp;check&nbsp;to&nbsp;avoid&nbsp;unneeded&nbsp;matches&nbsp;outside&nbsp;the&nbsp;municipality&nbsp;the&nbsp;user&nbsp;is&nbsp;working&nbsp;with.&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;hope&nbsp;to&nbsp;get&nbsp;this&nbsp;“W&nbsp;Liberty”&nbsp;issue&nbsp;resolved&nbsp;and&nbsp;let&nbsp;the&nbsp;boss&nbsp;test&nbsp;it.&nbsp;&nbsp;He’s&nbsp;the&nbsp;one&nbsp;that&nbsp;makes&nbsp;the&nbsp;decisions&nbsp;and&nbsp;pays&nbsp;for&nbsp;stuff&nbsp;like&nbsp;this.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks,&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![ThinkGeo](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/thinkgeo/32/25029_2.png) [@ThinkGeo](https://community.thinkgeo.com/u/ThinkGeo)\
**Post date:** [October 12, 2010, 1:18am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/18 "2010-10-12T01:18:38Z")

</div>

&nbsp;Allen,  
  
  
  
I&nbsp;really&nbsp;cannot&nbsp;reproduce&nbsp;your&nbsp;problem&nbsp;on&nbsp;my&nbsp;local&nbsp;machine&nbsp;correctly,&nbsp;I&nbsp;used&nbsp;the&nbsp;TigerData&nbsp;2009&nbsp;as&nbsp;the&nbsp;data&nbsp;source&nbsp;in&nbsp;the&nbsp;SQL&nbsp;Server&nbsp;2005,&nbsp;currently,&nbsp;we&nbsp;have&nbsp;added&nbsp;the&nbsp;ability&nbsp;for&nbsp;matching&nbsp;the&nbsp;PrefixDirection&nbsp;and&nbsp;SuffixDirection&nbsp;fields,&nbsp;&nbsp;before&nbsp;you&nbsp;start&nbsp;to&nbsp;match&nbsp;the&nbsp;street&nbsp;address,&nbsp;you&nbsp;should&nbsp;set&nbsp;the&nbsp;PrefixDirection&nbsp;column&nbsp;name&nbsp;or&nbsp;SuffixDirection&nbsp;column&nbsp;name,&nbsp;we&nbsp;have&nbsp;exposed&nbsp;the&nbsp;API&nbsp;to&nbsp;set&nbsp;them,&nbsp;please&nbsp;see&nbsp;the&nbsp;code&nbsp;below:

&nbsp;

`geocoder = new Geocoder();            StreetSQLServerMatchingPlugin streetSqlMatchingPlugin = new StreetSQLServerMatchingPlugin(txtSQLConStr.Text);            streetSqlMatchingPlugin.TableName = txtTableName.Text;            streetSqlMatchingPlugin.StreetColumnName = "fullname";            streetSqlMatchingPlugin.LeftFromAddressColumnName = "lfromadd";            streetSqlMatchingPlugin.RightFromAddressColumnName = "rfromadd";            streetSqlMatchingPlugin.LeftToAddressColumnName = "ltoadd";            streetSqlMatchingPlugin.RightToAddressColumnName = "rtoadd";            streetSqlMatchingPlugin.PrefixColumnName = "PrefixDirection";            streetSqlMatchingPlugin.SuffixColumnName = "SuffixDirection";            streetSqlMatchingPlugin.StreetTypeColumnName = "StreetType";            streetSqlMatchingPlugin.LeftZipColumnName = "zip";            streetSqlMatchingPlugin.RightZipColumnName = "zip";            geocoder.MatchingPlugIns.Add(streetSqlMatchingPlugin);`&nbsp;&nbsp;Please&nbsp;use&nbsp;the&nbsp;code&nbsp;above&nbsp;to&nbsp;try&nbsp;again&nbsp;and&nbsp;if&nbsp;there&nbsp;are&nbsp;still&nbsp;have&nbsp;any&nbsp;problems&nbsp;can&nbsp;you&nbsp;give&nbsp;us&nbsp;a&nbsp;part&nbsp;test&nbsp;data&nbsp;of&nbsp;your&nbsp;database&nbsp;so&nbsp;that&nbsp;we&nbsp;can&nbsp;deal&nbsp;with&nbsp;it&nbsp;better,&nbsp;&nbsp;

Thanks,&nbsp;&nbsp;

Scott,

---

<div class="post-metadata">

**Author:** ![Allen](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/a/bbce88/32.png) [@Allen](https://community.thinkgeo.com/u/Allen)\
**Post date:** [October 12, 2010, 7:24am UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/19 "2010-10-12T07:24:49Z")

</div>

Hi&nbsp;Scott…&nbsp;  
&nbsp;&nbsp;  
&nbsp;Sure,&nbsp;I’ll&nbsp;give&nbsp;it&nbsp;another&nbsp;try.&nbsp;&nbsp;If&nbsp;it&nbsp;still&nbsp;doesn’t&nbsp;work,&nbsp;I&nbsp;can&nbsp;extract&nbsp;a&nbsp;small&nbsp;number&nbsp;of&nbsp;representative&nbsp;records&nbsp;from&nbsp;the&nbsp;table&nbsp;into&nbsp;a&nbsp;script.&nbsp;&nbsp;What’s&nbsp;the&nbsp;best&nbsp;way&nbsp;to&nbsp;get&nbsp;that&nbsp;data&nbsp;to&nbsp;you?&nbsp;&nbsp;I&nbsp;guess&nbsp;if&nbsp;it’s&nbsp;just&nbsp;a&nbsp;few&nbsp;lines&nbsp;of&nbsp;SQL&nbsp;script&nbsp;I&nbsp;can&nbsp;just&nbsp;paste&nbsp;it&nbsp;in&nbsp;the&nbsp;body&nbsp;of&nbsp;a&nbsp;message&nbsp;here.&nbsp;&nbsp;&nbsp;  
&nbsp;&nbsp;  
&nbsp;Allen

---

<div class="post-metadata">

**Author:** ![ThinkGeo](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/thinkgeo/32/25029_2.png) [@ThinkGeo](https://community.thinkgeo.com/u/ThinkGeo)\
**Post date:** [October 12, 2010, 9:02pm UTC](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225/20 "2010-10-12T21:02:48Z")

</div>

Allen,&nbsp;  
&nbsp;&nbsp;  
&nbsp;You&nbsp;are&nbsp;right,&nbsp;if&nbsp;you&nbsp;still&nbsp;have&nbsp;any&nbsp;troubles&nbsp;you&nbsp;just&nbsp;need&nbsp;to&nbsp;give&nbsp;us&nbsp;the&nbsp;script&nbsp;for&nbsp;your&nbsp;database&nbsp;table,&nbsp;but&nbsp;when&nbsp;you&nbsp;test&nbsp;it,&nbsp;please&nbsp;make&nbsp;sure&nbsp;the&nbsp;enter&nbsp;column&nbsp;names&nbsp;are&nbsp;correct,&nbsp;according&nbsp;to&nbsp;my&nbsp;test,&nbsp;it&nbsp;worked&nbsp;fine.&nbsp;  
&nbsp;&nbsp;  
&nbsp;If&nbsp;you&nbsp;have&nbsp;any&nbsp;questions&nbsp;please&nbsp;let&nbsp;us&nbsp;know,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Scott,

[Next page](https://community.thinkgeo.com/t/geocoding-from-sql-server-data/7225.md?page=2)