Pervasive SQL

  • I'm a little off topic here, but need some feedback. Has anyone worked with Pervasive SQL and how does it compare to SQL Server?

  • It's not as strong a product as Microsoft SQL Server, but has a lot of similarities.

    K. Brian Kelley, GSEC

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/

    K. Brian Kelley
    @kbriankelley

  • Is the basic structure of Pervasive SQL more similar to MS Access or SQL Server? (Does it have just one data file for the database or are there multiple files as in SQL Server?)

  • Haven't really worked with it more than troubleshooting an app that relies on it, so I'm afraid I don't know. Perhaps another reader might?

    K. Brian Kelley, GSEC

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/

    K. Brian Kelley
    @kbriankelley

  • Pervasive.SQL is actually built on top of the old Btrieve database. When Novell bought SoftCraft (the developer of Btrieve), they wanted a server-side RDBMS application (NetWare Loadable Module) implemented to prove that NetWare could be more than just a file and print server. The SoftCraft developers wrote NetWare SQL as a SQL abstraction layer on top of the Btrieve data engine (later renamed the MicroKernel Data Engine, or MKDE). When Novell divested the group, the company was renamed Btrieve Technologies and the product renamed Pervasive SQL, and then, when Btrieve was thought to be passé, they renamed themselves again to Pervasive Software.

    Each table is a separate Btrieve file, which includes its indexes. There are also data dictionary files (DDFs) for stored procedures and the metadata. There is no redo log (and it is not a true ACID RDBMS), if that's what you mean by SQL Server's "multiple files."

    --Jonathan



    --Jonathan

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply