Fetch from SQL Server

Fetch from SQL Server queries one or more tables in a SQL Server database and brings the results into your Multi FileFeed (MFF) as CSV files. Use it to source data directly from an internal database instead of exporting files by hand.

Availability: GA

What it does

• Input: source (no upstream input). This transform starts an MFF branch by connecting directly to a SQL Server database.
• Output: one CSV file per selected table, containing the current rows in that table.
• The transform connects using the configured SQL Server account, reads the tables you select, and emits each as a CSV file for downstream transforms.

When to use it

• Reference or transactional data lives in an internal SQL Server database and needs to reach OneSchema regularly.
• You currently export tables to CSV by hand before starting an MFF.
• You want to combine database-sourced tables with files fetched from other connectors in the same MFF.

How to configure it

In the MFF builder, add a Fetch from SQL Server node as a source at the start of your MFF.

Settings

Configuration tips

• Select only the tables you need; large tables increase fetch time and downstream file size.
• Confirm the SQL Server account has read access to the schema containing your tables before saving the node.

Example

Setup

A Customers table with 10,000 rows in an internal SQL Server instance.

Output

A Customers.csv file containing all current rows and columns from the table.

Troubleshooting

Connection errors

• Confirm the SQL Server account's credentials, host, and port are correct.
• Check whether the database's firewall or network rules allow connections from OneSchema's fetch infrastructure.

Table schema changed unexpectedly

• If columns were added or removed in the source table, downstream transforms that reference specific column names may need to be updated.

See also

• Fetch from Google Cloud Storage
• Fetch from SFTP
• Fetch Salesforce Data