Brad Allison (9/15/2016)

---

Yep, it looks okay. In doing further investigation and trying to trace the issue through execution results, it looks like the permissions on the destination table changed somehow. So what I ended up doing (because I did find out that a column was inserted into the tsv file) was dropping the original table out of SQL and re-creating it with the newer tsv information. And now it works. Frustrating and six hours of work