What changes for you
If range discovery cannot create reliable boundaries, Omni Loader warns and falls back to one unsliced work item instead of inventing unsafe predicates.
Scale · Table slicing
Turn one very large table into parallel, bounded work.
Omni Loader divides large tables into independent slices using source partitions or discovered ranges, then schedules the biggest work first to keep workers productive.
Parallel work planner Divide · schedule · balance
Workers active
Inputs
PartitionsREADY
Date + number rangesREADY
Text + file rangesREADY
Slice planner Divide · schedule · balance
Outputs
Worker 01READY
Worker 02READY
Worker 03READY
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.
Create slices from native source partitions, numeric ranges, dates and times, text prefixes, an explicit slice column, or file row ranges.
Why this path matters
Use structure the source can expose.
Create slices from native source partitions, numeric ranges, dates and times, text prefixes, an explicit slice column, or file row ranges.
The outcome
We will identify usable slice keys, source pressure, worker limits, and the target ingestion budget.
The payoff
See what the capability changes.
1–64
Worker control
Set the concurrency budget for the migration environment.
1–3,600
Slices per table
Break exceptional tables into manageable ranges.
Largest first
Useful scheduling
Keep workers occupied instead of leaving the hardest table until last.
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.
Source/target workers and ingestion workers have separate controls so staged cloud loads can be tuned around both extraction and target ingestion.
Multiple slicing strategies
Use structure the source can expose.
Create slices from native source partitions, numeric ranges, dates and times, text prefixes, an explicit slice column, or file row ranges.
- Source partitions
- Numeric and temporal ranges
- Text-prefix ranges
- File row ranges
Safe fallback
An unsliceable table still moves.
If range discovery cannot create reliable boundaries, Omni Loader warns and falls back to one unsliced work item instead of inventing unsafe predicates.
Separate ingestion capacity
Balance extraction and destination work.
Source/target workers and ingestion workers have separate controls so staged cloud loads can be tuned around both extraction and target ingestion.
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.
- Source partitions
- Numeric and temporal ranges
- Text-prefix ranges
- File row ranges
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.
Use structure the source can expose.
Create slices from native source partitions, numeric ranges, dates and times, text prefixes, an explicit slice column, or file row ranges.
An unsliceable table still moves.
If range discovery cannot create reliable boundaries, Omni Loader warns and falls back to one unsliced work item instead of inventing unsafe predicates.
Balance extraction and destination work.
Source/target workers and ingestion workers have separate controls so staged cloud loads can be tuned around both extraction and target ingestion.
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
- Worker control
- Slices per table
- Use structure the source can expose.
- An unsliceable table still moves.
- Give the largest tables a migration plan of their own.
Take the next step
Give the largest tables a migration plan of their own.
We will identify usable slice keys, source pressure, worker limits, and the target ingestion budget.
Plan my migration