FAQs

An XML-based application generator to read and display any relational database with full awareness of the data relationships, independent of the native application.

To reduce application clutter where data history has accumulated and is causing operational inefficiency. DataNovata is a one-stop resource to replace data access from any application source.

Any system of record. DataNovata is vendor agnostic. DataNovata only needs to access the database and it can be customized quickly to look like the original application.

Archive data can be time-consuming to retrieve and is avoided if users need easy access to data history. DataNovata provides immediate user access to the archive in a business-as-usual manner.

No. DataNovata generates an application that will view the archive data. Hosting and archiving services are available from a variety of vendors.

DataNovata maps the original application database schema, table relationships and metadata. It generates a view of all the data access paths. The most frequently-used screens are customized to look like the source application.

• There is no ‘write’ to records viewed within DataNovata.
• The user interface can be modified.
• Only useful screens are rendered, minimizing the scope of each project
• The DataNovata application is accessed through a web browser link

Yes. As long as the database has a JDBC/ODBC driver.

First, the data needs to be migrated from its non-relational source to an SQL-based RDBMS. As many pre-relational databases have well-defined schemas there is no loss in translation. Otherwise, our Application Architects write scripts in the DataNovata Toolkit, to build the structure to match the source legacy operation. DataNovata has been used to decommission many non-relational database applications.

No. DataNovata configures an application based on the relational database in state. It does not migrate.

All DataNovata applications have a standard suite of governance features for data management, retention and privacy:

• LDAP-compliant security gateway
• Audit traceability by access role and data point
• Data retention/purging customizable policy framework
• Data masking
• Notes database
• Bookmarking
• Legal Hold
• File export

DataNovata can include stored procedures defined in the database into the user interface. In addition, our Application Architects can design simple scripts to perform calculations and joins which then become part of the application configuration process. This makes it possible to represent any data point even if it is not evident within the database schema.

DataNovata does not need to read the source database to generate an application. It can read database output from as basic a format as a .csv file, which can usually be exported from applications with encrypted databases.

No. All the development work can be done on a local server you designate with permissions. The design and configuration can all be done from remote. There is no need to move your data outside of your designated infrastructure.

Each application you replace may be associated with different savings. These can be:

• Mainframe MIPS
• Cost of storage
• Operational savings
• 3rd-party OS, DB and application licenses
• Hardware removal
• Internal support service chargebacks
• 3rd-party support.

Some NoSQL databases have an ODBC driver. Having said that, the value of DataNovata is its automatic ability to represent an application view of structured data relationships. Metadata is useful and could make DataNovata an excellent starting point for creating a structured view of unstructured data, once the unstructured data was organized into a table format.