SCCM SQL 2022 Install Guide

In the first part of this SCCM Current Branch blog series, we planned our hierarchy, prepared our Server and Active Directory.

Click the following link to see all supported SQL versions. For our post, we will install SQL 2022 locally on the same server where the Primary Site will be installed.

SCCM SQL 2022 Install Guide

• Execute Setup.exe from the SQL installation media, select New SQL server stand-alone installation

Image may be NSFW.
Clik here to view.

• Provide the product key and click Next

Image may be NSFW.
Clik here to view.

• Review and Click Next

Image may be NSFW.
Clik here to view.

• Check Use Microsoft Update to check for updates and click Next

Image may be NSFW.
Clik here to view.

• Review the list of install rules.

Image may be NSFW.
Clik here to view.

• Uncheck Azure Extension for SQL server as this feature isn’t needed for SCCM

Image may be NSFW.
Clik here to view.

• Select SQL Server Feature Installation

• Select the Database Engine feature and specify the SQL installation directory. This is the directory for the program files and shared features

Image may be NSFW.
Clik here to view.

• Select Default instance and ensure that your instance is created on the SQL Volume

Image may be NSFW.
Clik here to view.

• Set all services to run as the SQL domain account that you created previously and set the services startup type to Automatic

Image may be NSFW.
Clik here to view.

• On the Collation tab, set the Database Engine to use SQL_Latin1_General_CP1_CI_AS

Image may be NSFW.
Clik here to view.

• In the Server Configuration tab, set the authentication mode to Windows Authentication and in the SQL Server Administrators add your SCCM Admins group

Image may be NSFW.
Clik here to view.

• In the Data Directories tab set your drive letters correctly for your SQL databases, Logs, TempDB, and backup

Image may be NSFW.
Clik here to view.

• On the TempDB, complete the various information based on the Database sizing section below.

Image may be NSFW.
Clik here to view.

• With SQL 2022, it is now possible to set the minimum/maximum memory(RAM) for the installation as part of the installation.

Image may be NSFW.
Clik here to view.

• Click Install

Image may be NSFW.
Clik here to view.

• Complete the installation by clicking Close

Install SQL Server Management Studio (SSMS)

• Back in the SQL Server Installation Center, click on Install SQL Server Management tools.

Image may be NSFW.
Clik here to view.

• This will redirect you to the Download page of SQL Server Management Studio. SSMS is no longer tied to the SQL server installation in terms of version.

Image may be NSFW.
Clik here to view.

• Adjust the installation path if need, then click Install

SQL compatibility level

By default, when installing SQL 2022, the compatibility level will be at 160 for any new databases added to the instance.

At the moment, the recommended and supported level needs to be set at 150.

• Post SCCM installation, in SQL management studio, properties on the CM database.
• Under options, change the Compatibility level to SQL server 2019 (150) and hit ok.

Image may be NSFW.
Clik here to view.

For more details about SQL compatibility level with SCCM, see Microsoft learn.

Install SQL Reporting Services

• Back in the SQL Server Installation Center, click on Install SQL Reporting Services.

Image may be NSFW.
Clik here to view.

• The SQL reporting services is just like the Management console, it requires a separate download

Image may be NSFW.
Clik here to view.

• Click on Install Reporting Services

Image may be NSFW.
Clik here to view.

• Provide the Product key.
  • Tip: you can find the product key from the main SQL 2022 installer.

Image may be NSFW.
Clik here to view.

• Accept License terms

Image may be NSFW.
Clik here to view.

• Click Next

Image may be NSFW.
Clik here to view.

• Select the installation path, click Install

Image may be NSFW.
Clik here to view.

• Click Close to configure later the SQL Server Reporting Services

Image may be NSFW.
Clik here to view.

Apply latest SQL 2022 CU

At the time of this writing, the latest cumulative for SQL 2022 is CU17. We will install it to have an updated SQL installation. Note that SQL 2022 does not have a minimum CU requirement.

• Download and execute SQL 2022 latest CU
• Accept the license terms and click Next
• Leave default values, click Next
• Wait for Check File in Use and click Next
• Click Update
• Update completed, might require a reboot

SPN Creation

When you configure SQL Server to use the local system account, a Service Principal Name (SPN) for the account is automatically created in Active Directory Domain Services. When the local system account is not in use, you must manually register the SPN for the SQL Server service account.

Since we are using a domain account, we must run the Setspn tool on a computer that resides in the domain of the SQL Server. It must use Domain Administrator credentials to run.

Run both commands to create the SPN, Change the server name and account name in each commands.

• setspn -A MSSQLSvc/yourservername:1433 yourdomainSQLSA
• setspn -A MSSQLSvc/yourserver.fullfqdn.com:1433 yourdomainSQLSA

To verify the domain user SPN is correctly registered, use the Setspn -L command

• setspn –L yourdomainSQLSA

SQL Configuration

MEMCM setup verifies that SQL Server reserves a minimum of 8 GB of memory for the primary site. To avoid, the warning, we’ll set the SQL Server memory limits to 8GB-12GB (80% of available RAM).

• Open SQL Server Management Studio
• Right click the top SQL Server instance node
• Select Properties
• In the Memory tab define a limit for the minimum and maximum server memory. Configure and limit the memory to 80% of  your server available RAM. In my case I have 16GB available.
  • Minimum 8192
  • Maximum 12288

Image may be NSFW.
Clik here to view.

Database Sizing

We always recommend creating the SCCM database before the setup. This is not mandatory; SCCM will create the database for you during setup but will not create it the optimal way. We strongly recommend watching the The Top Ten Lessons Learned in Managing SQL session from MMS2013, which cover it all.

We follow the guide made by MVP, Kent Agerlund to estimate my DB sizing need. Visit his blog post and download the provided Excel file. Input your values in the blue cells and keep it for the next part. We’ll create the DB using those values using a script in the next section.

For this blog post, We’ve created a Database for 2000 clients, 2 processors, 2 cores and 16GB RAM.

Image may be NSFW.
Clik here to view.

Create Database

To create the database, you can use Kent’s script and input your values (as returned previously in the Excel file) OR  use the following one, which is simple:

The Name value will become your Site Code during the SCCM installation. Be sure to select a unique Site Code.

• **Replace all XXX value with your 3 character Site Code**
• **Change the values of  the Filename, Size, MaxSize and FileGrowth. Change the location of the file to your SQL and Logs drives**

USE master
CREATE DATABASE CM_XXX
ON
( NAME = CM_XXX_1,FILENAME = ‘E:\SCCMDB\CM_XXX_1.mdf’,SIZE = 7560, MAXSIZE = Unlimited, FILEGROWTH = 2495)
LOG ON
( NAME = XXX_log, FILENAME = ‘G:\SCCMLogs\CM_XXX.ldf’, SIZE = 4990, MAXSIZE = 4990, FILEGROWTH = 512)
ALTER DATABASE CM_XXX
ADD FILE ( NAME = CM_XXX_2, FILENAME = ‘E:\SCCMDB\CM_XXX_2.mdf’, SIZE = 7560, MAXSIZE = Unlimited, FILEGROWTH = 2495)

Review the Site Database properties

• Open SQL Management Studio
• Right click your DB, Select Properties
• In the General tab, verify that the SQL collation name is SQL_Latin1_General_CP1_CI_AS

Image may be NSFW.
Clik here to view.

• In the File tab, verify that your database files has been created with the script value
• Verify that the file is located on your SQL Volume
• Change the database owner to SA. By default the owner will be the account which created the database.

Image may be NSFW.
Clik here to view.

If you find out that you made an error, you can safely delete the Database using SQL Management Studio and rerun the script.

• Open SQL Management Studio
• Right click your DB, Select Delete

Image may be NSFW.
Clik here to view.

TempDB sizing

Run the following scripts to size the TempDB. (using the value returned by the Excel file)

**Change the values of Filename, Size, MaxSize and FileGrowth. Change the location of the file to your TempDB drives**

USE master
CREATE DATABASE CM_XXX
ON
( NAME = CM_XXX_1,FILENAME = 'E:SCCMDBCM_XXX_1.mdf',SIZE = 7560, MAXSIZE = Unlimited, FILEGROWTH = 2495)
LOG ON
( NAME = XXX_log, FILENAME = 'G:SCCMLogsCM_XXX.ldf', SIZE = 4990, MAXSIZE = 4990, FILEGROWTH = 512)
ALTER DATABASE CM_XXX
ADD FILE ( NAME = CM_XXX_2, FILENAME = 'E:SCCMDBCM_XXX_2.mdf', SIZE = 7560, MAXSIZE = Unlimited, FILEGROWTH = 2495)

Review the TempDB properties

• Open  SQL Management Studio
• In  System Database, Right click the TempDB, select Properties
• In the File Tab, verify that your database files has been created with the script value
• Ensure that the TempDB and log are on the TempDB volume

Image may be NSFW.
Clik here to view.

SCCM SQL 2022 Install – SQL Communications

To ensure proper SQL communication, verify that settings are set accordingly in SQL Network configuration

• Open SQL Server Configuration Manager
• Go to SQL Server Network Configuration / Protocols for MSSQLServer
• On the Right Pane, right-click TCP/IP and select Properties
• In the Protocol tab
  • Enable: YES
  • Listen All : NO

Image may be NSFW.
Clik here to view.

• In the IP Addresses tab
• IP1 (which should have your Server IP)
  • Active : YES
  • Enabled : YES
• All other IP and IP ALL
  • Active : YES
  • Enabled : NO
  • TCP Dynamic Ports : Blank value
  • TCP Port : 1433

Image may be NSFW.
Clik here to view.

Once the modification has been made, restart the SQL Server Service.

The server is now ready for the SCCM installation. We hope that this SCCM SQL 2022 Install Guide was helpful.

Overview | SCCM Current Branch Step-by-Step Installation Guide

The post SCCM SQL 2022 Install Guide appeared first on System Center Dudes.