|
CONNX® FAQ'S |
Functional General Technical Functional
General
Technical
Functional
What Client and Server Platforms does CONNX support? See Requirements Matrix. More Information: Matrix How can I manage a secure environment when cross platform joins are involved? CONNX Security is ideally suited to handle cross platform
security issues. Comprehensive security capabilities have been designed into the basic CONNX architecture to ensure maximum data protection. All information, regardless of which database it is stored in, is protected through the table and user level security. Users are given access to certain datasets, depending on their job classification and other factors. Degrees of access can be specified for individual users or for groups of users. A 128-bit encryption algorithm is used to protect vital information in the password-protected CONNX Data Dictionary. CONNX validates the user name and password supplied in the ODBC connection against the database or system being accessed. With what off the shelf software packages does CONNX integrate? CONNX integrates with any ODBC compliant application such
as the following: Does CONNX support networked, internet, and remote users? Yes. CONNX supports TCP/IP across LAN's, WAN's, Intranets, Extranets, and the internet as well as through DECnet. Additionally, CONNX also has data compression capability which will increase performance when using the CONNX client over a slow or remote connection. Can I combine multiple data sources in one query? Yes. CONNX allows you to combine multiple disparate data sources in one query. Basically CONNX presents all of your data as one single relational database. CONNX will also optimize query processing by distributing the load between client and server to reduce processor load and take into account the capabilities of each data source in doing so. Can I create "Views" of my data using CONNX? Yes, the CONNX Administrator allows authorized users to define data views which join tables, select data and restrict access. These views are then available to front end applications and are presented as logical tables. Because the views are defined centrally they are available across the enterprise to authorized users regardless of the front end tool chosen. Can the results of multiple queries be combined into one result set? Yes. Starting in CONNX 8, CONNX supports the SQL UNION command, which allows the result sets of multiple queries to be combined into one. Does CONNX have wizards to guide me in configuring a data source? Yes CONNX has wizard driven assistance for configuring a datasource and importing meta data. Yes CONNX allows for a silent installation. The product
must first be installed once and installation choices made and recorded. It can then be
installed without prompting for choices. If I install a new version of CONNX will it automatically update my CDD? Your CONNX CDD does not automatically get updated. How long does it take to configure CONNX and a standard data query tool using the CONNX wizards? Using the new CONNX Wizard technology, the time required to setup a CONNX data dictionary has been reduced to approximately ten minutes. Yes. The ODBC & OLE-DB Specifications permit users to limit query execution times (Query Timeout), and limit the number of rows returned. Currently, CONNX does not return a "time estimate" for query execution. However, CONNX can return a "query execution plan", which describes how CONNX will attempt process a query. What does the insert/select feature do for me? The Insert/Select features allows you to insert the
request of one query into another table. This capability is useful when developing complex
reports where the creation of temporary tables is necessary to store intermediate results.
The Insert/Select also facilitates the transfer of data between database platforms using a
single SQL statement: Does CONNX integrate with CA-MANMAN? Yes CONNX enables ODBC access to CA-MANMAN through our
Oracle DBMS Driver. Does CONNX Integrate with SCT Plus Applications? Yes CONNX provides access to SCT Plus application data through our RMS Driver. There is specific functionality built into CONNX to handle the data access requirements of SCT users. GeneralYou call CONNX a Data Access Engine. What does that mean? Many ODBC drivers exist for accessing a single type of database. If you were to acquire several of them you would be able to access multiple databases. The catch here is that each would appear as a separate data source. Many front end applications are unable to or make it difficult to access multiple datasources. Thus your choice of front end applications or even development tools is limited. Even if your application is able to access multiple data sources you will typically take a performance hit as each driver is separately interrogated and data is staged on the client to perform a join. Your data access capabilities are also limited by the functionality of the weakest or least capable driver. In addition a multi driver solutions suffers from multiple points of failure, multi vendor support responsibility, and vendor bias. CONNX is truly different because all of the data sources accessed are presented to the client application as if they came from ONE SINGLE Relational Database. A Data Access Engine also provides functionality such as meta data management, security, advanced SQL and data conversion that simply are not core components of a simple ODBC driver. Can you access more than one database concurrently with CONNX? Yes, CONNX allows access to multiple heterogeneous databases concurrently. This allows you to join data from disparate datasources regardless of their type or location. All of the tables in your enterprise databases are represented as if they are contained in one enterprise spanning database. CONNX pricing for all databases except DataFlex is server-based. The price for CONNX server licenses depends on the size and configuration of the mainframe server and the number of users on that system. Is there an evaluation period? Yes. Please Fill in our on-line form for more information. What role do customers have in influencing development of new releases? All new releases go through a stringent market study. Suggestions for product enhancements (Request for Change) are collected from a variety of sources including our feedback form on this site, focus groups, site visits, contact with technical support, and direct contact with our sales executives. More Information: Feedback Form Yes. CONNX respects the existing security of the database accessed. CONNX also allows storage of database logins to automate authentication. In addition CONNX allows further user, group, application, field and record (through views) level security. Is CONNX a "datapump"? What does that mean? CONNX can act as a "datapump", but it is much
more. A "datapump" simply moves data from one location to another. The need for
a datapump usually arises when an application is being migrated from one platform to
another. How does CONNX fit into plans to migrate to newer platforms? SolutionsIQ is committed to supporting all major
databases on all platforms. This also include newer databases such as SQL Server, Oracle,
DB2, Sybase, Informix. The CONNX 8 family of products will deliver on our commitment to
support these databases, and round out or support for all data on the enterprise. Yes CONNX is Y2K compliant. Please see CONNX Y2K whitepaper. CONNX also provides date windowing capability that can extend the life of your Non Y2k Compliant data. Will I have to change my database design to work with CONNX? No. CONNX works with your existing database structure. Does CONNX have a graphical user interface (GUI)? Yes, the CONNX Administrator allows system administrators and developers to configure and maintain metadata, security, data sources, and views. Does CONNX provide a GUI to the metadata? Yes. CONNX provides a Windows application called the Data Dictionary Administrator, which allows the user to create and maintain the metadata, create views, and establish additional security. What kind of online help is there to assist me in using CONNX? The CONNX user reference guide is available through online help. How long does it take to install CONNX? CONNX Client installation takes about 5 minutes. Typically installation time on the server can take up to 30 minutes depending on the number of servers and data sources involved. Yes. As the Euro is simply a new type of currency, CONNX is capable of storing and retrieving any type of monetary value. Traditional data warehouses store a static copy or snapshot of the data. The CONNX approach is to provide real-time access to the disparate data. Within companies where data is time-critical, the warehouse approach is undesirable because of the static nature of the data. Until CONNX, there was no simple or efficient way to access data from disparate data sources. CONNX is the key to real-time access to multiple data sources. Can CONNX help with data warehouse projects already in progress? Yes. CONNX has several features that can help in data
warehousing projects. Most large corporations have several databases on mainframe systems. One of our goals is for CONNX to provide a single source for native support for all major databases in use by organizations today. Digital is a significant portion of the legacy mainframe database market, and it is key that we support the databases on the Digital platform. Data conversion is one of the most underestimated tasks in database projects. If a company cannot properly decipher the data stored in a remote database, then the data is useless. Data conversion is key to providing seamless access to disparate databases. One of the goals of CONNX is not only to provide connectivity, but to provide access to all data on the enterprise. Most corporations have many types of databases. CONNX provides access to all of those databases without the time and inconvenience of configuring separate ODBC drivers for each database, and the uncertainty that they will all work together properly. Most desktop applications do not allow the use of more than one data source or do so inefficiently. CONNX removes that limitation. Additionally, the CONNX Data Dictionary allows customers to create applications that are database-independent by creating views in the CONNX Data Dictionary instead of in the database itself. As a result, CONNX is not just an ODBC driver but an enterprise-wide data connectivity product. Most definitely. We have had several customers who initially purchased CONNX to assist in a migration off their legacy system; however, CONNX worked so well that they postponed indefinitely their migration plans. Once customers realize that they can access their data in real-time from the desktop, they begin to understand they can solve their immediate business problems without a costly migration. TechnicalWhat level of ODBC compliance and conformance does CONNX support? CONNX is a ODBC level 2 driver. CONNX was developed with
the ODBC 2.5 specification. Where does the metadata reside? The CONNX Data Dictionary functions as the metadata repository. This is a PC file that has the extension of (*.CDD). It can reside either on a server (for centralized access), or locally on the client machine. This sensitive information is encrypted using a 128bit key. How much hard drive space does CONNX require? See Requirements Matrix. More Information: Matrix What are the minimum and recommended client and server configurations? See Requirements Matrix. More Information: Matrix Does CONNX support multi tier architecture? Yes. CONNX can be installed in a Client/Server and n-tier configurations. In either case CONNX distributes the workload to minimize network traffic and processor load. CONNX also works in 3-tier web application environments, including Microsoft Internet Information Server. CONNX also works with development tools designed for n-tier distribution including Borland C++ Client/Server edition, and Borland Delphi Client/Server edition. Yes. By default, CONNX communicates to the VMS Server
using port 6500. This port must be opened or proxied in order for CONNX to work properly
though a firewall. What kind of impact does CONNX have on application databases? CONNX is designed to have a minimal impact on application
databases. Does CONNX work with RDO, DAO and ADO? Jet engine? Yes. CONNX will work with the RDO, DAO, ADO and Jet engine data wrappers. Does CONNX support the star schema and normalized models? Yes. CONNX is capable of working with any database model for relational databases. Does CONNX take advantage of keys or indexes when it searches? Is it automatic? Yes. The CONNX SQL Optimizer automatically takes advantage of keys & indexes on the tables in the queries. It depends. Does CONNX optimize SQL queries automatically? Yes. CONNX has an advanced SQL Optimizer which will quickly determine the best way to execute your queries. Does CONNX let you set processing limits for queries? No. Currently, CONNX does not allow administrators to set processing resource limits for query execution. CONNX has a distributed SQL Engine that will examine
several factors when performing joins. CONNX includes a unique high-performance, disparate database join technology that allows CONNX to join tables together from separate databases. This functionality means that if data is stored in two or more different databases, CONNX will join the data from the separate databases as if the database were one physical database. This is extremely important when developing mission-critical, enterprise-wide applications that span several physical databases. Are CONNX versions backward compatible? Yes. CONNX Versions are backward compatible except where noted in the CONNX documentation. Database technology is changing at a rapid pace. CONNX has a solid core on which the additional features and extensions are built. By ensuring our core architecture would fulfill our current requirement and future needs, we also reduced the time to market with these new features. Our new core architecture allows us to quickly add support for other databases and open access technologies. [Home][Products/Services][User Stories][Support][News/Events][Contact Us] |