title: SQL performance tuning with LinqPad
body: <p>I am DBA &amp; Software engineer, who administers SQLServer 2016 Enterprise Database. The Application Sql is written in EntityFramework rather than Stored procedures.</p>
  
  <p>Should DBAs place team's EF queries in Linqpad to performance tune in development? I learned about LinqPad last week, and amazed how it translates Linq queries into SQL. Sometimes Linq queries are unpredictable/random (MS is still working on product improvements). This way, I don't have to wait for a random query to hit SQLServer Profiler in Staging or Production. I can tune with application developers during sprint development.</p>
  
  <p>Would this be a proper strategy for performance tuning? I read many sql blogs, however no one discuss LinqPad strategy. Just inquiring if this would be helpful methodology in performance tuning.</p>