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 ...
    • The Lessons We Learned from Upgrading Web Service 8.2 to 8.5 in eStore

      Elliott Web Service 8.5 changed ORDER_NO, INV_NO, and other keys from numeric to alphanumeric to accommodate a bigger range. This results in changes in the Web Service interface. This article documents our experience when we upgraded the Web Service ...
    • Pervasive Backup Agent Is Not Compatible with Creating Work Files

      Release Date: 09/12/2017 Q - After PSQL 11 SP2, are both Backup Agent or Volume Shadowing Service (VSS) included for my backup purposes? Which one should I use? A - Based on Pervasive's recommendation: Which Backup Solution Should I Use? If you are ...
    • 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 ...
    • Report Desk: Resolution of Pervasive.Data.SqlClient.dll

      Release Date: TBA Version 8.6 Actian/Pervasive introduced a bug in versions 12 and 13 of their SQL client regarding LongVarChar columns exceeding 64K in length. This bug could impact Report Desk. They have provided us a fixed version of ...