Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Improve Pervasive Performance

Status
Not open for further replies.

STF26

IS-IT--Management
Dec 9, 2003
130
US
I am currently working with a client that is running a DOS based application that uses Pervasive SQL 2000i. I was brought in to handle some performance issues. After obersving the application for a few minutes I realized that they needed tamedos to handle the keyboard inputs in Windows XP. Next step was to check out the AV exclusions. That was an issue also. I excluded all of the vital database components on the servers and workstations. After a couple of hours the usability of their program was tremendously improved.

I have noticed that their day to day reports take a long time to complete. I asked the office mangager to run a typical report while I observered the task manager on the server. The Pervaisve server process never went above 3-4%. Is there anyway we can boost performance during these reports? I have talked with serveral people and we have concluded-

1. Remove the unused protocols from Pervasive
2. I noticed that the person who setup the network built a backbone network between the two servers in their network. I have heard that Pervasive gets bogged down when there are two network adapters in the server it is loaded on. I think that this design with the backbone network is poor anyway so I will be removing it. It has already caused some major Active Directory name resolution issues because the Adapter in the backbone network keeps publishing itself in DNS.
3. Increase the cache size.

Is there anything else that I can do to improve the speed of these reports?

Thanks

STF
 
A couple of questions and a couple of comments:
1. Removing the unused protocols is a good idea.
2. Pervasive doesn't have any bogging problems with multiple NICs. What can cause problems is when Pervasive listens on the "wrong" NIC.
3. Cache can help in some cases, especially if the same data is read repeatedly.
Questions:
1. What requester are the DOS apps using (BREQTCP, BREQUEST, BREQNT, BTRBOX)?
2. What interface do the reports use (are they DOS based also or do they use Windows and possibly ODBC)?




Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
I am not sure how to determine which requester that they are using. Can you clue me in on how to do this? Could this be a problem?

The reports run in the same dos window as the program.
 
Is the DOS app started by a Batch file? If so, post it.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
@ECHO OFF
REM BREQUEST
MDS /nol

 
Looks like you are using BTRBOX (since BREQUEST has been REMmed out). Are you connecting using TCP/IP or SPX? Check the monitor for the active users and it'll give the network address as either a TCP/IP or SPX address. You can also look in "Communications" under the "Microkernel".


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician
Custom VB and Btrieve development.
 
TCP/IP is the protocol of choice. Nothing else is enabled. I checked the monitor and all of the users are connecting via tcp/ip.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top