I don't think so, as I would guess JET (this is from text or Excel?) is stripping the data. I would bring it in as text (either by formatting in Excel, or a schema.ini file) and then parse out what you need from the text value.
Well, it's possible to create a view and cast the timestamp(6) to timestamp(0), which corrects the issue in Tableau. However, I was hoping for a way to be able to deal with the issue after the data has been loaded into the .tde file, especially since the data extract (and therefore, visualizations) will be updated from the database every 15 minutes.
I can't find any information about what type of timestamp precision Tableau is supposed to support to determine whether this is a data-source specific issue or a general issue?
Probably source specific - I run into issues with precision the whole time (8:30:00 AM not the same as another 8:30:00 AM because of a rounding error by Tableau...)
Thanks. I decided to cast the information to less precision as a workaround.