We have an application running on Pega 7.x with MS SQL 2016 with compatibility mode set to 120. Now we are planning to migrate to Pega 8.x with 2019 (compatibility mode will be set to 150 and not 120). From the KB article, we understand that the “Report definition with any date filters” will not work. [ This is a known issue beginning in Microsoft SQL Server 2016 with rounding datetime vs. datetime2 values.]

Reference:

https://support.pega.com/question/pega-infinity8x-support-microsoft-sql-server-2019

Question:

1.    What should we do to make the report definition work again with 2019 and with compatibility mode 150(Default) 2.    We also have lot of data time fields in our application. Do we need to recreate or modify those properties and do anything? 3.    What are the other changes(Pega OOTB Features) that we must do in Pega application to make it work.

4. Does pegasystems provide any patch or component to handle this compatibility issue?

5. Is there any alternate solution to handle this compatibility issue?

6. Do we have any references where other customers implemented with MS SQL 2019 with default compatibility?

Query on below Info: [Can we know a list of Pega OOTB Report Definition which comes under this scenario]

If you are using Microsoft SQL Server 2016, 2017, or 2019 , and you have a Report Definition that is filtering for any of the out-of-the-box date/time values, you may see that no values are returned. This is a known issue beginning in Microsoft SQL Server 2016 with rounding datetime vs. datetime2 values.