Blob Extraction
Stop paying database prices for object storage. Omni Loader offloads BLOBs to S3, Azure Blob, or ADLSv2 during the migration, and leaves a lightweight reference in their place.
Are blobs eating most of your database's space?
Then they're eating most of your bill, too.
How this happens
It starts simple. Store the PDFs and images in the database, one less system to think about. Three years later, the BLOBs outweigh the actual data ten-to-one, and the monthly bill from your cloud provider becomes the wake-up call.
Cloud object storage is built for exactly this: cheap, durable, and ridiculous to try to recreate inside a database. If BLOBs are dictating your database tier, your backup windows, and your bill, it's time to move them.
Migrate and trim in one pass
The migration is the perfect moment to clean this up. Omni Loader does the offload as part of the data copy. No second pipeline. No follow-up project.
Turn on Blob Extraction when you set up the target. Point it at Amazon S3, Azure Blob, or ADLSv2. As rows copy, each BLOB is uploaded to object storage and replaced in the target with a lightweight identifier.
The target lands smaller, the backups land cheaper, and the long-term storage bill drops with it.
Land a slim, fast target database
Drop in the cloud storage credentials. The BLOBs go where they belong. The database stops being a graveyard for binary data.
Frequently asked
questions
Save time. Get the job done.
Tell us what you're moving.