Pervasive Community Site

Community Forum (formally DEVTALK) – Join the ever- growing Pervasive community in a lively, interactive e-nvironment where users can come together and discuss their choice of topics on Pervasive-based products.  Participants include Developers, Resellers, System Integrators, and End User and Pervasive team members.

Component Zone – Download the latest utilities and tools posted by third-party vendors.  The Zone is your quick stop for getting the latest tools our partners have to offer.

What's New

  • Re: Database In Use Calculation

    I would think that "DIR" would be the simple, command-line tool you need. Total file size should be just a good a measure as "active database file size" when it comes to allocating license costs. Total size will be larger than active size, but one would expect the ratio to be the same for each database, so it should meter out similarly...
    Posted to PSQL v12 (Forum) by BtrieveBill on 01-18-2017
  • Re: Database In Use Calculation

    The intent would be to break down a huge licensing costs and properly allocate them financially. And then provide some forecasting. But you are correct, not important enough to write a utility for it. If it was a simple command line, great. That said, I can see where it could be useful to SaaS people.
    Posted to PSQL v12 (Forum) by jonyelton on 01-18-2017
  • Re: Database In Use Calculation

    As database names are not required, the engine doesn't track usage by database at all. I suppose it would be possible to write a tool that reads the database names to locate the directories for each, then scans the list of open files, mapping each to a database using some sort of rules, and then provide a total from there. All of this can be done...
    Posted to PSQL v12 (Forum) by BtrieveBill on 01-18-2017
  • Database In Use Calculation

    Is it possible to get a breakdown of the database size in use by database name?
    Posted to PSQL v12 (Forum) by jonyelton on 01-18-2017
  • Re: Windows 10 Error 3115 on Client Build 12.10.067

    Is there any reason you are using PSQLv12 Client to talk to a PSQLv11 server? Officially, Actian tests the other way around -- using an older client to talk to a newer server, so that you can upgrade the server first, and get to the clients later on. Not that it shouldn't work, but making the versions match is definitely recommended. A 3111 status...
    Posted to PSQL v12 (Forum) by BtrieveBill on 01-18-2017