Configuration Issues for Transactional Interface
End users may need to know the following information about your transactional interface application. Include this information in the documentation you provide with your transactional interface application.
•
The amount of memory your application requires.
Your application may require more memory or disk space than the transactional interface requires on its own. Establish the disk space and memory requirements of your application and communicate this information to your users. For information about system requirements of the transactional interface, refer to Getting Started With Pervasive PSQL and to the Pervasive Software Web site.
•
Whether the application requires the transactional database engine configuration settings other than the defaults. In particular, consider whether end users need to change these transactional database engine options:
•
Create File Version. Does your application need backward compatibility with a previous version of the transactional database engine? If so, instruct your end users to set an appropriate value for this option.
•
Handles. Does your application need to use more than 60 logical file handles at one time? If so, instruct your end users to set this option to an appropriate value.
•
Index Balancing. Does your application set the Index Balancing file attribute on every file it creates? If so, your end users can use the default of Index Balancing turned off. If not, you may need to instruct your end users to turn Index Balancing on at the MicroKernel level. For more information, see Index Balancing.
•
Largest Compressed Record Size. Does your application use compressed records? If so, see Record and Page Compression in Advanced Operations Guide, and Choosing a Page Size, Estimating File Size, and Record Compression in this book.
•
System Data. Do all files in your database have unique keys? If so, the files are transaction durable. If not, your end users may want to set System Data to If Needed or Always in order to make the files transaction durable.
For descriptions of configuration options, refer to the Advanced Operations Guide.