Summary

This article details requirements to consider when hosting FlexNet Manager Suite databases on a SQL Server 2019 instance. 

Requirements

There are three points to check:

1. Ensure that you have installed Cumulative Update Package 25 (or later) for SQL Server 2019.
   
   
2. As FlexNet Manager Suite uses SQL CLR, and this is not compatible with the memory-optimized tables feature introduced in SQL Server 2019, disable TempDB_Metadata using either of the following processes, and then restart SQL Server:
   

   ALTER SERVER CONFIGURATION SET MEMORY_OPTIMIZED TEMPDB_METADATA = OFF

   or
   

   EXEC sp_configure 'tempdb metadata memory-optimized', 0
   GO
   RECONFIGURE
   GO

3. In SQL Server 2019, Microsoft introduced changes in Intelligent Query Processing that may cause queries used by FlexNet Manager Suite to fail. The most reliable workaround known to prevent these failures is to have the compatibility level set on all FlexNet Manager Suite-related databases hosted on a SQL Server 2019 instance to SQL Server 2017 (140).
   
   Some people have alternatively reported successfully resolving errors by turning off the following six Intelligent Query Optimizer components (as described in this Microsoft topic):

   ALTER DATABASE SCOPED CONFIGURATION SET BATCH_MODE_MEMORY_GRANT_FEEDBACK = OFF;
   ALTER DATABASE SCOPED CONFIGURATION SET ROW_MODE_MEMORY_GRANT_FEEDBACK = OFF;
   ALTER DATABASE SCOPED CONFIGURATION SET INTERLEAVED_EXECUTION_TVF = OFF;
   ALTER DATABASE SCOPED CONFIGURATION SET DEFERRED_COMPILATION_TV = OFF;
   ALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFF;
   ALTER DATABASE SCOPED CONFIGURATION SET BATCH_MODE_ON_ROWSTORE = OFF;

• The SQL Server instance may crash
  
  
• Errors may be observed in logging and output from various processes with the following SQL Server error message:
  

  Cannot continue the execution because the session is in the kill state​

• Inventory import process may fail with an error such as:
  

  2020-11-29 09:38:08,872 [INFO ] Failed to execute Writer 'CreateDiscoveredDevicesFromInventory' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\SyncDiscoveredDevice.xml, at step line 29
  Error: Invalid length parameter passed to the LEFT or SUBSTRING function.​

• Red error bar failures may be reported on web UI pages, with error details recorded in the webui.log file. An example of an error from the All Purchases page is:
  

  [ERROR 2021-08-03 07:01:27,580 1648582ms UiHelper_Grid ] Error retrieving data (a2f8814d-1e4c-412e-a0de-2e66bcfde3df)
   System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> DevExpress.Xpo.DB.Exceptions.SqlExecutionErrorException: Executing Sql 'SELECT [N0].[PurchaseOrderDetailID],[N0].[PurchaseOrderID],[N0].[PurchaseOrderNumber],[N0].[Vendor],[N0].[Description],[N0].[PurchaseDate],[N0].[SKU],[N0].[Type],[N0].[EffectiveQuantity],[N0].[TotalPrice],[N0].[LineItem],[N0].[Status],[N0].[CorporateUnit],[N0].[Publisher],[N0].[ProcessedBy],[N0].[StatusID],[N0].[UnitPriceRateID],[N0].[NotificationCount],[N0].[Notification],[N0].[SoftwareSkuID]
   FROM [dbo].[Grid_PurchaseListModel] [N0]
   WHERE (not (([N0].[CorporateUnit] is null or ([N0].[CorporateUnit] = @p0))))' with parameters '{}' exception 'System.Data.SqlClient.SqlException (0x80131904): Divide by zero error encountered.​

Additional information

SQL Server 2019 (with Cumulative Update 25 or later) is supported for use with FlexNet Manager Suite versions starting from 2020 R1.

Additional information about requirements for FlexNet Manager Suite servers can be found in the System Requirements documentation for each version.