Why does SQL Server Profiler trace skip records?

Question

I have a SQL Server Profiler trace and it's working for all commands.

But the profiler skips one record like below:

Exceed

typically it's memory related to the client when running real-time. if you save to a file and enable checkbox Server processes trace data, it won't happen. – Reflective

Answer 1

If you insert a large amount of data, for example more than 1 MB, into SQL database in one single operation, the chance are that SQL Profiler is going to skip this operation, leave all fields blank, and mark as “Trace Skipped Records”. Don’t worry. The operation is still inserted into database, and only SQL Profiler skips the operation.

Source of answer

Local