Is it possible to split a Pervasive database over multiple servers (for example, 50 tables on one server and 50 on another)?
Splitting your database onto multiple servers requires that you have a Pervasive PSQL server engine installed on each server, and each engine will service the files residing on that server. Btrieve applications can take advantage of this type of configuration by simply having the application open files at their specified locations, causing each engine to be used to service its local files. Relational applications can be set up so that a database has the dictionary and possibly some data files stored on one server, and other data files stored on another server. The application will connect to the SQL Engine on the server with the dictionaries, and request data via a Btrieve session to all other servers as necessary. This will incur some performance overhead since the data will have to go over the wire to get to the SQL engine before also going over the wire to get to the application.
Related Questions
- Is it possible that I use the TNTService component on a server with the database locked by the service manager? If so, how can I handle that?
- Is it possible to split a Pervasive database over multiple servers (for example, 50 tables on one server and 50 on another)?
- Is it possible to exclude from the delete policy some special custom tables not present in the original database schema?
