Installing mSQL (With Screenshots)

1. Download the installer
If you're a client, feel free to contact the support team for a link to the latest live version, if you want to evaluate the software, please reach out to us by requesting a demo

 

2. Make sure you close SSMS/BIDS/SSDT before starting the install

Run the .exe you downloaded, click next

 

3. Accept the terms, click next

 

 

4. Enter the activation code you received from our accounts team, or your account manager if you've requested a demo and talked to them about your requirements.

 

 

5. Choose your Region (we suggest United States in most cases)




6. Choose your install path

You can change install directory here now if needed, if you need to change it later you need to uninstall/reinstall

If you install on a test/QA machine as well as production, we highly recommend you keep paths consistent across environments. It's common for enterprise DBA's to want to install mSQL to a separate data drive separate from the OS. So make sure your Test/QA environments also have a separate data drive partition of the same name if that's the case, otherwise you'll get errors when moving packages across machines unless you edit certain paths before.

 

 

7. Choose your data folder

Again, if you are installing on a test/QA machine as well as production, we highly recommend you keep paths consistent across environments.

 

 

8. Choose whether to enable a web server, this is for the web UI that you can use to configure XML configuration files.

If this is a production server, we suggest choosing Disable.
If it’s a test/dev/qa machine you can install it but if you don't have IIS it will launch setup to add an IIS to your machine, you set the password here for the UI.
If you're planning on using SSIS only, we also suggest Disable.



 

9. If you purchased the 360 US Addressing module you will see this below, if you didn't purchase US addressing then skip to the next step.

 Important: make sure to click to install addressing components!

 

 

If you trialed mSQL without addressing, you'll need to rerun the installer and check this box.

  

10. Reporting

We suggest disabling on a production machine to reduce unneeded overhead

although if you need the CASS reports or other reports – you can enable, or reinstall later and enable

 

 

11. Check For Updates

We suggest disabling on all machines to reduce unneeded overhead

 

 

12. Choose Components - leave as is – and just click install

 

 

let it run through the install, near the end you'll have another window pop up

 

13. mSQL Configurator

*If you don't have a local SQL instance, just cancel out, the configurator does not work with remote instances. (although mSQL can with SSIS)
*If you don't want us creating databases with demo data and an assembly and stored procedures on your local instance, just cancel out, there are scripts available that you can do this after install as well, but then you need to remember to drop/recreate the assembly/SP's every time you reinstall or upgrade.


Otherwise, depending on what option you choose, it will try to import example data into a matchIT_SQL_demo database, It will create a separate matchIT_SQL database to house the assembly and stored procedures, or both.

If you're not sure, then we suggest choosing the 3rd option (both).

A. If you choose the first option, it will only make the matchIT_SQL database to house the assembly and stored procedures, depending on how locked down your permissions are it's normally easiest to just put in the SA user and use SQL authentication if you have that available, otherwise windows authentication is fine for most standard users.  You simply choose the local instance, click connect and create, then exit out of the configurator.

 

 

B. If you choose the second option, it will only try to import the demo data into a matchIT_SQL_demo database, windows authentication is normally fine for that. Again just choose your instance, click connect, and import, then exit out of the configurator.

 

C. If you choose the third option (both), then depending on how locked down your permissions are it's normally easiest to just put in the SA user and use SQL authentication if you have that available, otherwise windows authentication is fine for most standard users.   Again just choose your instance, click connect, create, and import, then exit out of the configurator.

 

14. At the end – you can choose whether or not to view the readme - 

Or you can always access them from the start menu later (acrobat reader is required) 

 

 

15. If you don't have 360Science US Addressing, you're done continue to the next article here

For clients with the 360Science US Addressing module:
As a note, addressing will not work out of the box, please follow the steps under option one in this article after installing mSQL 



Permissions changes required to run 360Science US Addressing:

Option 1: Allow it to work with both local and remote instances by setting the matchIT SQL Service to run as a domain level user

Change the matchIT SQL Service to run as a domain user instead of the computer’s Local Service account.  Then create a login for this account within the SQL Server instance.  Lastly, for each database within the SQL Server instance that the address correction will need access to, create a user for the login and give it the ‘db_datareader’, ‘db_datawriter’, and ‘db_ddladmin’ database roles.

The matchIT SQL Service can be configured from a command console as follows:

cd /d “C:\Program Files\mSQL\bin”
matchITSQL /stop /uninstallmatchITSQL /install:

matchITSQL /install:domain\username:password /start

If you are uninstalling then reinstalling the software or installing elsewhere, the matchIT SQL service will be recreated using the default Local Service account.  So you would need to rerun the above steps after each reinstallation or upgrade (a batch script, in a secure folder, could be created for this).

If you're upgrading, when installation starts, we simply stop the service, we don’t delete it.  When installation ends, we then restart the service.  It’ll use the credentials it was last configured for, it won’t revert to the default Local Service account.  You simply would run the full installer and it will update files with the newer version; only one version of mSQL can exist on a machine at a time.

 

Option 2: Only works with local instances

Additional configuration steps must be performed before the addressing stored procedure can be used (the following steps show how to configure addressing with the example database, matchIT_SQL_demo).

Firstly, the built-in Local Service account must be given write access to the database.  This is because the address correction actually occurs outside the stored procedure; it is run under the context of the matchIT SQL Service which, by default, uses the Local Service account (a low-privilege Windows service account).

Secondly, the account must be given the following roles for the matchIT_SQL_demo database: db_datareader, db_datawriter, and db_ddladmin.  Alternatively, the account can be given the db_owner role instead of these three roles.

Here are the steps that should be run in the Management Studio:

USE [master]
GO
CREATE LOGIN [LocalService] FROM WINDOWS
GO
USE [matchIT_SQL_demo]
GO
CREATE USER [LocalService] WITH DEFAULT_SCHEMA=dbo
EXEC sp_addrolemember ‘db_datareader’, ‘LocalService’
EXEC sp_addrolemember ‘db_datawriter’, ‘LocalService’
EXEC sp_addrolemember ‘db_ddladmin’, ‘LocalService’

If the matchIT SQL service isn’t running as the Local Service account (as per the above recommendations), use the account name (i.e. domain\username) in place of LocalService.