Data Migration Strategies and Transformation for Use by Third-Party Tool,
summary
Migrates millions of legacy XML documents into MarkLogic, using DMSDK for batched, multi-threaded loads with per-batch validation and collection tagging for success/failure; builds RSuite-conformant objects (content, resource, search, manage-object-ref) via modular XQuery modules that call CTS search and range/field/path indexes to reduce operations from minutes to seconds or milliseconds. Uses XDMP spawn to avoid conflicting-update errors and preserves untouched legacy metadata by storing it in key/value metadata and properties. Exposes content for third-party tools via WebDAV and REST APIs; approach proves scalable and recoverable.
AI-written summary · about
chapters (12)
- 0:00Introduction to migration
- 3:16Ruite architecture overview
- 5:25Registration process explained
- 7:13Optimizing XQuery functions
- 9:44Third-party API access
- 11:11Core MarkLogic features
- 13:17Lessons and best practices
- 16:05Tool evaluation and selection
- 19:19Registration challenges
- 22:52Metadata preservation methods
- 24:36Why MarkLogic was essential
- 27:09Q&A and closing
related talks
39mAutomating database migration - Amazon DMS tutorial
38mEfficient Reliable Database Migration: A Legacy Innovation Story
35mBest practices for migrating with databases
06mInterviewed at Gov 2.0 – Paul Norcini
31mModernizing a megascale database
40mData Migration Lessons from the Trenches
39mRethinking RDBMS Data Migration
42mOpenSearch Migrations: Modernize Without Worry