Vista Software
Apollo Database Server FAQ
See Also
Overview
Apollo Server Explained

Apollo Database Server™ FAQ

Frequently Asked Questions

This document provides answers to frequently asked questions about Apollo Database Server. This document is divided into several sections:

Send an e-mail directly to sales@vistasoftware.com if you have additional questions. Information presented in this document is subject to change without notice.

Recommended System Requirements

Recommended Client-Side System Requirements

  • Intel Pentium P133 or higher
  • Microsoft Windows 95/98/NT/2000/XP/Vista
  • Memory: 32 MB of RAM or more
  • Enough hard disk space to store your application

Recommended Server-Side System Requirements

Apollo Database Server will work properly on Windows 95 and Windows 98, however the threading model used in these two operating systems makes the server operate at less than optimal speeds. The performance of running Apollo Database Server on Windows 95/98 is not satisfactory to us and we do not endorse using these OS's.

  • Intel Pentium II 300 or higher
  • Microsoft Windows NT/2000/XP/Vista
  • Memory: 128 MB of RAM or more
  • 10 MB hard disk space

Competitor Comparisons

  1. How does Apollo Database Server compare to Advantage™ Database Server?

    Cost: Apollo is royalty free! Advantage requires that you purchase a license for each server you deploy. With Apollo Database Server, you purchase one server once and you may deploy it an unlimited number of times!

    Technology: Apollo Database Server builds on award-winning Apollo technology, which beat Advantage in the 200 Delphi Informant's Readers Choice Awards for "Best Database Engine".

    Apollo Database Server delivers much of the same functionality as Advantage. In fact, Apollo includes features not found in Advantage such as a free 2-User Server, built-in Internet support, Server DLL support, native TCP/IP connectivity, cross-tab queries, and more.

    Significant similarities are:

    1. Both products provide essentially the same core set of features.
    2. Both products support the DBF file format.
    3. The performance of both products is comparable (Benchmarks can easily be adjusted to highlight differences either way).
    4. The support provided by both companies is similar.

    Significant differences are:

    1. Apollo does not require you to purchase multiple server copies. With Apollo, you buy once and deploy many!
    2. The 2-User Apollo Server is FREE!
    3. Apollo Database Server implements an advanced threading model that scales very efficiently as number of connections increase. The Advantage Server implements thread-pooling, which in our testing does not scale as effectively as Apollo.
    4. Apollo features powerful Server DLLs that allow you to run native code on the server.
    5. Apollo has won numerous industry awards - beating Advantage in most of them.
    6. Implementing and maintaining an Apollo Database Server solution is easier. There is truly zero administration with Apollo.
    7. Apollo Database Server supports the popular CA-Clipper NTX index format.

    As you deploy multiple database servers, the savings with Apollo becomes staggering.

    Apollo recently won "Best Database Engine" and was voted runner up for "Product of the Year" in the Delphi Informant Readers Choice Awards 2000. Apollo beat Advantage and CodeBase by a wide margin. Voting was as follows:

General Questions

  1. Is it easy to install Apollo Database Server on both the client and server computers?

    Yes! Developers can have a fully deployed client/server system configured and running in 15 minutes. Additionally, there are no special client-side installation requirements for your client computers other than your Apollo-based client applications (i.e. an application developed using one of the Apollo local engines).

    In fact, Apollo Database Server client applications are easier to install than local Apollo applications because there are no client-side DLLs to install. The SDE DLLs are installed as part of the Apollo Database Server installation and those files go on the central server, not on the individual client computers.

  2. What happened to the Apollo Client/Server bundle?

    The Apollo Client/Server bundle was a promotional product introduced to launch Apollo Database Server and it is no longer sold. It was a bundle offer that included one copy of Apollo VCL with one copy the Apollo Database Server. Customers now need to purchase the Apollo local engines and the Apollo Database Server separately.

  3. What is the SDE?

    The SDE is the underlying, low-level database engine that is responsible for the actual data management. It comes in the form of several DLLs and it's functionality is essentially transparent to the developer. Apollo Database Server, Apollo VCL and Apollo OLE DB all use the SDE.

  4. If I purchase a copy of Apollo Database Server, which version of Apollo do I need to purchase? And do I need Apollo SQL?

    It depends on what development tool and technology you are using.

    If you wish to use SQL in non-client/server mode, then yes, you will need to purchase Apollo SQL.

    Apollo VCL provides Delphi and C++Builder developers with well-designed, native VCL components that integrate tightly into the Delphi and C++Builder environments. These VCL components allow your applications to connect directly an Apollo Database Server while supporting all data-aware controls.

    Apollo OLE DB allows ADO/OLE DB development environments to connect directly to the Apollo Database Server using powerful OLE DB technology. Microsoft Visual Basic, Visual C++ and even Delphi and C++Builder support ADO/OLE DB and each can use Apollo OLE DB.

    Note that the Apollo local engines (i.e. Apollo VCL, Apollo COM, Apollo OLE DB, Apollo Data Control) are not included with Apollo Database Server.

  5. Can Apollo Database Server support multiple applications?

    Yes, each Apollo Database Server can support multiple databases and/or applications connected to it. That means you can have several databases setup on the same Apollo Database Server, and have several different Apollo client applications connecting to the different databases, with unlimited client connections support for each application.

  6. We build and sell vertical market software. How can we effectively resell our software that uses Apollo Database Server to our customers?

    Unlike competing products, Apollo Database Server is royalty free, so there are special considerations to make when re-selling or deploying your Apollo-based applications.

Technical Issues

  1. Using Apollo products, can I use the same code set to develop stand-alone, peer-to-peer and client/server applications?

    Yes. Using one of the Apollo local engines, such as Apollo VCL or Apollo Data Control, developers can develop database systems that run as stand-alone applications, run in peer-to-peer network configurations or connect to the Apollo Database Server. The best part is, the same code set can be used for all three configurations! The Apollo local engines allow you to change the configuration from Local to Server.

  2. Does Apollo Database Server support SQL?

    Yes! Apollo SQL is built-in to the Apollo Database Server. It is a subset of SQL-92 standard.

  3. Why is Apollo SQL sold separately?

    Many Apollo customers do not use SQL in their applications therefore it would not be fair that these customers pay extra for something they don't need. Apollo SQL is an add-on for the Apollo local engines. It is designed for customers that do not need the power offered by Apollo Database Server, but want to use SQL statements to manage their stand-alone and peer-to-peer database applications.

  4. Does Apollo Database Server support Transaction Processing?

    Support for Transaction Processing is scheduled for a future release.

  5. Does Apollo Database Server support Stored Procedures?

    Yes! Apollo's version of Stored Procedures is called Server DLLs.

  6. How many users can connect to the Apollo Database Server at the same time?

    It depends on which edition of the Apollo Database Server you use. Apollo Database Server comes in several editions:

    • 2-User Edition supports 2 concurrent users.
    • 10-User supports 10 concurrent users.
    • Unlimited User supports an unlimited number of concurrent users.

  7. Can the Apollo Database Server be accessed over the Internet?

    Yes! In fact, the internal compression is so good and fast that even a 56K dial-up connection can be used to connect to an Apollo Database Server with surprisingly good performance. The key to good performance is to use SQL to access and manage data.

  8. What is included with Apollo Database Server?

    The following components make up Apollo Database Server:

    • One copy of Apollo Server application.
    • One copy of Apollo Server service for NT.
    • Apollo Server Manager
    • 32-bit SDE

  9. Is Apollo SQL available for non-client/server applications?

    Yes! Apollo SQL is sold separately as an add-on product.

  10. Can I run the Apollo Database Server as an NT 4 Service?

    Yes! The Apollo Database Server comes as both a standard Windows application and as an NT 4 Service.

  11. What development environments does Apollo Database Server support?

    Developers can use Apollo VCL under Delphi/C++Builder, Apollo Data Control under Visaul Basic, Apollo COM under any COM-enabled environment, or Apollo OLE DB under ADO-enabled environments.

  12. Will Apollo Database Server improve my network-enabled applications that support multiple users?

    Yes! With true client/server computing all operations such as indexing, scoping (i.e. SetFilter), query optimizations, record and file locking, etc. is done on the server, not the client. This greatly reduces network traffic and increases performance and robustness.

  13. Must I use SQL with Apollo Database Server?

    No! You can continue to use traditional table-based navigation using TApolloTable under Apollo VCL and the table-based features of Apollo OLE DB. To achieve optimal results, developers are encouraged to use SQL, but SQL is not required.

  14. Do client applications have to log onto the Apollo Database Server?

    Yes. You use the Apollo Server Manager to set up users for a given database.

  15. Does Apollo Database Server support replication?

    No.

  16. What protocols does Apollo Database Server support?

    Apollo Database Server is 100% TCP/IP based.

  17. Does Apollo Database Server support Novell? Does it include an NLM?

    Apollo Database Server is Novell-friendly, in that it can be deployed on any computer in the Novell network running Windows 95/98/NT/2000/XP/Vista. Apollo Database Server was designed to be a pure TCP/IP solution, not IPX/SPX. Furthermore, an NLM is not included because Novell has announced they are dropping their proprietary IPX/SPX format in favor of TCP/IP. Read the Apollo Database Server Explained document on our web site for information about Novell and IPX/SPX.

  18. Can Apollo Database Server support encryption/decryption for data over the Internet?

    Yes! You can configure your Apollo applications so that data sent between the Apollo Database Server and the Apollo client connection is encrypted and secure.

  19. Can I manipulate a database simultaneously with Apollo Database Server and with my CA-Clipper applications using the SIx Driver RDD?

    Yes! DOS file and record locking is fully supported.

  20. Do I have to buy a copy of Apollo Database Server for each end-user that uses the server?

    No!

  21. Does Apollo Database Server run with multi-processor systems on Windows NT? (2 processors, 4 processors, etc.)

    Yes. Apollo Database Server currently does not make special provisions for multiple processor systems, however a near future release will be optimized to take full advantage of multi-processor systems.

  22. We have noticed that when McAfee Virus Protection is running on our program directory that our Apollo database applications become slow. If McAfee is disabled, the Apollo application runs normal again. What's going on?

    It could be one of three things. If McAfee is running as a service under NT, perhaps the Priority is set too high. If McAfee is running under 95/98, then it would not be running as a service but rather as a background application. In this case, McAfee would be resource intensive. Finally, McAfee may be checking the actual data records for viruses, in which case you should probably set McAfee to ignore DBF, NTX, NSX, CDX, DBT and FPT files.

  23. Can Apollo Database Server control the numbers of users attached to it?

    Yes! The support was added to allow Apollo Database Server users to manage their customer base. This support is managed by the Apollo Server Manager application.

Apollo VCL

  1. Can the Professional Edition of Borland Delphi or C++Builder be used with Apollo Database Server, or do I need the Client/Server Edition of these products?

    Yes, the Professional Edition can be used with Apollo. You do not need the Client/Server Editions of Delphi or C++Builder to use Apollo Database Server, although those will work as well.

  2. Does Apollo Database Server require the BDE on either the client or server computer?

    No! Using the Apollo VCL components under Delphi or C++Builder allows you to get rid of the BDE. Apollo VCL does work with applications that use the BDE if needed, but no, the BDE is not required on either the individual client computers or on the server computer.

  3. I have many Apollo VCL applications running at the same site and I’d like to upgrade them to Apollo Database Server. What do I need to do?
    1. Install and run the Apollo Database Server on a server computer.
    2. Move all of your application’s data files into a directory on the server that can be accessed by all of your users.
    3. Run the Apollo Database Administrator program and setup an alias that points to the directory on the server containing your data files.
    4. Open your existing Apollo VCL applications using Delphi or C++Builder to your main Data Module or Form and drop a new TApolloConnection (automatically named "ApolloConnection1") component on your form.
    5. Set the ApolloConnection1.Host property to the IP address or domain name of the physical server machine where the Apollo Database Server is located. This establishes a global connection with the Apollo Database Server, which can be used by all other Apollo components. Please note, that if you are using TApolloDataset, you will need to upgrade all instances to TApolloTable or TApolloQuery before proceeding
    6. Lastly, for each TApolloTable component that already exists on your Form, set the TApolloTable.ApolloConnection property to point to the ApolloConnection1, and set TApolloTable.AccessMethod to "amServer". To take advantage of Apollo Database Server's SQL and Stored Procedure functionality, you can also use the TApolloQuery and TApolloStoredProc components.
  4. What is involved in developing Apollo Database Server applications under Delphi or C++Builder?
    1. Develop your Apollo-based client application using either Apollo VCL or Apollo OLE DB.
    2. Use the new TApolloConnection component to establish a connection to an Apollo Database Server by specifying an IP address or URL (e.g. 127.0.0.1 or www.vistasoftware.com) in the Host property. This establishes a connection to the server and provides access to all the databases hosted on the Apollo Database Server.
    3. You can optionally set the TApolloDatabase component’s ApolloConnection property to the TApolloConnection in order to connect to a specific database on the Apollo Database Server. Once the connection is established, select the desired database, which is located on the Apollo Database Server.
    4. Connect the TApolloTable and TApolloQuery components to the TApolloDatabase component or directly to the TApolloConnection component. Select the appropriate tables from the database that is hosted on the Apollo Database Server, which can be located locally, on an intranet, on a LAN or even on the Internet. The connection is transparent. TApolloQuery has more power than TApolloTable since a single query component can access multiple tables.
    5. When the client application is running and a table is accessed, the TApolloConnection component transparently manages the connection to Apollo Database Server at the specified IP address or URL address. The data managed is then handled entirely by the Apollo Database Server on the server computer and passed back to the client connections via the TApolloConnection! This is true client/server architecture at its best.

Apollo OLE DB Related

  1. Does Apollo OLE DB work with Apollo Database Server?

    Yes, Apollo OLE DB 6.0 supports Apollo Database Server.

International Issues

  1. Does Apollo Database Server run on Asian Editions Windows?

    Yes, Apollo Database Server supports Korean, Japanese and Chinese Windows 95/98/NT/2000/XP/Vista.

Apollo Database Engines
  

©1999-2008 Vista Software. All rights reserved.
http://www.vistasoftware.com Terms of use.