Installing Sage CRM is usually straightforward, but many installation issues come down to a small number of SQL Server prerequisites that are easy to miss, especially if you have not done a CRM install for a while.
This article walks through a simple, practical checklist to prepare Microsoft SQL Server Standard, Enterprise, or Express for a Sage CRM installation.
This guidance does not apply to Azure SQL Database, which has a different authentication and connectivity model. It is intended for on-premise or VM based SQL Server deployments.
Before you start
This article assumes:
-
You are installing Sage CRM on Windows
-
SQL Server is Standard, Enterprise, or Express
-
SQL Server may be on the same machine or a separate database server
-
You have administrative access to SQL Server
Step 1: Enable Mixed Mode authentication
Sage CRM uses SQL authentication during installation, which means Mixed Mode authentication must be enabled.
-
Open SQL Server Management Studio (SSMS)
-
Right-click your SQL Server instance and select Properties
-
Select the Security page
-
Under Server authentication, choose
SQL Server and Windows Authentication mode -
Click OK
Important:
You must restart the SQL Server service for this change to take effect.
Step 2: Enable and configure the sa account
The sa (System Administrator) account is often disabled by default. Sage CRM Setup requires it.
-
In SSMS, expand Security > Logins
-
Right-click sa and choose Properties
-
On the Status page, set Login to Enabled
-
Make sure also to set Permission to Connect to Database to Grant.
- On the General page, set a strong password
Tip:
Avoid starting the sa password with a special character such as @ or !. Some older Sage CRM versions had difficulty parsing connection strings when passwords began with special characters.
Step 3: Enable TCP/IP and set a fixed SQL port
Sage CRM always connects to SQL Server using TCP/IP, even if both are installed on the same machine.
-
Open SQL Server Configuration Manager
-
Expand SQL Server Network Configuration
-
Select Protocols for [YourInstanceName]
-
Right-click TCP/IP and choose Enable
-
Double-click TCP/IP and open the IP Addresses tab
-
Scroll to IPAll at the bottom:
-
Clear TCP Dynamic Ports so it is blank
-
Set TCP Port to 1433
-
-
Restart the SQL Server service using Configuration Manager
If you are unsure which port your SQL Server instance is currently using, see this Sage Community Hub article:
https://communityhub.sage.com/sage-global-solutions/sage-crm/b/sage-crm-hints-tips-and-tricks/posts/how-can-i-find-out-the-port-number-being-used-by-my-instance-of-ms-sql-server-express
Step 4: Confirm database level requirements
Before running Sage CRM Setup, check the following.
Case insensitive collation
Sage CRM requires a case insensitive collation.
For example:
SQL_Latin1_General_CP1_CI_AS
Sage CRM will not function on a case sensitive database.
SQL Server Browser service
If you are connecting to:
-
A named SQL instance, or
-
SQL Server on another machine
Then ensure the SQL Server Browser service is running in Windows Services.
Required driver on the Sage CRM application server
Sage CRM explicitly requires:
Microsoft OLE DB Driver for SQL Server v18 or later
Important points:
-
It must be installed locally on the Sage CRM application server
-
It is not guaranteed to be installed by SSMS
-
It must be installed separately
-
Newer versions such as v19 are fully supported
This driver is required for:
-
Sage CRM Setup
-
Upgrades and patches
-
Day to day runtime database connectivity
Summary checklist
Before running Sage CRM Setup, confirm:
-
Mixed Mode authentication is enabled
-
The sa account is enabled with a strong password
-
TCP/IP is enabled for SQL Server
-
SQL Server is listening on a known port
-
The database collation is case-insensitive
-
SQL Server Browser is running if needed
-
Microsoft OLE DB Driver for SQL Server v18 or later is installed on the CRM application server
Taking a few minutes to verify these steps can save a lot of time during installation and troubleshooting.