In a Profiler trace you can see INSERT BULK statements , which are a mechanism for interface between SQL Server and a client bulk copy API.For example : .Net SqlBulkCopy & ODBC Bulk Copy methods. The Profiler trace whill display the INSERT BULK statement but the FROM part , meaning you cannot view the values.

The INSERT BULK statement specifies the target tables \ columns including other meta data information - NULL management , triggers etc The tricky bit from a troubleshooting per, spective is you cannot view the values in the INSERT BULK statement. The values are transfered in a series of TDS messages after the INSERT BULK statement incorporating metadata information and the actual data. The data is in a binary format (encoded)

But there a few methods you can use to troubleshoot data load failures that utilise the INSERT BULK construct.

1) Use the Profiler trace events Error:Exception and Error:UserMessage or Extended Events These events can give you some error details when process fails. 2) Utilise the Ring Buffer events which can report error messages on Tabular Data Stream (TDS) transfers. TDS refers to a protocol for transfering data from applications to database servers. 3)Review error logs on the client side