The latest live version is 188.8.131.52
Note: We have dropped support for SQL 2005 in newer versions, and plan to drop support for SQL 2008 in the near future. For using SSIS with SQL Server 2019, you need mSQL 2.3.6 or newer. Please see Adding Data Tools/Integration Services to Visual Studio 2019.
Note: mSQL now has a new default install path. If upgrading from an older version, the old install path will be used. If you do a fresh install the new install path will be used. If you have existing mSQL installs we suggest changing the new install path to be consistent with your original path to ensure any packages transition to the new version.
Previous Live Versions:
For clients utilizing NCOA - ensure you're using 184.108.40.206 - and when setting up an NCOA task - under advanced - ensure that the Upload Protocol is set to FTPS for any new or existing tasks.
For Clients licensed for additional datasets such as Canadian Addressing or Geocoding, or if you incorporate custom fields into your overlap matching keys and don't use the addressing, you should use 220.127.116.11 and instead should use the install manager to download data updates on a bi-monthly basis.
You would also grab the local API installer for the addressing datasets via the instructions here:
For clients with CASS data, on a bi-monthly basis you will need to run the Install manager to update the data and copy from the machine you downloaded to any other machines using the data. For clients with standard verify/geocoding data you only need to run it once a year, but we still suggest running it on a quarterly basis.
We suggest arranging a call with support to go through the install, feel free to submit a request to arrange a call.
For step-by-step instructions on mSQL installation, go to this article:
Installing mSQL (With Screenshots)
*When installing mSQL for the first time you will be prompted for the activation code included in your new client activation email.
For info on upgrading packages to a newer version of SQL Server go to this article:
Upgrading an SSIS package to a newer version of SQL Server: