> Datamata SQL Portal > FAQ

FAQ

General Questions
1.1. What type of users is Datamata SQL Portal intended for?
1.2. What is Datamata SQL Portal's focus?
1.3. Can SQL Portal completely replace other database management tools for developers?
1.4. Which J2EE servers can SQL Portal run on?
1.5. Is SSL supported?
Installation and Configuration
2.1. Does the product come with JDBC drivers?
2.2. Is it possible to allow database access without the need to login?
JDBC Questions
3.1. What is the JDBC API?
Performance Questions
4.1. How many concurrent users can SQL Portal support?

General Questions

1.1. What type of users is Datamata SQL Portal intended for?

Datamata SQL Portal is to be used by everybody on an IT project. It is a primary SQL tool for light users, which could be testers, managers, analysts, architects. It is a secondary tool for heavy users, such as developers or DBAs, who already have power productivity tools setup on their PCs. They would use SQL Portal for quick, remote, or non-standard access, when some environment is not configured on their primary tool.

1.2. What is Datamata SQL Portal's focus?

SQL Portal feature set is not advanced or specialized, it rather appeals to the widest possible audience when simple SQL statements have to be executed against a database. The user value is in access simplicity, which is instant and completely maintenance free.

Overall focus of the product is in providing easy to use, secure, and drastically cost-efficient SQL access for everybody on a project. Major savings come from no need to maintain up-to-date connection configuration on everybody's PC.

1.3. Can SQL Portal completely replace other database management tools for developers?

No, SQL Portal does not include many advanced features, like storage procedure editing, etc. As a primary tool for database developers it will be insufficient. However, as a side tool for quick data enquiries it is proven to be indispensable even for most advanced users.

1.4. Which J2EE servers can SQL Portal run on?

Currently SQL Portal is tested on the following J2EE servers: Tomcat, WebLogic, WebSphere, Oracle OC4J, JBoss, Orion, Sun One. However, it is a standard Java J2EE web application and it will run on any compliant Servlet container.

1.5. Is SSL supported?

Yes. SSL is supported by all J2EE servers SQL Portal runs on. The product was extensively tested over secure connections and did not show any signs of degrading performance. See corresponding server documentation on how to setup SSL.

Installation and Configuration

2.1. Does the product come with JDBC drivers?

There are default drivers included for Oracle, MS SQL Server, MySQL, and FireBird databases (subject to drivers licenses). Drivers for other databases will have to be installed before the connections can be made.

However, if SQL Portal is installed on a server, which runs other DB applications, the drivers will be shared.

2.2. Is it possible to allow database access without the need to login?

Yes. It is possible to assign permissions to "anonymous" user. Everyone will get database access based on these permissions even before this person logs in.

JDBC Questions

3.1. What is the JDBC API?

JDBC stands for "Java Database Connectivity". It is a universally accepted standard for connecting Java applications to all sorts of databases.

Virtually all known databases have JDBC drivers created either by their vendors or third parties. There are dozens of drivers to choose from for most popular database applications and they range in price, size, and performance. There are free drivers available for most databases.

More information can be found at Sun Microsystems, including a good general overview page.

Performance Questions

4.1. How many concurrent users can SQL Portal support?

There is no design limit on the number of users. It will be restricted only by the hardware and server capacity.

SQL Portal, unlike business database applications, does not have to execute business logic. It just validates access security and passes all the work to databases. This means in most cases databases themselves or network capacity will be the access bottlenecks.

To illustrate the point SQL Portal was stress tested on Orion, which is a medium performance server, installed on 2mHz Intel machine. For 30 minutes 200 simulated users were hitting the same database with random delays from 0 to 0.5 seconds. Connection pool was set to have a maximum of 20 shared connections. To take network traffic out of consideration all setup was done on the same machine including locally installed Oracle database. A page with 10 records of data (8Kb) was delivered on average in 0.07 seconds with range from 0.01 to 0.8 seconds. A total of 332183 data pages was served in the period, or about 184 pages per second.

The test highlights that even with medium setup 200 users executing about one query a second will get response time of just a fraction of a second, when there is no large network delay.

 
  ©2003-2004 Datamata Corporation All rights reserved.