How to install MS SQL Server 2022 for System Platform 2023 R2 SP1

Hello Jimmy.

Besides those new features that you mentioned, I've found another difference in the installation steps between SQL Server 2019 and SQL Server 2022 that's not covered by the document for SQL Server 2019 (TN 10569). Specifically, in the Feature Selection step, SQL Server 2022 does not show the items "Client Tools Connectivity" and "Client Tools Backwards Compatibility" which are requested by TN 10569.
In SQL Server 2022 that implies some additional manual installation steps after the installation of MS SQL Server, which involves downloading and installing these features from Microsoft site:
- MS Visual C++ Redistributable for VS 2022 (required for MS OLE DB Driver for SQL Server)
- MS OLE DB Driver for SQL Server
- MS ODBC Driver for SQL Server
That's why I am looking for any AVEVA documentation which confirms if those steps or any other step are needed for SQL Server 2022 in a GR or Historian node.

Have you found that difference in your SQL Server 2022 installer? How did you resolve it?

Hi Ismael,

my installation was an upgrade from SQL Server 2019 to 2022, the installation process was quite fast and easy, it starts by downloading the install files and install them in one dialog, 

Those requites were already installed by System platform 2023 R2 on my machine, I did not have to install them before.

the SQL Server install did not request the installation of those components, and please note that my dev machine also have VS 2019 Community installed.

all i Had to do after the upgrade was to setup my 2020 SQL instance as the primary SQL instance.

Hi Ismael,

my installation was an upgrade from SQL Server 2019 to 2022, the installation process was quite fast and easy, it starts by downloading the install files and install them in one dialog, 

Those requites were already installed by System platform 2023 R2 on my machine, I did not have to install them before.

the SQL Server install did not request the installation of those components, and please note that my dev machine also have VS 2019 Community installed.

all i Had to do after the upgrade was to setup my 2020 SQL instance as the primary SQL instance.