At the end of 2002, Borland released InterBase version 7, featuring support for SMP, enhanced support for monitoring and control of the server by administrators, and more. Borland released InterBase 7.1 in June 2003, 7.5 in December 2004, and 7.5.1 on June 1, 2005.
In September 2010, Embarcadero announced the availability of InterBase XE. Its new features include a 64 bit client and server, improved security, improved scalability, support for dynamic SQL in stored procedures, and optimized performance of large objects with stream methods.
In Nov 2019, Embarcadero released InterBase 2020, followed by Update 1 release in May 2020. The InterBase 2020 release adds a number of new features, including tablespaces support for InterBase, allowing for better performance on servers with multiple data storage options. See further at -history
Use the Options property of TIBServerProperties to return server configuration information, including the version of the database and server, license and license mask information, and InterBase configuration parameters. These options are discussed in the following sections.
The service_name is the entry contained in the services file pointing to the port number which the InterBase server should bind to. Below is an example of a part of the file from the \drivers\etc\services file.
The InterBase environment variable or the -i switch is used for local connections. These values determines which InterBase server a client on the same machine will connect to. The InterBase environment variable for a client and server's -i switch must match to have a successful connection. So if InterBase server is started with the setting:
The InterBase server will accept remote connections on the TCP/IP port number 3051 as the service ib__a is set to port 3051. The local connections will be accepted from client on the same machine who have their InterBase environment variable set to C:\Program Files\interbase.
Older versions of InterBase servers (pre-7.5) can still run using the default setting. These pre-7.5 InterBase servers will accept remote connections on TCP/IP port number 3050. The local connections will be accepted when the client uses a pre-7.5 interbase client library.
We recommend using the -i switch to set the local InterBase variable for the server. The order in which InterBase server looks for the InterBase environment variable is as follow; Command line argument '-i', InterBase environment variable setting, InterBase Registry key setting, Server's current directory.
Unable to log into Local Server -gds_db after download of Interbase Developer Edition. Getting "Error logging into the requested server" Connection rejected by remote interface' .Using un/pw of SYSDBA masterkey.
You can use the Microsoft SQL Server Management Studio to connect your InterBase data to an SQL Server instance. Linked Server is a tool of MS SQL Server that allows to execute distributed queries to refer tables stored on non-SQL Server datbase in a single query. With linked servers, you can execute commands against different data sources such as InterBase and merge them with your SQL Server database. You can create a linked server with one of these methods: by using the options in the Object Explorer or by executing stored procedures.
The ability to connect other database instances on the same or remote server.
The ability to run distributed queries on heterogeneous data sources across the organization.
The ability to work with diverse data sources in the same way.
How to configure a SQL Server Linked Server to connect to InterBaseYou can follow the steps to create a linked server for InterBase in SQL Server Management Studio by using Object Explorer:
Error messages from ping indicate that there is a network problem. Check that the network is plugged in, that the network wires are not damaged, and that the client and server software is properly configured.
If the database server is behind a software or hardware firewall, all network traffic could be restricted and the client might not be able to reach the server at all. Some firewalls permit or restrict traffic based on the port to which the client attempts to connect. Because of this, it is not conclusive whether a given service can reach the server. Neither is it an indication of connectivity if the client can resolve the IP address; that merely indicates that the client can reach a name server that resolves the InterBase server hostname.
NetBEUI cannot route network traffic between subnets. Other protocols can also be configured to restrict traffic between subnets. If the client and server are on a complex network with multiple subnets, ask your network administrator if the network configuration allows you to route network traffic between the client and server in question using a given protocol.
You can simulate a client/server connection and test the configuration of the server without the additional variable of the client configuration and intervening network by connecting in a loopback mode.
Whether this test fails or succeeds, it helps to narrow the focus of further diagnostic tests. If it fails, you can infer that the configuration of the server is at fault. If it succeeds, you can infer that the server is not at fault and you can concentrate further tests on the client.
InterBase 2020 Developer Edition is installed with RAD Studio (does not apply to the Starter edition) and included in RAD Studio integrated license. InterBase 2020 ToGo does not have to be installed on any server or end-user workstation and it has two licensing options for deployment: ToGo and IBLite. This feature makes it easier for developers to create C++Builder and Delphi InterBase applications using RAD Studio.
You can use InterBase Manager to change database cache size of client map size. The InterBase Guardian Server Properties dialog enables you to display and configure these server settings. To access InterBase Guardian, right-click the InterBase Guardian icon in the System Tray. You can access the Server Properties dialog by any of the following methods:
The General tab of the Server Properties dialog is where you can view such server settings as the version, capabilities, number of databases, and number of attachments. You cannot edit the information displayed on this tab.
You cannot update the information displayed on the General tab; however, you can click Refresh at any time to retrieve the current server property information. If you need to view or configure server settings, click the IB Settings tab.
If you have successfully completed the setup steps, you can start up InterBase and Firebird at will; just take care they don't run at the same time. There are several ways to start and stop the database servers:
Easiest, most powerful and therefore recommended: go to and get DBServerToggler. This little feller, when started, nestles itself in the System Tray and does all the dirty work for you. You start and stop either server with the click of a button; if you start a server, DBServerToggler will first halt the other one if it's running. You can choose between application mode and service mode for each server independently. Add DBServerToggler to your Startup folder and you'll have it at your fingertips at all times.
If a server is installed as a service (Windows NT/2000/XP only), you can start and stop it from the Windows Services Manager, or from the command line as shown below. (Note: each box contains one command, to be given on a single line, and without any hyphens.)
If you have started an InterBase version up to 5.6 via the Guardian, you must give two net stop... commands to take it down: first for the Guardian, then for the server. With InterBase 6.0 and Firebird, stopping the Guardian automatically takes down the server as well.
To connect to InterBase Developer edition, the InterBase server must be (re)started every 48 hours. Failing to do so will result in the error "Unavailable Database". To start the InterBase server, select InterBase Server manager from the Embarcadero InterBase XE3 [instance=rad_xe3] group in the start menui and click the start button.
The Borland Local InterBase Server is a single-user Windows-based version of Borland's InterBase Workgroup Server, an SQL-compliant relational database management system (RDBMS). The Local InterBase Server includes Windows ISQL and the Server Manager, a Windows tool that can be used with Local InterBase Server or a remote InterBase server. Using the Local Interbase Server, you can access local databases through Windows ISQL or through a SQL application program.
Delphi applications can access a Local InterBase Server database through the Borland Database Engine (BDE) and the InterBase SQL Link. For more information on creating Delphi applications for SQL servers, see the Delphi Database Application Developer's Guide.
If you connect via tcp/ip, it should not matter where your Interbase binaries are located, as long as the interbase service is running. You also need to check wich port it is running on. Normaly it's on port 3050.
So the last IDE to install Interbase can set protocol to "local" and leave server blank, but to work on any other version you need to use tcp/ip. That applies to the connections in the Data Explorer as well. I had to modify each connection.
I see you have multiple server instances in IBConsole. How did you set them up? One of my attempts to solve my problem, I downloaded the separate install of Interbase, and could create separate instances during the install, but I can't see any way to do that later.
OK, I should explain--that screenshot is misleading. I originally installed IB 2020 with Delphi 10.4 on my developer machine. Then, I started doing some testing with web modules on my Windows Server under IIS so installed IB 2020 on there. After I registered that and started using it there, when I try to open a database on my developer machine, it tells me the license is already in use. I need to uninstall it from my developer machine--the only one I can really use in that screenshot is the one at the IP address that points to my Windows server. I included the screenshot to show that it's possible to register multiple databases with different instance names and ports. Sorry for the confusion.