The entry point for profiling are the DataContext.BeginProfiling method overloads that is used for initializing profiling with a variety of alternative profiling and filter scenarios. See the ProfilingExtensions class for usage examples.methods in the
Also see the Huagati.LinqToSQL.Profiler.Filters namespace for details on filter implementations.
Event arguments for the LogError event - raised if writing to the profiler log fails.
The ProfilingExtensions class contain DataContext extension methods that is used to initialize and to end Linq-to-SQL profiler query traces.
Query context identifying when/where etc for a Linq-to-SQL profiler log entry
The QueryInformation class correspond to a Linq-to-SQL Profiler log entry. It contain information about individual query executions such as the generated SQL Query, SQL Server I/O data and timings, execution context (machine, user, date/time etc), managed call-stack, and (optionally) also SQL Server Execution plans.
Query profiler session object. Do not create directly, instead use the DataContext.BeginProfiling methods to initiate profiling.
TableRead instances contain I/O statistics for individual tables involved/read/written during the execution of a query.
Delegate for the AfterSerializing event that is fired after a profiler log entry is serialized (or queued for serialization in case of asynchronous log writes).
Delegate for the BeforeSerializing event that is fired before a profiler log entry is serialized.
Delegate for the FilteredOut event that is fired if a profiler log entry is excluded from the log by a filter.
Execution plan mode for a Linq-to-SQL Profiler session. None = no execution plan, Estimated = SQL Server's estimated execution plan will be extracted, Actual = the actual SQL Server execution plan will be extracted.