- Time outs - entities like Case Requests, Related Cases, Phone, Milestones - these can have >100K records and they timeout frequently, every time we reload them. Interestingly, subsequent delta/incremental jobs load them all successfully.
- Example: One of the entities failed after running for 10+ hours - loaded 300K records out of 500K . We expect it will run for another 3-5 hours and load remaining records.
- Can't load multiple entities that has foreign key GUIDs from same table - results in resource unavailable error message.
- Scenario: Case GUID is a foreign key in Case Outcome and Milestone. If we execute both Case Outcome and Milestone entity at the same time, one of these entities will fail, perhaps after loading 100 or 200 records.
- To me it sounds like a table/entity locking issue where Case entity is locked while its being read by SSIS package(s).
- Is there something equivalent to SQL nolock table hint or any other solution so we can load multiple children's entities simultaneously?
Kaz