This is the first in a series of tutorials presenting the steps necessary to install and configure a new database to work with Microvellum.
We recommend the procedure below to install SQL Server 2017 Express. This will install the database software and create a named instance of the database so it is ready to be configured for use it in a network environment by Microvellum. Use this procedure as the first step in setting up an environment supporting the Unified Work Order Database.
In preparation for the installation, if using Windows 10, press the Windows key on your keyboard and enter “User Account” in the search box. Click on "Change User Account Control Settings" and set the slider to "Notify me only when apps try to make changes to my computer". This is an acceptable combination of security and ease of use.
1.) Download SQL Server 2017 Express at the page accessed by clicking here.
a. - Save the file to a known location on your local computer or network.
2.) Right click on the downloaded file and select "Properties". Check the checkbox for "Unblock" at the bottom if is available. Click OK.
3.) Again, right click on the downloaded file and select “Run as administrator”.
4.) Click “Yes” on the User Account Control box that asks if you want to allow the app to make changes to your device.
5.) The installation file will initialize and subsequently display the installation type dialog box. Select the Custom installation.
6.) Select where to download the files. Accept the default location, or Browse to different file path. Click “Install” to continue. The installation files will now download. This may take some time depending on your internet connection.
7.) Once the install package has been downloaded and the necessary files for installation have been initialized, the “SQL Server Installation Center” box will be displayed. Click “New SQL Server stand-alone installation…”
NOTE: You do not need to install SQL Server Reporting Services (SSRS) unless you will be creating reports outside of Microvellum.
8.) Read the Microsoft License Terms. If acceptable, check the checkbox to accept the license terms to continue the installation. Click Next.
9.) The install configuration will run a check to make sure that SQL Server is ready to be installed. Here are a couple of items to confirm before proceeding.
a. - Do not run the SQL Server installation on the same computer or server that is also a domain controller.
b. - If Windows Firewall is enabled you will need to set an exception for ports 1433-1434.
c. - General information about configuring firewalls may be found by clicking here.
d. - More specific information may be found by clicking here.
10.) Install Rules: make sure either all the rules pass successfully, or that any warnings are recognized and acted upon as necessary. The firewall may not have a status of Passed, but if you have configured the ports for firewall as described in the articles above, click Next.
11.) Feature Selection: accept the default settings and click Next.
Instance Configuration: name the instance of SQL Server that you are installing. If you don’t have a preference otherwise, leave it as is and click Next.
13.) Server Configuration: set the SQL Server Browser Startup Type property to “Automatic” if not already set to that value.
NOTE: Occasionally, installations will fail. If this happens, you may need to change the SQL Server Database Engine's account name to NT AUTHORITY\NETWORK SERVICE
14.) Database Engine Configuration: set the Authentication Mode to “Mixed Mode” and specify the System Administrator account (sa). Enter and make a note of the password in a secure location.
15.) Install necessary prerequisites.
a. - Microsoft R Open: click Accept and then Next.
b. - Python: click Accept and then Next.
16.) The SQL install program now uses the configuration settings you have given it and installs the software. Depending on your system, this could take up to 30 minutes.
17.) Now that you have SQL Server 2017 Express installed, the next step is to configure it for use with Microvellum. Click here for the next article in the series.
(modify the link in #17 when the 2017 article is completed)