The following is a guide on how to install SQL 2016 for your System Center Operations Manager (SCOM) 2016 environment. I will be installing SQL 2016 on a brand-new server with Windows Server 2016 installed.
To begin, I am going to set the following accounts as a Local Administrator on the server. Also, I am going to be creating two SQL instances, one for the Operations database, and the other for the Data Warehouse. Since this is for my personal lab, I am not dedicated storage/drives for the databases.
|domain\SCOM_AA||SCOM Action Account|
|domain\SCOM_DA||SCOM Data Access/SDK Account|
|domain\SCOM_SQL_READ||SCOM SQL Reader|
|domain\SCOM_SQL_WRITE||SCOM SQL Writer|
|domain\SQL_SA||SQL Service Account|
Next, let’s run the setup wizard as the SQL_SA account to make life easier down the road…
First thing I noticed, between SQL 2012/2014 and SQL 2016, a few changes/features have been removed/added. One that stands out is, the SQL Server Management Studio (SSMS) console is no longer here. Hmm.. I guess we can always connect to the databases from a console on another server/PC.
As mentioned, I am dedicated an instance for the Operations DB, and one for the Date Warehouse DB.
Setting the SQL Server Agent to Automatic, and specifying the service accounts for the two services.
Keeping the database engine collation as default, “SQL_Latin1_General_CP1_CI_AS“.
Here, I am adding all the SCOM/SQL service accounts and SQL service accounts as SQL server administrators.
Nice! This is new for SQL 2016 — being able to create TempDB‘s. Since my VM has 8 vCPU’s, looks like SQL 2016 picked up on that, and has decided to create a one-to-one relationship. Great, let’s get started within the installation…
Perfect! No errors. Keep in mind, we will need to repeat these steps to create the Data Warehouse instance.
Great! Now we can go ahead with the SCOM 2016 installation! See HERE, for that post.
If you need to install the SQL Server Management Studio (SSMS), continue reading…
Within the SQL Server Installation Center, we have the SQL Server Management Tools as an option, let’s choose that.
Hmm, that takes us here, “https://msdn.microsoft.com/en-us/library/mt238290.aspx“. I guess you can always download SSMS directly from the URL as well. Good to know!
Once downloaded, let’s run the installer…
Hmm, rather simple and straight-forward. Let’s launch that sucker!
Sweet, I can see the two SQL instances I just created, SCOM_DW and SCOM_OPSMGR, perfect!
I hope this helped!