{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/9647ef81d7d54543b36ec3c21b844212\" frameborder=\"0\" width=\"3840\" height=\"2880\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":2880,"width":3840,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":2880,"thumbnail_width":3840,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/9647ef81d7d54543b36ec3c21b844212-ecc4a7be69a18cdc.gif","duration":109.4425,"title":"AETL - Troubleshooting SQL Package Execution Issues 🛠️","description":"In this video, I discuss a simple package I created that writes to Microsoft SQL, which works well both individually and as part of a larger package. However, when I try to run this package as a scheduled task, it consistently fails, even though the SQL database shows that it has successfully written the records. I demonstrated this by clearing my table and attempting to write three records, but the execution log indicates a failure. I would appreciate any insights or suggestions on why this discrepancy is occurring. Please let me know if you have encountered similar issues or have any solutions."}