When monitoring SQL Server instances using collations such as _SC (supplementary character) or _UTF8 (UTF-8 encoding), the BLOCKING_LIST and DBSS_Blocking_History collections fail due to the use of legacy LOB types (text, ntext) in the SQL queries.
This issue isn't specific to SQL Server 2019. It affects any SQL Server version (2012 and later) where _SC or _UTF8 collations are used, due to the fact that text and ntext types don't support supplementary characters or UTF-8 encoding.
ERROR [RMI TCP Connection(1)-] com.quest.qsi.fason.core.collection.RMISubmissionCollection - An exception occurred during the execution of a processor from com.quest.qsi.fason.sqlserver.collection.processor.DBSSRMICallbacklGeneralProcessor class. The processor belongs to BLOCKING_LIST collection.java.lang.RuntimeException: java.lang.RuntimeException: Failed to execute collection [BLOCKING_LIST], reason=Cannot convert to text/ntext or collate to 'Latin1_General_100_CI_AS_SC_UTF8' because these legacy LOB types do not support UTF-8 or UTF-16 encodings. Use types varchar(max), nvarchar(max) or a collation which does not have the _SC or _UTF8 flags.
The SQL queries in the SQL Server cartridge use CONVERT(NTEXT, [text]), which fails under _SC or _UTF8 collations due to SQL Server limitations on legacy LOB types.
