November Windows Server patches causing issues with any version of BCM.
The Default SQL Driver from Microsoft, and included in Windows Server platforms, was updated and now causing BCM queries to execute endlessly, or very slowly.

The SQL Driver which is delivered by default with Windows server environments was updated in November 2022.
This causes some of the BCM queries to never end or take an extremely long time to execute.

The solution consists in using a different ODBC driver.

Ideally ODBC Driver 17 or ODBC Driver 18 will work.

In order to make this change, it is necessary to install the ODBC drivers from Microsoft, and can be found on this link :

https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16

Both the ODBC 17 and ODBC 18 Drivers are available on the above link.

Install the driver(s) on the BCM Master, and once done, you can then modify the vision64database.ini file.

First and foremost, make a copy of the original vision64database.ini file.

Stop the BCM service on the Master.

Possible solution number 1:

The ODBC Driver 17 can be installed and in this case the only change to make is in the ../master/config/vision64database.ini file.
The modification to make is on the database connection string, and has to be set like this:

DatabaseName=Driver={ODBC Driver 17 for SQL Server};Server=DB Server Name;Database=bcm database name

Possible solution number 2:

Alternatively, the ODBC Driver 18 can be installed and in this case, the simple connection string cannot be used in vision64database.ini.

Instead, an system DSN has to be configured at operating system level, under Control Panel > Administrative tools > ODBC Data sources (64-bit).
First, create a System DSN on the BCM Master as such:

On the next screen, it is extremely important that the option "Connection Encryption" is set to "optional", otherwise this will fail to test and connect to the database

In the end, after testing and saving, a System DSN using the ODBC 18 SQL Driver is created

Time to modify the vision64database.ini file and set this type of connection string instead of the original one:

Top of the file set

DatabaseType=ODBC

At database name section set

DatabaseName=BCM

BCM here corresponds to the DSN name created above.

Save the file and restart the BCM Service on the Master.

After this modification has been made and the service has restarted successfully, the security updates can be applied again, and the issue should not reappear.