Getting Illegal character from SQL DB
We are getting Illegal character (?) while retrieving a nvarchar field(TEMP-WRK-INFO) from a table in a cobol module. Below are region details:- Linux version - RHEL 8.3 MSSQL version - 2019 Initially, we got illegal character while converting the hex value to ASCII value. For example, when the amount of 894.55 is moved to TEMP-WRK-INFO, then hex value of (89 45 5C) is converted to ASCII as (?E\). This issue occurred as extended ASCII value is not converted correctly. We had a fix for this issue by changing the LANG to en_US.CP1252 in environment settings, then it worked for all extended ASCII value except for 81 and 90. When the hex value has the combination of 81 or 90, then we get the illegal characters. Same logic is working fine in windows environment.
SQL Server 2012 Native Client
Microsoft SQL Server 2012 Native Client is being flagged an obsolete software and will stop receiving security updates starting July 12th, but I have done a lot of searching on the internet and getting a mixed results on whether this is true or not. So I figured I would ask here to see if anyone else is dealing with this situation and what conclusion can be made here. For example, Microsoft has a blog post regarding the software that says the software is obsolete on July 12th, which can be seen here: https://techcommunity.microsoft.com/t5/sql-server-blog/snac-lifecycle-explained/ba-p/385381 However, I have been told that there is an exception to the rule that says it is supported "in SQL Server 2012 through 2019 until their respective end-of-support lifecycles", described at the bottom here: https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/support-policies-for-sql-server-native-client?view=sql-server-ver16 So I guess my ultimate question is: Will "SQL Server 2012 Native Client" still receive security updates post July 12th of this year?