Insert into Database
Infoveave Data Automation — Database
Transform it in the workflow. Land it in the database. Automatically.
The final step of any ETL pipeline is loading the processed, clean data into a database. Insert into Database is that step — taking the structured tabular output of upstream transformation activities and writing each row into the target table. With automatic column mapping and optional table auto-creation, you can wire up a complete data pipeline from raw file to database record without writing any custom load scripts. Works with PostgreSQL, MySQL, MSSQL, and all SQL-compatible databases configured in Infoveave Studio.
What Insert into Database does
Insert transformed rows from your Infoveave workflow directly into relational database tables. Supports auto-create table, column mapping, and batch inserts — automating your data loading step without custom scripts.
When to use Insert into Database
- You need to write processed or transformed data from a workflow activity into a database table
- You are building ETL pipelines where the final step is loading data into a SQL-compatible database
- You want to auto-create the destination table if it does not yet exist, based on the incoming data schema
- You need to map input column names to different target column names in the database schema
When to avoid it
- You need to update existing rows in a database — use Update Rows instead
- You need to run a custom SQL query on the database — use Execute Query
- Your destination is a file rather than a database — use Write to File in the Data Ingestion library
Where it fits in your Infoveave automation
Insert into Database is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Insert into Database
Real scenarios where this transformation saves hours of manual work.
Processed Transaction Loading
A daily reconciliation workflow cleans and categorizes incoming bank transactions using transformation activities. Insert into Database writes the reconciled records into the accounting database table, ready for the month-end reporting dashboard — with column mapping aligning the workflow field names to the database schema.
Quality Inspection Results Storage
An automated quality inspection pipeline collects measurement data from shop floor systems, applies tolerance-check transformations, and uses Insert into Database to land the results in the production tracking database. The auto-create option ensures new product lines get a destination table automatically.
Patient Record Ingestion
A clinical data pipeline parses incoming patient intake CSV files, applies field standardization, and inserts cleaned records into the hospital's MSSQL patient registry. Column mapping handles the conversion between the source file field names and the target table schema.
See Insert into Database in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
prod-postgres-dbcustomer_demographicstrueCountry → Country, Gender → Gender, Company → CompanyNameInput Data
| Country | Gender | Company |
|---|---|---|
| Japan | Male | Hirthe and Sons |
| France | Female | Sipes Group |
| Brazil | Male | Miller Inc |
Output Data
| Country |
|---|
| Japan |
| France |
| Brazil |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Connection
The registered database connection for the destination. Supports PostgreSQL, MySQL, MSSQL, Azure SQL, and other SQL-compatible databases configured in the Infoveave Studio connections panel.
Table
The name of the destination table in the connected database. The table must already exist unless Create Table If Not Exists is enabled.
Create Table If Not Exists
When enabled, Infoveave automatically creates the destination table based on the schema of the incoming data if no table with that name exists. Useful for onboarding new data sources or dynamic table generation in automated pipelines.
Column Map
Maps each input data column to its corresponding database table column. Allows renaming fields to match the target schema. Optional transformations can be applied before insertion. If no mapping is specified, columns are matched by name automatically.
Frequently asked questions
Everything you need to know about Insert into Database in Infoveave.
Also in Database — and what runs before & after
Transformations in the same family as Insert into Database, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Insert into Database is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
