Click here to return to FULL Migration Document Package
(for migrating program and database to new server)
Click here to return to FULL Install Document Package
(for new client program installations only)
Screenshots in this documentation are from SQL Server 2022 - Express Edition. However, as stated in our Installation and Migration outlines, we recommend using the latest recommended version of SQL.
See our System Specification for details.
The following 4 steps will be used for installing and configuring SQL for RFMS.
Step 2: SQL Configuration Manager Settings
Step 3: Windows Firewall: Open SQL Default Ports
Step 4: Install SQL Server Management Studio
IMPORTANT: Prior to beginning the installation of SQL
make certain .NET 3.5 & 4.7 are installed and enabled.
STEP 1: Install SQL Server
- Download the appropriate SQL installation file from Microsoft.
Note: We do not provide or maintain the installation files for SQL Server. For assistance with this, please reach out to Microsoft Support directly. - Run the SQL Installation file to install a new SQL instance.
- Select Custom for the installation type (this will allow you to configure SQL correctly for RFMS).
- Select, New SQL Server stand-alone installation or add features to an existing installation.
- License Terms: Review the license agreement. If you agree, select the I accept the license terms check box, and then select "Next."
Refer to the following notes for information and instructions concerning each of the relative subsequent pages.
- Global Rules: Setup will automatically advance to the Product Updates page if there are no rule errors.
- Microsoft Update: This page will only appear if the Microsoft Update check box in Control Panel > All Control Panel Items > Windows Update > Change settings isn't selected. Selecting the Microsoft Update check box changes the computer settings to include the latest updates for all Microsoft products when you scan for Windows updates. Important note concerning versions of SQL greater than SQL 2014: these versions rely more on Cumulative Updates over Service Packs. Because of this, updates are much different and will rely on your IT Professional in evaluating CU's and updating according to your environment.
- Product Updates: The latest available SQL Server product updates are displayed. If no product updates are discovered, Setup doesn't display this page and automatically advances to the Install Setup Files
- Install Setup Files: Setup provides the progress of downloading, extracting, and installing the Setup files. If an update for Setup is found and you specify to include it, that update will also be installed. If no update is found, Setup will automatically advance.
-
Install Rules: Setup checks for potential problems that might occur while running Setup. If failures occur, select an item in the Status column for more information. Otherwise, select Next.
Note: Windows Firewall settings will be addressed after SQL Installation (see Step 3).
- Installation Type: Select Perform a new installation of SQL Server.
- Azure Extension for SQL Server: Uncheck the box for Azure Extension for SQL Server, as this is not needed for a typical installation for RFMS.
Feature Selection:
- Select: Database Engine Services This is the only feature necessary. No other features listed here are necessary for SQL to run and be configured properly for RFMS. However, the technician can install as many features as the client desires.
Feature Rules:
- This page automatically advances if all rules pass.
Instance Configuration:
- Select: Named Instance and name the instance something that is easy to identify. In the following example we have kept it simple and named the instance “RFMS.”
Important: when naming the database DO NOT uses spaces - instead use underscore or hyphen, if necessary. Make sure to write down the instance name as it will be needed to configure the dbconnect.tps & dbconnect.xml file when setting up the program files. - Click “Next”
Server Configuration (be certain to review both tabs):
- Server Accounts Tab: Change the SQL Server Browser to “Automatic”
-
Collation Tab: Important: make sure collation shows SQL_Latin1_General_CP1_CI_AS
For clients installing SQL outside of the United States:
please make sure to check the correct collation and change it, if necessary.
Please Note: – there are many variations of this name, particularly on the last 3 sets of characters such as CP1_CI_AI and CP1_CS_AS – these variations are not correct. It must be SQL_Latin1_General_CP1_CI_AS or the client may get collation errors when accessing RFMS. If the collation is NOT CORRECT, change it by clicking Customize, and select the correct Collation. - Click “Next” to continue.
Database Engine Configuration:
- Authentication Mode: Select Mixed Mode (NOT Windows authentication mode).
-
Enter a password for the SA account. DO NOT SKIP THIS STEP
The SA password must be set up for RFMS connections to work properly. We suggest providing a strong password for this built-in SQL Server system administrator account. This password from here on is referred to as the client's "SA password."
Note: RFMS does not have access to any client passwords. Therefore, make certain to keep a record of this password and provide it to the client as it may be necessary to use it for ODBC connections at a workstation or for other SQL issues. This password is also used in the initial RFMS installation/setup. -
Specify SQL Server Administrators: click Add Current User.
Note: any other necessary admin accounts can also be added at this time. - Click, “Next”
After clicking “Next,” the installation process will begin. Please note, this process may take a while.
Complete:
- To complete the SQL Server installation process, select Close.
- Note: If prompted to restart the computer, do so now.
Step 2: SQL Configuration Manager Settings
- Open SQL Configuration Manager
- Select SQL Server Services
Note: The following log on account changes are optional as we have found them to help with server performance more often than not. However, they are not required.- Right-click SQL Server (the instance name is in parenthesis) and go to Properties.
- Change it to log on as the Built-in account “Network Service” and hit Apply.
- Right-click on SQL Server Browser, select Properties.
- Change it to log on as the Built-in account “Network Service” and hit Apply.
- Change it to log on as the Built-in account “Network Service” and hit Apply.
- Right-click SQL Server (the instance name is in parenthesis) and go to Properties.
- Expand SQL Server Network Configuration and select the Protocols for the new SQL Server Instance.
- Enable Named Pipes
- Enable TCP/IP
Note: We enable both during installation of SQL to ensure a smoother workstation setup process. However, these can be narrowed down to either TCP/IP or Named Pipes, depending on the governmental needs, if the client or technician desires a higher level of security.
Step 3: Windows Firewall: Open SQL Default Ports
Note: You will be opening ports 1433 for TCP, and ports 1433 and 1434 for UDP
- Open Control Panel > Windows Firewall > Advanced Settings
- Select Inbound Rules > New Rule (right side of the screen)
- Select “Port,” then click “Next"
- Select “TCP” and for Specific Local Ports enter 1433, then click “Next”
- Make sure Allow the Connection is selected, then click "Next"
- Make sure Domain, Private and Public are selected, then click "Next"
- Name the rule, then click “Finish”
- Repeat the above steps for UDP, but enter ports 1433,1434 (instead of just 1433)
Please note: Generally, SQL uses port 1433 for connections (TCP ) and port 1434 for management connections (TCP/UDP). Historically these ports were installed as static, but current SQL installations appear to be installing them as dynamic. However, each SQL Environment is unique and this occurs during the installation or setup of SQL depending on the environment, please review as necessary. For times that SQL is using ports different from ports 1433 and 1434, we recommend using tools like NetStat to determine which ports are being used and address them accordingly.
A final note about firewalls:
Please do not mistake these firewall settings for being the absolute only firewall ports that need to be opened. Firewall configurations can be more complex than they appear due to the overlapping nature in which firewall ports are assigned at a hardware level for physical firewalls, and the software level for operating system and software firewalls. That also does not mean it is not worth the trouble to ensure your firewalls are configured appropriately; the safety of your data is always worth the trouble.
In light of recent cyber-attacks and malware waves such as CryptoWall and CryptoLocker, we strongly recommend taking the necessary time to use programs such as NetStat to diagnose what ports need to be open. Simply turning off the firewall on a Server without other proper external protection could be very dangerous.
Step 4: Install SQL Server Management Studio (SSMS)
- Download the installation file for SQL Server Management Studio from Microsoft.
At the time of writing this article, the file can be found at the following link: - Run the downloaded installation file to install SSMS
- When complete, if prompted to restart computer, do so now.
- Before proceeding to the next document, verify you can open SQL Management Studio and connect to the Instance using the SA password created with this installation of SQL.
This completes Install and Configure SQL for RFMS
Follow this link to proceed to the next document: Backup and Migrate RFMS and Database
Comments
Article is closed for comments.