Sanford Whiteman Thanks for the additional details, Sanford. It looks like the describe endpoint actually gives you the field length (50, 255, or 2000) so I can match my SQL fields for those different field lengths. Additionally, several of the data types could all be captured by using a NVARCHAR data type (email, string, url, phone) seeing as they're just non date or numeric fields. I'm actually using MySQL as the destination DB platform so I don't have the option of using sparse. I'm not as familiar with MySQL as with SQL so I'll have to research to see if MySQL has an alternative (know of one yourself?). I'm also researching character sets and going down a rabbit hole there, so I'd appreciate any other suggestion you have (seeing as your title is integration architect). Thanks again!
... View more