Data Sources

Data sources in Gaio are a very important topic, because without data, the platform is useless. The main way to bring data to Gaio is by connecting to the company's Databases, where data is frequently stored.

Gaio connects to the main Database Management Systems providers (Oracle, Microsoft, MySQL, PostgreSQL, MariaDB, MemSQL, JDBC, S3 AWS, Salesforce) visually. You can also connect to Hadoop , which is a more recent source, but which can accumulate large volumes of data, although not in a visual way.

Each Gaio connection is pointed to a database. This means that if you want to connect to two databases within the same DBMS, it will be necessary to create two connections and these can be granted access to different groups of people .

The interface is very simple and can be accessed within the Administration environment in the top menu, clicking on the Sources button .

  1. List of databases available on this Gaio server.

  2. Type of DBMS for each connection.

  3. Add new database.

  4. Change the settings for a database connection.

Connection and not import

At this point, Gaio now has access to the tables of this connected database. However, no data has been brought yet. The data will come when an analyst in an application's Studio creates a Query that goes to the tables in that database and executes it. At this point, the query will be executed, the data will be exported, imported into Gaio, populating an internal Gaio table.

Gaio uses native connectors to communicate with DBMSs, which guarantees greater performance in data traffic.

Each DBMS has its connection peculiarities, but in general some fields are repeated. Below is a MySQL database connection screen:

  1. DBMS: choice of DBMS to which the connection will be made.

  2. Name: it is important that the name reflects the data source as this is how analysts will see this source in Gaio.

  3. IP/Address/Server: address of the DBMS server.

  4. Port: enter the bank's door.

  5. Database: name of the database on the server.

  6. User: user registered in the database.

  7. Password: database user password.

  8. Allow SQL execution: allow the analyst to create SQL and execute it on the server.

Last updated