Trace Skipped Records

An interesting issue that i saw it first time this week when using the profiler:

Trace Skipped Records....

Apparently that's what it sounds: the profiler was too "busy" or loaded, so it skipped few records...

"Busy"/loaded can be few things:

Long text that was caught and the profiler can't display it in TextData column, busy or loaded server or something in the machine where the profiler isd executing.

This thong is a known issue in Microsoft:

https://connect.microsoft.com/SQLServer/feedback/details/304225/msft-edw-profiler-displays-trace-skipped-records-for-large-530kb-batch

I didn't fing a lot about it, here 2 useful links:

http://blog.consultdba.com/2010/09/trace-skipped-records-what-is-this-and.html

https://scarydba.wordpress.com/2009/10/28/snags-with-profiler-gui/