FAQ:SSIS:GeoCode Logging Advisory: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 1: Line 1:
[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
[[SSIS:Data Quality Components|← SSIS:Data Quality Components]]
{{CustomTOC}}
{{CustomTOC}}
==Reprocess Inputs Update==
;SetLatitude
:Use of SetLatitude will prevent records previously coded with GeoCoder Object from being counted towards your overall usage. By setting these properties to the values previously returned from GeoCoder Object, any records whose current values match the values set in the properties will not be counted against your total usage.
;SetLongitude
:Use of SetLongitude will prevent records previously coded with GeoCoder Object from being counted towards your overall usage. By setting these properties to the values previously returned from GeoCoder Object, any records whose current values match the values set in the properties will not be counted against your total usage.


==SSIS 6.4: GeoCode Logging Advisory==
==SSIS 6.4: GeoCode Logging Advisory==

Latest revision as of 01:08, 22 November 2017

← SSIS:Data Quality Components


Reprocess Inputs Update

SetLatitude
Use of SetLatitude will prevent records previously coded with GeoCoder Object from being counted towards your overall usage. By setting these properties to the values previously returned from GeoCoder Object, any records whose current values match the values set in the properties will not be counted against your total usage.
SetLongitude
Use of SetLongitude will prevent records previously coded with GeoCoder Object from being counted towards your overall usage. By setting these properties to the values previously returned from GeoCoder Object, any records whose current values match the values set in the properties will not be counted against your total usage.


SSIS 6.4: GeoCode Logging Advisory

2016 Q4

In order to utilize your on-premise GeoCoder, you must open up a port so you may communicate with our servers (no private data is transferred through this port – this is purely for tracking purposes). Please download this file (ftp://ftp.melissadata.com/updates/GeoLogTest.zip) and follow the steps providing below to so we may assist you faster in providing a solution to your problem. This tool is to detect whether or not our servers are able to communicate with you or not.

1. Ensure you have the following files in your C:\Program Files\Melissa DATA\DQT\Data (or equivalent) folder.

mdGeoCanada.db
mdCbsa.dat
mdCbsa.idx
mdGeo.cty
mdGeo.dat
mdGeo.idx
mdGeo.lic
mdGeo.plc
mdGeoPoint.dat
mdGeoPoint.idx

2. Unzip the Downloaded file, and move it to your desired location.

3. Select x86 or x64 bit depending on your system architecture (if unknown, select x86).

4. Double click “GeoLogTest.exe” and click OK.

5. Enter your License Key in the License Field.

6. Enter a directory for the log file to be created (Optional).

a. If you leave as-is, the log file will be created in the same directory as your GeoLogTest.exe
b. If you choose to leave it blank, a console window will pop up with your logging information.

7. Ensure your DataPath is set to the correct location (Where your Data folder is inside your Melissa Data Folder).

8. Set your postal code (Optional).

9. Set the postal codes Plus 4 (Optional).

10. Click “Lookup”.

11. Send the trace log to your Melissa Data Tech Support Representative and we will determine the solution that best fits your needs.