<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/9647ef81d7d54543b36ec3c21b844212&quot; frameborder=&quot;0&quot; width=&quot;3840&quot; height=&quot;2880&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2880</height><width>3840</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2880</thumbnail_height><thumbnail_width>3840</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/9647ef81d7d54543b36ec3c21b844212-ecc4a7be69a18cdc.gif</thumbnail_url><duration>109.4425</duration><title>AETL - Troubleshooting SQL Package Execution Issues 🛠️</title><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.</description></oembed>