Jump to content

User:Andi Database Productivity Tool/sandbox

From Wikipedia, the free encyclopedia

Andi is a database productivity tool with features that allow users to access their data, regardless of their SQL knowledge. Andi is used by System Testers, Business Analysts, Developers, Production Support, Performance Testers, Database Administrators or general users needing access to their data. Andi provides SQL access to relational and non-relational databases using a JDBC Driver. Andi is designed for selecting data, sorting, filtering, and analyzing result sets containing hundreds of thousands, to millions of rows of data limited only by the physical memory.

Supported databases and environments

[edit]

Andi supports access to relational and non-relational databases using JDBC drivers. Progress Software provides enhanced, high speed JDBC drivers to access a broad range of databases.

BIG DATA

[edit]
  • Apache Cassandra
  • Apache Hadoop Hive
  • Cloudera CDH Hive
  • Hortonworks Hive
  • Pivotal HD Hive
  • Amazon EMR Hive
  • MapR Hive
  • Cloudera Impala
  • MongoDB
  • SAP Sybase IQ
  • Pivotal Geenplum
  • Teradata
  • Amazon Redshift
  • Spark SQL
  • SAP HANA

RELATIONAL

[edit]
  • Oracle Database
  • IBM DB2
  • IBM Informix
  • Microsoft SQL Server
  • MySQL
  • SAP Sybase
  • PostgreSQL
  • Pervasive SQL (Btrieve)
  • Progress® OpenEdge®
  • Progress® Rollbase®
  • Clipper
  • Dbase
  • Foxpro

SaaS/Cloud

[edit]
  • Data Sources Using Salesforce1 Lighting Connect
  • Salesforce.com
  • Database.com
  • FinancialForce
  • Force.com Applications
  • Hubspot
  • Marketo
  • Microsoft Dynamics CRM
  • Microsoft SQL Azure
  • Oracle Eloqua
  • Oracle Service Cloud
  • ServiceMAX
  • Veeva CRM

Supported Operating Systems

[edit]

Andi runs on all Windows 32 bit and 64 bit platforms.

History

[edit]

Kerry O'Brien, a Software Developer, started the design process for Andi in 2001 out of frustration with the currently available tools. Having completed development of a large batch job, started integration testing. Unfortunately, the batch job modified a large tree of related tables so verifying the data meant running a stream of SQL statements, one at a time. The process involved executing a SQL statement, grab a key value and use it to select a child table and so forth. Unfortunately, by the time he executed the nth statement, the question that came to mind is "did I use the right key value". At that point, there is no other choice but to start over. After two frustrating days of failed testing, Kerry went home and created a prototype version of the Andi View Organizer and completed his testing the next day, in fifteen minutes.

References

[edit]
[edit]