What changes for you
Large objects and engine-specific types can require a different writer than scalar rows. Omni Loader changes the loading path rather than pretending every row has the same constraints.
Data path · Adaptive loading
Use the fastest safe writer for each target and row shape.
Omni Loader selects among provider bulk APIs, multi-row statements, parameter binding, direct file writers, streaming, and target-native ingestion instead of forcing every engine through one generic path.
Provider-aware delivery Measure · select · tune
Best path selected
Inputs
RowsREADY
Prepared batchesREADY
Staged filesREADY
Adaptive writer Measure · select · tune
Outputs
Bulk APIREADY
Native ingestionREADY
Multi-row SQLREADY
The job to be done
Move the full dataset without turning failure into a restart.
A large migration is not finished when the first rows arrive. Omni Loader keeps parallel work productive, adapts the loading path to the target, and records enough progress to recover the part that failed.
SQL Server, PostgreSQL, MySQL, Oracle, Db2, Spanner, and other adapters choose loading strategies from their actual capabilities and limits.
Why this path matters
Fast paths where they are supported.
SQL Server, PostgreSQL, MySQL, Oracle, Db2, Spanner, and other adapters choose loading strategies from their actual capabilities and limits.
The outcome
We will identify the provider path, fallback cases, batching limits, and representative benchmark for your migration.
The payoff
See what the capability changes.
Provider-native
Bulk APIs
Use engine bulk loaders when the type shape allows it.
Automatic fallback
Complex-value handling
Switch paths when LOBs or target limits require it.
Target-aware
Native ingestion
Feed warehouses and cloud platforms in their preferred shape.
Where the work happens
The details that make the result usable.
Read each capability as part of the operating path. The important question is not whether a feature exists, but what work it removes and what evidence it leaves behind.
At a glance
A visual summary of the work.
Statement modes chunk work by row count, payload size, and engine-specific restrictions while managing transactions and periodic commits.
Provider-specific decisions
Fast paths where they are supported.
SQL Server, PostgreSQL, MySQL, Oracle, Db2, Spanner, and other adapters choose loading strategies from their actual capabilities and limits.
- Bulk copy
- Multi-row statements
- Bound parameters
- Direct and hierarchical writers
Type-aware fallback
Keep difficult values explicit.
Large objects and engine-specific types can require a different writer than scalar rows. Omni Loader changes the loading path rather than pretending every row has the same constraints.
Bounded batches
Respect statement and parameter limits.
Statement modes chunk work by row count, payload size, and engine-specific restrictions while managing transactions and periodic commits.
Before you choose
Check the path against your environment.
Use the page-specific details below as a short discovery checklist. They are the conditions and work areas that shape the capability, not generic product promises.
- Bulk copy
- Multi-row statements
- Bound parameters
- Direct and hierarchical writers
The path to confidence
See the work. Make the call. Prove the result.
The page keeps the product detail close to the decision it supports. Your team can see what the software handles automatically, what it changes for the target, and what the result leaves ready to operate.
Fast paths where they are supported.
SQL Server, PostgreSQL, MySQL, Oracle, Db2, Spanner, and other adapters choose loading strategies from their actual capabilities and limits.
Keep difficult values explicit.
Large objects and engine-specific types can require a different writer than scalar rows. Omni Loader changes the loading path rather than pretending every row has the same constraints.
Respect statement and parameter limits.
Statement modes chunk work by row count, payload size, and engine-specific restrictions while managing transactions and periodic commits.
Keep the plan connected
Take the next useful step.
A capability becomes easier to operate when the next decision follows from the constraint you just uncovered. Explore the related work that completes this part of the path.
Your working set
What this page leaves you with
- Bulk APIs
- Complex-value handling
- Fast paths where they are supported.
- Keep difficult values explicit.
- Match the loading path to the real target.
Take the next step
Match the loading path to the real target.
We will identify the provider path, fallback cases, batching limits, and representative benchmark for your migration.
Plan my migration