PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider

PSQL 13, Micrsoft SQL Integration Service & Pervasive PSQL OLE DB Provider

Release Date: 3/26/2019
Version: PSQL 13

An Elliott user recently upgraded from PSQL 12 to PSQL 13 R2 (13.30.011. 000). The user also replicated Elliott data (in this particular case, the attribute database) to their MS SQL 2012 server by using integration services (used to call DTS. ) After the server upgrade to PSQL 13 R2 (the client of the MS SQL server was still on PSQL 12), we noticed the attribute table was corrupted by using the integration services. See sample screen below:


After further investigation, we found that if we switched the provider from "Pervasive PSQL OLE DB" to "Pervasive Provider, Current Release," then the problem is resolved.  See sample screen below:

We did this switch with the PSQL 12 client on the MS SQL server. We did not test whether the problem would be resolved if we installed the PSQL 13 client on the MS SQL server.  The PSQL 13 R2 server was running PSQL version 13.30.011.000. It is also possible a future PSQL 13 revision may resolve this issue.


EMK


    • Related Articles

    • How to Investigate or Debug Report Desk Problem by Using SQL Statement

      Released Date: 1/25/2025 Version: 8.6 & Higher Report Desk is based on the PSQL relational engine. It sends a SQL statement to the PSQL engine to retrieve data. Sometimes, you don't get the result back as you expected, so what next? For example, when ...

    • An Example of Debugging NOTE_ORD_VIEW PSQL Expression Evaluation Error

      Q - When I try to access the NOTE_ORD_VIEW in the PSQL control center, I get this error: "[LNA][Pervasive][ODBC Engine Interface]Expression evaluation error." See sample screen below. It does not display any results, but it does display the create ...

    • Can I Dynamically Adjust Elliott / PSQL 11 Server Memory?

      In the virtual server environment, it is very easy to adjust the server's memory in order to better suit your requirements and more efficiently use the server hardware. However, it is important for you to be aware that the PSQL 11 engine license can ...

    • Configure PSQL Server Memory Usage

      Version: Any Release Date: 12/17/2021 Q - Can you tell us why PSQL process is taking up so much memory? Is there anything we can do? See sample screen below: A - PSQL server by default can take up about 60ish% of the server memory. This is ...

    • A Case to Optimize PSQL Query Performance with INNER JOIN SYCONTCT & SYCONREL Tables

      Release Date: 11/29/2023 Version: 7.x & Up Q - With our custom web application, we attempt to find an existing customer and associated contact when creating new customers via the Elliott web services. We are finding the customer just fine, but when I ...