Visualize SQL Server and PostgreSQL query execution plans for Entity Framework and LINQ to SQL queries directly within LINQPad.
LINQPad.QueryPlanVisualizer is a visualizer extension for LINQPad that displays query execution plans for SQL Server and PostgreSQL databases. It helps developers understand and optimize Entity Framework Core and LINQ to SQL queries by providing graphical insights into query performance and missing indexes.
Developers using LINQPad with Entity Framework Core or LINQ to SQL who need to analyze and optimize database query performance for SQL Server or PostgreSQL.
It integrates directly into LINQPad, offering a seamless workflow for query optimization without switching to external tools, and supports advanced features like missing index detection and plan sharing.
SQL Server and PostgreSQL query execution plan visualizer for LINQPad
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Displays query execution plans directly within LINQPad, eliminating the need to switch to external tools, as shown in the screenshots and feature list for a streamlined workflow.
Identifies and generates missing index scripts for SQL Server queries from the plan, enabling quick performance optimizations without manual analysis.
Works with both SQL Server and PostgreSQL, providing flexibility for teams using different database systems with Entity Framework Core, as stated in the README.
Allows exporting plans to external services like Brent Ozar's Paste The Plan, facilitating collaboration and advanced diagnostics with industry-standard tools.
Version 2.1 and newer require Microsoft Edge WebView2 Runtime installation, adding complexity to setup and potential compatibility issues on systems without it.
Separate versions for LINQPad 5 and 6 create confusion and maintenance overhead, as users must manually select the correct version based on their LINQPad edition.
Only explicitly supports Entity Framework Core 5 and LINQ to SQL, excluding other ORMs or newer EF Core versions without clear documentation on updates.