Expand all | Collapse all

issue with the ODBC Driver

  • 1.  issue with the ODBC Driver

    Posted Mon February 22, 2021 10:27 AM
    We have SQL Server 2005 which has linkedserver created on it with informix ODBC driver through dsn datasource. Which is running properly. Currently we are migrating it to SQL Server 2019. After migrating,The linked server query is getting executed till 15th minute. After that driver is giving the following error.

    it ran for 15:16 then it has thrown this.

    But the same query working in the sql server 2005 server.

    Driver version details in sql server 2005.

    Server Details:

    Driver version details in sql server 2019.

    Server Details:

    bhimagonolla sureshgoud

  • 2.  RE: issue with the ODBC Driver

    Posted Tue February 23, 2021 01:04 AM
    Hi Bhimagonolla,

    Based on information you shared there is difference between ODBC DSN values for CLIENT_LOCALE between SQL Server 2005 and SQL Server 2019 machines. In 2015 both CLIENT and DB LOCALEs are set to same value, hence no conversion taking place! and you are not seeing -2005 error (this error is related to CLIENT and DB locale conversion issue). Whereas in 2019, CLIENT LOCALE is en_US.CP1252 (which is actually correct for client locale and default in ODBC) and DB LOCALE is en_US.819 (default ODBC).

    I think few things:
    1. You need to check why CLIENT LOCALE is pointing to en_US.819 in SQL Server 2015 setup? May be you encountered similar issue in past and changed to current value from en_US.CP1252 default?
    2. Change the CLIENT LOCALE to en_US.819 in SQL Server 2019 and give it a try, most likely you will not encounter -2005 error. However for CLIENT LOCALE en_US.819 on Windows may not be the best choice!
    3. You should also enable "Use Server Database Locale" checkbox, that will ensure value of Database Locale to be correctly reflected the actual value of locale on which your database is created.
    4. In short, you need to ensure correct value of CLIENT and DB locales for your applications.
    5. Last but not least, You seem to be using pretty old version of ODBC/CSDK 3.50, you should try the latest version i.e. ODBC/CSDK 4.50.FC5

    Hope this helps


    Sheshnarayan Agrawal