|Previous Article||matchIT SQL Index||Next Article|
1) Get the installer.
If you're a client, you can log in and download the latest version of matchIT SQL here, if you would like 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 Kingdom 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 matchIT SQL 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) If you are planning on using Stored Procedures then you will need to choose 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 none.
If it’s a test/dev/qa machine – we suggest Cassini (the default), if you choose IIS because it's already installed on that server, you will need to make more permissions changes after install. read more on that here.
if you're planning on using SSIS only, we also suggest none.
*note Cassini will be removed from the installer based on client feedback wanting to allow a more secure web server, so going forward it will be IIS or nothing.
9) If you purchased the addressIT module you will see this below, if you didn't purchase addressIT then skip to the next step.
Important: make sure to click to install addressing components!
If you trialed matchIT SQL without addressing, you'll need to rerun the installer and check this box.
If you are installing the addressIT module then please refer to the additional addressing instructions under step 15.
You can enable the output of reports here which can be output in a number of different formats, if you choose to disable, you will have to reinstall and to enable reporting at a later date
11) Check For Updates
Here you can enable or disable automatic notification of matchIT SQL updates when they are released. If you enable this then a scheduled task is created and a message box will be displayed notifying you when an update is available. Please note this this will not update matchIT SQL automatically, it simply lets you know when an update is available on our website and it is up to you when to upgrade.
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) matchIT SQL Configurator
*If you don't have a local SQL instance, just cancel out, the configurator does not work with remote instances. (although matchIT SQL 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) If you don't have addressIT, you're done and you can continue to the next article
For clients with the addressIT module:
During the Installing phase of matchIT SQL, the installer will stop and ask you to place additional licensing files in a folder before it can continue (please contact our support department at firstname.lastname@example.org if you have not already been supplied with these)
Once you have placed these files in the correct location, click OK. If you do not have these licence files then you can click OK and addressing data will be downloaded but the addressing functionality will not work until these licences are in place and the Capscan Pool Manager service has been started.
Click Begin on the screen below
Once the data has downloaded, click on Close
at the end – you can choose whether or not to view quick start guide and readme -
or you can always access them from the start menu later (acrobat reader is required)
As a note, addressing will not work out of the box, please follow the steps under option one in this article after installing matchIT SQL
Permissions changes required to run addressIT:
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\matchIT SQL\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 matchIT SQL 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:
CREATE LOGIN [LocalService] FROM WINDOWS
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.
|Previous Article||matchIT SQL Index||Next Article|