[{"data":1,"prerenderedAt":208},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fstreams\u002Funderstanding-streams":3},{"id":4,"title":5,"body":6,"description":199,"extension":200,"meta":201,"navigation":202,"path":203,"redirect":204,"seo":205,"stem":206,"__hash__":207},"docs\u002Fdocs\u002Fstreams\u002Funderstanding-streams.md","Understanding DBConvert Streams",{"type":7,"value":8,"toc":186},"minimark",[9,13,17,26,31,34,51,54,58,61,66,69,83,86,90,93,104,112,116,129,133,164,168],[10,11,5],"h1",{"id":12},"understanding-dbconvert-streams",[14,15,16],"p",{},"A stream is a saved data-movement workflow in DBConvert Streams. It defines the source and target connections, execution mode (Load or CDC), selected tables\u002Fschemas\u002Ffiles\u002Fquery scope, bundle size, reporting intervals, optional limits, and target structure\u002Fdata policies.",[14,18,19,20,25],{},"Use streams when you move beyond exploration and want DBConvert Streams to execute data transfer work. For step-by-step configuration, see the ",[21,22,24],"a",{"href":23},"\u002Fdocs\u002Fstreams\u002Fstream-configuration-guide","Stream Configuration Guide",".",[27,28,30],"h2",{"id":29},"streams-vs-explorer-workflows","Streams vs. explorer workflows",[14,32,33],{},"The product has two layers:",[35,36,37,45],"ul",{},[38,39,40,44],"li",{},[41,42,43],"strong",{},"Explorer \u002F SQL workflows"," for inspecting data, testing access, and validating queries",[38,46,47,50],{},[41,48,49],{},"Stream workflows"," for actual Load and CDC execution",[14,52,53],{},"This distinction matters because evaluation starts on the first stream run, not when you browse data in Data Explorer.",[27,55,57],{"id":56},"stream-types","Stream types",[14,59,60],{},"DBConvert Streams has two core execution modes.",[62,63,65],"h3",{"id":64},"load-mode","Load mode",[14,67,68],{},"Use Load mode for:",[35,70,71,74,77,80],{},[38,72,73],{},"one-time migrations",[38,75,76],{},"initial loads",[38,78,79],{},"query-driven extraction workflows",[38,81,82],{},"file-oriented export workflows where supported by the selected source and target combination",[14,84,85],{},"Load mode finishes when the selected scope has been processed.",[62,87,89],{"id":88},"cdc-mode","CDC mode",[14,91,92],{},"Use CDC mode for:",[35,94,95,98,101],{},[38,96,97],{},"ongoing replication from supported transactional database sources",[38,99,100],{},"continuous propagation of inserts, updates, and deletes",[38,102,103],{},"keeping downstream targets synchronized after an initial load",[14,105,106,107,111],{},"CDC support is narrower than Load support. Use the ",[21,108,110],{"href":109},"\u002Fdocs\u002Fguide\u002Fintro#capability-matrix","Capability Matrix"," before assuming a source or target combination is CDC-ready.",[27,113,115],{"id":114},"lifecycle-expectations","Lifecycle expectations",[14,117,118,119,123,124,128],{},"Streams move through states from ready to running to finished, stopped, or failed. See ",[21,120,122],{"href":121},"\u002Fdocs\u002Fstreams\u002Fstream-states-lifecycle","Stream states and lifecycle"," for the full state diagram and transitions. Use ",[21,125,127],{"href":126},"\u002Fdocs\u002Foperations\u002Fobservability","Observability"," to monitor current state, logs, and run history.",[27,130,132],{"id":131},"best-practice-flow","Best-practice flow",[134,135,136,143,154,157],"ol",{},[38,137,138,139,25],{},"Validate source access in ",[21,140,142],{"href":141},"\u002Fdocs\u002Fdatabase-explorer\u002F","Data Explorer",[38,144,145,146],{},"Pick the mode that matches the job:\n",[35,147,148,151],{},[38,149,150],{},"Load for bounded transfer",[38,152,153],{},"CDC for ongoing synchronization",[38,155,156],{},"Start with a smaller scope when testing a new workflow.",[38,158,159,160,163],{},"After the first run, check that the stream reached the ",[41,161,162],{},"finished"," state and that the transferred row count matches expectations in the run history.",[27,165,167],{"id":166},"related-docs","Related docs",[35,169,170,174,180],{},[38,171,172],{},[21,173,24],{"href":23},[38,175,176],{},[21,177,179],{"href":178},"\u002Fdocs\u002Fintegration\u002Fconversion-mode","Understanding Load Mode",[38,181,182],{},[21,183,185],{"href":184},"\u002Fdocs\u002Fintegration\u002Fwhat-is-cdc","Understanding CDC",{"title":187,"searchDepth":188,"depth":188,"links":189},"",2,[190,191,196,197,198],{"id":29,"depth":188,"text":30},{"id":56,"depth":188,"text":57,"children":192},[193,195],{"id":64,"depth":194,"text":65},3,{"id":88,"depth":194,"text":89},{"id":114,"depth":188,"text":115},{"id":131,"depth":188,"text":132},{"id":166,"depth":188,"text":167},"Understand what a stream is, when to use Load vs CDC, and how stream execution fits into the product model.","md",{},false,"\u002Fdocs\u002Fstreams\u002Funderstanding-streams",null,{"title":5,"description":199},"docs\u002Fstreams\u002Funderstanding-streams","VY9whq7mkknYptvWlAybqiWCVUI8BrF4VOO9sgJgUHg",1783896284804]