Hello everyone.
We have a table with a BLOB column and It's size is spiraling out of control. As it stands 90% of the database space is consumed by this one table. It is also impossible to dbexport the database in a timely manner because an unload of this single table takes more than 24 hours.
We want to migrate the BLOBS to the filesystem and back them up separately.
My first thought was to rename the base table, add a filepath column, do a lotofile on the blobs in batches and update the blob column to NULL.
Then create a view that looks like the original table and use INSTEAD OF triggers for updates/inserts/deletes.
Is this a feasible approach? Has someone already migrated blobs to the filesystem successfully?
Thanks in advance,
-Snorri
------------------------------
Snorri Bergmann
------------------------------