Question

2
Replies
44
Views
Suman Gumudavelly (GUMUDAVELLY)
Ford Motor Company
Pega Operations, CoE and Administration
Ford Motor Company
US
GUMUDAVELLY Member since 2011 13 posts
Ford Motor Company
Posted: March 4, 2021
Last activity: April 1, 2021
Posted: 4 Mar 2021 20:07 EST
Last activity: 1 Apr 2021 1:27 EDT
Solved

Microsoft SQL Server 2019 Compatibility Setting

This post is inquiring about the Database Compatibility  setting for MS SQL 2019.  

When we have upgraded one of the Pega application to 7.x couple years ago, we ran into an issue where Report Filters didn't work as expected, this was due to changes in MS SQL 2016 version, where Microsoft has changed datetime to datetime2. 

The solution provided for that issue is by changing the Compatibility  setting to 120 [Essentially running MS SQL 2016 as MS SQL 2014]. This setting was reflected in later releases of Pega Support Guides. 

However, for MS SQL 2019, I do not see any such special notes. Now, the Question is: 

Does we need to change the Compatibility  setting to 120 even for MS SQL 2019

or 

Does any fix provided by Microsoft 

Note: I have validated Pega 8.5.1 data model and none of the date time fileds changed to support datetime2, still referring datetime only. 

==

SR-D55043: Filter not working properly in 7.4

==

If you are using Microsoft SQL Server 2016, and are filtering for the pxUpdateDatetime value in your Report Definition, you may see that no values are returned.  This is a known issue with Microsoft SQL Server 2016 with rounding datetime vs. datetime2 values.  Details: 

This post is inquiring about the Database Compatibility  setting for MS SQL 2019.  

When we have upgraded one of the Pega application to 7.x couple years ago, we ran into an issue where Report Filters didn't work as expected, this was due to changes in MS SQL 2016 version, where Microsoft has changed datetime to datetime2. 

The solution provided for that issue is by changing the Compatibility  setting to 120 [Essentially running MS SQL 2016 as MS SQL 2014]. This setting was reflected in later releases of Pega Support Guides. 

However, for MS SQL 2019, I do not see any such special notes. Now, the Question is: 

Does we need to change the Compatibility  setting to 120 even for MS SQL 2019

or 

Does any fix provided by Microsoft 

Note: I have validated Pega 8.5.1 data model and none of the date time fileds changed to support datetime2, still referring datetime only. 

==

SR-D55043: Filter not working properly in 7.4

==

If you are using Microsoft SQL Server 2016, and are filtering for the pxUpdateDatetime value in your Report Definition, you may see that no values are returned.  This is a known issue with Microsoft SQL Server 2016 with rounding datetime vs. datetime2 values.  Details: 

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/de5dbf3e-8c95-40f4-9e31-b71f1f31983d/change-in-datetime2-implementation-in-sql-server-2016?forum=transactsql

This is a deliberate change in SQL 2016, which appears only if you have the compatibility set to 130 (which is the default).  The short-term solution is to set the compatibility level to what it was for MSSQL 2014, which was 120.  (MSSQL 2014 does not have this issue.)

===

Pega Infinity Support Guide: https://community.pega.com/knowledgebase/documents/platform-support-guide-8x

***Edited by Moderator: Pooja Gadige to add support case created tag***
Pega Platform 8.6 System Administration Cross-Industry System Administrator Support Case Created