我的团队中的一员最近搬到LinqPad作为他的主要查询工具（仍然将使用SQL工作室的时间）为强迫自己使用LINQ更自然使用的简单的目的。我认为这是一个pretty的好主意，正在考虑要求我的团队的其他成员作此开关。没有人有任何想法/想法采取这种方式？

早期的问题，我有...

我觉得能写出优秀的ANSI SQL是一个LOB开发的关键。由于LINQ是微软的东西，是技能，他们将在LINQ学习价值的充分发展他们的ANSI SQL技术，牺牲特别是当（当），他们转移到以后的生活中其他的工作/职责。开发者开发（内部和公司外部的）对我来说是非常重要的。

有没有在SQL工作室将非常怀念在LinqPad的特性？

确实LinqPad有长期的生活吗？换句话说，大家都觉得LinqPad是一个产品，将继续增长，因为.NET和SQL增长？

有没有在SQL工作室将非常怀念在LinqPad的特性？

请问LinqPad的显示估计的执行计划的？

A member of my team recently moved to LinqPad as his primary query tool (still will use SQL Studio at times) for the simple purpose of forcing himself to make using LINQ more natural to use. I thought this was a pretty good idea and am considering asking the rest of my team to make this switch. Does anyone have any thoughts / ideas on taking this approach?

Early questions I had...

I feel being able to write good ANSI SQL is critical for a LOB developer. Since LINQ is a Microsoft thing, is the skills they will learn in LINQ worth the sacrifice in fully developing their ANSI SQL techniques, particularly if (when) they move on to other jobs/duties later in life. Developer development (inside and outside of company) is extremely important to me.

Are there any features in SQL Studio that will be sorely missed in LinqPad?

Does LinqPad have long term life? In other words, does everyone feel that LinqPad is a product that will continue to grow as .NET and SQL grows?

Are there any features in SQL Studio that will be sorely missed in LinqPad?

Does LinqPad Show Estimated Execution Plan ?