database-bulk-loadinglisted

# Database Bulk Loading ## Purpose Choose the least costly ingestion mechanism that still preserves the required validation, atomicity, recoverability, and online workload. “More threads” and “larger batch” are not goals; success means meeting the actual load window and correctness contract. A safety review can retain an adequate mechanism without increasing throughput. ## Inputs required ```text engine, server/driver versions, topology, durability and replication mode: source format/location/trust, rows and bytes, row width, and error distribution: target constraints, triggers, indexes, generated keys, and online traffic: required atomicity, duplicate/upsert semantics, rejection policy, and restart point: current mechanism, batch size, transaction size, throughput, CPU/I/O/log/network, and heap: window/SLO, staging/disk/log headroom, privileges, and rollback constraints: ``` Reuse existing configuration, tests and measurements; ask only unresolved questions that change the mechanism, atomicity or recovery contract. Continue independent inspection while those are resolved. Collect the inputs relevant to the decision rather than requiring a new full study. For JVM implementation changes, inspect compiler release/toolchains, runtime images, resolved JDBC driver and ORM versions, connection properties and transaction-manager ownership. This skill imposes no Java baseline; preserve the project's target and dependencies. When missing timing or failure evidence could change t