DelphiFAQ Home Search:

Connecting to InterBase on Windows 2003 Server is very slow


comments6 comments. Current rating: 4 stars (2 votes). Leave comments and/ or rate it.


It takes about 20 to 30 seconds to connect to an Interbase server running on a box with Windows 2003 Server. The same happens on Windows ME but not on other operating systems such as Windows XP or Windows 2000 Server. I'm using InterBase 5.6


It's a known issue that versions prior to 7.1 do have a bad connect/disconnect behaviour on Windows 2003 Server.

The solution is to upgrade to InterBase 7.1 or avoid using Windows 2003 Server if you are stuck with InterBase 5.6.

If you are stuck with both, then turn off system restore and see if that solves the problem. Microsoft
introduced a bug in XP that causes slow connections. This might apply to Windows 2003 Server as well.


2006-01-12, 19:31:48
anonymous from United Kingdom  
If your server utilises hyperthreading this also can slow down interbase
2006-03-11, 04:48:00
anonymous from Australia  
The hyperthreading suggestion has worked well for both my XP and Ws2003 installations. Its great when the solution to an exceedingly irritating thing is so simple as a tweak in the system setup. Now of course, as a confirmed obsessive compulsive, I am worried about whether I am getting the server performance I need under load.
Many Thanks.
2007-02-13, 04:28:08
anonymous from Harare in Mashonaland East, Zimbabwe  
im also looking for that help (slow connection from Interbase & Hyperthreading),since our applications run on Windows 2003 Server and Win Xp clients, please help
2007-03-26, 13:15:53   (updated: 2007-03-26, 13:21:59)
anonymous from United States  
Found this solution on another board, and copied it here for the benefit of future seekers. I implemented this tool and it worked great for my syst.

PosPosted by: Rob Roberts (IP Logged)
Date: January 27, 2005 01:48PM

Versions of Borland's Interbase database engine prior to v7.5 have a similar problem on hyperthreading servers. There is a program called IB_Affinity.exe that can be used to 'pin' a process to a single logical processor on hyperthreading systems. It solves the problem with Interbase. But it isn't specific to Interbase. It can be used for any program. I don't know whether it will solve your problem or not, but it might be worth a try.

It is available for download here: []. (Although I don't know if that is the most recent version. I believe that some earlier versions only worked with Interbase.)

--Rob Roberts

2009-06-03, 01:24:24
anonymous from Philippines  
Damn! I'd been looking for a solution to this problem for a very long time!!!
I modified the ibconfig file --> CPU_AFFINITY 1
2015-02-01, 02:58:55
The forum is a brhigter place thanks to your posts. Thanks!



NEW: Optional: Register   Login
Email address (not necessary):

Rate as
Hide my email when showing my comment.
Please notify me once a day about new comments on this topic.
Please provide a valid email address if you select this option, or post under a registered account.

Show city and country
Show country only
Hide my location
You can mark text as 'quoted' by putting [quote] .. [/quote] around it.
Please type in the code:

Please do not post inappropriate pictures. Inappropriate pictures include pictures of minors and nudity.
The owner of this web site reserves the right to delete such material.

photo Add a picture: