While I have mentioned SQL from time to time, it has usually been in reference to a specific issue. Today I am I am going to talk about some of the things to keep in mind if you are performing a new SQL install for a new Infor CRM SLX server. While I am no SQL guru, I have installed it quite a few times, and am familiar with the SQL options needed to get Infor CRM SLX to work properly.
Most folks using older versions of Infor CRM SLX (8.3 and earlier) generally use SQL 2012 or 2014, while folks on more current versions (8.4 and later) generally use SQL 2016 or 2019. Check the compatibility matrix at Support.Infor.com to verify precising which versions of SQL will work with you version of CRM. Unless you have some reason to use an older version of SQL, I would suggest using the most recent version that is compatible. Note that if your database is small enough (comfortably less that 10GB), you could get by with SQL Express, which is free. Any larger, and you will need the full licensed version of SQL.
When you actually run the SQL install, choose a new stand-alone installation, and then Agree and Next through several screens. You will eventually get the screen where you are choosing what features to install. The only features that are required by CRM are the SQL Engine and Replication. You are free to add any other desired features, and you will definitely want to include the Management Console if some version of it is not already installed. The next screen will ask you to name the SQL instance. If this will be the only version of SQL on the server, you can just leave this at the default. If you are installing multiple versions of SQL, I would suggest naming the instance after its version of SQL (SQL2014 in the example shown).
As the next step in the install, you will be asked to select the authentication mode and set the password for the SA account. You will need to choose mixed authentication mode, as that mode is required to set up the sysdba account CRM uses. Feel free to add whatever other users you need to administrate SQL, but these will not affect CRM. Then click Install and let the install run.
Now that SQL has been installed, you need to log in and create the sysdba user. Log in to your new SQL instance, expand Security, and right click on Logins. Choose New Login, and a window will pop up allowing you to create the sysdba login. Give it that username, the password of your choice, and uncheck Enforce Password Policy (to make sure it does not expire). Click OK to create that login, and your SQL instance ready to be set up with a CRM database. (Note: do not give sysdba any additional server roles beyond the default Public role. Giving it any other roles will cause issues with CRM’s database connection.)